Baseline requirements/enhancements for Reserves system:
Identify the top requirements for Reserves in each area (not only what is currently lacking):
Processing side:
- Pulling in bibliographic data to automate the populating of fields (replacement for function of Tom's Ares Tools).
- Support for bibliographic fields other than just monographs or serials (i.e. music, scores, etc.). All formats should be recognized; likewise, should be flexible/extensible enough to grow and work with new media.
- Archive and reuse course reserve lists over a many year period.
- Ability to track the status of items and move items to/from queues as needed.
- Ability to delete and/or clean up items.
End-user interface: for students (CUL Course Help)
- Clear, intuitive interface for students seeking Reserves (Usability group is working on this piece).
- This should include issues of call numbers, facet sorting, grouping, location and alphabetical sorting.
- Reasonably fast response time.
End-user interface: for faculty/instructors
- Ability to track the status of items.
- Clear, step-by-step instructions for instructors to submit and track requests, including clear guidelines on copyright issues.
- Open URL (to enable faculty to request items and be able to get bibliographic data).
Back end issues
- Structured course data - person creating course reserves must select from authoritative course roster descriptors.
- No complications with Blackboard in the creation of course reserve lists.
- Reporting functions, including the ability to gather statistical information (circulation)and to print reserve lists for archival purposes without having to use a print screen function.
Support issues
- Minimal or no down time.
- Vendor must be responsive to requests for fixes and enhancements.
- Key staff who work with Reserves (in Access Services or IT/Systems) must be available the first month of Spring or Fall semesters; at minimum there should be backup staff who can perform these individual's functions.
- Clear communication between reserves processing staff. There should be at least one quality control person to gather problem reports & communicate to Atlas.
1 Comment
Michael N. Cook
Implementing OpenURL will require someone to build a web frame or something similar to "contain" pages with which to use OpenURL's functionality. We need to ask Dean's group to develop this.
Q: How does Ares handle an OpenURL?
Also, ask Dean if Systems can write a web-based version of Tom's Tools. This could go hand-in-hand with activating web services between Ares and Voyager.
Most used features of Tom's Tools: import by barcode, create item in Voyager, migrating from a Voyager reserves list into Ares.