when importing, create portfolio links *after* Process / Normalization Rules ( NR ) are applied (and not before as it is now)
Right now static links in portfolios can be derived form 856 tags in imported MARC records.
Sometimes however we need to manipulate those links to fit the needs of our institution. We could do that easily with a process based on a Normalization Rule (NR) defined in the import profile. But this doesn't work, since our changes to 856 are not considered by Alma when creating the Static links in Portfolios. Our best guess is that static links are created before NR/process are applied and not after. That's a pity.
It would be great if static links were extracted from 856 $u tags after the NR/process manipulation.
Thank you and best regards,
Luigi Siciliano
when importing, create portfolio links after NR are applied and not before
Luigi Siciliano
shared this idea
-
Luigi Siciliano
commented
I derived from this idea a CERV Enhancement request ( AENH-I-36430 ). As suggested by Elizabeth York in the comment below, the CERV request is about an option to choose whether to extract portfolio links from 856 before or after NR are applied, and not just to always use another default behavior.
-
Luigi Siciliano
commented
Let me add that 856 example is just the most import use case that came to my mind. Other MARC field can mapped to portfolios, for Example Public Note or Library.
And the code for the Library is hardly delivered by the publisher in the MARC records, but can be easily be added in the NR embedded in the import profile. The Public Note is another good example. -
Elizabeth York
commented
I want to strongly suggest that if this were to be implemented, this would need to be an option where libraries could select to either create portfolios before or after the normalization process.
There is a very good reason for portfolios to be created before the normalization process--when we import bibliographic records for electronic resources, we want their portfolio links to be created or updated, but we do not want to create 856 fields in our bib records. So, we have a norm rule to remove 856 fields from bib records, and this rule goes into effect nicely after portfolio creation/update. In Alma, access to e-resources is provided via portfolio links, not 856 fields. The portfolio link is what should be maintained and updated to provide consistent access, and Alma gives us great tools to manage our portfolios in batches in our electronic collections. We don't want to be creating 856 fields on our bib records, which would unnecessarily duplicate our portfolio links and be hard to maintain--we want to maintain our links to e-resources in our portfolios alone!
So, I ask Ex Libris, if you implement this, please do not make this a global change so that norm rules are applied before portfolio creation for all customers. If you do implement this, please allow customers to choose whether norm rules should be applied before or after portfolio creation.
-
Jack
commented
Yes, we need this! The first 856 field in our records have cover image JPG files. Alma creates the link using this JPG file. If we could run our normalization process BEFORE Alma creates the links, we could remove this 856 field or make sure it isn't the first 856 in the record. Otherwise, our links are all wrong. Thanks.