October 13, 2010

CUL Reserves Interest Group meeting, Mann 160, 3:30-5:00pm

1. Identifying what can/can't be fixed by Spring
   1. One major improvement would be to implement the OpenURL button in the CUL catalog and in Ares. This function is already available in Ares but we have not activated it (no one could agree where the button should go in the Catalog). This is something we'd have to ask Dean and his staff to work on (i.e. where does the button go and what it does).
   2. Have Atlas pursue web services for Ares 3. Not having this feature is a possible deal killer with Ares going into the future as it keeps us still using Ares 2.5.
   3. Dean would probably have to appoint someone (R. Silterra?) to talk to Atlas about what services are available from Voyager that would work with Ares. Something would have to be built on our end to work with Ares.
   4. Dealing with duplicate courses - if possible, Joanne will generate a report showing duplicate courses; the relevant Reserves staff will do cleanup.
   5. Tom Trutt will update the course submission page to get rid of choice "garbage" at the bottom.

1. Improving instructions for instructors
   The info at the bottom of http://www.library.cornell.edu/svcs/serve/res is insufficient and needs to be fleshed out with bullet points to make things more clear. Same thing at http://www.library.cornell.edu/svcs/serve/res/resinfo#guidelines_inlibrary - this needs to be revised and made more clear. Joanne (editing) and Vanessa (wording) will work on this.

1. Ares web form for instructors: direct to Blackboard?
   No - this would cause more problems for some instructors/units.

1. 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.). All formats should be recognized.
• 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.
• 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?