MIGRATED TO ONEDRIVE - RAPIDILL Publishing - from Confluence
Background
In Millennium, print journal & book chapter files for RAPIDILL were generated using Create Lists, and then manually submitted to RAPIDILL via Excel files once a year. E-Journal files were generated via Serials Solutions 360 Services and were also submitted to RAPIDILL manually.
In Alma, it is possible to automatically publish files (sets) on a regular basis, removing the need for manual intervention. We create a logical set in Alma Manage Sets, and then create an OAI-PMH publishing profile for the set and specify which MARC tags and item-level metadata should be output. The publishing profile is scheduled to run on the first of every month.
Initial Alma Configuration
We initially configured three RAPIDILL publishing profiles in Spring 2018.
CAMS-7 - Getting issue details... STATUS
See the Jira ticket for documentation and additional details.
Updates to the Profile
In Fall 2018, following the switch of Library Search from the Primo Central interface to Blacklight, TUL's ILL department requested that the e-resource links in the Electronic Journals publishing profile be redirected from Primo to Blacklight URLs. It was not easily possible to accomplish this in the Alma publishing profile, since Alma's URLs are structured using the Primo open URL base. However, we were able to change the link from a Primo open URL to a direct link to the resource via Alma's uresolver.
WEB-728 - Getting issue details... STATUS
See the Jira ticket for additional details.
Ongoing Quality Control
In Jira there is a recurring task in the ARAM project to verify that the monthly RAPID ILL publishing was successful.
RAPIDILL Contacts
Sam Friedman
Assistant Coordinator, RapidILL
Colorado State University
Office: (970) 491-7601
Cell: (612) 345-1545