Legend:
| Status | ||||
|---|---|---|---|---|
|
| Page Properties | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||
|
Recommendation
Reasoning
Background
Currently, UC users utilize the CDL Request Interface to submit their Document Delivery Service (DDS) requests to their local home campus library’s Resource Sharing or DDS units. With the implementation of SILS, Request will no longer provide a patron interface into DDS for scanning (digitization) and paging services at any UC campus, DDS will need to be implemented through Alma/Primo VE and/or through other local systems.
Dependencies
There is a wide range of operational diversity among UC DDS units that will need to be maintained with any new implementation. The distinctive nature of any UC Document Delivery Service is dependent on components such as 1) Type of services offered. 2) User eligibility. 3) Cost to user. 4) Campus libraries that offer DDS. Therefore any potential integration of a UC DDS unit into Alma/Primo on either a consortial or individualized basis should at least examine the following parameters:
TYPE OF SERVICES: Does the campus and/or individual library DDS unit offer book paging and delivery service only, scanning/digitization service only, or both of these services.
USER ELIGIBILITY: Which user groups and/or status of users are eligible to use a campus and/or individual library Document Delivery Service.
COST TO USER: Does a campus and.or individual library DDS unit charge their users for the service(s) or is it free to them. Do they charge some user groups, but not others.
CAMPUS LIBRARY LOCATIONS: Which campus library locations offer a DDS (“turned on”) and which ones do not (turned off).
The ability to charge fees and track payments are needed for some UC DDS units but not necessarily for all. Both options need to be available.
UC DDS configurations should be flexible enough to easily reconfigure as campus/library needs shift, As an example, due to the COVID-19 environment, the UCI DDS configuration is starting out with only two of the four library locations turned on, less restrictive user eligibility, and free of charge. But later on UCI may want to add a third library location, or decide to limit UCI user eligibility and possibly charge.
Primo VE can be used as the primary new user interface to submit DDS requests.
Questions to consider
Given the wide range of operational diversity and flexible needs of UC campus DDS units is harmonization possible or even desirable?
The four operational parameters listed (services, eligibility, cost and campus library participation) help define most of the distinctions between UC DDS units, Are there other distinguishing operational parameters that should be considered as well?
If it is more feasible to go with individualized campus configurations, can these distinctive operational parameter needs be used to build some templates or models that can assist in configuring UC DDS with Alma/Primo?
UCI has developed a Document Delivery Service using Alma/Primo that offers both book delivery and digitization. It has the ability to turn campus library locations on and off for DDS. In the current environment, eligibility is set for anyone with a UCI library card and the service is free. Can this be used as a potential configuration model template?
Even on an individualized campus by campus basis, can the operational needs of all UC DDS units be satisfied through Alma/Primo configurations? Or will a significant amount of workflow still have to be performed through local systems?
Will it be problematic for any campus DDS unit to use Primo VE as the new patron user interface for submitting DDS requests? If so,what are potential other solutions?
Resources
Configuring Digital Fulfillment in Alma
An IGELU slideshow on implementing digitization in Alma
https://www.slideshare.net/frenaville/yes-we-can-implementing-digitization-requests-in-alma
Action Log
Action/Point Person | Expected Completion Date | Notes | Status |
|---|---|---|---|