Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

03:10-04:30 PM

Zoom: contact chair for link and password

Attendees

Not attending

Discussion items

Item

Desired Outcome

Time

Who

Notes

Decisions

Local group takeaways

Actions

1

Updates

30 mins

All

Vanguard first impressions!
SF: Question about indexing old system numbers. Index can be customized (enabling the field, adding it to the simple or advanced search menu) at Alma configuration >> Search configuration >> Search indexes.
SD/LA got multi-match reports. Need to investigate what caused NZ to reject the records.
LA/UCB: Log-in set up has not completed.
SCP: Two data sets coded database resulted in less desirable collection (database) records. They should have been portfolios. Will be corrected at the next test load.
SB: New metadata editor has caused an issue with indexing?

PPC approved on a moratorium on all edits (both IZ and NZ) until Septemeber 21. Read-only between today and 21st.

Quick NZ demo (Liz)
How to tell where the record came from? – does not appear yet. (Followup: NZ has not been completed yet)
Local 856 in the bib: if the record becomes the NZ master it will be shown in other campuses IZs – need to be re-evaluated.
Search results can be filtered by institution.

Please post more questions to Slack.

2

Bib record management in the NZ

Review and possibly vote on Vanguard recommendations

20 mins

All

Bib record management in the Vanguard

Thoughts on campuses managing as much as they can in their IZ?
What can be done only in NZ? – Deleting NZ records and possibly processing OCLC updates (if implemented).
Generally, NZ admin. accounts are limited in most consortia.
Import profile has “Use NZ” option.
IZ-to-NZ method could cause an issue with Primo display?

Recommendation for Vanguard: IZ-to NZ, identify issues, and develop use cases for using NZ admin. access.
Import profile: if the set is in a category of record that belongs to NZ, generally the profile should be set so that the records be imported for NZ matching first, and copied down to IZ.

Should “Enforced NZ” be considered?
Enforced NZ disables the ability to add records to IZ only --
Maybe it’s more restrictive than we need?

How can SCP’s local fields (in NZ 9XX range) be protected?
The fields can be configured to be manageable in NZ only (NZ admin >> Alma configuration >> Search index).

How many edits are campuses allowed to make to NZ records? – not in this decision page’s scope. Will be discussed as a separate topic.

Vote on the recommendation next week.

Review the documentation on enforced NZ.

Shi will test if the “NZ edit only” option works to protect SCP local fields in sandbox.

3

OCLC updates

Recommendation has been drafted. Vote next week.

Review the recommendation and send feedback

Future agenda items

mapping for 700/7XX fields

using 005 fields during migration?

OCLC update service during Vanguard?

  • No labels