Revised: June 30, 2025
Local Fields for Primo VE are additional MARC bibliographic fields that can be configured to display and be used for search and faceting beyond the default fields pre-configured in the Primo VE system. I-Share institutions are able to set up Local Fields for Primo VE in their Alma IZs, but in our shared consortial environment, Local Fields have effects beyond just your local Primo VE instance.
Local Fields in Primo VE can be created by two methods: the MARC21 Fields Method or the Normalization Rule Method. For more details on these two methods, please see below.
The CARLI Discovery Primo VE Committee has identified a set of common fields for display (and in some cases, search and/or facets) that have been distributed from the NZ to all I-Share IZs in Local Fields 51-100.
Please note that not all Local Fields can be Local Extensions in the Alma Metadata Editor. In a shared bibliographic environment like I-Share, some Local Fields may not be appropriate for data that is unique to your library's copy. For example, while Ownership History (local_field_75, MARC 561) and Binding History (local_field_76, MARC 563) are defined consortially as Local Fields, when a bibliographic record is shared in the network, these data are not appropriate for all I-Share libraries and may not persist if the bib record is replaced/updated in future. Such library-specific data may be better suited to the holdings record notes fields rather than bib record notes. See also CARLI documentation on I-Share Common Definitions for Local Extensions and How-To: Using Local Extensions for Copy-Specific Bibliographic Data.
Some fields in the list below (indicated with **) can be configured now, but the data may not display, search, or facet in Primo VE until the semi-annual Primo VE indexing process has completed. Ex Libris states that the indexing will be finished by August 3, 2025.
Local Field number | Local Field name | MARC field definitions | Use for Search and/or Facet? | Status |
local_field_51** | Attribution | 245 $c | no | Distributed 1/16/2025 |
local_field_52** | Publishers | 260 $b and 264 $b | Search - yes | Distributed 1/16/2025 |
local_field_53** | Playing Time (hh:mm:ss) | 306$a | no | Distributed 1/16/2025 |
local_field_54** | Technical Specifications | 344 $abcdefghij and 345 $ab3 | no | Distributed 1/16/2025 |
local_field_55** | Arrangement | 351 $abc3 | no | Distributed 5/8/2025 |
local_field_56** | Audience | 385 $a, 521, and 008[22] | Search - yes; Facet - yes | Distributed 1/16/2025 |
local_field_57** | Creator Characteristics | 386 $ai3 | Search - yes; Facet - yes | Distributed 1/16/2025 |
local_field_58 | General Notes | 500, 515, 550 | Search - yes | Distributed 7/26/2024 |
local_field_59 | Item Specific Notes | 501, 533, 544, 562 | Search - yes | Distributed 7/26/2024 |
local_field_60 | Bibliography | 504 | no | Distributed 7/26/2024 |
local_field_61 | Restrictions | 506 | no | Distributed 7/26/2024 |
local_field_62 | Production Credits | 508 | Search - yes | Distributed 7/26/2024 |
local_field_63 | References | 510 | Search - yes | Distributed 7/26/2024 |
local_field_64 | Performer | 511 | Search - yes | Distributed 7/26/2024 |
local_field_65 | Event | 518 | Search - yes | Distributed 7/26/2024 |
local_field_66 | Cite As | 524 | no | Distributed 7/26/2024 |
local_field_67 | Supplement | 525 | no | Distributed 7/26/2024 |
local_field_68 | Physical Description | 530 | no | Distributed 7/26/2024 |
local_field_69 | System Details | 538 | no | Distributed 7/26/2024 |
local_field_70 | Use Restrictions | 540 | no | Distributed 7/26/2024 |
local_field_71 | Source of Acquisition | 541 | no | Distributed 7/26/2024 |
local_field_72 | Biographical/Historical Note | 545 | no | Distributed 7/26/2024 |
local_field_73 | Language Notes | 546 | no | Distributed 7/26/2024 |
local_field_74 | Index/Finding Aids | 555 | no | Distributed 7/26/2024 |
local_field_75 | Ownership History | 561 | no | Distributed 7/26/2024 |
local_field_76 | Binding Information | 563 | no | Distributed 7/26/2024 |
local_field_77 | Related Items | 580 | Search - yes | Distributed 7/26/2024 |
local_field_78 | Publications | 581 | no | Distributed 7/26/2024 |
local_field_79 | Action Note | 583 | no | Distributed 7/26/2024 |
local_field_80 | Exhibition | 585 | Search - yes | Distributed 7/26/2024 |
local_field_81 | Awards | 586 | Search - yes | Distributed 7/26/2024 |
local_field_82 | Local Notes | 590 - 599 | Search - yes | Distributed 7/26/2024 |
local_field_83** | Dates of Publication | 362 $az | no | Distributed 5/8/2025 |
local_field_84** | Musical Key | 384 $a3 | Search - yes; Facet - yes | Distributed 5/8/2025 |
local_field_86** | Numeric Designation of Musical Work | 383 $abe3 | Search - yes; Facet - yes | Distributed 5/8/2025 |
local_field_87** | Instrumentation | 382 $aben3 | Search - yes | Distributed 5/8/2025 |
**Indicates the field may not be available for display, search, or facet until the semi-annual Primo VE indexing is completed on August 3, 2025.
I-Share libraries may choose how to configure the distributed consortial field(s) for display in their Primo VE (or not):
In a shared Primo VE network environment such as CARLI's, Ex Libris documentation strongly advises against individual Institution Zones (IZ) using the Local Fields Normalization Rule Method unless those Normalization Rules are coordinated and identical across the consortium in every IZ and the Network Zone (NZ). CARLI staff are investigating further to understand the full extent of this recommendation, but tests suggest that if the Normalization Rules are not coordinated and identical, users may see record data differently depending on how and where they search.
Even with the Local Fields MARC21 Field Method (see the "How to Create Local Fields" section below on more information about this method of creating Local Fields), Ex Libris documentation recommends that consistent usage of Local Fields across IZs is desirable so that a user does not experience changing display data when switching search scope or when switching between their local Primo VE view for their institution and the Primo VE Union View. To date, I-Share libraries have not coordinated Local Fields established under the MARC21 Field Method, but we may need to do so in future.
I-Share institutions can set up and configure additional Local Fields in Primo VE for display, searching, or facets by using the MARC21 Field Method. See step-by-step instructions below.
If an I-Share institution has a MARC bibliographic field that you would like to display that is not possible using the MARC21 Field Method—that is, outside of the set 009, 09X, 490, 5XX, 69X, 9XX, or a field within that set that requires conditional logic—contact CARLI Support so that we can maintain a list of such fields for future consortial consideration.
I-Share institutions should not configure any Local Fields for Primo VE using the Normalization Rule Method.
If your institution has already used the Normalization Rule Method to create Local Fields, please notify CARLI Support at so that we can work with you to test network implications and consider if these fields could be consortial fields.
If you have any suggestions for other Local Fields to be configured consortially, please submit them to CARLI Support or the he CARLI Discovery Primo VE Committee for consideration. Thank you!
Local Fields in Primo VE can be created by two methods--the MARC21 Fields Method or the Normalization Rule Method--but as discussed above, I-Share institutions should use the MARC21 Fields Method only. The Ex Libris documentation Managing and Displaying Local Fields for Primo VE describes all possible options for how to create Local Fields, but a straightforward overview of the process using the MARC21 Fields Method is as follows.
You will need to role of Discovery Admin to create local fields using the MARC21 Fields Method:
Primo VE comes pre-configured with a set of MARC bibliographic fields for display, search, and facets.
The Ex Libris document Mapping to the Display, Facets, and Search Sections in the Primo VE Record details the mapping of MARC bibliographic data for display, searching, and faceting in Primo VE.
An IZ can have up to 50 Local Fields (01-50). As a consortium, CARLI can distribute up to 50 more Local Fields from the NZ (51-100), for a total of 100 possible Local Fields.
On the Alma Configuration Form I-Share libraries filled out during migration to Alma, some institutions listed specific local fields that Ex Libris staff set up for them as part of migration.
Local Fields should not be confused with Local Extensions, which are a set of fields (09X, 59X, 69X, 77X, 78X, 9XX) that can be applied to bibliographic records in Alma to indicate local IZ data in a shared network bib record.