Legend:
Status | ||
---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Page Properties | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||
|
Recommendation
Updated (in green) 5/13/2021
Fields 900-949 are reserved for the Network Zone. Campuses must move all data out of this range prior to migration, regardless of whether the data is purely local or not. This includes, but is not limited to, data generated during OCLC exports. The sole exception is 936 fields with both indicators blank (936##) and those can only be left as-is if the campus is sure that they have never included local data of any kind. If there is any doubt about the existence of local data in a 936## field, campuses should move their 936 data into another field and RMFG can re-visit which data to add back to the NZ range post-migration. The rest of the mapping can be adopted by the end of Phase 4.
...
Lastly, the 9XX ranges do not apply to SCP data since they will be using the 900-949 NZ range.
Background
Test Load page: https://uc-sils.atlassian.net/wiki/pages/resumedraft.action?draftId=858554619
...
Up to 10 local fields can be added to Analytics. It’s unclear whether that means 10 per campus or consortium.
Action Log
Action/Point Person | Expected Completion Date | Notes | Status |
---|---|---|---|
Finalize field choices and report to PPC for approval(Resource Management FG) | 03/12/21 | Done | |
Send final choices to ILSDC (Resource Management FG) | 03/12/21 | Done | |
Updated 5/13/21 | Done |