2023-01-18 Meeting notes

Greetings

Jill

Topics for discussion

1. Committee and Task Force updates

   1. IDTF: discussed our first set of mappings for supplemental terms from the Homosaurus and start working within our campuses and local organizations to look into headings related to Indigenous groups in California

   2. ask at NACO training about adding names IDTF gives us

   3. afterwards we’ll talk about policy planning for name additions in coordination with the wiki authorities/ linked data group

   4. Sharing record sets with NZ

2. OA editing in the NZ

   1. Per Nerissa:
      My first priority for identifying records to apply the 506 field to would be NZ collections that are labeled Open Access, as presumably, everything in those collections are supposed to be OA.  My second priority would be to apply the 506 field to any NZ Federal (or CA?) document record that contains an 856 field, as they are all OA as well.

      SDSU is now starting to talk about creating an local OA cataloging policy to address when to add individual OA titles to our IZ, and when to apply the 506 field, as well as batch applying it to gov docs with 856 fields in our IZ.

   2. create norm rule and put it in the NZ so everyone can run it

3. Other ideas for secondary resource types

   1. Government Documents (example)

      1. check how to filter out state University press

   2. Comic Books/Graphic Novels (example)

   3. juvenile materials

   4. manuscript vs. published book

   5. theses - check current filter

   6. magazines - 'g' vs. journals

   7. Others?

4. Advocating for an NZ manager in the CO’s office

   1. also talk to Marcus and Kara

   2. Checks Daily OCLC Record Loads (Checking New & Updated Records and troubleshooting multi-match records);

   3. Performs monthly NZ Record Cleanup (to ensure removal of unused records with no inventory in the NZ) - automated now, but confirm syncs work;

   4. Responds to campuses’ requests for troubleshooting bibliographic records via the NZ Troubleshooting Form; 

   5. Contacts campuses to resolve/move inventory to appropriate records to ensure quality of the database and compliance to record policies;

   6. Performs periodic analysis of records via Analytic reports (to identify duplicate records; or, other issues such as local fields in NZ records, etc.).

   7. Provided assistance to campuses using the NZ;

   8. Collaborated with others in areas related to resource management workflows and NZ record management and impact to other functional areas (such as Resource sharing);

   9. Updated and deleted records for e-book packages in collaboration with Jessica Hartwigsen; 

   10. Led Normalization Rule Group charged with reviewing, approving, and implementing Primo normalization rule requests for the display of data in Primo.

   11. Developed documentation related to the NZ management tasks;

   12. Participated as the CO Representative in the Resource Management Functional Committee and other related groups (NZ Management Group; CSU TS Monthly Testing Group)

   13. Load agreed e-resource record collections for CSU-wide use for situations were the CZ records are sub-par or non-existent (example: California state e-resources) - see Washington DC Policy for model - identify a set to show volume of impact

   14. Liaise with OCLC

5. Topics for joint meeting with Discovery group

   1. What can we do to better influence deduplication and collocation?

   2. Does the usage data for facets make us feel we should pay more or less attention to adding subject, genre, and resource type information in the MARC records?

   3. have they seen any secondary resources types that know should be added

6. Report a resource links - Marcus Jun will present at TS forum tomorrow

   1. Primo VE link to report content concerns
      Sorry I missed the ts open forum yesterday. (I was on a roll corralling our print periodicals.)I heard people were asking about how SF State users can report concerns about harmful or problematic content.
      We use a general electronic service (GES) and here’s our documentation and info from the knowledge center.
      https://docs.google.com/document/d/1Phf7Itgqz50wPeIuPmADzodhpg9RMzCJBETgMoBrMzc/edit?usp=sharing
      Configuring Discovery Interface Display Logic for Primo VE The form and statement were developed by our library’s Content Warning Working Group.
      https://sfsu.libanswers.com/form?queue_id=5801Refreshing the webpage to get the link to display was a bug I created. (Whoops) I had two Service Availability Rules that did the same thing so I removed one, saved, and the link displays fine now.

Action Items