Page Comparison

Item

Desired Outcome

Time

Who

Notes

Discussion

Actions

Announcements

Share short pieces of need-to-know information

5 min

All

• Upcoming meetings with ExL (complete list)

• TJ - When merging bib records between Main library and Law Library, found that not all inventory shows up in Primo

  • Catherine: Double check if the Law Library has locations suppressed at the location configuration level

  • Kevin: Interested in hearing what comes of this issue

• Catherine: Around February, discovered everything was coming in as brief level 1 - new metadata configuration rules. Check brief level settings if going to use in merging records

• TJ: Campuses please share successful brief level settings

  • Catherine might bring brief level rules issue to AEFG and RMFG

RMFG and AEFG Decisions

https://docs.google.com/document/d/1qEe-LeTvJo9GcLSR24YKGKwVURzCuo-CHtkg6L3G6mk/edit

5 min

All

• Groups still discussing local 856 fields

• RMFG reviewing things to leave out of the NZ

  • Can add $9LOCAL to 773/774 fields for boundwidths - in case there’s confusion

  • TJ: 774 should be fine as container record will stay in IZ

• RMFG also reviewing OCLC updates decision

Marcive update (if there is one)

5 min

Ryan Finnerty

• Haven’t loaded April files yet, but PPC is deciding just decided today when that the last final Marcive load will be this April

• Later discussion –

  • What are the different types of scenarios we have (Print AND electronic? Print only? Electronic which is broader than UCSD? Local focuses on MARCIVE profile that’s not covered by UCSD.

• UCSD has been processing lots of MARCIVE updates since the test load (mostly URL updates)

Update on Day 1 post migration data cleanup document

Groups summarize/bring anything up that needs further discussion or clarification

30 min

All

https://docs.google.com/document/d/14pPaqCwoiQcdG2ZbimdjZQ8IdRhGmBz2YyHoviOUUeM/edit?usp=sharing

• Breakouts!

• Group 2 recommendations:

  • Technical migration – will be done/prioritized at the local level

  • Identifying corrupt characters

    • 1) ILSDC should have a normalization rule ready to go/share in the NZ that will do the updates that can be done in bulk (editing the double-daggers, etc)

    • 2) Existing Alma campuses should run the corrupt characters Indication rules on their test DB and production, in order to identify/flag any potential problems before that can be cleaned up in our existing systems now;

    • 3) we should be prepared to run either ONE indication rule and then split up (by campus?) or 10 indication rules (e.g. HAS 035 (cui) AND HAS [corrupt characters]). How this cleanup work will be divided remains to be determined.