72 results found

1. Allow GES to access coverage information to calculate available services for articles

   Our library uses GES service availability rules to disable our ILL services request link for articles “when resource is owned by the institution and available.” However, GES interprets a journal as available if we have coverage for any length of time, even if coverage is not available for the article in question. This leads to a number of CDI articles showing “No services available,” as we do not have an available link for access (not having coverage for that particular date/issue), and the ILL link is disabled because the system thinks we have coverage. It would be helpful to have GES logic take journal coverage into account so that ILL services can be made available for patrons when the library does not have access to the desired article.

   Our library uses GES service availability rules to disable our ILL services request link for articles “when resource is owned by the institution and available.” However, GES interprets a journal as available if we have coverage for any length of time, even if coverage is not available for the article in question. This leads to a number of CDI articles showing “No services available,” as we do not have an available link for access (not having coverage for that particular date/issue), and the ILL link is disabled because the system thinks we have coverage. It would be helpful to have… more

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  User Functionality  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Enable separate search profiles, scopes, and slots for Advanced Search

   We request the ability to display search profiles, scopes, and slots separately and selectively in Simple and Advanced Search. Today, any search profile added to a search configuration automatically appears in both Simple and Advanced Search together; it is not possible to configure them separately. We would like the option to display the profiles, scopes, and slots in Simple Search only, or Advanced Search only, or both. We request this at all levels of search profile/scope/slot configuration. We have developed scopes based on special collections. Given the nature of the content, it would be beneficial to only have scopes available in Advanced Search and not in our main Simple Search bar. We also have some functionality we developed that only works in a 'library only' search profile. However, we do not want to add scoped searching into our main Simple Search bar but only Advanced. If this feature were added, with the granularity to allow scopes ONLY in Advanced or Simple Search, it would allow greater functionality and options to libraries. This would allow users to perform a more complex search and with scopes applied (e.g. title and author and date and scope in one go). This enhancement would provide additional parity between the two search options and allow enhanced functionality and options for libraries.

   Submitted to NERS 2024 and CERV 2025 (PENH-I-28352)

   We request the ability to display search profiles, scopes, and slots separately and selectively in Simple and Advanced Search. Today, any search profile added to a search configuration automatically appears in both Simple and Advanced Search together; it is not possible to configure them separately. We would like the option to display the profiles, scopes, and slots in Simple Search only, or Advanced Search only, or both. We request this at all levels of search profile/scope/slot configuration. We have developed scopes based on special collections. Given the nature of the content, it would be beneficial to only have scopes available… more

   4 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  User Functionality  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Cross-Institution favorites

   In a consortial environment, we would like to see favorites shared across institutions.

   Currently, favorites from institution A are only visible when logged into institution A but not when logged into institution B and vice versa.

   Our desired behaviour would be that all favorites from all institutions are shown, regardless of which institution a user is logged in to.

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  User Functionality  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Research Assistant: make filter button more noticeable

   It appears to us that several of our users of the Research Assistant don't notice the filter option left to the search box. Our request is to make the filter button more noticeable, e.g. by making it blue like the arrow to the left of the search box and by and by providing a mouse-over text.

   4 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  User Functionality  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Sort Favorites by Call Number

   Allow sorting of "My Favorites" by Call Number. Currently, you can only sort "My Favorites" by Date Added, Author, and Title.

   6 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  User Functionality  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. List of Stop Words in Catalan

   Alma/Primo clients in Catalan cannot use the Full Text Indexing utility in Primo VE with all its functionality because there is no Stop Word List implemented in Catalan.

   Because of this and the 10,000 terms limit per indexed file, the included PDFs are not fully indexed.

   https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/Go_VE/Step_3%3A_Configuration/040Go_VE%3A_Converting_Primo_Data_Configuration_to_Primo_VE/060Go_VE%3A_Full_Text_Indexing_in_Primo_VE

   We are 17 university libraries and a national library (Biblioteca de Catalunya) that form part of the University Union Catalogue of Catalonia (CCUC); 2 university libraries from València (Universitat Jaume I and Universitat d’Alacant); and 62 collaborative institutions with special libraries.

   We contribute to the visibility of more than 12 million documents and resources.

   We need Full Text Indexing utility in Primo VE to work with a list of Catalan stop words.

   List:

   ---

   on aqui alla alli dins fora sobre sota davant darrere rere amb sense contra en entre a de des per
   quan aleshores abans despres durant mentre ja encara
   com aixi tambe tampoc si no i o ni pero perque nomes potser
   que aixo allo quelcom aquest aquesta aquests aquestes aquell aquella aquells aquelles algun alguna alguns algunes altre altra altres mateix mateixa mateixos mateixes
   qui quin quina quins quines qual quals ell ella ells elles se hi ho ne li lo la les los jo nosaltres vosaltres me em nos vos
   quant tan tant tanta tants tantes poc poca pocs poques molt molta molts moltes tot tota tots totes
   un una uns unes el la els les al als del dels seu seva seus seves teu teva teus teves meu meva meus meves
   es eren fou foren sigui siguin seria serien estar esta estan estava estaven haver ha han havia havien tenir tenen tenia tenien sembla semblen
   --/--

   Alma/Primo clients in Catalan cannot use the Full Text Indexing utility in Primo VE with all its functionality because there is no Stop Word List implemented in Catalan.

   Because of this and the 10,000 terms limit per indexed file, the included PDFs are not fully indexed.

   https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/Go_VE/Step_3%3A_Configuration/040Go_VE%3A_Converting_Primo_Data_Configuration_to_Primo_VE/060Go_VE%3A_Full_Text_Indexing_in_Primo_VE

   We are 17 university libraries and a national library (Biblioteca de Catalunya) that form part of the University Union Catalogue of Catalonia (CCUC); 2 university libraries from València (Universitat Jaume I and Universitat d’Alacant); and 62 collaborative institutions with special libraries.

   We contribute to the visibility of more than 12 million documents and… more

   56 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  User Functionality  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Customize brief display of fees in user account - Primo VE

   On the overview page in the fees tile it displays 4 lines of information. If a user need more information they have to click on the entry to do so. One of the pieces of information in the drill down is if the fee was transferred to an outside entity such as bursars. Given there is a Pay Fees button even if transferred fees are present on this tab it would be nice to be able to have more lines display or at the least be able to order the display so what we feel is most important shows in brief display. That way with this easy to see designation and a relabel of the button (which we have done) users can know if fees can be paid using the button or if they should go somewhere else.

   On the overview page in the fees tile it displays 4 lines of information. If a user need more information they have to click on the entry to do so. One of the pieces of information in the drill down is if the fee was transferred to an outside entity such as bursars. Given there is a Pay Fees button even if transferred fees are present on this tab it would be nice to be able to have more lines display or at the least be able to order the display so what we feel is most important shows in… more

   •  

   •  

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  User Functionality  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Change CDI handling of Language data for Primo

   CDI Language data in handled in ways which have undesirable impact on patrons in Primo, such as:
   • A default language is applied to all records in a CDI feed for use in Primo in the Language field display, search, and facet. This may be done when the CDI provider feed has no record-specific Language information available automatically and the provider has not otherwise advised that all the records are in a specific known language and confirmed that this Language can be applied to the records in CDI
   • Records may be allowed to merge into a CDI logical record even when the Language data differs across participant records. All of the participant record Language values are then included in the Language facet bar ‘outlier’ languages stripped out, and then one Language value may be selected to display in the record according to library full text activations, even if it contradicts the Language facet value

   It is understood that the CDI is a massive index and that strategies such as collection level normalisation rules are necessary in order to manage this scale of data.
   However, it is feared that the experience of individual users is inappropriately de-prioritised and lost in these decisions focused on “acceptable” percentages of impact, which may seem tiny relative to the size of the index, but may be significant to actual people using our discovery layer.
   The practical reality is that such handling of Language information at a broad scale in CDI causes a negative impact for people using Primo, as the information is clearly incorrect and features cannot be used as expected.
   It may be argued that patrons are unlikely to encounter such issues on a regular basis, but this also ignores common knowledge of human nature that even one or two experiences of being presented with clearly false information is enough to build distrust in all future experiences.

   For example, the Language facet cannot be used when a patron is specifically trying to target results in a certain language, when they know in advance or learn from initial results that their search term may return records for multiple languages with different meanings.
   ISSUE
   “Persona” has different meanings in Spanish and English and the patron wants the English variation.
   STRATEGY
   With a search by “personas school principals” the patrons deliberately selects to include only the Language facet value of English and exclude the Language facet value of Spanish.
   BUT
   Ex Libris has applied Language facet value of English broadly as a default in the CDI provider feed and/or has artificially selected a Language from participant records to display in the record regardless of the Language in the facet.
   RESULT
   The patron sees in their results many records stating English when they are clearly in Spanish in both the metadata and full text.
   Examples (screenshots attached):
   • cdicrossrefprimary105944reopvol30num1201925194
   • cdiunpaywallprimary1014295idonlinev15i583330
   • cdijstorprimary_40654076
   OUTCOME
   This patron may then submit a complaint to the library or simply decide that their library provides a poor service and stops using our discovery layer in favour of other options.

   When opening a case to report such patron complaints with examples of unexpected incorrect information in Primo, it is advised that this behaviour is expected and that current handling was chosen over other options to mitigate the impact of insufficient provider CDI metadata in Primo.
   This could be by including a Language information in the records of ‘No linguistic content’ or ‘Undetermined’ to ensure a facet count matched to a result count, not allowing records to merge when there are Language differences, and not presenting Language facet values which do not match Language display values.

   Ex Libris considers it a “resolution” to such cases for defect reports to document this behaviour, shifting responsibility to their library customers to explain to complaining patrons.

   This approach focusing on quantity over quality does not centre the individual user as a person, and disregards the harm to the professional reputation of libraries, degrading the trust our patrons place in our services and which we are responsible to provide for our institutions, to support teaching, learning, and research.

   Now that such behaviours have been documented over time as “expected”, this issue moves from hope it is resolved as a defect, to a product enhancement request that Ex Libris change the current design decisions causing this problem.

   This submission requests that Ex Libris reconsider and change these practices with the individual user in mind, committing to align Language data across display, search, and facets and to consistently present only accurate Language information in the Primo discovery layer.

   CDI Language data in handled in ways which have undesirable impact on patrons in Primo, such as:
   • A default language is applied to all records in a CDI feed for use in Primo in the Language field display, search, and facet. This may be done when the CDI provider feed has no record-specific Language information available automatically and the provider has not otherwise advised that all the records are in a specific known language and confirmed that this Language can be applied to the records in CDI
   • Records may be allowed to merge into a CDI logical record… more

   •  

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  User Functionality  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Improve Primo linking to limit dead/inaccurate links

   To prevent user confusion, frustration, and access delays, we would like Ex Libris' Primo to mirror a feature that LibKey calls "Entitlement Confirmation," which would help prevent delivering dead links to end users, especially when Metadata in the CDI is lacking or incorrect.

   Delays between publishing and availability, especially with third-party databases (like EBSCOHost), happen often and can vary in length due to the nature of aggregation. The proposed change would confirm if content is available before indicating to end users that it is. This saves user and staff time and effort, streamlining the process and managing expectations while providing exemplary service.

   To prevent user confusion, frustration, and access delays, we would like Ex Libris' Primo to mirror a feature that LibKey calls "Entitlement Confirmation," which would help prevent delivering dead links to end users, especially when Metadata in the CDI is lacking or incorrect.

   Delays between publishing and availability, especially with third-party databases (like EBSCOHost), happen often and can vary in length due to the nature of aggregation. The proposed change would confirm if content is available before indicating to end users that it is. This saves user and staff time and effort, streamlining the process and managing expectations while providing… more

   22 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  User Functionality  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. "Remember all filters" should be selected by default

    We want "Remember all filters" to be selected by default. It confuses our users who expect that their filters will remain while they change their search, only to find that they had to click "Remember all filters" first. We'd rather them have to de-select "Remember all filters" if there's a reason they don't want to retain them in their searching.

    Relates to https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/34854556-make-facets-sticky-by-default-for-the-session, where the "default" part was never instituted.

    65 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  User Functionality  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Do not interpret words in phrase searches as Boolean operators

    At ETH Library, we use UDK classification. The UDK notations are always in capital letters, and some contain words as “AND” or German “UND”. “AND” and “UND” are defined as Boolean operators in our Primo VE. This leads to the following problem: when a user clicks on an UDK notation that contains such a word (e.g. on “PFLANZEN + BÄUME + BLUMEN (MOTIVE IN KUNST, LITERATUR UND FILM)” in this record: https://eth.swisscovery.slsp.ch/permalink/41SLSP_ETH/lshl64/alma990015558430205503), a search for “subject equals exact phrase” in the advanced search is triggered. Although a phrase search is performed, the word UND is interpreted as a Boolean operator, and therefore the search returns 0 results.
    We think that the search in Primo VE should be improved so that no word in a phrase search is interpreted as Boolean operator. Since it is not possible for a phrase to contain a Boolean operator, the current search behavior is a bug and should be fixed.

    At ETH Library, we use UDK classification. The UDK notations are always in capital letters, and some contain words as “AND” or German “UND”. “AND” and “UND” are defined as Boolean operators in our Primo VE. This leads to the following problem: when a user clicks on an UDK notation that contains such a word (e.g. on “PFLANZEN + BÄUME + BLUMEN (MOTIVE IN KUNST, LITERATUR UND FILM)” in this record: https://eth.swisscovery.slsp.ch/permalink/41SLSP_ETH/lshl64/alma990015558430205503), a search for “subject equals exact phrase” in the advanced search is triggered. Although a phrase search is performed, the word UND is interpreted as a Boolean… more

    42 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  User Functionality  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Add Search within "Journals by Category" results

    Journals by Category is less useful since each category could have hundreds of results. For example, searching by the category "Psychology" produces 623 journals. EDS' journal search allows you to search within that category--so in this case, you'd be able to search a specific topic among only the 623 psychology journals identified. We have professors who require students to find ten articles in Economics/Accounting journals that are published in the USA. A search within the category Economics journals for a topic, and perhaps even the location facet, would help these students out!

    4 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  User Functionality  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Highlight OCR text within image in Viewer, not just in full text field

    Digital representations seen in the Alma-D Viewer, accessed through Primo, are often PDFs with OCRed text. These items have a "Full Text" field with this text displayed with the item's metadata in the side pane, and using a browser's "CTR+F" function will highlight results for a searched word, but this functionality would be helpful if it also extended to highlighting the word in the image as well. In dense newspapers, for example, the user may find the needed word in the block of full text, but he would then need to examine the image carefully to track down the instance of its original appearance.

    Digital representations seen in the Alma-D Viewer, accessed through Primo, are often PDFs with OCRed text. These items have a "Full Text" field with this text displayed with the item's metadata in the side pane, and using a browser's "CTR+F" function will highlight results for a searched word, but this functionality would be helpful if it also extended to highlighting the word in the image as well. In dense newspapers, for example, the user may find the needed word in the block of full text, but he would then need to examine the image carefully to track down the instance… more

    2 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  User Functionality  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Add Reserves "Reading List" to facets navigation panel.

    This would allow a clean up project for a multiple location library system. It would bring reserves more closely aligned with standard cataloging by basically using the Course as a high level catalog record (think bib level), Reading List as middle tier (holdings level shelving location). By combining the Course to one entry with the reading lists showing shelving, it would take our records from five courses and five reading lists per class offering to one course with five reading list. This would help clean up database space and form more consistency across locations.

    • 

    10 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  User Functionality  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. PrimoVE should allow disabling of Aggregator Content Data

    Improving OpenAIRE Links in PrimoVE: A Customization Proposal

    Many of the OpenAIRE links in our system are currently unreliable. To address this issue, we propose the following enhancements:

    1) Aggregator Content Data Class: We recommend introducing an aggregator class specifically
    for Aggregator Content Data in the code. This class would allow us to apply custom styling
    and control the display of OpenAIRE links.

    2) CSS Customization: If we had a dedicated <span class="OpenAIRE">, we could easily add CSS
    rules to hide OpenAIRE links. Currently, we lack this flexibility, and our users are
    inundated with potentially unreliable links. Other Contenre Data could also be hidden wtih <span class="Datacite"> and <span class="Crossref">

    3) Customization for Libraries: By implementing individual CSS classes for each Aggregator
    Content, libraries could tailor their custom1.css file to selectively hide specific
    classes they deem unnecessary in PrimoVE.

    4) Simplicity of CSS Tags: Adding a CSS tag is a straightforward process compared to modifying
    the complex Display Configuration Full Record Services. It provides a more accessible way to
    manage link visibility.

    For more details, refer to the knowledge article on Primo: Fixes to Aggregator Content Data.
    https://knowledge.exlibrisgroup.com/Content/Knowledge_Articles/Primo/Knowledge_Articles/Primo%3A_Fixes_to_Aggregator_Content_Data

    Additionally, you can explore and support this idea on the Ex Libris Community Ideas forum: OpenAIRE Customization. https://ideas.exlibrisgroup.com/forums/574345-content/suggestions/33452563-https-www-openaire-eu

    Let’s enhance the user experience by fine-tuning our link display in PrimoVE!

    Improving OpenAIRE Links in PrimoVE: A Customization Proposal

    Many of the OpenAIRE links in our system are currently unreliable. To address this issue, we propose the following enhancements:

    1) Aggregator Content Data Class: We recommend introducing an aggregator class specifically
    for Aggregator Content Data in the code. This class would allow us to apply custom styling
    and control the display of OpenAIRE links.

    2) CSS Customization: If we had a dedicated <span class="OpenAIRE">, we could easily add CSS
    rules to hide OpenAIRE links. Currently, we lack this flexibility, and our users are
    inundated with potentially unreliable links. Other Contenre Data… more

    4 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  User Functionality  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    AdminTamar Ganor (Admin, Ex Libris) responded

    Hello,

    We have made some adjustments for the OpenAIRE records on the content side, you can read more in this Knowledge Article:

    https://knowledge.exlibrisgroup.com/Content/Knowledge_Articles/Alma/Knowledge_Articles/OpenAire_in_CDI

    The other options you have mentioned may be addressed in the Primo Product side - I have moved this idea to the Primo Idea Exchange for the Product team to review.

    Kind regards,

    Tamar Ganor

    Content Product Manager

16. Primo Header is cut off at a certain Window Size

    When one reduces the size of the browser window, the button for the advanced search moves into the “hidden” menu. Right before it disappears, it is cut off and can no longer be read. Furthermore horizontal scrolling is required in order to visually grasp the other menu items such as "Login" and "Menu". As far as we could check, this affects a browser window size from around 600px to 800px.

    This does not depend on local CSS modifications. It is a general UX issue that affects responsive design and furthermore is breaking with the WCAG accessibility guidelines (WCAG 2.1, 1.4.10, https://www.w3.org/WAI/WCAG21/Understanding/resize-text.html).

    When one reduces the size of the browser window, the button for the advanced search moves into the “hidden” menu. Right before it disappears, it is cut off and can no longer be read. Furthermore horizontal scrolling is required in order to visually grasp the other menu items such as "Login" and "Menu". As far as we could check, this affects a browser window size from around 600px to 800px.

    This does not depend on local CSS modifications. It is a general UX issue that affects responsive design and furthermore is breaking with the WCAG accessibility guidelines (WCAG 2.1, 1.4.10, … more

    60 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  User Functionality  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Article level records from Alma should populate resource sharing form correctly

    Article records from CDI will populate the Primo VE resource sharing form correctly, as a document delivery option for when there is no full-text available.
    However, when it comes to article level records from Alma, the Journal title is incorrect (instead, the article title is entered into this field) and other information is missing, like publication year, volume, etc. Overall the article is not recognized in the Context Object as an article, but instead treated as a journal - thus omitting all fields not relevant to a journal record.
    Example:
    
    1 - Go to: https://kbdk-kgl-psb.primo.exlibrisgroup.com/permalink/45KBDK_KGL/1pioq0f/alma99124396529705764. See that the resource type is Article (this is expected) in the brief results and in the full display.
    2 - Check the PNX and see that in the adddata section that:
    format = journal
    genre = article
    atitle = High-protein diet during pulmonary rehabilitation in patients with chronic obstructive pulmonary disease
    jtitle = Danish medical journal [online]
    3 - However, when you check the CTO:
    rft.stitle > High-protein diet during pulmonary rehabilitation in patients with chronic obstructive pulmonary disease
    rft.jtitle > High-protein diet during pulmonary rehabilitation in patients with chronic obstructive pulmonary disease
    rft.genre > journal
    rft.object_type > JOURNAL
    4 - See the following screenshot of the resource sharing form: the Journal Title is incorrect and other information like the publication year, volume is not included.
    https://www.screencast.com/t/rA9G9rcuh

    This has of course been reported as a defect (case # 06707109), but is deemed by ExLibris to be an enhancement request.

    Article records from CDI will populate the Primo VE resource sharing form correctly, as a document delivery option for when there is no full-text available.
    However, when it comes to article level records from Alma, the Journal title is incorrect (instead, the article title is entered into this field) and other information is missing, like publication year, volume, etc. Overall the article is not recognized in the Context Object as an article, but instead treated as a journal - thus omitting all fields not relevant to a journal record.
    Example:
    
    1 - Go to: https://kbdk-kgl-psb.primo.exlibrisgroup.com/permalink/45KBDK_KGL/1pioq0f/alma99124396529705764. See that the resource… more

    50 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  User Functionality  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Landolt-Börnstein collection

    Can you please add the Landolt-Börnstein collection since it isn't available in SFX? Our library has the entire collection through Springer Materials. Thank you

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  User Functionality  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Privacy in patron letters

    Currently, patrons receive detailed item information in patron letters. We would like to make it possible for patrons to turn off letters (such as when they do not want this detailed information living in their email accounts).

    In testing, we found that the current 'Personal Details' configuration in Alma (https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/060Library_Card_Configuration/Configuring_Personal_Details_Settings_for_Primo_VE) does not allow us to limit patron changes to ONLY the notification preferences.

    26 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    4 comments  ·  User Functionality  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Add the creation date to the titles in the Saved Search Letter

    Users can set an alert on the Saved Searches page and will then receive the Saved Search letter by email whenever there are new results for their saved search. However, a new result is not necessarily a new publication. The Saved Search letter could also contain older publications which are new to the inventory of the discovery system. For the users, it would be helpful to already see in the Saved Search letter the creation date of the titles, so that they know which results are real new publications. In Primo VE, however, it is currently not possible to add the creation date to the displayed data for a title in the Saved Search letter. It would be great if this option would be added.

    Users can set an alert on the Saved Searches page and will then receive the Saved Search letter by email whenever there are new results for their saved search. However, a new result is not necessarily a new publication. The Saved Search letter could also contain older publications which are new to the inventory of the discovery system. For the users, it would be helpful to already see in the Saved Search letter the creation date of the titles, so that they know which results are real new publications. In Primo VE, however, it is currently not possible to add… more

    7 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  User Functionality  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating