Acquisitions: Monograph Ordering
...
The ordering function is an area where it's more possible to imagine an integrated environment than many other technical services functions because of the nature of an order as opposed to actually handling a physical piece. For example, Columbia could order books for Cornell, and have them delivered to Cornell, especially when we arrive at the place where we use the same library management system.
...
For more, see this group's Phase 1 Report.
...
Acquisitions: Monograph Receiving
...
- Meet and discuss findings with the other relevant working groups (Ordering, Copy Cataloging, Batch Processing).
- Explore points of "harmony" and "discord" revealed in Phase 1.
- Critical issues to explore:
- Shelf ready
- Cataloging upon receipt
- University accounting restrictions
For more, see this group's Phase 1 Report.
...
Acquisitions: Print Serials
...
Because the requirements of print serials are so distinct and dependent on the organizational structures, we have found potential shared activities rather limited. It is hard to see how staff at the two organizations could effectively substitute for each other. However, making the organizational structures more similar (e.g., re-centralizing checkin at Columbia, discontinuing series and sets orders at Columbia) might lead to greater similarity in staff expectations and procedures. With the changes in Cornell's handling of binding tasks, Columbia may also want to reconsider where responsibility for binding and adding is located.
...
For more, see this group's Phase 1 Report.
...
Automation & Technology: Batch Processing
...
To investigate and learn what batch functionalities and record load features are built in to ALMA and see how easily existing record load workflows at Cornell and Columbia can be expected to migrate.
...
For more, see this group's Phase 1 Report.
...
Cataloging & Metadata: Copy Cataloging
...
Possible documentation sharing especially related to RDA training for copy catalogers
...
For more, see the link to this group's Phase 1 Report on their wiki page.
...
Cataloging & Metadata: Database Maintenance
...
Obviously maintenance is done very differently at both Columbia and Cornell, but ultimately it doesn't make a difference how each system does it as long as the work gets done. Except for a few specific maintenance processes which will need to be reviewed in later phases of this project, it may be best to keep each institution's "database maintenance culture" similar to how they were pre-2CUL, especially since both systems would require major overhauls of maintenance procedures, policies, and personnel in order to make them work the same. Unlike many of the processes being looked at for 2CUL, large changes in database maintenance procedures will affect many staff members in libraries across both campuses.
For more, see the link to this group's Phase 1 Report on their wiki page.
...
Cataloging & Metadata: Non-MARC Metadata
...
The working group has identified some areas of possible collaboration during Phase 2 of the 2CUL Technical Services Integration; note: the order of the following list does not necessarily reflect prioritization.
...
For more, see this group's Phase 1 Report.
...
Cataloging & Metadata: Original Cataloging
...
Below are some areas that we have identified for further exploration. Collaboration in some areas (e.g. training) can proceed more or less immediately, while others will need careful planning. We propose to continue to develop this list as we proceed with Phase 2.
...
For more, see this group's Phase 1 Report.
...
E-Resources: General and Troubleshooting
...
A sub-group of the eResources Group will be analyzing the knowledge bases of systems currently and/or potentially used. Selection and shared implementation of joint systems will be critical to realizing an integration of eResources activities.
...
- Off-campus access and variable browser configuration testing - BrowserStack - implementation underway. Both CULs had been using a product called BrowserCam until it was discontinued about a year ago. Since then, we have explored a few options to provide staff with a way to test off-campus use of resources. BrowserStack is now in use at both libraries. There is a subscription cost for BrowserStack that is currently being covered by IT units.
- Troubleshooting tracking system|../../../../../../../../../../display/2cullts/Tracking+system+brainstorming||||||\ - A single incident tracking system for managing all troubleshooting reports. The team is working on a features wish list to help inform our recommendations. We will consider systems that are already available in addition to other options. Both CULs have access to Jira and potentially other incident tracking systems. Some key features should be:
- LIBIT-L@cornell.edu and cul-eproblem@columbia.edu or other appropriate sources of reports should feed directly into the system to avoid re-entry.
- Easy to identify Cornell or Columbia issues
- Ability to route issues to non-e-resource staff and to communicate with vendors and patrons via the system.
- More information on troubleshooting tracking system can be found here|../../../../../../../../../../display/2cullts/Tracking+system+brainstorming||||||\.
- Common ERM/LMS - To improve information access and data normalization that is essential to efficient and effective joint troubleshooting. Key possibilities include:
- Serials Solutions ERM Suite and Consortial add-on - The team is going to examine cost, implementation & migration workload, gain vs. loss regarding Alma migration to develop a recommendation whether to pursue an interim joint ERM option.
- 2CUL's Alma implementation timeline will be an important variable.
- Workflow and information access - We are working to better organize and eventually consolidate useful information about policies, procedures, and best practices.
- Develop guidelines of what to handle at 2CUL level, what to route to "owning" library.
- Provide a dashboard of common responses, access to troubleshooting tools, and contact information for us4e by all troubleshooting staff.
- Automated link/access checking - Callisto - http://sharpmoon.com/callisto/ - This product has to potential to improve our pro-active troubleshooting efforts by helping us identify access problems before our users report them and ensuring that IP address ranges are properly implemented by vendors. Callisto allows for a consortial view, allowing us to compare access to resources across the 2CUL partners.
...