Fredrik Solvang Pettersen
My feedback
8 results found
-
275 votes
An error occurred while saving the comment -
230 votes
Fredrik Solvang Pettersen
supported this idea
·
-
29 votes
Changing the status back from Accepted. Please continue to vote on the idea as your votes will help us prioritize the development. Thank you.
Fredrik Solvang Pettersen
supported this idea
·
An error occurred while saving the comment
Fredrik Solvang Pettersen
commented
Hello! This suggestion was accepted two years ago. Are there any plans to act on this idea soon? We continue to believe that it would significantly enhance the rollover procedure for many institutions. If it is not planned, we are open to hearing counterarguments and engaging in further discussions.
-
4 votes
Fredrik Solvang Pettersen
shared this idea
·
-
30 votes
Fredrik Solvang Pettersen
supported this idea
·
-
342 votes
Fredrik Solvang Pettersen
supported this idea
·
-
42 votes
Fredrik Solvang Pettersen
shared this idea
·
-
47 votes
An error occurred while saving the comment
Fredrik Solvang Pettersen
commented
We second that this proposal would be a very good enhancement. Having all (or a subsection) of addresses displayed in Primo would help users spot mistakes in their own addresses and make it more transparent when choosing how to process home orders. This in turn would reduce the amount of mistaken shipments and confusion among librarians and patrons.
Fredrik Solvang Pettersen
supported this idea
·
We fully support this request. As a consortium managing Primo VE for more than 70 institutions, this is a limitation our members run into directly. We have configured local subject fields tied to specific vocabularies, precisely to allow more precise subject searching, only to find that authority enrichment from 1XX/4XX fields doesn't apply to those fields. This creates an inconsistent experience: users get preferred/non-preferred term expansion when searching the generic Subject field, but not when using the more targeted local fields that institutions have gone out of their way to configure. That undermines the whole point.
Extending authority enrichment to locally configured fields feels like a natural completion of functionality that already exists. We hope Clarivate will prioritize it.