Primo
Your feedback matters to us. Help us improve Primo by telling us what you’d like to see using the message areas below. You can also can support something already posted.
We would love to be able to respond to every idea that is submitted, but this is not feasible. We are, however, committed to responding to the most popular ideas—those that have received the most points.
For more information please review our FAQ and guidelines. Thank you.
- or
No existing idea results
- ~ No ideas found ~
673 results found
-
Journal search>Browse by categories : allow indexing of Unimarc journals (PrimoVE)
Currently, only journals described in Marc21 are indexed by subject in Journal Search.
The Unimarc community is now large in Alma/PrimoVE, and the Browse by Categories function would be useful if it took into account all formats.
The idea would be to allow indexing of journals described in Unimarc, which have Rameau/LC subject fields in 60X and LCC field in 680.40 votesHi,
We would like to update that this idea is still not planned, but still being examined for a future release.
Best regards,
Yael.
-
Item policy translations
In Alma the Institutions have no possibility to add the translations for the policies. In multilingual consortia environments the only possibilities are to display in Discovery the policy description in English or to add all description translations in the same field. Neither these solutions are user friendly.
The translations should be distributed from the Network.104 votes -
Make consistent the use of CDI record data in Primo UI
Current CDI design in Primo UI is to expose metadata from all participant records for both returning results from a search query, and in the values presented for selection in facet for filtering results, but the display of metadata within records is only by site-specific activations.
This means that a user can search for a term in Primo, have results returned on the basis of that term, select the value for the term in a facet, but then not see the term in the record display.The negative impact of this design decision includes:
* a user is confused by the Primo results list, as there is no indication as to why results were returned, even when the user has specifically targeted data such as an Advanced Search by a specific subject that is then nowhere to be found in the records displayed
* a user can't effectively filter results by facets, because when they do so and look at the records, they can see no relationship between their actions and the resulting records
* a user can't take advantage of lateral links, to generate an Advanced Search query of all the entries for the search term to expand their initial results set, such as all records in a specific subject, because there is no lateral link displayed in the record
* a user is missing key data when exporting by RIS to EndNote, RefWorks, BibTex etc, such as keywords not included, as well as this information not being included in other Send to options of Export to Excel, Print, and EmailEx Libris design should be reviewed and made holistic and meaningful, to either:
1. Hide all the data ie if data is hidden from display, it should also be hidden from search and facets (and any other elements)
2. Show all the data ie if data is used in search and facets, then it should also be shown in displayCurrent CDI design in Primo UI is to expose metadata from all participant records for both returning results from a search query, and in the values presented for selection in facet for filtering results, but the display of metadata within records is only by site-specific activations.
This means that a user can search for a term in Primo, have results returned on the basis of that term, select the value for the term in a facet, but then not see the term in the record display.The negative impact of this design decision includes:
* a user is confused by…342 votes -
Please add to the PRIMO VE mapping table documentation the last update date and mark the new changes in red.
Hello,
We recently discovered that the Primo VE mapping table was updated with new information.
It would be very helpful if you could add last update date and mark in red the new information, the same way that LC mark in red the new information in Marc 21.
If you would apply this suggestion also to other documentation pages it would be great.
Thanks,
Dafna35 votes -
Index Item Level Information
We have entered journal contents into item records. Currently, journal contents is only searchable if the title is available electronically. We would like users to be able to retrieve contents from our physical journal holdings when searching in Primo. This information is contained in the public note field of the item record - having the option to make this searchable would be of great benefit to our users.
Public level notes can be seen in the Primo record, but they cannot be searched so users have to know what they're looking for before they look for it.78 votes -
Enable authority Record Enrichment in Primo VE on local subject fields
In addition to the indexing of bibliographic metadata, Primo VE indexes preferred and non-preferred terms from 1XX and 4XX fields in related Alma authority records. However, this works only in the generic advanced search Subject field.
We need Primo VE to enable authority record enrichment on local fields as well.
Indeed, we have configured local subject fields that are more specific than the default Subject field. These enable searching only on specific subject vocabularies. But configuring such fields does not include the enrichment capability.
87 votes -
Sorting of collection page witch contains only subcollections
When in Alma a collection page contains only subcollections, in Primo, default sort will be "Relevance", with option to change to title.
If the collection page contains only Titles default sort will be "Sort titles by" value set in the Discovery tab of the Collection Resource Editor, with options to change to any sort that is available in the search results page results.It would be very desirable if the sorting setting in Alma would take effect for a collection page containing only subcollections, so that you could sort the subcollections not only by relevance but also alphabetically.
29 votes -
Classification Authority Record Enrichment in Primo VE
In addition to the indexing of bibliographic metadata, Primo VE indexes preferred and non-preferred terms from 1XX and 4XX fields in related Alma authority records.
This is not the case for classification authority records. In the old Primo, it was possible to enrich bibliographic records with additional terms available in 7xx fields of the classification record. For instance:
153 ##$aE860$hUnited States$hLater twentieth century, 1961-$hNixon's administration, 1969-August 9, 1974$jWatergate Affair, 1972-
750 00$aWatergate Affair, 1972-1974.Could you enable enrichment with 7xx fields of classification authority records in the same way fields 1xx and 4xx of authority records enrich bibliographic records in Primo VE?
In addition to the indexing of bibliographic metadata, Primo VE indexes preferred and non-preferred terms from 1XX and 4XX fields in related Alma authority records.
This is not the case for classification authority records. In the old Primo, it was possible to enrich bibliographic records with additional terms available in 7xx fields of the classification record. For instance:
153 ##$aE860$hUnited States$hLater twentieth century, 1961-$hNixon's administration, 1969-August 9, 1974$jWatergate Affair, 1972-
750 00$aWatergate Affair, 1972-1974.Could you enable enrichment with 7xx fields of classification authority records in the same way fields 1xx and 4xx of authority records enrich bibliographic records in…
104 votes -
Ranking of search results by Resource Sharing Library
Concerning search results in Primo : could it be made possible to rank different holdings of the same title by Resource Sharing Library of the patron? This way the patron would see on top of the list the item that is the easiest accessible to him. At present patrons often request items from another library because they did not notice the title is also available at their own library.
126 votes -
Make the Availability indicator for consortia match what was in Primo BO
We have has several users report in a week that they are confused by the lack of accuracy in the availability indicator in Primo VE. For example Milwaukee noticed that this item shows that it is available in another institution- https://wisconsin-uwm.primo.exlibrisgroup.com/permalink/01UWI_ML/cc3uhc/alma9912304483902121
If I check that institution the item is checked out and if I look it Alma it has been out for over a year. https://wisconsin-uwosh.primo.exlibrisgroup.com/permalink/01UWI_OSH/hvjabb/alma991004692621402126Now compare it to Primo BO you will note that in the institutional holdings area, it says Out of the Library. - https://uwi-primoalma-prod.hosted.exlibrisgroup.com/permalink/f/104qq38/UWI71401656290002121 We would want VE to be accurate so users do not think that another institution has an item, when it is really checked out.We have has several users report in a week that they are confused by the lack of accuracy in the availability indicator in Primo VE. For example Milwaukee noticed that this item shows that it is available in another institution- https://wisconsin-uwm.primo.exlibrisgroup.com/permalink/01UWI_ML/cc3uhc/alma9912304483902121
If I check that institution the item is checked out and if I look it Alma it has been out for over a year. https://wisconsin-uwosh.primo.exlibrisgroup.com/permalink/01UWI_OSH/hvjabb/alma991004692621402126
…Now compare it to Primo BO you will note that in the institutional holdings area, it says Out of the Library. - https://uwi-primoalma-prod.hosted.exlibrisgroup.com/permalink/f/104qq38/UWI71401656290002121 We would want VE to be accurate so users do not40 votes -
Allow us to collapse like locations for a library using mapping table like classic
In classic Primo we would able to collapse like locations for a library using a mapping table. For example we have some very large buildings and for logistics we have locations like Stacks 3rd floor and Stacks 4th floor. In the facets it would be nice to just have Stacks be grouped all together. This also allows us to create custom pre-filter for our libguides.
47 votes -
Allow additional links to be added to my library account
In classic Primo we were able to add our ILL link to the library account area, so users could go over and see the rest of their loans. We would like the ability to do this again and have it show up on the loans tab in the My Library Account.
36 votes -
Enable the Hebrew Acronym file in CDI
I would like the Hebrew Acronym file to work in the same manner for local and remote records and enable the correct retrieval of records with any of the many Hebrew words that are comprised of initials (eg פלמ"ח, תנ"ך, תשנ"א, אדמו"ר, בג"ץ, רמב"ם, מפא"י…….).
Currently, searching a term either with or without the " sign will retrieve the term both with and without the quotation sign (") but ONLY for local records. Until this will work in CDI, many remote records will not be retrievable when searching terms that can be written in both ways (with or without the " sign).
I would like the Hebrew Acronym file to work in the same manner for local and remote records and enable the correct retrieval of records with any of the many Hebrew words that are comprised of initials (eg פלמ"ח, תנ"ך, תשנ"א, אדמו"ר, בג"ץ, רמב"ם, מפא"י…….).
Currently, searching a term either with or without the " sign will retrieve the term both with and without the quotation sign (") but ONLY for local records. Until this will work in CDI, many remote records will not be retrievable when searching terms that can be written in both ways (with or without the…
167 votes -
Personal name (600/610/611) should be included in Browse subject of Primo VE
Currently Primo VE does not search 600/610/611 as part of a Browse subject search. That means that a patron cannot view or browse through all of the subject headings for books about “Luther, Martin” or “Morrison, Toni.” The 600/610/611 fields are searchable in Alma as “names” but not browsable in Primo VE as subjects. Leaving out personal names goes against the common expectation in library systems to find all subjects including those that describe people, companies, etc. A similar entry exists in the Alma part of Idea Exchange: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/35782486-browse-by-subject-headings-to-include-600-610-611
68 votes -
Enable search and browse also for item call numbers, not only holdings
Hi
We switched to Primo VE some months ago and are really missing a call number index that shows all our call numbers, in items as well as in holdings.
https://slidetodoc.com/three-types-of-call-numbers-in-alma-yoel
"Item Call Number – is it in Primo VE search indexes?
• The item call number cannot be added as a Primo VE search index.
• Of the three call numbers only the “Holding Call Number” can be added as a Primo VE search index."Our call number index is set to "callnumber.4 – Shelving control number call number", our item call numbers are type 4, but they are missing in the call number index.
https://basel.swisscovery.org/discovery/browse?vid=41SLSP_UBS:live
Examples:
https://slsp-ubs.primo.exlibrisgroup.com/permalink/41SLSP_UBS/mmbbsj/alma9920741170105504
No hit in call number index search for
UBH Bc I 50
UBH Bc I 51
UBH Bc I 52
https://basel.swisscovery.org/permalink/41SLSP_UBS/mmbbsj/alma9910081250105504
Can not be found in the call number index under UBH AL VII 42:1993
We know that it can be done in Alma (see screenshot), but we need the function also in Primo.
In addition to the index search, please also index the item call numbers for simple and advanced search.
Hi
We switched to Primo VE some months ago and are really missing a call number index that shows all our call numbers, in items as well as in holdings.
https://slidetodoc.com/three-types-of-call-numbers-in-alma-yoel
"Item Call Number – is it in Primo VE search indexes?
• The item call number cannot be added as a Primo VE search index.
• Of the three call numbers only the “Holding Call Number” can be added as a Primo VE search index."Our call number index is set to "callnumber.4 – Shelving control number call number", our item call numbers are type 4, but they are…
586 votes -
Results for e-resources when narrowing down to IZ
The users expect that with the facets, you would be able to filter electronic resources by library and/or IZ that licensed them. This is currently not the case. When filtering by location, e-resources (incl. external data sources) are not delivered as results.
Electronic resources should be recognized by Primo as owned by libraries and institutions like physical resources. We would highly appreciate if Ex Libris could make this possible.
172 votes -
Improve the search for non-preferred terms
The search of a non-preferred term works correctly with standard indexes.
Non-preferred terms are currently indexed in the creator, title and subject fields but they are not additionally indexed in a local search field.
For example the advanced search of a non-preferred term doesn't work when a local search field is chosen.The search for non-preferred terms should be also enabled for local fields
SF 00927933
51 votes -
Ability to customise resource sharing status messages displayed in MyAccount Requests tab
We would like the ability to customize patron-facing status messages during the interlibrary loan process.
• Client feedback clearly indicates that status messages that are meaningful for library staff can be misleading to the Primo end user. Note: The Borrowing RS Request Statuses Alma configuration page (Alma configuration / Fulfillment / Resource Sharing) does not include external description / customisation options like other mapping/code tables, e.g. Physical Locations or Discovery Interface Display Logic Labels.
• The “Pick up” message gives the impression that the item is ready for pickup. UNSW patrons sometimes go to the library to pick up the item only to discover that the request is still in progress. Also, the message is not relevant to UNSW staff for digital copies as these are mailed to the requester. The ability to customise or optionally suppress this message is required per Resource Sharing type (physical or digital) and per request status (e.g. only display pickup details when the item is ready for pickup OR display “The digitised copy has been emailed to you”)
It must be possible to:
a. Customise the patron facing status messages e.g. Change “ILL. Created borrowing request” to “Status: Your request is being processed”
b. Optionally suppress the Pick up label and library name or to customise the message per request type (physical or digital) and request status.We would like the ability to customize patron-facing status messages during the interlibrary loan process.
• Client feedback clearly indicates that status messages that are meaningful for library staff can be misleading to the Primo end user. Note: The Borrowing RS Request Statuses Alma configuration page (Alma configuration / Fulfillment / Resource Sharing) does not include external description / customisation options like other mapping/code tables, e.g. Physical Locations or Discovery Interface Display Logic Labels.
• The “Pick up” message gives the impression that the item is ready for pickup. UNSW patrons sometimes go to the library to pick up the…
35 votes -
"Report To Ex Libris" for CDI issues
Currently it is only possible to report Collection and Portfolios issues via the "Report to Ex Libris" functionality of Alma.
Colleagues from our e-resources department (who also manage most of the CDI settings) would be glad to use this reporting tool also for CDI issues: wrong URLs, incorrect "Full Text Rights in CDI", etc.Please, provide a CRM Cateogry "CDI" in the form and include some CDI data (like now Collection ID, Portfolio ID).
This would make it much easier for us to report CDI problems, and support team would also benefit from standardized requests.124 votes -
Increase the number of local fields for search and facets
If the library has many specialized and local fields it should be possible to improve the user search without the build-in restriction of 10 locally defined fields. There should not be a limit to use of local fields.
103 votes
- Don't see your idea?