I would be nice if there were a way to show a list of all of the bibs cataloged using FA (Fast Add) to the cataloging main page so that the catalogers can beef up those records. Of course it would need to have a preference to control whether it shows or not.
Just as something you could do that wouldn't require all the work and overhead of a syspref... You could make a report that links to the titles of these books, and put a link to that public report in the news on the intranet home page. Might be easier than what you're asking for.
The news doesn't show on the cataloging page ... I read the enhancement in bug 5523 and thought that if processing books show there so should fast add (based on requests I get in training). I do have a fast add report that I give people, but I was envisioning this as a list of titles (clickable) that were cataloged as fast add in the big blank area below the cataloging buttons - maybe two columns side by side - one for in processing and one for fast adds. Just brainstorming here :)
So it sounds like what you really want, is a cataloging module dashboard type display, an overview of actionable things a cataloger might need to do.
I'll give you that there is a lot of white space in the cataloging "home page" that could be usefully used for such a display - *that* would be an awesome enhancement (and not one that I think people would mind being on all the time).
just thinking about this - you could put things like * serials expected this week * items that were marked lost x months ago that need to be deleted or billed * fast adds that need to be deleted or fleshed out and on and on. You could use the public reports functions to get the data into the page if it were set up correctly, then the list of what you could show would be practically infinite possibility.
Yes, Yes and Yes :) Lots we could do - and like I said it looks like bug 5523 is gonna add something there already, so .... more to come I hope :) Nicole
Still valid?
A cataloguing dashboard would still be neat.
I reckon this is a duplicate of bug 5523 and that Liz is right that the approach should be to use Javascript and a SQL report. *** This bug has been marked as a duplicate of bug 5523 ***