Announcements | Share short pieces of need-to-know information | 10 min | All | CB: Updated timeline for migration just posted to BaseCamp. IMPT: Vanguard extract due dates are pushed back a few weeks, but data clean up still may not be completed, but more records may be more “ready” to go. TK: SpCol FG discussing local fields and data and ability to configure Primo VE and test to check ability to display local data. | | |
Review of Task List | Maintain Awareness of Incomplete Tasks | 5 min | All | Add labels to blog post: TJ demonstrates where & how to add labels. Should we just determine a few labels to use, perhaps some controlled vocab terms? Some labels were added in meeting. P to E training: may not be necessary for this group? Vanguard groups may receive training, and each campus has met or will meet with ExL for P to E training, so training for this group may not be needed now.
| All can check off the “add labels to blog post” as done - as was completed in meeting. Plan to keep P to E training on list of action items, but move due date to after the Vanguard load, so we have better idea of our needs.
| |
Non-9XX local data for the VanguardDecision | Review decision made by Resource Management Functional Group Discuss if there is any concern | 10 20 min | All | Per RMFG decision, four options for what to do with non-9XX fields is now available. If campus moves Move local fields to new local fields to ; thoroughly document changes as crosswalk. Options for specific fields linked. Some fields can be moved to holdings. Local All local data can all be moved to 590, 690, etc. if time is not available for detailed mapping. Or, keep Keep data in existing fields and see what happens (data may be lost). Some combination of 1-4.
Libraries may have the capacity to do only some or one of these options, as time and ability permits. For Vanguard, campuses may determine to use one method on one subset, and another on a different subset, and experiment to see which method is most successful. Key is to track decisions, changes and “test” records to see results and fix for final migration. 856 fields also may need to be moved to 9XX fields, to copy over (SCP will do this), because 856 fields may be lost. Group may identify these and other fields that were moved to 9XX and are lno no longer needed, post-migration. UCSD wrote up list of instructions for 5XX and has emailed to group. UCR has created decision documentation for delete, merge or migrate 5XX, 9XX fields. Boundwiths are major issue, ExL says not to put in NZ, but many consortia do put materials in NZ. Often, titles do not go to NZ because of lack of holdings, but linked items are visible (via 774, etc). May be future item/issue. | to this decisions UCSB Vanguard Decisions: not changing fields that map to Primo fields, as this would require major changes prior to Vanguard Load. Not changing vendor-related 9XX for Vanguard. Testing MMS IDs for Vanguard and the links to Primo, etc.
For Alma Libraries: May create doc in ILSDC Shared Drive to house common/useful normalization rules. For Alma Libraries - UCs can develop specific prefix/standard for saving clean-up norm rules to community zone, so all can use them, prior to migration.
| |
BaseCamp orientation | Have basic understanding of what BaseCamp is about and how it works | 15 min | All | Orientation of BaseCamp - messages, notifications, etc. Archives: for completed or closed messages/questions; archived items are searchable. Tags for questions/issues for different areas, so you can filter questions by category, if needed. CB and TK can post questions to BC for group, as questions are identified and bubble up. All SILS members will not have access to BC, but chairs, ICs and other select members will have access.
| Group determined calendar from BC would be useful, particularly extract dates, migration dates, etc. CB can export the calendar, leave only important dates such as extract dates, due dates, etc. and send it to group, probably as a google calendar.
| - Catherine Busselen pull BaseCamp Calendar and export as Google Calendar (or similar) to share with group.
-
|