October 27, 2010
(Much of the discussion of the meeting is reflected on the main page for this project, specifically, in the Goals, Scenarios to evaluate->Evolving recommendation, Aspects sections.
Tom demo'd staff/faculty interfaces, native and Web, including 'Tom's tools'.
Tom will be adding Javascript validation to Ares Web interface, to normalize department codes, section codes, to match how it is done at Cornell. There is a registrar ID field in Ares, Tom may be able to constrain courses to departments based on new registrar Web Service.
Jesse offered another possible long-term alternative: Ares as status checker on items for faculty, processing aid for staff, but Voyager is really where reserves are processed.
Action Items:
- All: review Adam's meeting notes for completeness and accuracy, edit as necessary, including the following updates to the main page: Goals, Scenarios to evaluate->Evolving recommendation, Aspects.
- Tom: contact Jeannie after meeting about likelihood of making updates to Z39.50, email the group with any response received.
- Adam: schedule next meeting.