Update URL in porfolio when attached bib record's 856 is updated
When the URL in a bib record attached to a portfolio is updated (individually edited, or batch load/overlay of records), there should be a setting to the action so that the URL in an attached portfolio would also be updated and we don't have to remember to manually do this. We have had 2 recent instances, one where we used APIs to update bib records using our old PURL manager to use our new one, only to find that the portfolio URLs also needed to be changed separately, and one where we have a batch of vendor records with changed URLs that we had to delete and re-add in order to get the portfolio URL updated. Both of these were large batches... We'd like to tell Alma to synch URLs in the attached portfolios when we make a manual edit, or load/overlay a batch of records.
If there's a way to do this we don't know, please tell us!
Laura Akerman
shared this idea
Dear community,
Thank you for bringing this idea to our attention.
We analyzed it carefully, and identified that such enhancement might be risky. Therefore we decided that it will not be implemented for now.
Thanks for your understanding.
Tamar Fuches
Alma product team
-
Darren J. Furey
commented
I agree with Mary Grenci's comment below. User access to electronic resources in Alma is delivered via the portfolio. The 856 is only used to load e-resource records and create portfolios. This change would need to be configurable at the institution level and must be an opt-in configuration rather than an opt-out configuration.
-
mike john commented
This really is splendid. Thanks a ton for taking the time to describe all of this. Visit following link to get McAfee security for your online devices https://www.go-mcafee.com/activate/
-
Verity Allison
commented
We have just encountered a similar issue in our implementation of Rialto, it would be great if there was a way to push the updated 856 field to the associated portfolio.
-
Karen Abel
commented
We also think this idea is great. We would just want to ensure that the facility could be switched on or off as needed.
-
Mary Grenci commented
This suggestion would be a big problem for institutions that use the OCLC master record as their bib record. Master records can contain many 856 fields with only some (or none) of them being relevant to a particular library. It would be a huge problem to have changes to those 856 fields automatically update portfolios. So, if implemented it must be configurable at the institution level and the default configuration when first implemented must be set to off (that is, implementing this should require an institution to specifically turn it on).
-
Craig Rosenbeck
commented
I agree! We are running into this issue with OverDrive titles. We have a normalization rule to update the 856 field with the updated URL with the import profile but the portfolio is created before the rule is ran.
-
Patt Leonard
commented
And I would add to that, have the system re-sort the updated portfolios, because they currently display in Alma and Primo in the order (or the reverse order) added to the system, which is confusing, when, for example, volume 3 is obtained after volume 4 has been loaded (so they display--depending on where you're viewing them--as: 1, 2, 4, 3, or 3, 4, 2, 1).