706 results found

1. Smart login messages - Do not show login message in the ViewIt for Open Access material

   If a user is not logged in they get the Login message on the ViewIt and GetIt tab, whether they need to login to access that resource or not.

   For example, Open Access material.

   We have had many instances of users complaining that they have to login to access OA material. In fact they do not need to login to access this material. The Primo login message is confusing and misleading the user to think that they do need to login.
   See for example the following Open Access material in our Primo instance.
   https://primo-direct-apac.hosted.exlibrisgroup.com/primo-explore/fulldisplay?docid=RMIT_ALMA_DC11160517080001341&context=L&vid=RMITU&lang=en_US

   In this example the resource is available Open Access and anyone can access it without logging in.
   But Primo continues to display the Login message in the View Online section of the full record.

   To resolve this confusion can the login messages be made situation sensitive?
   If a record has an Open Access indicator can the Login message on the ViewIt section of the full record be hidden.

   If a user is not logged in they get the Login message on the ViewIt and GetIt tab, whether they need to login to access that resource or not.

   For example, Open Access material.

   We have had many instances of users complaining that they have to login to access OA material. In fact they do not need to login to access this material. The Primo login message is confusing and misleading the user to think that they do need to login.
   See for example the following Open Access material in our Primo instance.
   https://primo-direct-apac.hosted.exlibrisgroup.com/primo-explore/fulldisplay?docid=RMIT_ALMA_DC11160517080001341&context=L&vid=RMITU&lang=en_US

   In this example the resource is… more

   34 votes

   Vote 0 votes 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. Searching an item corresponding to a specific record is not possible if not logged in to the IZ that owns this item

   If you are logged in an IZ A and you are searching a specific item belonging to a specific record, you will find it only if this IZ A owns this item. If you are logged in IZ B that does not own any item of this title, the holdings are merged into one or several records (deduped) and you cannot distinguish which item belongs to which record.
   Example:
   IZ A has 6 records of one title; each record has one item.
   In the IZ A, searching this title, you will find 6 records, each one with its item
   IZ B has no item of this title (no holdings).
   In the IZ B, searching this title, you will find 1 record with the 6 holdings merged.
   What we would like to achieve is that the search returns the same display of results, with all holdings visible in all IZs, regardless of which IZ owns the item.

   If you are logged in an IZ A and you are searching a specific item belonging to a specific record, you will find it only if this IZ A owns this item. If you are logged in IZ B that does not own any item of this title, the holdings are merged into one or several records (deduped) and you cannot distinguish which item belongs to which record.
   Example:
   IZ A has 6 records of one title; each record has one item.
   In the IZ A, searching this title, you will find 6 records, each one with its item
   IZ… more

   • 

   34 votes

   Vote 0 votes 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  ·  Primo VE  ·  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. Give Us Feedback: control on which page the icon is displayed

   We would like to control on which page the new "Give Us Feedback" tool icon (May 2022 release) is displayed.
   We are using this tool only for reporting broken links. We need the icon only on the Full View of the search results, but currently, it must be displayed on all pages.
   Actually, most of the feedbacks from our users have been sent by accidentally clicking the icon on the Brief View of the search results, Primo VE home page, etc.
   So, it would be helpful if we could control on which page the icon is displayed.
   Please support this idea.

   We would like to control on which page the new "Give Us Feedback" tool icon (May 2022 release) is displayed.
   We are using this tool only for reporting broken links. We need the icon only on the Full View of the search results, but currently, it must be displayed on all pages.
   Actually, most of the feedbacks from our users have been sent by accidentally clicking the icon on the Brief View of the search results, Primo VE home page, etc.
   So, it would be helpful if we could control on which page the icon is displayed.
   Please support this… more

   34 votes

   Vote 0 votes 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  ·  Primo VE  ·  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. Allow manual control of thumbnails in Primo records

   Primo uses Syndetics to supply thumbnails of book covers for records within Primo. However, when Syndetics provides an incorrect image based on their data, it requires a ticket and often several weeks to correct it. In contrast, some records have no thumbnail at all and use a default gray book icon. Libraries should have the option to use this default icon when Syndetics is providing an incorrect image, or to upload and use local images in cases of records that have no images in Syndetics (for example, with archival and special collection books that are old enough that they have no ISBNs or commonly known covers available).

   Primo uses Syndetics to supply thumbnails of book covers for records within Primo. However, when Syndetics provides an incorrect image based on their data, it requires a ticket and often several weeks to correct it. In contrast, some records have no thumbnail at all and use a default gray book icon. Libraries should have the option to use this default icon when Syndetics is providing an incorrect image, or to upload and use local images in cases of records that have no images in Syndetics (for example, with archival and special collection books that are old enough that they have… more

   34 votes

   Vote 0 votes 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  ·  Primo VE  ·  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. Display import profile name also for for failed import jobs

   Currently, the scheduled job "Import Data to Primo VE" gives us the name of the import profile/external data source that was harvested, but only if the job ran successfully. If not, only the name of the job will be given, but not which profile it ran on. This is true both in Alma and for the corresponding e-mail notifications. We would be glad if this could be changed so that the profile name is always displayed, as the current behaviour is making troubleshooting issues with the import profiles quite cumbersome, especially if several are affected at once.

   34 votes

   Vote 0 votes 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  ·  Primo VE  ·  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 VE be able to get information from AVA and INT holding fields

   Currently, Primo VE's normalization rules can only use information from bibliographic records, so it is not possible to obtain and process information from holdings. The classic version of Primo can get this information from the AVA and INT holdings fields but Primo VE can not perform this task.

   33 votes

   Vote 0 votes 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  ·  Primo VE  ·  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. Allow fields available in the CTO to be used in General Electronic Services (GES)

   Fields found in the CTO should be available to use in url templates and service availability rules within General Electronic Services (GES).

   We use some GES's to link out to our resource sharing system that uses OpenUrl parameters in the url template. We've discovered that many books only have editors and don't include that information in the general author attributes within the CTO. Instead, the editor gets added to rft.sau in the CTO and it is the only field in the record that contains editor information. If you add this field to the url template in the GES and you get an error (error message = "The URL Template you entered contains invalid parameters: rft.sau").

   I submitted a support case through Alma, which got transferred to the Primo team, and was closed with a comment about Alma not being designed to do this and to submit an idea exchange.

   Here are some examples where any author related information is only available in the rft.sau field.

   https://suny-ups.primo.exlibrisgroup.com/discovery/fulldisplay?docid=alma991060177899404801&context=L&vid=01SUNY_UPS:TEST&lang=en&search_scope=IZNZCI&adaptor=Local%20Search%20Engine&tab=IZNZCIslot&query=any,contains,health&facet=rtype,include,books&offset=0&displayCTO=true

   https://suny-ups.primo.exlibrisgroup.com/discovery/fulldisplay?docid=alma991061866007504801&context=L&vid=01SUNY_UPS:TEST&lang=en&search_scope=IZNZCI&adaptor=Local%20Search%20Engine&tab=IZNZCIslot&query=any,contains,health&facet=rtype,include,books&offset=0&displayCTO=true

   https://suny-ups.primo.exlibrisgroup.com/discovery/fulldisplay?docid=alma991061724439004801&context=L&vid=01SUNY_UPS:TEST&lang=en&search_scope=IZNZCI&adaptor=Local%20Search%20Engine&tab=IZNZCIslot&query=any,contains,health&facet=rtype,include,books&offset=0&displayCTO=true

   Finally, because these are not local records, there is no workaround to add the editor field to other fields and get used within other existing and working openurl fields.

   Fields found in the CTO should be available to use in url templates and service availability rules within General Electronic Services (GES).

   We use some GES's to link out to our resource sharing system that uses OpenUrl parameters in the url template. We've discovered that many books only have editors and don't include that information in the general author attributes within the CTO. Instead, the editor gets added to rft.sau in the CTO and it is the only field in the record that contains editor information. If you add this field to the url template in the GES and you… more

   33 votes

   Vote 0 votes 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  ·  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

8. Discovery collections per library and unfiltered view

   In our consortium we have some mixed IZs, which means different libraries, mostly in the same geographical area, that are part of the same IZ.
   Users accessing via the local library interface are interested mainly in that specific library Discovery collection. But at the same time they might be also interested to know if a resource is available in the near by libraries, as it could be easily accessible physically or to request it.
   We have activated the relevant configurations and Discovery collections displays correctly for the specific libraries only. But when the view is filtered and "Local copy unavailable" displayed, the user might overlook that there is the item near by and that it can be requested.
   We would like to have a configuration that keeps the get it section display as it is per default (with the "view _ to _ libraries _ for _ collection _ discovery" parameter turned to false), but at the same time displays the collections only for the relevant libraries (as we have when "view _ to _ libraries _ for _ collection _ discovery" parameter is set to true).

   In our consortium we have some mixed IZs, which means different libraries, mostly in the same geographical area, that are part of the same IZ.
   Users accessing via the local library interface are interested mainly in that specific library Discovery collection. But at the same time they might be also interested to know if a resource is available in the near by libraries, as it could be easily accessible physically or to request it.
   We have activated the relevant configurations and Discovery collections displays correctly for the specific libraries only. But when the view is filtered and "Local copy unavailable"… more

   33 votes

   Vote 0 votes 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  ·  Primo VE  ·  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. Instant Insight into FRBR Versions in the Search Results

   We have received feedback from our users that they would like to get an initial overview of a FRBR group’s contents directly in the results list. When encountering the representative record of a FRBR group, they want to immediately see how many online resources and physical copies are included, along with other useful details such as publication dates or resource types.
   A straightforward implementation could be to enhance the link to the versions list so that it not only shows the total number of versions but also indicates how many available online (consortia: only online resources that are available in the respective IZ / no viewit_other) and print resources are included. More advanced solutions could go further by displaying additional information about each version.
   We believe this enhancement would improve both the generic and the preferred FRBR display, as it would reduce unnecessary clicks and help users assess relevant resources more efficiently and even prevent users from overlooking relevant resources.

   We have received feedback from our users that they would like to get an initial overview of a FRBR group’s contents directly in the results list. When encountering the representative record of a FRBR group, they want to immediately see how many online resources and physical copies are included, along with other useful details such as publication dates or resource types.
   A straightforward implementation could be to enhance the link to the versions list so that it not only shows the total number of versions but also indicates how many available online (consortia: only online resources that are available in… more

   33 votes

   Vote 0 votes 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

10. Provide option to disable course information being indexed for search in Primo VE

    We have chosen not to display course information in our Primo VE but found that local records appear higher in our search results when they are attached to a Leganto reading list. Support tell me that 'it is part of OTB and by default it will be indexed’.

    In the ‘Search Section Mapping’ part of the 'Mapping to the Display, Facets, and Search Sections in the Primo VE Record' Knowledge Center page, it says: 'Course information – Primo VE indexs the course name, code, and instructor for records associated with course reading lists.'

    We don't understand why course and instructor names should be considered in a search over bibliographic data when we are not displaying any course data in the results. It affects user confidence in the search results and is another thing our subject librarians need to explain.

    We strongly believe it should be optional, as I believe it was with Primo BO (where 'Course reserve information is not published to Primo unless Alma is configured to publish course enrichment information'), hence it is another Feature Alignment issue with Primo VE in comparison to Primo BO.

    We have chosen not to display course information in our Primo VE but found that local records appear higher in our search results when they are attached to a Leganto reading list. Support tell me that 'it is part of OTB and by default it will be indexed’.

    In the ‘Search Section Mapping’ part of the 'Mapping to the Display, Facets, and Search Sections in the Primo VE Record' Knowledge Center page, it says: 'Course information – Primo VE indexs the course name, code, and instructor for records associated with course reading lists.'

    We don't understand why course and instructor… more

    32 votes

    Vote 0 votes 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  ·  Primo VE  ·  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. Support for Numeric Subfields (e.g., $0, $1) in MARC to PNX Mapping in Primo VE

    Currently, numeric subfields such as $0 and $1 are excluded from Primo VE’s standard MARC to PNX mapping. This prevents institutions from displaying and passing on crucial metadata, such as authority IDs, in/from the Primo VE UI.

    Please map at least subfields $0 and $1 to PNX
    This would greatly benefit libraries that rely on authority control and linked data, ensuring that identifiers like VIAF and GND IDs can be used for enhanced metadata display and linking within Primo VE as provided for by the MARC standard .

    Use Case Example:
    A record with multiple subject headings (650 fields) includes corresponding $0 subfields containing GND IDs.
    Currently, these IDs are not accessible, meaning they cannot be displayed or linked to external authority services.
    With the proposed enhancement, institutions could properly map these identifiers to custom fields and improve metadata accuracy and display options.

    By mapping numeric subfields to PNX, Ex Libris would significantly enhance Primo VE’s ability to support linked data and authority control, aligning it better with modern metadata standards.

    Currently, numeric subfields such as $0 and $1 are excluded from Primo VE’s standard MARC to PNX mapping. This prevents institutions from displaying and passing on crucial metadata, such as authority IDs, in/from the Primo VE UI.

    Please map at least subfields $0 and $1 to PNX
    This would greatly benefit libraries that rely on authority control and linked data, ensuring that identifiers like VIAF and GND IDs can be used for enhanced metadata display and linking within Primo VE as provided for by the MARC standard .

    Use Case Example:
    A record with multiple subject headings (650 fields) includes… more

    32 votes

    Vote 0 votes 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  ·  Primo VE  ·  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 a multilingual keyboard to the User Interface

    Our patrons want to search in multiple languages in Primo, e.g. Chinese, Russian, Arabic, etc. When they come to the library they are often limited, because of the local keyboards. A virtual multilingual keyboard would be an ideal solution to support their needs.
    Portal Judaica (cf. screenshot attached) provides an example of how to implement this in the user interface. The website https://www.lexilogos.com/ supports a variety of languages to give you an idea of which languages should be supported by the virtual keyboard. Thank you for voting.

    [internal reference PRM-252]

    •  

    31 votes

    Vote 0 votes 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

13. Change behaviour of collection discovery for frbrized titles

    At the moment collection discovery in Primo VE shows for frbrized titles only one entry, even if there are two entries added two the collection (print and electronic version e.g.). If the user clicks on the entry, he gets a record and not a list of versions as he does when clicking on an entry in the brief results list. This is confusing, because the user might think, the one record he found (print or electronic) is the only one available. The user is likely to overlook the rather small versions line.

    I see to possible solutions:

    1. (preferred) If two records are added to a discovery collection, they are not frbrized in the context of collection discovery.

    2. Collection discovery behaves the same way the brief results list does. I.e. clicking on a frbrized entry, a list of versions opens.

    Thank you in advance for considering this.
    Andreas Bigger

    At the moment collection discovery in Primo VE shows for frbrized titles only one entry, even if there are two entries added two the collection (print and electronic version e.g.). If the user clicks on the entry, he gets a record and not a list of versions as he does when clicking on an entry in the brief results list. This is confusing, because the user might think, the one record he found (print or electronic) is the only one available. The user is likely to overlook the rather small versions line.

    I see to possible solutions:

    1. (preferred) If two… more

    31 votes

    Vote 0 votes 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  ·  Primo VE  ·  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. Pipe setting improvement: allow to exclude specific OAI sets from a pipe

    We would like to have the possibility to exclude one or more specific sets when we harvest the data with OAI-PMH protocol in Primo.
    This option would have 2 results:
    - to reduce the number of imported records
    - we wouldn't have to set specific normalization rules in order to exclude the records we don't want to show in Primo

    31 votes

    Vote 0 votes 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  ·  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

15. Ability to create URL redirects for deleted collections

    Alma offers institutions the ability to create collections to facilitate discovery and access to groups of related resources. In addition to being displayed on the Collections Lobby page, collections can be made accessible via direct links on websites, research guides, or course syllabi. However, when a collection is deleted, any links or bookmarks to that collection are broken. To avoid this, customers should have the ability to configure redirects for collection page URLs that can be used to route visitors to another page.

    Related documentation:

    https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/050Inventory/050Managing_Collections

    https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/130Configuring_Advanced_Search_Interfaces_for_Primo_VE/Configuring_Collection_Discovery_for_Primo_VE

    31 votes

    Vote 0 votes 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  ·  Primo VE  ·  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. Include subfield k from 245 in title index (important for manuscripts/archives)

    Subfield k of the 245 title field should always be indexed. Currently, it is only indexed when subfield a is absent. OCLC makes clear that both subfields may be used together: "Use subfield ǂk also to indicate "form" even if a formal title is given in subfields ǂa, ǂb, and ǂc." From: https://www.oclc.org/bibformats/en/2xx/245.html

    This subfield is important for manuscripts and archives. Examples from OCLC:

    245 ǂa Four years at Yale : ǂk diaries, ǂf 1903 September 16-1907 October 5

    245 ǂa The charity ball : ǂb a comedy in four acts : ǂk typescript, ǂf 1889 / ǂc by David Belasco and Henry C. DeMille

    Subfield k of the 245 title field should always be indexed. Currently, it is only indexed when subfield a is absent. OCLC makes clear that both subfields may be used together: "Use subfield ǂk also to indicate "form" even if a formal title is given in subfields ǂa, ǂb, and ǂc." From: https://www.oclc.org/bibformats/en/2xx/245.html

    This subfield is important for manuscripts and archives. Examples from OCLC:

    245 ǂa Four years at Yale : ǂk diaries, ǂf 1903 September 16-1907 October 5

    245 ǂa The charity ball : ǂb a comedy in four acts : ǂk typescript, ǂf 1889 / ǂc by David… more

    31 votes

    Vote 0 votes 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  ·  Primo VE  ·  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. Primo Analytics - language usage

    On Primo Analytics, make it possible to see which language users are selecting e.g. Welsh and English.

    30 votes

    Vote 0 votes 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  ·  Primo VE  ·  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. Preference of links from link resolver over link in record in brief results for merged records

    When one or more of the records in a merged group is coming from a collection using the link resolver, and other records are coming from collections using the link in the record, the link in record type of link is always displayed in the brief result list. It should be possible to choose to always display a link resolver type of link instead.

    30 votes

    Vote 0 votes 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  ·  Primo VE  ·  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. Sorting of collection page witch contains only subcollections

    When in Alma a collection page contains only subcollections, in Primo, default sort will be "Relevance", with option to change to title.
    If the collection page contains only Titles default sort will be "Sort titles by" value set in the Discovery tab of the Collection Resource Editor, with options to change to any sort that is available in the search results page results.

    It would be very desirable if the sorting setting in Alma would take effect for a collection page containing only subcollections, so that you could sort the subcollections not only by relevance but also alphabetically.

    29 votes

    Vote 0 votes 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  ·  Primo VE  ·  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. Dedup and FRBR cluster monitoring

    Since BIRT reports in back office are being deprecated and they are not available in VE, those who implement Dedup or FRBR will have no way to monitor the clusters that goes beyond what's currently in analytics (just a report of cluster sizes). Size of clusters is important, but when "impossibly large" clusters form (we recently noticed many, up to 89 members!), we need to be able to see the records forming the cluster in order to diagnose problems. The BIRT tool is way too slow and unwieldly for this purpose but provides useful information: contents of the fields that add up to a score for each cluster. The Dedup Tools in Primo and Primo VE are helpful when a "bad cluster" is brought to our attention by a customer, but we should not have to wait for this to happen if the cluster size, or random sampling, can bring problems to light. Regular Primo customers need better tools that will provide a more usable output in modern spreadsheet or document formats, and VE customers need similar tools to sample and monitor clusters. If this can be part of Analytics that would be fine, otherwise a separate set of tools is needed.

    Since BIRT reports in back office are being deprecated and they are not available in VE, those who implement Dedup or FRBR will have no way to monitor the clusters that goes beyond what's currently in analytics (just a report of cluster sizes). Size of clusters is important, but when "impossibly large" clusters form (we recently noticed many, up to 89 members!), we need to be able to see the records forming the cluster in order to diagnose problems. The BIRT tool is way too slow and unwieldly for this purpose but provides useful information: contents of the fields that… more

    29 votes

    Vote 0 votes 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