326 results found

1. Include DOIs in references in APA 7th ed. format for records coded with Dublin Core.

   Exlibris has just updated the APA 7th ed. citation format settings to include the DOI for MARC21-encoded records (idea exchange: Improve APA citation format to include the DOI for an article), but we also want Exlibris performs the same process for Dublin Core-encoded records.

   Users are increasingly turning to PRIMO to obtain the citation reference of a record they are interested in and in many cases their metadata is in DublinCore format, as more and more catalogs integrate repositories that encode information following this format.

   90 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  ·  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

2. Open Access Indicator for Unimarc records

   Open Access Indication in Primo VE is currently supported for Marc21 and Dublin records : https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/030Primo_VE_User_Interface/Open_Access_Indication_in_Primo_VE
   Please support Unimarc record, too !

   134 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  ·  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. NZ/IZ linking in consortia

   Background: MARC 776 is used to establish a link between related records (Also available in another form:). If a link cannot be established, a title search is started instead.

   In a consortial environment, there is an issue with this: Primo VE is only able to establish a link if both the linking and the linked-to title are available locally. This happens because Primo depends on Alma functionality for related records to establish a link and Alma is building them within institution scope only (Network is considered just another institution in this regard). This means that as soon as only the linking title is available in an IZ, a title search will be started.

   To give an example: We have a journal with the main title “Recht” (Law), which links to an electronic version of the same title. In IZ that do not have the electronic version, a title search for Recht/law will be started instead, leading to over 27’000 results – from a link that promised to lead to a different version of the same title. See also pdf below.

   This behaviour makes 776 largely unusable for consortia, where it would be important for that our patrons are able to find resources that are not available locally as well or where we’d at least want a system that can recognize if something is locally available and only displays the link in this case.

   Background: MARC 776 is used to establish a link between related records (Also available in another form:). If a link cannot be established, a title search is started instead.

   In a consortial environment, there is an issue with this: Primo VE is only able to establish a link if both the linking and the linked-to title are available locally. This happens because Primo depends on Alma functionality for related records to establish a link and Alma is building them within institution scope only (Network is considered just another institution in this regard). This means that as soon as only the… more

   • 

   133 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  ·  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 Online Services Order to sort by current access

   We need the ability to move to top of View It a service with current access (this means the coverage statement is open-ended, ie Available from 1998 - current).

   Users get overwhelmed with the long list of services often displayed, and ordering the list according to interface or electronic collection name doesn't address the most important aspect, whether there is current access or not. As an example, on Proquest interface Z, journal title X may provide current access, but journal title Y on the same Proquest interface Z may only have archive access. We only want to put journal title X at the top, not journal title Y.

   Solution: add a configuration to Online Services Order to move to top a service with current access (Until Year/Until Month/Until Day/Until Issue fields are empty).

   We need the ability to move to top of View It a service with current access (this means the coverage statement is open-ended, ie Available from 1998 - current).

   Users get overwhelmed with the long list of services often displayed, and ordering the list according to interface or electronic collection name doesn't address the most important aspect, whether there is current access or not. As an example, on Proquest interface Z, journal title X may provide current access, but journal title Y on the same Proquest interface Z may only have archive access. We only want to put journal title… more

   235 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  ·  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. Primo VE : Alignment of Unimarc normalization rules with Marc21 normalization rules for the creation of the author facet

   The current OTB normalization rules for the creator/contributor facet in Primo VE differ between Marc21 and Unimarc records. Unimarc rules consider more elements than Marc21, leading to inconsistencies and duplicate facets for the same author.
   For example, from personal name fields (fields 70#), Exlibris uses the entry element, the part of name, the qualifier, Roman numerals and dates (a, b, c, d, f) for “Personal name” responsibility statements. In Marc 21, only the entry element is retained (a).

   Key Issues:

   1- Duplicate Facets: Two facets are created for the same author, one based on Unimarc and the other on Marc21.
   2- Search Inconsistencies: The facets do not filter search results uniformly, with Unimarc facets often limiting searches to printed documents and Marc21 facets refining searches for online resources.
   

   Proposed Solution:

   Align the Unimarc and Marc21 normalization rules to simplify the author facet. This pragmatic approach will improve search functionality until authority identifiers are widely adopted.

   Please refer to the attached document for more details and proposed modifications to the Unimarc standardization rules.
   Thank you in advance for any support you can give to this idea.

   Alexandre Faure
   Université de Bordeaux

   The current OTB normalization rules for the creator/contributor facet in Primo VE differ between Marc21 and Unimarc records. Unimarc rules consider more elements than Marc21, leading to inconsistencies and duplicate facets for the same author.
   For example, from personal name fields (fields 70#), Exlibris uses the entry element, the part of name, the qualifier, Roman numerals and dates (a, b, c, d, f) for “Personal name” responsibility statements. In Marc 21, only the entry element is retained (a).

   Key Issues:

   1- Duplicate Facets: Two facets are created for the same author, one based on Unimarc and the other on Marc21.

   … more

   • 

   73 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  ·  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. Disabling automatically generated links for related records if the associated NR is disabled.

   Primo VE is capable to automatically create links to related records via MARC 7xx fields.
   As these links where not working well for us, we were looking to turn them off with a NR, by setting “set pnx."display"."relation" to "N/A"” for 776 specifically.
   Unfortunately, this turned out not to work in all cases. As Ex Libris explained this is because
   - in the related records, they differentiate between child records and parent records
   - for child records, as the specific relation field is included, Display NR takes effect
   - for parent records, as the specific relation field is not included, and the opposite link is added automatically, Display NR cannot have any effect

   This means we can only disable links from child to parent records but not the other way around. What we would like to see is that, if a relation from a child to a parent record is supressed, the automatically added opposite link should also be supressed.

   Primo VE is capable to automatically create links to related records via MARC 7xx fields.
   As these links where not working well for us, we were looking to turn them off with a NR, by setting “set pnx."display"."relation" to "N/A"” for 776 specifically.
   Unfortunately, this turned out not to work in all cases. As Ex Libris explained this is because
   - in the related records, they differentiate between child records and parent records
   - for child records, as the specific relation field is included, Display NR takes effect
   - for parent records, as the specific relation field is not included,… more

   62 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  ·  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. Responsive label "item in place/not in place" for open shelf items

   Our available items in open rack cannot be requested for local pickup but this is confusing for patrons as there is a physical request button (only for a Transit request - the Owning Library is missing as pickup location). Only for items NOT in place and items in STACKS, the Owning Library is an additional Pickup location.

   As the option for local pickup for open shelf items depends on the availability and location (item in place/item not in place), we would like to change this label and add information about requestability and access to items (see image attached). But this status has to be mapped to the Holding Location (or item policy?), to distinguish between open shelf and stacks:

   • items in OPEN SHELF that are NOT available (on loan): requestable for local pickup and transit
   • items in OPEN SHELF that are available: only requestable for transit)
   • items in STACKS that are available/not available: requestable for local pickup and transit

   Is it possible to have a "responsive" status label, but only for items in open shelf?

   Our available items in open rack cannot be requested for local pickup but this is confusing for patrons as there is a physical request button (only for a Transit request - the Owning Library is missing as pickup location). Only for items NOT in place and items in STACKS, the Owning Library is an additional Pickup location.

   As the option for local pickup for open shelf items depends on the availability and location (item in place/item not in place), we would like to change this label and add information about requestability and access to items (see image attached). But this… more

   •  

   40 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  ·  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

8. Display ebook reading format (HTML, EPUB, PDF etc.) in Primo (VE) full display

   When displaying links to Ebook providers in Primo (VE) full display it would be suitable to have a notice of what ebook reading formats accessible for each provider. Instead of having to click further to the each provider to retrieve the information. Even information about online reading and/or download option would be suitable.

   30 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  ·  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. Primo VE facet for collections regardless of inventory type

   I would like to propose an out of the box facet for collections that can include all 3 inventory types.

   We have users that need to be able to filter their search results by ‘collections’ or groupings that contain physical, electronic and digital resources. For example, our Original Materials ‘collection’ is made of physical items, digital items and electronic items that we have catalogued in local electronic collections.

   Currently, there are OOTB facets based on physical inventory (Library and Location) but none that combine all 3 inventory types.

   As a workaround, we have utilised the digital collection facet for this purpose. Although it is primarily used for digital records, it does support any type of record. However, this means that our Collection Discovery pages contain all of our collection items and some physical and electronic items without cover images or thumbnails. It also results in our Original Materials collection including 272,505 items instead of being used to showcase select resources as the functionality intended. We have to manually update these collections regularly as new items are catalogued.

   The creation of this facet type would improve collection discovery for uses by allowing libraries to create collections of resources regardless of inventory type.

   I would like to propose an out of the box facet for collections that can include all 3 inventory types.

   We have users that need to be able to filter their search results by ‘collections’ or groupings that contain physical, electronic and digital resources. For example, our Original Materials ‘collection’ is made of physical items, digital items and electronic items that we have catalogued in local electronic collections.

   Currently, there are OOTB facets based on physical inventory (Library and Location) but none that combine all 3 inventory types.

   As a workaround, we have utilised the digital collection facet for this… more

   25 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  ·  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

10. Search should be more forgiving of spelling errors/incorrect searches

    We would like the search in Primo VE to be more forgiving in terms of spelling mistakes and incorrect searches, akin to other search engines, as this is what our users are mostly familiar with. For example, searching “Das Leid des jungen Werter” instead of “Die Leiden des jungen Werther” will find the searched for title on Google, Amazon as well as a local bookshops online platform, while on Primo VE, the book itself, of which we have several versions in our catalogue, is not found at all and only some related literature is shown. Another example would be “The count of Monte Christo”. Searching for “The count of montecristo” or “The count of monetchristo” will only bring up partially related literature. Again, other platforms will easily find the correct title.

    We would like the search in Primo VE to be more forgiving in terms of spelling mistakes and incorrect searches, akin to other search engines, as this is what our users are mostly familiar with. For example, searching “Das Leid des jungen Werter” instead of “Die Leiden des jungen Werther” will find the searched for title on Google, Amazon as well as a local bookshops online platform, while on Primo VE, the book itself, of which we have several versions in our catalogue, is not found at all and only some related literature is shown. Another example would be “The… more

    29 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  ·  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. Improved Display of Coverage Statements for Taylor and Francis Journals autoholdings collection.

    Taylor and Francis adds multiple coverage rows to reflect the different purchasing methods. For example, one line may represent perpetual access while another indicates current access. This is why some coverage statements appear to overlap.
    We propose to:
    1. Retain the purchase type (e.g., perpetual, current) for each coverage statement within Alma.
    2. Present only non-overlapping coverage statements to users in primo.
    This enhancement is planned as an upgrade to the current functionality, but there is no set release date as of now.
    To help expedite this enhancement, the support team suggested to open an idea exchange to encourage all users to vote for this idea. The votes can help prioritize this enhancement and contribute to improving user experience.

    Taylor and Francis adds multiple coverage rows to reflect the different purchasing methods. For example, one line may represent perpetual access while another indicates current access. This is why some coverage statements appear to overlap.
    We propose to:
    1. Retain the purchase type (e.g., perpetual, current) for each coverage statement within Alma.
    2. Present only non-overlapping coverage statements to users in primo.
    This enhancement is planned as an upgrade to the current functionality, but there is no set release date as of now.
    To help expedite this enhancement, the support team suggested to open an idea exchange to encourage all… more

    53 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  ·  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. Do not show availability for CDI/Alma records with matching GTI ID

    Occasionally, CDI records will show availability for physical items (holdings/digitization offers via Rapido), and the physical records will show online availability. To our understanding, this is due to a matching GTI ID. We were informed in a SF case that it is currently not possible to resolve this. As this leads to confusion for our libraries (mainly digitization requests for an electronic resource) we would be glad if a solution could be found to no longer show these incorrect availabilities (or at least for the digitization requests to show the physical record they were actually placed on).
    Example: https://ubs.swisscovery.slsp.ch/permalink/41SLSP_UBS/giv3ks/cdi_askewsholts_vlebooks_9783540488491

    66 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  ·  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

13. Related titles in Primo VE records display: separate window

    When records have bib-to-bib relationships via 8XX (or 7XX), the list of related titles is displayed in the Details section of the series/host record. Unfortunately, the list is currently sorted alphabetically by the title, which is very user-unfriendly with a large number of linked titles.

    This behavior has already been criticized in this idea. Unfortunately, it is still not possible to sort the related titles logically by sequence or volume.

    The Austrian Library Association (OBV) uses Primo BO and has implemented a user-friendly solution for displaying related titles:
    In the case of multi-volume works and series, the individual volumes are displayed via a link in a separate window. There the volumes can be sorted by publication date, relevance etc.

    Example: Opere di Francesco de Sanctis, https://permalink.obvsg.at/AC01614297

    Austria is working with PLK fields for their solution. During the publishing process from Alma to Primo, the related records are added as PLK fields to the source record. For an example, please see here the source record for Opere.

    In Primo VE we would like to be able to add the relationships to the source data set, as it is the case in Primo BO with the PLK fields.

    When records have bib-to-bib relationships via 8XX (or 7XX), the list of related titles is displayed in the Details section of the series/host record. Unfortunately, the list is currently sorted alphabetically by the title, which is very user-unfriendly with a large number of linked titles.

    This behavior has already been criticized in this idea. Unfortunately, it is still not possible to sort the related titles logically by sequence or volume.

    The Austrian Library Association (OBV) uses Primo BO and has implemented a user-friendly solution for displaying related titles:
    In the case of multi-volume works and series, the individual volumes are… more

    •  

    144 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  ·  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. Integrated Library Mapping and Analytics for Primo VE

    Develop an integrated library mapping module for Primo VE featuring interactive floor plans with clear, step-by-step directions. Seamlessly integrate this module into Primo VE's existing infrastructure, ensuring a user-friendly interface accessible to all patrons.

    Benefits:
    • Enhanced user experience: Streamline the path from digital search to physical item retrieval, reducing frustration and improving overall user satisfaction.
    • Valuable collection analytics: Gain insights into patron behavior, optimize collection placement, and make data-driven decisions about space allocation.
    • Streamlined workflow: Replace third-party solutions, reducing complexity and simplifying library operations.
    • Improved accessibility: Ensure all users can easily navigate the library by providing clear navigation for all users, regardless of mobility.
    Additional Details:
    • Provide an option to upload location maps into Alma, associating them with call number ranges for stacks or shelves.
    • Display the relevant map within Primo VE search results for physical items based on call number, with clear directions to the shelf.

    Conclusion: This integrated library mapping solution will change the way patrons interact with physical collections, bridging digital search and physical retrieval, while gaining deeper insights into libraries' collection usage.

    Develop an integrated library mapping module for Primo VE featuring interactive floor plans with clear, step-by-step directions. Seamlessly integrate this module into Primo VE's existing infrastructure, ensuring a user-friendly interface accessible to all patrons.

    Benefits:
    • Enhanced user experience: Streamline the path from digital search to physical item retrieval, reducing frustration and improving overall user satisfaction.
    • Valuable collection analytics: Gain insights into patron behavior, optimize collection placement, and make data-driven decisions about space allocation.
    • Streamlined workflow: Replace third-party solutions, reducing complexity and simplifying library operations.
    • Improved accessibility: Ensure all users can easily navigate the library by providing… more

    112 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  ·  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

15. Allow institutions to exclude the 776 from the CDI holdings file

    Proposal: allow institutions to exclude the 776 from the CDI holdings file

    Problem: sometimes local services for book title X in a series get matched to CDI records for book title Y (a different title in the series). Users click on the service and are taken to the wrong book, which is frustrating. According to Ex Libris, Alma uses the 776 field to generate the holdings file that is sent to CDI to calculate availability, and this is what causes the incorrect matching.

    The solution of removing identifiers from the 776 as outlined in this Knowledge Article is not feasible, because it goes against correct cataloging practice. Even if we were to remove the 776 in our local bib, it would get overwritten with the next bib update.
    Why Do CDI Records for Book Series Titles Appear Incorrectly as "Full Text Available"? How Can I Correct This? - Ex Libris Knowledge Center https://knowledge.exlibrisgroup.com/Alma/Knowledge_Articles/Why_Do_CDI_Records_for_Book_Series_Titles_Appear_Incorrectly_as_%22Full_Text_Available%22%3F_How_Can_I_Correct_This%3F

    The 776 should not be used to calculate availability, as it is not an indicator of whether a particular institution has access to the alternative format, only that the alternative format exists. Therefore, institutions should have the ability to exclude the 776 from the holdings file published to CDI.

    Proposal: allow institutions to exclude the 776 from the CDI holdings file

    Problem: sometimes local services for book title X in a series get matched to CDI records for book title Y (a different title in the series). Users click on the service and are taken to the wrong book, which is frustrating. According to Ex Libris, Alma uses the 776 field to generate the holdings file that is sent to CDI to calculate availability, and this is what causes the incorrect matching.

    The solution of removing identifiers from the 776 as outlined in this Knowledge Article is not feasible,… more

    85 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  ·  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. Provide option to remove 490 field from Browse Index

    We would like the option to remove the 490 series description field from the Browse index. Because we use 490 for series description and 8XX for the authorised form of series in the same record, the browse series feature in Primo counts one record twice. If we could have the option to remove this from the Browse index, this would solve the problem. It would need to be optional as it is clear that some Primo Libraries rely on the 490 for this purpose.

    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…)
    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. Purchase Request date

    Add the user's purchase request date on their Primo library card in their account.

    We would like that the user can see the date when he create a purchase request date on his Primo library card in his account.

    We think that's will be an improvement for the users.

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

18. Primo VE customize logo tooltip/description

    Allow tooltip/description text to be added to the uploaded logo in the Primo VE view customization, similar to the "Links Menu" customization description.
    This is a basic usability feature that should be easy to configure.
    Our usability testing showed that about half the users expected the logo to go back to the main Primo VE search landing page rather than the library's home page (as many libraries have configured). Having a description on hovering would help clarify for users.

    11 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  ·  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. Pair display of 880 fields with their linked MARC field

    When a record includes multiple 880 fields paired with multiple entries from the same MARC field, for example multiple 700 and 880-700 fields, Primo VE displays all the 700 fields and then all the 880-700 fields. This display loses the link between the two fields, and a user cannot easily connect the non-Latin script (in the 880 field) with the paired Romanised form (in the 700 field).

    In the MARC record the link between fields, such as a 700 and its paired 880-700, is coded in the $6. If the Primo VE display normalisation rules syntax allowed you to compare values in the $6 from the 700 and 880-700 fields and create the pnx display fields for 700 and 880-700 in the same rule, then the linkage could be displayed through the ordering of the fields (i.e. 700, 880-700, 700, 880-700, …).

    When a record includes multiple 880 fields paired with multiple entries from the same MARC field, for example multiple 700 and 880-700 fields, Primo VE displays all the 700 fields and then all the 880-700 fields. This display loses the link between the two fields, and a user cannot easily connect the non-Latin script (in the 880 field) with the paired Romanised form (in the 700 field).

    In the MARC record the link between fields, such as a 700 and its paired 880-700, is coded in the $6. If the Primo VE display normalisation rules syntax allowed you to compare… more

    112 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  ·  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. Saved search alerts - avoid spamming

    Currently a user can enter any email address for alerts to be sent to. To avoid misuse, institutions should be able to configure so that a user can only choose an email address that is in their user account contact details already.

    Also, if the institution does not use such a configuration, and the user inserts an email address that is NOT in their user account, then there should be an email verification process. Alerts will not be sent until the recipient clicks a message to verify they have control of that email address and willing to receive them. Assumes also that the unsubscribe link works for any recipient email address.

    Currently a user can enter any email address for alerts to be sent to. To avoid misuse, institutions should be able to configure so that a user can only choose an email address that is in their user account contact details already.

    Also, if the institution does not use such a configuration, and the user inserts an email address that is NOT in their user account, then there should be an email verification process. Alerts will not be sent until the recipient clicks a message to verify they have control of that email address and willing to receive them. Assumes… more

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