| | | | | | | |
---|
1 | Gather & Announcements | Assemble as a group and share info | 5 | Team | | mtg on 10/31 to avoid conflict with the Unit 17 Table Team meeting | |
2 | Interim Report Status | Review feedback so far | 10 | Team | Interim report sent to OT 8/1/2023: Some comments received from sub-groups No official feedback yet from OT Any feedback from Jared or Nicole from our last meeting?
| CKG group is appealing…what makes something a SILS group vs CKG? | |
3 | Review RM-OST Draft Proposal for Expanded NZ Access | Provide feedback/additional use cases on the draft proposal | 10 | Team | | | Everyone add their additional comments to the document or place them on the next mtg’s agenda |
4 | Work plan goal discussion: Provide recommendations for models of work | Compile a list of questions from our documents & discussions; decide which questions our group can answer, and which an ongoing group could tackle; decide on recommendations to propose | 30 | Carla/All | See spreadsheet for OARM-PT Workflow Proposals Discuss metadata maintenance Brought up the issue of Worldcat Daily Updates on CDL-managed OCLC records. Currently, CDL OCLC holdings symbols are excluded from getting Worldcat Daily Updates. If OA records are managed in NZ, that means they will not be automatically updated via this method. Conversation was previously discussed at SCP-AC about potentially merging all the various -ER symbols into one, but did not move forward How should we tackle metadata maintenance for CZ records, especially enhancing records with OA metadata, given our principle that OA resources should be tagged as such, and that we consider OA metadata part of metadata quality? (ex: a CZ record/collection that is OA, but none of the bib records have OA metadata, and adding it to CZ records may not be advisable because they are following PCC Provider-Neutral Guidelines, which does not currently allow for the OA metadata) More broadly, should we advocate for OA status to be captured at the portfolio/URL level rather than the bibliographic record level, as there are many cases of resources being both OA and paywalled (although, if a resource is OA, we should probably focus on that access point rather than the paywalled access point)? This seems like it would be a larger discussion/advocacy project/Idea Exchange In the meantime, can we also explore the Public Access Model in Alma’s Electronic Portfolio Editor Acquisitions tab as a place to record “open access”? Example of how it displays under the Online Access section (“Access Model Please note that the platform supports unlimited and unrestrict…” I guess the statement shouldn’t get too long or it will get cut off XD ) There was also the question of the use case of the 506 OA metadata beyond user discovery; this metadata could be useful for analytics of our collection; UCLA public services is creating a libguide of OA resources for those who don’t have credentials, such as community users and alumni, where being able to have a reliable OA facet could be important.
Discuss Advocacy | | |
5 | Report back from SILS groups | Understand what other SILS groups and campuses are doing in relation to OA | 5 | All | | | |
6 | Wrap up & Homework | Review actions and decisions | | Team | | | |
7 | 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. 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. Who would review the list of the updates and do the cleanup? TBD.
| | |
8 | | | 60/60 | | | | |