Pending agreement, a number of functions can be shared in CLO18 collaborative network. These include: configuration tables; letters; users; licenses for e-resources; vendors; search PO lines; bibliographic and authority records; external-search configurations; import profiles; fulfillment information; resource-sharing rota; consolidated analytics information; central publishing to discovery and OpenURL resolving.
The document below examines options for consortium configuration of services and network sharing. It provides an account of functions arranged by the broader service, i.e., Fulfillment, Resource Management, eResources, Discovery, etc. Advantages to the consortium as well as challenges have been noted. The document also contains links to the Ex Libris Knowledge Center.
Note: that some collaborative network features may require consensus from CLO18 on whether to form a fulfillment network or a resource sharing network.
The document below provides food for thought, yet this is still room for more work – information can be added as we learn more. There is a column to add discussion questions. Additional information may need to be obtained from Ex Libris in order to determine what might be the best time to configure some options.
Questions:
I had some questions about possible network zone configuration for ERM and Primo VE as I was listening to the onboarding presentation on Sept 21 – but I didn’t want to sidestep the presentation away from possible questions individual libraries might have. These relate more to the networking strategy below:
1. Maria noted that there is no common ERM: if this is new to libraries, is there something new as a consortium that should be considered and discussed at the define stage? How to manage configuration if it’s decided that this is indeed wanted?
2. Primo VE decisions on consortium interface may be needed at define phase. Not sure if there is a form, or some process for this.