70 results found

1. 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

2. 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

3. 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

4. enable a search of parentheses () in middle of word

   Currently, Primo is unable to retrieve titles containing parentheses in the middle of a word (eg א(י)מניות : אימהות מביאות אמנות לעולם). It seems elementary that Primo should be able to retrieve any record based on its exact title.

   See the following links displaying the issue:

   the search with parentheses:
   https://haifa-primo.hosted.exlibrisgroup.com/primo-explore/search?query=any,contains,%D7%90(%D7%99)%D7%9E%D7%A0%D7%99%D7%95%D7%AA%20:%20%D7%90%D7%99%D7%9E%D7%94%D7%95%D7%AA%20%D7%9E%D7%91%D7%99%D7%90%D7%95%D7%AA%20%D7%90%D7%9E%D7%A0%D7%95%D7%AA%20%D7%9C%D7%A2%D7%95%D7%9C%D7%9D&tab=default_tab&search_scope=books_and_more&vid=HAU&lang=iw_IL&offset=0

   without parentheses:
   https://haifa-primo.hosted.exlibrisgroup.com/primo-explore/search?query=any,contains,%D7%90%D7%99%D7%9E%D7%A0%D7%99%D7%95%D7%AA%20:%20%D7%90%D7%99%D7%9E%D7%94%D7%95%D7%AA%20%D7%9E%D7%91%D7%99%D7%90%D7%95%D7%AA%20%D7%90%D7%9E%D7%A0%D7%95%D7%AA%20%D7%9C%D7%A2%D7%95%D7%9C%D7%9D&tab=default_tab&search_scope=books_and_more&vid=HAU&lang=iw_IL&offset=0

   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

5. 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

6. 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

7. 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

8. 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

9. 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

10. 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.

    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