Any data in the 5XX-7XX range that is local (that is not part of the OCLC master record) needs to be moved to a protected local field. In addition, Ex Libris recommends that institution-specific data be moved out of fields 900-949 and that only consortial data stay in those fields for the Network Zone. All campus-specific data in these fields needs to be relocated or deleted.
R = Resource Management A = ILSDC C = Acq/ERM, Discovery FG I = PPC; ILSDC
Decision-making process
Due date
...
***Campuses can map other 9XX data however they like but should keep in mind that long-term RMFG will be asking campuses to adopt the 9XX standardization found here: https://www.carli.illinois.edu/products-services/i-share/physical-res-man/local_extensions. The fields above represent an initial pilot project. ILSDC will be providing comments on when/if campuses can adopt the rest of the mappings before go-live or in the months following.
The 900-949 range is reserved for SCP and other Network Zone work.
For go-live we will want to call out some Acquisitions-specific fields.
Reasoning:
All of the campuses will have to move some degree of local data in order to migrate and so RMFG agreed that this was a good time to look more holistically at what could be gained by more sweeping standardization. CARLI had done a lot of that work already and there were a lot of fields that matched how both VG and non-VG campuses were using data in Alma. The group agreed that there will be significant workload implications in trying to adopt such a large scale standardization project and so agreed to pilot a few fields in order to avoid demanding too much of the ILSDC group and to allow time for testing. In addition, the group noted that moving fields around in Alma is easy enough that if campuses have some straggling data for go-live that would be fine but that the long-term goal is to get all of the data into the mapping linked above. Standardization will allow the campuses to take better advantage of Alma and to share some of the more complicated aspects like normalization and merge rules along with import profiles. It will allow us to create shared documentation and to better help one another with workflows. It also helps other groups that rely on the bibliographic data (Discovery, Acquisitions, Fulfillment) to standardize their own practices and to create more unified user experiences.