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)

RMFG and AEFG Decisions

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

5 min

All

Marcive update (if there is one)

5 min

Ryan Finnerty

• 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.