Local bibliographic data
Owning group | RM-CMOS |
---|---|
Type of documentation | Policy |
As-of date | Jul 17, 2024 |
Related Ex Libris Documentation:
Network-Managed Records in a Network Zone - Ex Libris Knowledge Center
Policy:
With few exceptions, all local data (i.e., data that is not in the WorldCat record) should be added to bibliographic records in local extensions. Local extensions will only be visible in your institution's instances of Alma and Primo VE.
You can add a local extension by selecting “Add Local Extension” in the MDE (Editing Actions - Add Local Extension; or Ctrl+L):
You can also add local extensions via a template or by using an import profile--for those methods make sure $$9 LOCAL is appended to the end of the field.
You can verify that a field is a local extension because it will have the “institution” icon.
Currently, Alma is configured so that users may not add 590 fields directly to NZ records.
It is not possible to add a local extension by adding the field in Connexion/Record Manager and exporting directly to the NZ via the OCLC Gateway Export. If you do export a record from Connexion/Record Manager with a local field, it will be added to the NZ.
Local data added to the NZ record not as local extensions will not be protected from overlay.
Only certain fields can be added as local extensions (full mapping below): 09X, 59X, 69X, 77X, 78X, and 9XX.
Fields 900-949 are reserved for the Network Zone and should not be coded as local extensions. Campuses should not use this range for any local bib data, except for “transactional” fields used during imports that will be removed during normalization. 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.
Exceptions:
CDL Acquisitions brief records have a standardized 590. (See https://uc-sils.atlassian.net/l/cp/sW7grrkr )
090 fields may be exported from Connexion and used immediately to populate the call number in holdings records. However, they will not be protected from overlay unless they are coded as local extensions.
Local data added to WorldCat with a $5 code for your institution does not need to be coded as a local extension in Alma.
Current field mappings:
Local 5XX data:
590 | Local public note |
591-599 | Other local 5XX data (optional)
|
Local 6XX data:
690 | Local Subject Added Entry--Topical Term |
691 | Local Subject Added Entry--Geographic Name |
692 | Reserved for future use |
693 | Reserved for future use |
694 | Local Index Term--Genre/Form |
695 | Added Class Number |
696 | Local Subject Added Entry--Personal Name |
697 | Local Subject Added Entry--Corporate Name |
698 | Local Subject Added Entry--Meeting Name |
699 | Local Subject Added Entry--Uniform Title |
NZ 9XX data
Field/Range | Definition | Analytics | Notes |
901 | SCP former System ID |
| NZ Search Label: SCP Bib Number (901) |
902 | Report NZ record for deletion |
|
|
904 | MMS ID for merged record |
| System-generated |
908 | Shared NZ processing note (ex. RMFG MARCIVE test) | Local param 08** |
|
910 | Bound-with and related record note |
|
|
920 | SCP participating campus code |
|
|
924 | CDLA/SCP vendor title key or GOBI Order Key |
| NZ Search Label: SCP Title Key (924) |
925 | CDLA/SCP vendor invoice# via GOBI |
|
|
926 | CDLA/SCP GOBI Collection ID |
|
|
927-929 | CDLA local use |
|
|
930 | SCP former 793 (collection title hook) | NZ Local Param 01 | NZ Search Label: SCP Former 793 (930) |
935 | Suppressed record OCLC number |
|
|
936 | CDLA/SCP Collection name via GOBI |
|
|
946 | SCP copy of 856 (Including GOBI records) | NZ Local Param 03 | NZ Search Label: SCP Copy of 856 (946) |
949 | SCP cataloger statistics (Including GOBI batch note) | NZ Local Param 04 | NZ Search Label: SCP Statistics (949) |
Local 9XX data
950-955 | Not standardized |
|
|
956 | Copied 856 data |
|
|
957-968 | Not standardized |
|
|
969 | Course reserved field |
|
|
970 | Local Added Entry--Personal Name |
|
|
971 | Local Added Entry--Corporate Name |
|
|
972 | Local Added Entry--Meeting Name |
|
|
973 | Local Added Entry--Uniform Title |
| Use for 793 data and (if desired) other local collection titles* |
974 | Local Added Entry--Uncontrolled Related/Analytical Title |
|
|
975 | Local Resource Identifier |
|
|
976 | Local Series Added Entry--Personal Name |
|
|
977 | Local Series Added Entry--Corporate Name |
|
|
978 | Local Series Added Entry--Meeting Name |
|
|
979 | Local Series Added Entry--Uniform Title |
|
|
980-991 | Not standardized |
|
|
992 | System IDs that pre-date the current migration (i.e. not your current system ID) (optional for campuses that want to use 1 field for their current ID and one for other IDs from previous migrations) |
|
|
993-995 | Not standardized |
|
|
996 | System IDs (both current IDs and previous IDs if only 1 field is desired) | Local param 09** |
|
997-999 | Not standardized |
|
|
CZ 9XX data used by Ex Libris
Field | Description |
---|---|
906 | A material type (e.g., JOURNAL, BOOK, or VIDEO) created when a title list is loaded into the Alma CZ. It doesn't display OOTB in Primo, and it's not used to generate resource or material type facets |
922 | A note added to CONSER records created by print to electronic record conversion. If a proper electronic CONSER record comes into the CZ, it will replace the converted record |
999 | An attribution note from an Ex Libris project that indicates the record was from the Harvard Library Bibliographic Dataset |
The SILS mission is to transform library services and operations through innovation and collaboration. The future is shared!
Question? Contact AskSILS-L@ucop.edu