558 results found

1. Find e-Journal by Title search

   Add the following radio buttons to the Find e-Journal by Title search:

   *Contains
   *Starts with
   *Exact

   193 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 Interface  ·  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. Combining searches from search history into a new search

   My colleagues misses the functionality from our previous discovery system to combine searches in the search history list into a new search in an easy way, e.g. S1 AND S3

   97 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…)
   24 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
   AdminYael (yael.shahar@clarivate.com, Ex Libris) responded

   This is currently not planned to be developed. We might evaluate it again in the future.

   Currently we are removing the "Under review" status.

   
   

3. Add an Abstract resource type for the Primo Central Index

   Primo Central Index contains many records for abstracts of conference papers that have been published in journal issues/supplements.

   These records are given the Article resource type in Primo. This confuses users, who when they find these items expect a full-length article instead of a short abstract.

   It also creates problems with link resolvers, which attempt to generate article-level links and fail (publishers usually do not provide these abstracts as individual articles).

   To fix this, Primo Central should be given a new resource type for abstracts.

   The sources for these records are usually large indexes such as Scopus or Web of Science, which already mark these items as abstracts. This would make it easy to reclassify items as the Abstract resource type.

   Primo Central Index contains many records for abstracts of conference papers that have been published in journal issues/supplements.

   These records are given the Article resource type in Primo. This confuses users, who when they find these items expect a full-length article instead of a short abstract.

   It also creates problems with link resolvers, which attempt to generate article-level links and fail (publishers usually do not provide these abstracts as individual articles).

   To fix this, Primo Central should be given a new resource type for abstracts.

   The sources for these records are usually large indexes such as Scopus or Web of… more

   171 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…)
   3 comments  ·  Other  ·  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. Generate a report of the MMSID's harvested by Primo Back Office

   We would like to be able to generate a report of the MMSID's harvested by Primo Back Office.

   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…)
   2 comments  ·  Administrative Tools  ·  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. “My Favorites” pin should indicate number of records in favorites

   In the Primo New UI, there is the “my favorites” pin icon at the top right of the screen (screenshot below of the pin). We ran some usability surveys and found that users would like an indication, via the icon, that something is there. Like the number if pinned items and/or a different color indicating that something is there.

   •  

   45 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 Interface  ·  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. Primo Central Index ( PCI ) - more granularity in excluding content from activated resources - e.g. exclude from index by resource type

   Right now in Primo Central Index the customer can either activate or not a resource. But sometimes more granularity would be appreciated. Namely adding a filter by resource type allowing inclusion or exclusion in the index would be very useful. Please note: it's not a matter of adding a resource type in PCI. It's a matter of excluding records with a specific resource type from activated resources.

   For example, some resources/data sources contains not only articles, but also journals and other resource types we actually catalogue. Since right now dedup does not work between local records and PCI, this ends up leading to a lot of duplicated entries in the search results (1 for the journal in the catalogue + 1 for the same journal in PCI).
   Allowing us to exclude Journals from PCI, thus having only articles, would greatly reduce noise and bias in the search results.

   Right now in Primo Central Index the customer can either activate or not a resource. But sometimes more granularity would be appreciated. Namely adding a filter by resource type allowing inclusion or exclusion in the index would be very useful. Please note: it's not a matter of adding a resource type in PCI. It's a matter of excluding records with a specific resource type from activated resources.

   For example, some resources/data sources contains not only articles, but also journals and other resource types we actually catalogue. Since right now dedup does not work between local records and PCI, this ends… more

   103 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  ·  Other  ·  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. text

   Allow users to text themselves call number/location for an item

   192 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…)
   25 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

8. Embargoed resources displaying in Primo

   Currently records from within an embargo period are discover-able to end-users via Primo.
   The user then thinks we have access to the records and selects it only to be presented with No full text available.
   Embargoed records are outside of our coverage range and should not display in our discovery interface.

   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…)
   0 comments  ·  Other  ·  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. Put useful data into the RSS feeds created by Primo

   Technically RSS feeds created by Primo are working. But from a content perspective the feed is a mess.

   Let's start with the feed header:

   Primo delivers <rss version="2.0">
   The standard specification are at http://www.rssboard.org/rss-specification . It was published in August 2002. The RSS 2.0 specification is copyrighted by Harvard University and is frozen. Please use RFC 4287 also known as Atom.
   https://tools.ietf.org/html/rfc4287
   It is simply the better option for may reasons.
   http://www.intertwingly.net/wiki/pie/Rss20AndAtom10Compared

   The description of the feed is <title>Records from Primo</title> .
   As a user I would like to see my search terms in the feed title - like in the brief result screen in the web interface. At minimum it should be the name of the service where this feed is coming from. The name of software used to create the feed is useless to a reader.

   The link to the source is pointing back to the Primo main page with the classic user interface. But that's confusing for institutions using the new user interface!

   Let's have a look to a feed item:

   A cruical element of RSS feeds is the
   <pubDate>Thu, 09 Nov 2017 16:25:22 GMT</pubDate>
   The specification says: "Its value is a date, indicating when the item was published." In a Primo feed this is always the same date; I assume it is the time stamp when the feed was created. Please change this immediately. RSS management software cannot handle it because the pubDate is used for chronological sorting and to find out what's new. What's needed is the publication date of the publication or second best the date and time when the record was added to the Primo index.

   The delivered link in the link field is "the URL of the item". It's pointing back to the full view of the record in Primo. That makes sense. But if available I would like to get the OpenURL here because I want to connect my users to the article or the service page and not to the Primo record again. It's fulfillment at this point!

   Why the same link is also in guid is a mystery to me. RSS standard says: "guid stands for globally unique identifier. It's a string that uniquely identifies the item. When present, an aggregator may choose to use this string to determine if an item is new." What about the PNX ID?

   Last not least the description:
   <description>Plasmodium Falciparum -- Analysis ; Proteases -- Analysis ; Proteins -- Analysis ; Phosphates -- Analysis ; Malaria -- Analysis;</description>
   Often it incorporates only "N/A" or sometimes subject headings. But the description should include the same information as the brief view in the web interface of Primo like bibliographic information, identifier, subject headings, language, etc. This is what the user will see in his feed reader of choice or what a feed aggregation system can use to give meaningful context for the title of this item. Of course it's tricky because a Primo search delivers very different types of content with very different metadata. Books have authors; journals have not. Articles are published in a journal and pictures have a resolution and digital objects have a file format.

   Today there are no customization options for the feed content. If the settings of the brief view are applied to the feed too, it would improve the item description massively and solve the description problem. This need is solved for the export to a reference management software. The RSS feed for a query is not so much different from that.

   Technically RSS feeds created by Primo are working. But from a content perspective the feed is a mess.

   Let's start with the feed header:

   Primo delivers <rss version="2.0">
   The standard specification are at http://www.rssboard.org/rss-specification . It was published in August 2002. The RSS 2.0 specification is copyrighted by Harvard University and is frozen. Please use RFC 4287 also known as Atom.
   https://tools.ietf.org/html/rfc4287
   It is simply the better option for may reasons.
   http://www.intertwingly.net/wiki/pie/Rss20AndAtom10Compared

   The description of the feed is <title>Records from Primo</title> .
   As a user I would like to see my search terms in the feed title - like in… more

   55 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  ·  Integration with other systems  ·  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. Allow Primo to comply with the "force password change on next login" setting in Alma for internal users

    Alma has the internal user setting "Force password change on next login". Primo does not comply with this setting, so there is no way to force patrons to change their passwords in Primo. This is problematic, because our internal user accounts have a very insecure default password initially set for them. Please consider implementing this feature for Primo

    173 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…)
    8 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. Allow for consistant customizations in the new UI

    The open discovery of the new UI allows customers to customize the new UI, extend its functionalities, and connect Primo with external services.
    This framework can offer an important added value to institutions; it can enable them to respond to specific needs of their user community.
    We want to implement extensions for functionalities like:
    • Offer a button “report a problem” that allows a user to report a broken link or another problem with a specific source he found. The form sends this message to our helpdesk, together with useful debug info like : is the user on or off campus, browser version used, search query, pnx-id,.. and his e-mail address when he is signed in. Our e-resources staff finds this functionality extremely useful: more linking issues are reported now and they can be handled in a more efficient way.
    • Offer a button “Pay fines” that allows a user to pay fines online. The button is only displayed when the user has fines.

    These are extensions that we currently implemented in our old UI.
    But creating extensions that make use of session data (like user email, vid, …) are time consuming and risk full:
    • Time consuming because documentation is limited not to say non-existing, this requires reading the code. It has a high maintenance cost since after every release, extensions can break and it is difficult to find out why because of the lack of clear release notes.
    • It is risk full because we don’t know whether we will be able to fix the functionality in the two weeks between release on staging and production. It is also risk full because we don’t know if the extensions will still work after the transition to Angular 2.

    Our request is :
    Please provide us with session data in every component so we can quickly create components.
    One way to make the extensions manageable and future proof, is to use a data model (see primo-explore-dom). If the data is framework agnostic it will become more portable and working with data is easier and almost timeless.
    This way everybody can develop within the reach of their skillset and more institutions would be able to take profit of the open discovery framework.
    But we are open to any solution to overcome the issues mentioned.

    The open discovery of the new UI allows customers to customize the new UI, extend its functionalities, and connect Primo with external services.
    This framework can offer an important added value to institutions; it can enable them to respond to specific needs of their user community.
    We want to implement extensions for functionalities like:
    • Offer a button “report a problem” that allows a user to report a broken link or another problem with a specific source he found. The form sends this message to our helpdesk, together with useful debug info like : is the user on or off… more

    205 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  ·  Integration with other systems  ·  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. Facet "language" not working

    The facet "language" in Primo is not working correctly. When I choose another language than german or english, e.g. italian, I got german or english titles whose authors have an italian background. This is not making any sense. Especially our chinese students expect titles in chinese when they use this facet. And as it is a global problem I think ExLibris has to find a solution. I checked with several Primo catalogues from other libraries:

    e.g.
    http://www.getty.edu/research/library/
    https://fu-berlin.hosted.exlibrisgroup.com/primo_library/libweb/action/search.do?vid=FUB
    https://library.wlu.ca/
    http://primo.abdn.ac.uk:1701/primo_library/libweb/action/search.do (they obviously deactivated the language facet already while it is not working)
    http://primo.tug-libraries.on.ca/primo_library/libweb/action/search.do?vid=WATERLOO&reset_config=true
    http://primo.bib.uni-mannheim.de/primo_library/libweb/action/search.do?vid=MAN_UB
    http://onesearch.slq.qld.gov.au/primo_library/libweb/action/search.do?vid=SLQ&fromLogin=true
    http://primo.ub.uni-due.de/primo_library/libweb/action/search.do
    http://catalogue.solent.ac.uk/primo_library/libweb/action/search.do?vid=SSUVU01
    http://whel-primo.hosted.exlibrisgroup.com/primo_library/libweb/action/search.do?vid=44WHELF_ABW_VU1&reset_config=true
    http://bvb-new-primo.hosted.exlibrisgroup.com/primo_library/libweb/action/search.do?vid=49BVB_UBG01_VU1
    https://hollis.harvard.edu/primo_library/libweb/action/search.do?vid=HVD
    a.s.o.

    In all libraries I checked there is the same problem that the language facet is not working correctly. So I hope that other libraries will vote for this enhancement request as it is a fatal error in the facets functionality. And I think we should not accept this failure.

    The facet "language" in Primo is not working correctly. When I choose another language than german or english, e.g. italian, I got german or english titles whose authors have an italian background. This is not making any sense. Especially our chinese students expect titles in chinese when they use this facet. And as it is a global problem I think ExLibris has to find a solution. I checked with several Primo catalogues from other libraries:

    e.g.
    http://www.getty.edu/research/library/
    https://fu-berlin.hosted.exlibrisgroup.com/primo_library/libweb/action/search.do?vid=FUB
    https://library.wlu.ca/
    http://primo.abdn.ac.uk:1701/primo_library/libweb/action/search.do (they obviously deactivated the language facet already while it is not working)
    http://primo.tug-libraries.on.ca/primo_library/libweb/action/search.do?vid=WATERLOO&reset_config=true
    http://primo.bib.uni-mannheim.de/primo_library/libweb/action/search.do?vid=MAN_UB
    http://onesearch.slq.qld.gov.au/primo_library/libweb/action/search.do?vid=SLQ&fromLogin=true
    http://primo.ub.uni-due.de/primo_library/libweb/action/search.do
    http://catalogue.solent.ac.uk/primo_library/libweb/action/search.do?vid=SSUVU01
    http://whel-primo.hosted.exlibrisgroup.com/primo_library/libweb/action/search.do?vid=44WHELF_ABW_VU1&reset_config=true
    http://bvb-new-primo.hosted.exlibrisgroup.com/primo_library/libweb/action/search.do?vid=49BVB_UBG01_VU1
    https://hollis.harvard.edu/primo_library/libweb/action/search.do?vid=HVD… more

    • 

    101 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…)
    6 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. proximity search operator for fulltext search in Primo Central

    A strong argument for a discovery index compared to a bibliographic database is the incorporation of full text in the index. I have not found an actual number or a percentage how many Primo Central collections are full text searchable. But we all know: it is significant. Since this year all Primo Central searches will always expand to full text.
    https://knowledge.exlibrisgroup.com/Primo/Knowledge_Articles/Primo_Central_Full-Text_Searching

    The most powerful feature for full text search is proximity.
    https://en.wikipedia.org/wiki/Proximity_search_(text)

    Aleph was able to support proximity for small hitsets
    https://knowledge.exlibrisgroup.com/Aleph/Knowledge_Articles/Proximity_doesn't_work_for_larger_results.

    ... and Summon has a proximity feature
    https://knowledge.exlibrisgroup.com/Summon/Product_Documentation/Searching_in_The_Summon_Service/Search_Features/Summon%3A_Boolean%2C_Phrase%2C_Wildcard_and_Proximity_Searching#proximity

    Proximity search is currently not supported nor planned in the Primo/Primo Central roadmap. Although as part of the search engine algorithm the proximity is being calculated and records in which the query words are closer (we call the distance slop) will be rank higher.

    It would be great to add proximity operator to the Primo search syntax and to support proximity search in Primo Central.

    A strong argument for a discovery index compared to a bibliographic database is the incorporation of full text in the index. I have not found an actual number or a percentage how many Primo Central collections are full text searchable. But we all know: it is significant. Since this year all Primo Central searches will always expand to full text.
    https://knowledge.exlibrisgroup.com/Primo/Knowledge_Articles/Primo_Central_Full-Text_Searching

    The most powerful feature for full text search is proximity.
    https://en.wikipedia.org/wiki/Proximity_search_(text)

    Aleph was able to support proximity for small hitsets
    https://knowledge.exlibrisgroup.com/Aleph/Knowledge_Articles/Proximity_doesn't_work_for_larger_results.

    ... and Summon has a proximity feature
    https://knowledge.exlibrisgroup.com/Summon/Product_Documentation/Searching_in_The_Summon_Service/Search_Features/Summon%3A_Boolean%2C_Phrase%2C_Wildcard_and_Proximity_Searching#proximity

    Proximity search is currently not supported nor planned in… more

    175 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…)
    9 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

14. Allow to delete records in Primo BE ( included dedup records )

    Right now the only way to delete a record in Primo is to refer to a KB Article [1] explaining how to write an xml OAI-PMH record with status 'deleted' and let the xml file to be ingested by a pipe. The procedure is cumbersome and error prone (e.g. issues with compression of the file on non linux machines etc.) and it does not always work properly. For example, dedup records are not properly deleted by this procedure.

    It would be good to provide a feature in the Primo BE allowing to look for specific PNX and to delete it. This should work with both plain records and dedup records.

    [1] https://knowledge.exlibrisgroup.com/Primo/Knowledge_Articles/How_to_delete_a_specific_record_from_Primo%3F

    Right now the only way to delete a record in Primo is to refer to a KB Article [1] explaining how to write an xml OAI-PMH record with status 'deleted' and let the xml file to be ingested by a pipe. The procedure is cumbersome and error prone (e.g. issues with compression of the file on non linux machines etc.) and it does not always work properly. For example, dedup records are not properly deleted by this procedure.

    It would be good to provide a feature in the Primo BE allowing to look for specific PNX and to delete it.… more

    44 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…)
    3 comments  ·  Administrative Tools  ·  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. List of Loans - Indicate if item is Requested

    It should be possible to indicate in the patron's List of Loans in the Library Account whether an item is requested, otherwise, it is not clear if the due date is sooner than on other loans because it is a Reserved item or because it was Requested by another reader.

    54 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 Interface  ·  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

16. Add Show Actions icons to My Favorites

    Option to add all the Show Actions icons to display on My Favorites, or at least some icons such as the print and e-mail icons, instead of just the ...

    Please see screen capture attached.

    •  

    96 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…)
    5 comments  ·  User Interface  ·  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. Ignore call number prefix (subfield k) when indexing for Call Number Browse

    Primo's browse search "By Library of Congress Call Numbers" includes the call number prefix (holdings record field 852 $k) when generating the browse list. At UGA, we use that prefix for oversize volumes (Folio, Ff), and for a variety of branch locations, special statuses and shelving areas (Juv, Ref, Vet Med, etc.).

    As a result, any holdings with a prefix do not show up alongside holdings in the same call number range, essentially hiding many titles from patrons interested in browsing the shelf list. (This would be an issue for staff as well, but shelf list browsing works correctly in Alma.)

    Please reconfigure Primo's browse search to ignore (but, ideally, still display) the call number prefix when generating this index.

    Primo's browse search "By Library of Congress Call Numbers" includes the call number prefix (holdings record field 852 $k) when generating the browse list. At UGA, we use that prefix for oversize volumes (Folio, Ff), and for a variety of branch locations, special statuses and shelving areas (Juv, Ref, Vet Med, etc.).

    As a result, any holdings with a prefix do not show up alongside holdings in the same call number range, essentially hiding many titles from patrons interested in browsing the shelf list. (This would be an issue for staff as well, but shelf list browsing works correctly in… more

    145 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

18. Add option to view complete authority records in Primo

    Primo does not show the complete authority record. In Aleph the end user could see the authority record through the link from Primo to the OPAC. As ALMA has no such option the end user has no way of seeing the complete authority record with all the RDA fields. If the complete authority record is displayed, not only some of the fields, the end user can find important information about the author with one click.

    47 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 Interface  ·  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. Add a search results permalink to the New UI results page

    When we do searches in Primo for patrons, we often want to be able to send them to a list of results, rather than a specific item.

    There is a jquery customization the classic UI created by Western Washington University at https://www.orbiscascade.org/blog/9/?bid=121

    However, that customization does not work on the new UI, and requires users to be able to create a SQL database to store redirects, and to store files on a local server.

    Ideally, search results permalink functionality could be built into Primo's New UI.

    The attached screenshot shows the WWU search results permalink in action.

    •  

    38 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

20. [Primo] - frbr - improve algorythm - consider all keys and not only the first matching key

    In Primo FRBR documentation is explained that (I added ** signs):
    "
    In the FRBRization process, the keys are compared. If a record has a matching key with another record, it is added to the same FRBR group. Once a match is found, the system does not continue searching for matches since a record can belong to one FRBR group only.
    "
    In our experience this may lead to false positives. When comparing keys between frbr candidates, the system should consider instead the whole set of matching keys, not just the first matching one. And for example do not group records having more non matching keys than matching keys.

    In attachment an example where the books share the title and only 1 of the authors. This is not uncommon in case of exhibitions catalogues where the artist works together with the curators. FRBR considers the 2 different books as 2 different versions.

    Here are matching keys of the record proposed as example:
    Record 1 (2006):
    <frbr><t>1</t><k1>$$Kubzroyoux jean christophe$$AA</k1><k1>$$Kubzdean tacita$$AA</k1><k1>$$Kubzwarner marina$$AA</k1><k1>$$Kubzgreer germaine$$AA</k1><k3>$$Kubztacita dean$$AT</k3></frbr>
    Record2 (2004)
    <frbr><t>1</t><k1>$$Kubzde cecco emanuela$$AA</k1><k1>$$Kubzdean tacita$$AA</k1><k3>$$Kubztacita dean$$AT</k3></frbr>

    In Primo FRBR documentation is explained that (I added ** signs):
    "
    In the FRBRization process, the keys are compared. If a record has a matching key with another record, it is added to the same FRBR group. Once a match is found, the system does not continue searching for matches since a record can belong to one FRBR group only.
    "
    In our experience this may lead to false positives. When comparing keys between frbr candidates, the system should consider instead the whole set of matching keys, not just the first matching one. And for example do not group… more

    •  

    116 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…)
    3 comments  ·  Other  ·  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