...
- Identifying what can/can't be fixed by Spring
- Improving instructions for instructors
- Ares web form for instructors: direct to Blackboard?
- Baseline requirements/enhancements for Reserves system:
Identify the top 3 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).
- Open URL (to enable faculty to request items and be able to get bibliographic data).
- Support for bibliographic fields other than just monographs or serials (i.e. music, scores, etc.).
- Ability to gather statistical information (circulation).
- Print reserve lists for archival purposes without having to use a print screen function.
- Archive and reuse course reserve lists over a many year period.
b) End - Others?
End-user interface (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, and alphabetical sorting.
- Clear, step-by-step instructions for instructors to submit and track requests, including clear guidelines on copyright issues.
- Others?
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.
- Others?
Support issues
- Minimal or no down time.
- Key staff who work with Reserves (in Access Services or IT/Systems) should not be on vacation first week of Spring or Fall semesters.
- Clear communication between reserves processing staff.
- Vendor must be responsive to requests for fixes and enhancements.
- Others? c) Back end issues
d) Support issues