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
4 results found
-
Include the item barcode as part of the data published from Alma to Primo in the AVA field to improve item search in Primo
Request for Alma item barcode be included in the data that is published to Primo as part of the Alma publishing functionality to enable barcode searchability in the Primo keyword search. We have discovered that items migrated from our previous ILS do contain the item barcode(s) in the MARC 945 $$i and is written to the search:general field of the PNX. As such, those items are keyword searchable via their barcode in Primo. However, for items created in Alma, the item barcode is not written to the bib record and is therefore not searchable in Primo. Adding the item barcode manually to the bib 945$$i for each item as part of our processing is not a viable alternative.
We would like an enhancement to Alma publishing that would add the item barcode to the data published in the "AVA" field. This functionality would improve workflow for staff when they need to search a record in Primo without having to navigate out of the items screen in Alma to retrieve the OCLC number, the MMSID or the ISBN, or to pull up the record in Primo when the book is in-hand without needing to key in the title or ISBN.
Examples of migrated records with the item barcode in the 945 $$i:
http://alliance-primo.hosted.exlibrisgroup.com/CC:cc_alma:CP71153242760001
http://alliance-primo.hosted.exlibrisgroup.com/CC:cc_alma:CP71188416360001451Request for Alma item barcode be included in the data that is published to Primo as part of the Alma publishing functionality to enable barcode searchability in the Primo keyword search. We have discovered that items migrated from our previous ILS do contain the item barcode(s) in the MARC 945 $$i and is written to the search:general field of the PNX. As such, those items are keyword searchable via their barcode in Primo. However, for items created in Alma, the item barcode is not written to the bib record and is therefore not searchable in Primo. Adding the item barcode…
465 votes -
Less duplicate records in Primo Central Index results
Primo Central grouping is based on the existing FRBR workflow, including the grouping process at the database level (the way the Search engine handles grouping) and the Front End functionality. It is used to prevent duplicate records in the results list.
Unfortunately, many records are not added to FRBR groups because the system considers the metadata are not rich enough. With the increase of records provided by (Open Access) aggregators and repositories, the number of duplicate records will certainly not decrease.
Could Ex Libris improve the FRBR workflow for Primo Central records in order to reduce the number of duplicate results and consolidate the FRBR groups?
Examples of duplicate records:
Accuracy of prediction of gene content in large animal populations and its use for candidate gene detection and genetic evaluation
3 results (2 FRBR groups):
- TNproquest195858157 and TNfaoagrisUS201300875183
- TNcrossref10.3168/jds.2007-0231, TNscopus2-s2.0-42449094585, TNsciversesciencedirectelsevierS0022-0302(08)71293-1, TNmedline18349258
- TNorbi2268/23076Linguistic symbiosis between event loop actors and threads
2 results (1 FRBR group):
- TNsciversesciencedirectelsevierS1477-8424(08)00024-9
- TNscopus2-s2.0-51649125887 and TNcrossref10.1016/j.cl.2008.06.005Efficient control of transient wave forms to prevent spreading depolarizations
2 results (1 FRBR group):
- TNarxiv0705.3398
- TNscopus2-s2.0-39649117125, TNsciversesciencedirectelsevierS0022-5193(07)00579-6, TNcrossref10.1016/j.jtbi.2007.11.019, TNmedline18177900Le traitement de la modalité épistémique dans les traductions françaises de On the Origin of Species de Charles Darwin
3 results:
- TNerudit1038687ar
- TNscopus2-s2.0-85017546223
- TN_proquest1870219718Primo Central grouping is based on the existing FRBR workflow, including the grouping process at the database level (the way the Search engine handles grouping) and the Front End functionality. It is used to prevent duplicate records in the results list.
Unfortunately, many records are not added to FRBR groups because the system considers the metadata are not rich enough. With the increase of records provided by (Open Access) aggregators and repositories, the number of duplicate records will certainly not decrease.
Could Ex Libris improve the FRBR workflow for Primo Central records in order to reduce the number of duplicate
…203 votesHi all,
We are moving this idea to "Closed" to release your votes, as it is no longer relevant with CDI.
Best regards,
Yael.
-
Ensure that CZ & CDI Metadata is Linked Data Ready
I was advised by the Linked Data Group to post this idea here because I submitted the following for the LOD Working Group webinar in December:
Broader strategic and commercial alliances required to ensure that data is ready to be linked?
To engender confidence in CZ and make it linked-data ready, why don’t the Company do business with e.g. Backstage Library Works for authority control clean-up and maintenance?
Metadata is a global commodity so all stakeholders have responsibility for creating, sharing, enriching and maintaining it, and of course there are costs for all of these elements which we could share.
Isn’t this the best way to ease the burden on libraries and leverage our metadata improvements for mutual and sustainable benefit?
I note that this document alludes to the Company taking a lead in creating a new open metadata platform and preserved data in an open format.
https://knowledge.exlibrisgroup.com/Alma/Product_Materials/010Roadmap/Linked_Open_DataPreserving metadata is not the same thing as maintaining it because metadata evolves e.g. authorities are deleted, changed and new ones created.
In light of this I would ask that the Company explore strategic commercial partnerships to ensure that any metadata that they manage (knowledgebases, platforms) is properly maintained.
Jane
I was advised by the Linked Data Group to post this idea here because I submitted the following for the LOD Working Group webinar in December:
Broader strategic and commercial alliances required to ensure that data is ready to be linked?
To engender confidence in CZ and make it linked-data ready, why don’t the Company do business with e.g. Backstage Library Works for authority control clean-up and maintenance?
Metadata is a global commodity so all stakeholders have responsibility for creating, sharing, enriching and maintaining it, and of course there are costs for all of these elements which we could…
16 votes -
Allow multiple custom CSS stylesheets per view
At the Digital Theological Library, we have multiple campuses, each of which has its own view. All of the views use the same basic custom design, but each one needs its own specific CSS tweaks. Maintaining this would be much simpler if all of the views could have two custom CSS files: one with the basic design rules and one with the specific design tweaks. That way, when the base design is updated, the view-specific CSS can't accidentally be disturbed by copying and pasting within a single stylesheet, and Primo UI managers like me won't need to copy and paste across all of our views in the first place. The view-specific stylesheet would need to be listed after the main CSS in the <head> of the page to avoid incorrect cascading.
Another option that would be even easier to use from my perspective but would probably be harder to implement would be to have a set of system-wide view styles that could then be overridden with individual custom.css stylesheets. Either solution would greatly improve my workflow for maintaining multiple views and would also benefit other Primo institutions with multiple campuses or customized views.
At the Digital Theological Library, we have multiple campuses, each of which has its own view. All of the views use the same basic custom design, but each one needs its own specific CSS tweaks. Maintaining this would be much simpler if all of the views could have two custom CSS files: one with the basic design rules and one with the specific design tweaks. That way, when the base design is updated, the view-specific CSS can't accidentally be disturbed by copying and pasting within a single stylesheet, and Primo UI managers like me won't need to copy and paste…
3 votes
749 results found
-
Direct Reporting of Incorrect CDI Metadata to Ex Libris
We would like to suggest introducing a dedicated option, such as a platform or a feedback button in Primo, that allows patrons to report incorrect CDI metadata directly to Ex Libris.
Currently, such reports are generally forwarded to libraries, which then need to investigate the issue and, where necessary, forward it to their consortium, which in turn opens a Salesforce case with Ex Libris. This can be a time-consuming process involving several intermediaries, especially when the issue concerns a single incorrect metadata field.
A direct reporting option would streamline this process by ensuring that feedback reaches the team responsible for CDI data quality without requiring libraries, consortia and the Salesforce team to act as intermediaries. This would reduce the administrative workload, simplify the reporting process for patrons, and potentially lead to faster corrections and improved metadata quality.
We would like to suggest introducing a dedicated option, such as a platform or a feedback button in Primo, that allows patrons to report incorrect CDI metadata directly to Ex Libris.
Currently, such reports are generally forwarded to libraries, which then need to investigate the issue and, where necessary, forward it to their consortium, which in turn opens a Salesforce case with Ex Libris. This can be a time-consuming process involving several intermediaries, especially when the issue concerns a single incorrect metadata field.
A direct reporting option would streamline this process by ensuring that feedback reaches the team responsible for…
3 votes -
Citation of Digital Resources
Digital resources are available for viewing and downloading through Primo. We hope the citation feature could be enhanced to include information about the digital collection from which an item originates, similar to citation options provided by many content databases.
For example, when viewing a document in a Gale database and selecting the Cite option, the generated citation includes the database name, URL, and date accessed.
We would love to see similar functionality for digital resources in Primo. Ideally, a generated citation could include:
The digital collection name (or institution name)
A persistent link to the collection or item
The date accessed
This information would help users create more complete and accurate citations for materials accessed through digital collections. It would also increase the visibility of institutional digital collections and encourage users to explore additional related content.
Would it be possible to support this functionality in Primo?
If there are recommended metadata fields or bibliographic record elements that Primo could use to populate this information consistently, many institutions would likely be interested in adopting those guidelines.
Thank you for your consideration!
Digital resources are available for viewing and downloading through Primo. We hope the citation feature could be enhanced to include information about the digital collection from which an item originates, similar to citation options provided by many content databases.
For example, when viewing a document in a Gale database and selecting the Cite option, the generated citation includes the database name, URL, and date accessed.
We would love to see similar functionality for digital resources in Primo. Ideally, a generated citation could include:
The digital collection name (or institution name)
A persistent link to the collection or item
The date…
17 votes -
Have a filter and/or way to identify AI Generated Resources in Primo
With publishers like Springer including AI Generated Books in their packages ex Skeletal Muscle Physiology, Criticism and Critical Theory: A Machine Generated Overview, and Mastering Machine Learning: From Basics to Advanced (which has been retracted)
It would be useful to have a way to indicate AI Generated Resources in the metadata and to have a filter in Primo and/or have a way to easily identify them as AI Generated material.
2 votes -
Concept-level ANDing for Natural Language Search expansions in Primo VE NDE UI
As a library patron using Ask Anything / Natural Language Search in Primo VE NDE UI, and as a discovery administrator supporting those patrons, I would like Natural Language Search to cluster synonyms into semantic concept groups and AND those concept groups together, while keeping OR within each concept group for synonym expansion.
Today the documentation states: “The elements of the query… are classified by the AI system, which uses this information to generate the basic Boolean query and then expands it using related concepts to create six permutations of the basic query. The permutations are used to generate an expanded search term for the query. In this expanded search term, all of the permutations are included, with logical OR relationships between them”
Current example:
User query: what is the relationship between heart attacks and mood?
Generated expansion: (heart attacks) OR (myocardial infarction) OR (mood) OR (emotional state) OR (depression) OR (psychological effects)
Desired expansion: ((heart attacks) OR (myocardial infarction)) AND ((mood) OR (emotional state) OR (depression) OR (psychological effects))
This would allow natural language queries to return precise, intersection-based results instead of a broad OR of all synonyms, improving recall relevance and user trust in Ask Anything.
This preserves synonym recall via intra-concept OR while restoring precision via inter-concept AND, which matches user intent for “X and Y”, “relationship between X and Y”, “effects of X on Y” type questions.
The Known Issue in the current documentation – “In cases where identifiers or authors are detected, the relation between the different fields may appear as OR (except for the first variation) instead of AND, which results in expanded search results” – would be addressed.
As a library patron using Ask Anything / Natural Language Search in Primo VE NDE UI, and as a discovery administrator supporting those patrons, I would like Natural Language Search to cluster synonyms into semantic concept groups and AND those concept groups together, while keeping OR within each concept group for synonym expansion.
Today the documentation states: “The elements of the query… are classified by the AI system, which uses this information to generate the basic Boolean query and then expands it using related concepts to create six permutations of the basic query. The permutations are used to generate an…
3 votes -
Make replaced DEI terms clickable hyperlinks in Primo record displays
The new configuration feature "DEI - List of terms to exclude from Heading" is a valuable tool that allows libraries to replace offensive or outdated Library of Congress Subject Headings with preferred terminology (for example, replacing "McKinley, Mount (Alaska)" with "Denali, Mount (Alaska)").
However, currently, when a subject heading is replaced using this feature, the updated term loses its hyperlinking functionality in the detailed display.
Subject heading links are a core discovery path in Primo, enabling users to explore related materials easily. Disabling hyperlinks on DEI-updated headings creates an inconsistent browsing experience and penalizes discovery on records using preferred terminology.
3 votes -
Improve Resource Recommender Navigation and Type Visibility in Primo NDE
In Primo NDE, the Resource Recommender initially displays a maximum of three recommendations. When additional recommendations are available, users must navigate through them using a horizontal carousel, advancing one entry at a time by clicking a small arrow control.
This design creates several usability issues:
- The arrow is the only indication that additional recommendations exist.
- Users cannot easily determine how many recommendations are available.
- Users cannot see how many recommendation types are represented.
- Users cannot view a complete list of all recommendations.
- Accessing later recommendations requires repeated one-by-one, click-by-click, navigation
This experience differs significantly from the Primo VE original UI. In the original UI, users could select "See all [number] suggested resources" to open a popup containing all matching recommendations. The recommendations were displayed together and organized by type, allowing users to quickly review all available options and select the most relevant resource.Improvement 1
Restore the "See all [number] suggested resources" functionality in Primo NDE.
This enhancement would allow users to:
- View the total number of available recommendations.
- See all recommendation types represented.
- Review all recommendations in a single display.
- Access resources more quickly and efficiently without repeatedly advancing through a carousel.Improvement 2
Revise the logic used to select recommendations for the initial three-item display.
Currently, when multiple recommendations exist across multiple recommendation types, the initial display is limited to recommendations from only the first two types, typically displaying:
- Two recommendations from the first type
- One recommendation from the second type
Additional recommendation types are excluded from the initial display.
In Primo NDE, this limitation is even more problematic because users must navigate through all recommendations from the first two types before they can discover that additional types exist.
Instead, when multiple recommendation types are available, the initial three-item display should present one recommendation from each of the top three recommendation types. This approach would improve visibility, expose users to a broader range of recommendation options, and better reflect the full set of available recommendations.Benefit
These changes would improve discoverability, reduce unnecessary navigation, make recommendation types more visible, and provide a more efficient user experience while preserving the existing Resource Recommender functionality.In Primo NDE, the Resource Recommender initially displays a maximum of three recommendations. When additional recommendations are available, users must navigate through them using a horizontal carousel, advancing one entry at a time by clicking a small arrow control.
This design creates several usability issues:
- The arrow is the only indication that additional recommendations exist.
- Users cannot easily determine how many recommendations are available.
- Users cannot see how many recommendation types are represented.
- Users cannot view a complete list of all recommendations.
- Accessing later recommendations requires repeated one-by-one, click-by-click, navigation
This experience differs significantly from…29 votes -
Add limiter for methodology.
It would be helpful to be able to limit search results by methodology (i.e. qualitative, quantitative, longitudinal, etc.) using the "Tweak my results" facets. I realize that students can sometimes use the subject limiters or phrase searches. However, it would save time if there were a dedicated limiter for this.
Our APA collections include limiters based on methodology and other unique facets.
3 votes -
About the Topic - collapse and expand
In the same way that the Resource Recommender section in Primo NDE can now be expanded and collapsed, we would like the About the Topic feature to offer the same functionality.
Ideally, we would want the About the Topic to be collapsed by default, with users having the option to expand it when needed.
The feature contains valuable contextual information and should remain readily accessible to users. However, when displayed with the Resource Recommender section, it occupies a significant amount of space at the top of the results page, pushing the search results further down and affecting the user experience.
2 votes -
Collection page sorting option that places digitized titles first
Primo does not currently offer a collection page sorting option that places digitized titles first. The available options are relevance, title, date, and author.
Displaying readily accessible materials first would improve the user experience and make the search results page more visually appealing.1 vote -
Showcase discovery collections on Primo landing page
We would like to use the Primo landing page showcase to highlight our discovery collections. However, "Display Showcase in Landing page" only allows us to select a Primo saved search, which produces a poor user experience: the collection thumbnails display poorly, and selecting one of the collections brings the user to the Full Details record for the collection, instead of to the collection's landing page.
Instead, we would like the "Display Showcase in Landing page" configuration to allow us to select all or selected discovery collections. When a user on the Primo landing page selects one of the collection thumbnails, they should go to the collection landing page instead of Full Details.
We would like to use the Primo landing page showcase to highlight our discovery collections. However, "Display Showcase in Landing page" only allows us to select a Primo saved search, which produces a poor user experience: the collection thumbnails display poorly, and selecting one of the collections brings the user to the Full Details record for the collection, instead of to the collection's landing page.
Instead, we would like the "Display Showcase in Landing page" configuration to allow us to select all or selected discovery collections. When a user on the Primo landing page selects one of the collection thumbnails,…
2 votes -
Change License Terms of Use labels separately in CSS file
This original idea was closed but it there was no yes or no on the idea.
Currently, to create bolded labels for License Terms of Use, you have to go into the Alma configuration, created new license term labels with the a bold tag. That is a lot of extra work because then you have to go to the license terms tab and move the current terms to the new field with the bold labels. That is a lot of extra steps to get a bolded label so that the display in PrimoVE looks better and the text isn't running together. It would be a lot easier if we could update the CSS file in VE to change the labels to bold or strong.Original Idea:
Enhance license term labels experience in Primo VE
Change English translation for a license term label
There is no possibility to change the English translation for a license term label once it is created even though other languages are configurable.Enclose license term label in a separate HTML tag in Primo VE so it can be styled with CSS
Right now in Primo VE, the license term label although it comes from distinct fields in Alma, is outputted together with the license term text in one HTML tag. We need to have the license term label in a separate HTML tag so it can be styled by CSS.This original idea was closed but it there was no yes or no on the idea.
Currently, to create bolded labels for License Terms of Use, you have to go into the Alma configuration, created new license term labels with the a bold tag. That is a lot of extra work because then you have to go to the license terms tab and move the current terms to the new field with the bold labels. That is a lot of extra steps to get a bolded label so that the display in PrimoVE looks better and the text isn't running…31 votes -
Online Services Order: Preference ebook links with unlimited / three user licenses
I want to add an option to reorder in the Online Services Order in the configuration menu so that ebooks with unlimited or three user licenses display first in the links for a record
https://csu-sdsu.primo.exlibrisgroup.com/permalink/01CALS_SDL/smpn3s/alma991023227756702917
Users tend to click the first link and then we get turnaways.
4 votes -
Make the Resource Recommender initial expand/collapse display configurable
In NDE, the Resource Recommenders (Recommendations) area can be collapsed/expanded. By default, the display is expanded, and the user can collapse it. We would like the option to display the area collapsed by default, allowing the user to expand it only if they want to see the recommendations. The justification is that the Resource Recommenders area takes up a good deal of space and many users would prefer to get directly to searching. A collapsed default display would present a more streamlined search experience. Institutions can opt to "expand by default" or not the different areas in Full Record Services, and we would like to see this configuration option for the Resource Recommenders (Recommendations) area, as well.
In NDE, the Resource Recommenders (Recommendations) area can be collapsed/expanded. By default, the display is expanded, and the user can collapse it. We would like the option to display the area collapsed by default, allowing the user to expand it only if they want to see the recommendations. The justification is that the Resource Recommenders area takes up a good deal of space and many users would prefer to get directly to searching. A collapsed default display would present a more streamlined search experience. Institutions can opt to "expand by default" or not the different areas in Full Record Services,…
2 votes -
Allow configuration of the default expanded/collapsed state of facets in Primo NDE
In Primo NDE, we would like administrators to be able to configure the default expanded or collapsed state of individual facets in the All Filters panel.
Currently, the location_code facet is automatically expanded whenever the All Filters panel is opened.
There is no supported configuration option to control the default state of individual facets.
We suggest adding a configuration option that allows administrators to define, for each facet, whether it should be:
expanded by default
collapsed by defaultIdeally, this could be configured at view level together with the other facet settings.
6 votes -
create a book showcase without logging into Primo
It would be helpful if the book showcase could use a search/set from Alma, a collection ID, or a search URL from Primo, rather than a Primo saved search. We are not able to log into Alma with the same accounts we use in Primo.
4 votes -
Rank records within FRBR group by relevancy to search terms (not just highlight one preferred record)
Description:
This is a follow-up to a previously "completed" idea: "Relevancy sorting in FRBR version list display should use terms searched" (209 votes). That idea was addressed only for Preferred Record mode, by highlighting a single matching record at the top of the version list. We don't think this fully solves the underlying problem, in either display mode.
The problem:
A FRBR group can contain several records that are all relevant to the user's original search terms. For example, multiple translations by the same translator, or several relevant editions.
In Generic mode, opening the group shows an unranked list of all versions. Relevant matches can be buried many pages deep, with no connection to the original search.
In Preferred Record mode, the fix implemented only surfaces one matching record. This can make the problem less visible: a user sees one confidently displayed match and has no indication that 2-3 more equally (or slightly less) relevant versions exist inside the group. It looks solved, but the ranking problem is just hidden rather than fixed.
Grouping records according to FRBR principles in general is good and something we want to keep recommending to our institutions. However, if it negatively affects users’ attempts to reach a known item or semi-known items by placing these unintuitive roadblocks in their way, it is not good enough. In many cases, the user would be better off if the search had never been FRBR’ized.
The proposed solution:
Rank/sort the records within the FRBR group itself by relevancy to the original search terms, in both Generic and Preferred Record display modes. That way, the user will immediately spot the relevant results after opening the FRBR group but will still enjoy the benefits of a less cluttered initial results list.
Example:
Searching "Iliad Richmond Lattimore" returns a FRBR group for Homer's Iliad. Opening the group should surface Richmond Lattimore's translations at or near the top based on its relevance to the search the user made, not require paging through many unrelated editions/translations to find them.
We hope that you will vote for this suggestion! Feel free to add other examples in the comments below.
-The BIBSYS-consortia
Description:
This is a follow-up to a previously "completed" idea: "Relevancy sorting in FRBR version list display should use terms searched" (209 votes). That idea was addressed only for Preferred Record mode, by highlighting a single matching record at the top of the version list. We don't think this fully solves the underlying problem, in either display mode.
The problem:
A FRBR group can contain several records that are all relevant to the user's original search terms. For example, multiple translations by the same translator, or several relevant editions.
In Generic mode, opening the group shows an unranked list of…
191 votes -
Add the option to create a Primo AI Research Assistant search box
Add the option to create a Primo AI Research Assistant search box. Our library would like to create a Primo AI Research Assistant search box on our homepage. We were told this is not possible due to authentication issues and the lack of deep linking.
1 vote -
DOI autofill on the Book Chapter request Resource Sharing form
We would like a DOI autofill feature for Book Chapter requests on the stand-alone Resource Sharing form on Primo NDE.
This already exists on the Article request RS form.3 votes -
Display the resource types filter bar in Primo NDE advanced search results
In the pre-NDE UI of Primo VE, the resource types filter bar was displayed inside the basic search bar at the top of the page, just under the search term input field. It functioned primarily as a pre-search filter. As such, it made logical sense that one wouldn't see the filter bar after conducting an advanced search.
But in NDE, the filter bar appears just above the search results. It only shows up once the results have loaded, so it's only possible to use it as a post-search filter. Despite this difference of use in NDE, the resource types filter bar only displays above search results when a basic search is conducted. It's absent when an advanced search has been conducted. This is confusing our users because while they expect a different search form for advanced search, they don't expect the results display to lack a familiar feature.
As I understand it, the resource types filter bar did at one time display in NDE, but it was removed because it was causing problems. I don't know the nature of those problems, but if they could be resolved and the filter bar returned to the advanced search results display, it would improve the user experience greatly.
In the pre-NDE UI of Primo VE, the resource types filter bar was displayed inside the basic search bar at the top of the page, just under the search term input field. It functioned primarily as a pre-search filter. As such, it made logical sense that one wouldn't see the filter bar after conducting an advanced search.
But in NDE, the filter bar appears just above the search results. It only shows up once the results have loaded, so it's only possible to use it as a post-search filter. Despite this difference of use in NDE, the resource types filter…
27 votes -
Hold and Booking Request Form Needs More Customization
The Hold and Booking Request Form should have more customization options or branching logic to help libraries that have multiple branches.
For example, we have a main library and three branch libraries that are all on the same Primo discovery (we also have a law library that is on their own Primo). Our main library branch got book lockers last year for our users so they can easily pick up their holdings. However, user services noticed that some patrons were struggling to access higher or lower lockers. They asked if we could have a check box on the holdings request form to indicate that they want a more accessible locker. However, we ended up finding a couple of issues with this request.
1.) Due to the way the form is built, it is all or nothing. Our Fine Arts Library does not have lockers, so the check box appears when users select their library for book pickup, even though they don't have lockers. We worry that this will cause some confusion for both the users and the branch libraries (see image below). Ideally, the form should be able to change based on the chosen location.
2.) The verbage from the check box appears along with additional comments made by the requester. When we receive the request, everything is jumbled into the request notes field, making it messy, and quite frankly, a little ugly. 😆 (see image below)
If even one of these changes could be made, that would be amazing!
The Hold and Booking Request Form should have more customization options or branching logic to help libraries that have multiple branches.
For example, we have a main library and three branch libraries that are all on the same Primo discovery (we also have a law library that is on their own Primo). Our main library branch got book lockers last year for our users so they can easily pick up their holdings. However, user services noticed that some patrons were struggling to access higher or lower lockers. They asked if we could have a check box on the holdings request…
6 votes
- Don't see your idea?