Utilize LDR and MARC fixed fields (006,007,008) in Primo VE resource type configuration
Currently it's not possible to utilize LDR and MARC fixed fields (006,007,008) in Primo VE resource type configuration. It would be helpful, if regular expressions could be used to utilize these fields. That way facets could be created for DVDs, Blu-Ray discs and streaming video etc. without workarounds, using standard cataloging.
There is a similar idea already posted for Advanced Search, but we were advised by Ex Libris to list this separately.
This functionality is now available in Primo VE April 2019 release.
Stacey van Groll commented
This should not be marked as Complete.
The content of this request is clearly for AND, and yet the development in-system is OR, in that only one field can be used.
In this way, it is also not correct that this is marked as Complete on the Primo VE Feature Alignment page when it is also there as AND: "Local Resource Type Normalization for MARC Leader and Fixed Fields".
It is not right that a clear request can be submitted, be accepted and Planned with no indication it would be limited, and then the community waits for release six months, only to find that it is not what was asked for or what was promised.
Then the whole cycle starts over again with the idea here: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/38592511-utilize-data-from-multiple-fields-ldr-and-fixed-f
Emma Booth commented
RE: "This functionality is now available in Primo VE April 2019 release."
The functionality introduced in the April 2019 release only allows you to map resource-types from data in a single MARC field.
Primo VE should to be able to determine the resource-type from combinations of data in multiple MARC fields i.e. fixed-field coding in the 006/007/008 field in conjunction with the LDR field.
This is particularly crucial for complex e-resources not coded as language material as changing LDR position 6 to m for computer file or p for mixed materials changes the definitions of positions 18-34 in the 008 field. This means that data in the LDR/006/007/008 fields cannot be assessed in isolation, but must be combined in order to accurately determine the resource-type.
Jen Frys commented
Please consider this enhancement.
Christopher Thomas commented
I agree. 33X fields could be used, but they are lacking in many pre-RDA records and minimal level records. 006/007/008 is the most consistent source for this data.
Nancy Babb commented
In Advanced Search, Primo includes a default set of Resource Types and allows the definition and use of 20 additional local Resource Types. In Primo VE, the definition of these local Resource Types is limited to MARC fields and subfields, and excludes the MARC LDR and fixed fields (006/007/008). As is clear in the documentation about default resource types (Mapping Resource Types in Primo VE), the MARC LDR and fixed fields are a primary and crucial source for resource type identification, and their exclusion makes it very difficult to effectively map to desirable resource types. These fields are available for local resource type definition in Primo, but are lacking only in Primo VE.