Jill, I'm with you 100 percent! We need decoder rings sometimes to
figure out why a book was kicked back. On a related note, I'm also
frustrated that the step 1 page doesn't put kicked back books at the
top like it used to. Now we have to actively search through 300 to
400 books to see if any of our validations have been kicked
back. Whoever planned this new step 1 system wasn't thinking about
how this would fully impact us. They apparently assumed that the
books that languish on the list were because we only took books from
the top of the list. If they'd have asked us about it, they'd have
found that those books are languishing for several good reasons, most
of them having little to do with being at the bottom of the list. As
it stands, Gustavo could kick back as many as 15 of my validations
without me knowing about it unless I go hunting for them. I really
don't like it when developers make dicisions based on what they
assume is the problem without asking the people who it impacts most,
the end users. That's what seems to be happening here, and it isn't
working out as the Bookshare staff hoped it would. Addressing the
underlying issues related to the languishing books would get the
results they wanted. As it is, people just use control f and skip
past the languishers to get to the new books they want to work on.
Gustavo's kicking back books to the step 1 page without any explanation bothers me more than any other thing Bookshare staff does. Do they think that volunteers have nothing better to do than keep looking on the step 1 page to see if their book has been kicked back there and nothing better to do than to try to figure out what the problem is, especially when it is often nothing that we can determine. If it sounds like this makes me angry, it does.
To unsubscribe from this list send a blank Email to bksvol-discuss-request@xxxxxxxxxxxxx put the word 'unsubscribe' by itself in the subject line. To get a list of available commands, put the word 'help' by itself in the subject line.