| | | | | | | |
---|
1 | Gather & Announcements | Assemble as a group and share info | 5 | Team | | | |
2 | Discuss Questions from OARM Chart #1 - What is considered OA? #2 - How do we decide to use OCLC/vendor or CZ records, and what are the minimum requirements for a quality bib record? | Develop answers to questions that arise from our workflow chart Finish our review of the SCP OA Definition document by early March to send to stakeholders | 30 | All | | | |
3 | Review Work Plan Draft and discuss meeting frequency | Introduce work plan draft. Determine if current meeting frequency will help us meet our charge | 15 | All | | | |
4 | Report back from SILS groups | Understand what other SILS groups and campuses are doing in relation to OA | 5 | All | E-Resources - Discovery - Resource Management - allUC merge rule #1 has been updated: the rule will no longer protect existing 506 field. Campus Updates - Other (JSC, SCLG, CKGs, etc.) - Primo Content Monthly Newsletter February 2023 - “we have corrected and aligned most of the 506 fields in Alma.” “506 0_ $f Unrestricted is added by Ex Libris to Community zone records that have DOAJ portfolios. 506 indicators that were not an indication for Open access were removed, for example: 506 \\$a Access restricted to University X users only 506 1\$a Access restricted to subscribers We still have some 506 on non-OA records, but eventually they will be removed as well (no definite time line at the moment).”
| | |
5 | Wrap up & Homework | Review actions and decisions | 5 | Team | | | |
6 | Parking Lot | Capture important topics for future discussion | | Team | How to find items that are OA but have slipped thru the cracks, not being labeled OA? Something coming from Discovery group Another area is to rethink JSC and whether they want to continue approval role. Considering ongoing maintenance of OA in Alma/Primo - who is responsible? Statistics/Resource Management as related to the workflow Related to CZ Updates Task List: Consider a cleanup project to compile a list of open access collections in the IZ that are already activated in the NZ. Deactivate and delete those collections from the IZ. This would help with maintenance since we would not have to sift through redundant data if we decided to use the CZ updates task list. “OA cooperative” Solving the missing OA links issue: determine what is within our scope: From Becky: UCSD’s Serials Cataloging Group has the following info as to how UCSD is handling this. Please read the following especially the Content Corner Update: “Are we doing anything with the Community Zone Updates Task List at the moment? When a portfolio is deleted from a community-managed CZ collection, the IZ copy of the portfolio is deactivated and unlinked from the CZ and becomes a "local" portfolio. We currently have no way of being notified of these changes except via targeted periodic sweeps. Using the CZ updates task list would give us a list of updates that directly affect our resources. Who would review the updates, how often, etc.? Who would take care of cleanup?”
a. Content corner: 2022 Alma CKB Release Notes: September-December b. [Moved to Parking Lot] c. Who would review the list of the updates and do the cleanup? TBD.
| | |
7 | | | 60/60 | | | | |