Current Action Items
| Excerpt Include | ||||||
|---|---|---|---|---|---|---|
|
Goals:
...
Primary:
- Explore scenarios for improving faculty interface to
...
- retrieve information from Voyager and import into Ares, possibly through OpenURLs.
- Enhance staff interface to import bibliographic and holdings information from Voyager into Ares.
Secondary:
- Enhance faculty interface to allow record creation, status updates in Voyager from Ares, including checking out books, putting items on hold, recall, etc.
...
- Enhance staff interface to import bibliographic and holdings information from Voyager into Ares.
Scenarios to evaluate:
Evolving recommendation:
...
- makes it easier for staff to get information from Voyager to Ares in staff interface
- would eliminate need for Tom's Tools, thereby eliminating maintenance burden
- could solve Music library's issues (identifying scores)
- enhancement on existing functionality in Ares, so should be smaller scope, makes Ares more marketable for Atlas
Still needAlso implement:
- callback scenario to create records in Voyager, update Voyager statuses. (Use SIP or NCIP interface?) Have to buy NCIP module from Voyager, and in the past, we decided not to buy this, but instead get by with SIP capabilities instead for BorrowDirect needs.
- faculty interface improvements, use Z 39.50 interface also? (Instead of Web Services.) We can inject custom Javascript into Ares, so we can add Voyager interaction to Ares itself, make custom Voyager search/results screen in iframe that use Voyager Z39.50 or Web Services. Button in results screen does Ares OpenURL injection, necessary Voyager updates. (Ares uses jQuery for AJAX.)
Finally, would still like additonal additional Ares Web Services for adding/editing items also.
...