681 results found

1. "Report To Ex Libris" for CDI issues

   Currently it is only possible to report Collection and Portfolios issues via the "Report to Ex Libris" functionality of Alma.
   Colleagues from our e-resources department (who also manage most of the CDI settings) would be glad to use this reporting tool also for CDI issues: wrong URLs, incorrect "Full Text Rights in CDI", etc.

   Please, provide a CRM Cateogry "CDI" in the form and include some CDI data (like now Collection ID, Portfolio ID).
   This would make it much easier for us to report CDI problems, and support team would also benefit from standardized requests.

   124 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

2. Enable Custom Configuration of Primo Normalization Rules for Local Authority Search

   Current Situation: Local authority search records are currently displayed with hard-coded normalization rules (NRs).

   Proposed Change: Allow users to configure Primo normalization rules for local authority search. This flexibility will enable us to normalize authority records and display fields according to our specific needs.

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

3. EZProxy (Primo institution wizard) more granular application against specific collections

   Currently in Primo institution wizard (Primo Home > Ongoing Configuration Wizards > Institution Wizard > Delivery Base URLs) you can enter an EZProxy base URL. If a proxy is added it will be applied to all Link in Record type resources (though there is the option to exclude OA collections). I would like more granularity so that we could choose to apply the proxy to certain Link in Record type collections, but not to apply the proxy to others.

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

4. Add Journal Read and Publish Details to Alma and Make Them Discoverable in Primo

   As libraries continue to add more read and publish journal agreements, it’s important that researchers are able to easily discover which journals are part of these agreements, the open access article publishing charges that are and are not covered by these agreements, and other relevant details related to open access publishing from the library’s read and publish agreements.

   There are several open access journal discovery products that provide end users with this kind of information, but they must perform searches on separate platforms, and library staff must maintain these holdings outside of Alma.

   Examples include:

   ChronosHub: https://stanford.chronoshub.io/?q=%220021-9371%22&journaltitle=Journal%20of%20British%20Studies

   Open Journal Finder by Consortia Manager:

   https://university-of-south-carolina-columbia.openjournalfinder.com/journals/yYP1r3?p=eyJxIjoiam91cm5hbCBvZiBicml0aXNoIHN0dWRpZXMifQ%3D%3D

   The above products use data from a variety of sources, such as publishers, OpenAlex, etc., to gather journal APC costs, publishing activity at the library’s university, and more. Libraries can add notes about their read and publish agreements that display in the corresponding journal records. And journals whose APCs are included in a library’s read and publish agreements prominently indicate that there are no costs for researchers to publish open access articles.

   This would need to be a cross-product enhancement involving Primo for end user discovery, Alma for electronic resources management and licensing aspects of transformative agreements, Alma Analytics for tracking publishing usage of these agreements and combining it with COUNTER read data, and content operations for the metadata for APC costs, institutional publishing activity, etc.

   As in the examples above, some read and publish/APC metadata will appear in brief search results (e.g., whether the APC is covered by the library agreement). At the same time, more details would be available in full journal records (such as Creative Commons licenses, a publisher description of the journal’s scope so authors can determine relevant journals for their research, unique details about the read and publish agreements that the library can customize from within Alma, publishing activity in that journal at that institution, open access publishing instructions for authors (customizable by library), etc.. Researchers would need to be able to use facets to limit their search results to journals whose APCs are covered by their library’s read and publish agreements.

   Use Cases:

   Researchers wanting to find open access journals without any author fees could search Primo using limiters for journals included in their library’s read and publish agreements and subject areas. 
   
   Libraries could achieve a greater return on investment from their read and publish agreements by making their offerings more visible at the point of need. The information would be easy for researchers to understand, reducing the need for library staff to respond to questions about eligible journals and OA author publishing costs. 
   
   Researchers would not need to search a third-party platform; they could simply use Primo to find this information, a tool they are already familiar with. 
   
   Library staff would not need to maintain read and publish holdings in a separate system; they would be managed in Alma alongside the library’s other electronic resources. 
   
   Library staff could run Analytics reports on their researchers’ utilization of the publishing parts of read and publish agreements to more easily assess their return on investment and inform renewal decisions. 
   

   Justification

   Libraries are investing more and more of their acquisitions budgets in read and publish journal agreements, and researchers need the ability to easily discover these details via Primo searches. Providing details about whether or not researchers need to pay to publish open access articles helps researchers make informed decisions on where to publish and better comply with government open access mandates across the world. It could also help libraries achieve a greater return on investment from these agreements and more easily assess them to make data-informed renewal decisions.

   As libraries continue to add more read and publish journal agreements, it’s important that researchers are able to easily discover which journals are part of these agreements, the open access article publishing charges that are and are not covered by these agreements, and other relevant details related to open access publishing from the library’s read and publish agreements.

   There are several open access journal discovery products that provide end users with this kind of information, but they must perform searches on separate platforms, and library staff must maintain these holdings outside of Alma.

   Examples include:

   ChronosHub: https://stanford.chronoshub.io/?q=%220021-9371%22&journaltitle=Journal%20of%20British%20Studies

   Open Journal Finder… more

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

5. Improve usability of exclude/include facet options

   Based on recent usability testing of the new UI we have found that our users appeared to be confused about how to include and exclude facet options from their results set. One of the main pain points seemed to be that they did not know that they were able to exclude a specific facet option (for example to exclude English items from the results set most of our users ticked all options under the language facet other then English rather then just excluding the English option).

   At the moment the option to exclude only appears when someone hovers over the facet option, and it appears on the right of the text of the facet option. Although the option to include a facet also only appears when the mouse hovers over the text of the facet option because it appears on the left of the text it is more obvious, as users will be reading left to right, then something that appears after the text.

   We feel the overall usability of the exclude/include facet option functionality could be improved by:

   1. Moving the exclude option so it is next to the include option on the left of the facet options
   2. Both options are made static so users are aware there are filtering options without the need to hover over the text of the facet option.
   3. Currently a tool tip exists for the exclude option, but there isn't a equivalent tool tip for include. We would like a tool tip to be available for both options.

   Based on recent usability testing of the new UI we have found that our users appeared to be confused about how to include and exclude facet options from their results set. One of the main pain points seemed to be that they did not know that they were able to exclude a specific facet option (for example to exclude English items from the results set most of our users ticked all options under the language facet other then English rather then just excluding the English option).

   At the moment the option to exclude only appears when someone hovers over the… more

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

6. Display both active (payable) AND accruing fines/fees at Fine+fees tab of a user’s account

   Fines+fees tab of a user’s account does not show the balance of the accruing fines. Fines+fees tab doesn’t include the information of the loans that have accruing fines on them, and this confuses clients. They should be able to see this information easily and understand the difference between active and accruing fines.

   We propose that Fine+fees tab of a user’s account should display the total amount of active and accruing balance; the active (payable) balance with the Pay button beside it and the accruing balance. We also wish that the fine type of the loans that have accruing fines would be "Accruing". To illustrate the difference between these two, the following text could be shown on the tab: "Active balance is the sum that you can pay immediately; accruing balance can be paid only after you have either renewed or returned the loans in question. Current fines balance is the sum of active and accruing balance."

   We also wish that the previous specification of balance (total-active-accruing) would be visible on the Overview tab along with the current "Pay fine" button.

   Please see the attached document. There is a related idea that has already been accepted on Alma's Idea exchange: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/44219130-display-both-active-payable-and-accruing-fines-f

   Fines+fees tab of a user’s account does not show the balance of the accruing fines. Fines+fees tab doesn’t include the information of the loans that have accruing fines on them, and this confuses clients. They should be able to see this information easily and understand the difference between active and accruing fines.

   We propose that Fine+fees tab of a user’s account should display the total amount of active and accruing balance; the active (payable) balance with the Pay button beside it and the accruing balance. We also wish that the fine type of the loans that have accruing fines would… more

   •  

   121 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

7. "Search within results"

   We would like to propose a "Search within results" option for Primo. "Search within results" would be a keyword search across all fields present in a user's results list. This is an option offered in common databases, such as Web of Science, so it is something users expect. We feel this search function would increase Primo's usability particularly for inexperienced users.

   120 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 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. IZ level view configuration

   As a library network with a large number of Primo views, it can be extremely laborious to update every single view for configuration options that are identical in each view. These include in particular all configuration options that can be found in the General, Links, Advance Search, Brief results, Brief record display and Full Record Services tab of the view configuration menu.

   This kind of centralised view management would need to be available at the IZ level as it does not fulfil the same purpose as the possibility to distribute configuration from the the Network Zone to the various Institution Zones (in our context, we have two IZs for different types of libraries, with different configuration requirements).

   Indeed, this could be of interest not only to a library consortium but to any standalone library that manages several views.

   As a library network with a large number of Primo views, it can be extremely laborious to update every single view for configuration options that are identical in each view. These include in particular all configuration options that can be found in the General, Links, Advance Search, Brief results, Brief record display and Full Record Services tab of the view configuration menu.

   This kind of centralised view management would need to be available at the IZ level as it does not fulfil the same purpose as the possibility to distribute configuration from the the Network Zone to the various Institution… more

   116 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. [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 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  ·  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

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

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

11. Apply Display Logic Rules to CDI direct linking records

    Currently, records that provide full text solely via a CDI link-in-record URL are not subject to Display Logic Rules (see documentation note below). This leads to inconsistent behavior and display compared to other CDI records.

    For example, our article ILL General Electronic Service is configured not to display when there is full-text available on a record. This works as expected for records that have full-text provided via the link resolver, but for CDI direct linking records, the ILL GES displays alongside the full-text link. This confuses our patrons, who think that the presence of the ILL link means the full-text link isn't working.

    We request the capability to apply display logic rules to CDI direct linking (link-in-record) records as we can do for CDI records with link resolver full-text.

    Documentation note, added due to case #06712066: "Display logic rules are only applied when the Alma link resolver provides the links. CDI direct linking records are not generated by the Alma link resolver mechanism; therefore, Display logic rules are not applied for them."
    https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/080Configuring_Delivery_Services_for_Primo_VE/Configuring_Discovery_Interface_Display_Logic_for_Primo_VE

    Currently, records that provide full text solely via a CDI link-in-record URL are not subject to Display Logic Rules (see documentation note below). This leads to inconsistent behavior and display compared to other CDI records.

    For example, our article ILL General Electronic Service is configured not to display when there is full-text available on a record. This works as expected for records that have full-text provided via the link resolver, but for CDI direct linking records, the ILL GES displays alongside the full-text link. This confuses our patrons, who think that the presence of the ILL link means the full-text… more

    •  

    •  

    115 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

12. Push record to Zotero

    Add the Zotero reference manager as an additional action link in the "Send to" section, just like Mendeley or EndNote.

    113 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

13. Please make the MARC bib. 245 subfield p from the bibliographic record available.

    The MARC 245 subfield p from the bibliographic record is not exposed to Primo. This means that the data in the b245p is not available to display to users in the My Account section of Primo, as part of the requesting process and on pull slips for items. This becomes important when the items have 245a data that is the same. For example, when a video game has the same name with more info in the 245p like the ones below.
    b245a b245p
    Angry birds. Star Wars
    Angry birds. Trilogy
    Assassin's creed. Brotherhood
    Assassin's creed. Revelations
    Batman. Arkham Asylum
    Batman. Arkham city
    Batman. Arkham origins
    Call of duty. Black Ops
    Call of duty. Black ops II

    I would like to see the bib. 245 p added.

    examples of issues attached.

    The MARC 245 subfield p from the bibliographic record is not exposed to Primo. This means that the data in the b245p is not available to display to users in the My Account section of Primo, as part of the requesting process and on pull slips for items. This becomes important when the items have 245a data that is the same. For example, when a video game has the same name with more info in the 245p like the ones below.
    b245a b245p
    Angry birds. Star Wars
    Angry birds. Trilogy
    Assassin's creed. Brotherhood
    Assassin's creed. Revelations
    Batman. Arkham Asylum
    Batman.… more

    • 

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

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 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…)
    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. Include available NZ e-inventory within IZ Alma/Primo VE browse indexes

    For consortia with Network Zones, the centralized management of electronic resources is an integral function of the NZ. However, the Alma Browse Bibliographic Headings functionality used for the Primo VE Browse Search indexes omits e-resources available to an institution via the NZ.

    Within the Metadata Editor, staff can select either 'Institution' or 'Network' when using the Browse Bibliographic Headings function. Selecting 'Institution' includes records from the IZ level, which omits anything where electronic access has been distributed to that institution from the NZ. Selecting 'Network' includes all records from the NZ level, regardless of the institution's physical holdings or electronic access.

    The Primo VE Browse Search uses the Alma Browse Bibliographic Headings 'Institution'-level index. As a result, our end users (students, faculty, reference librarians, etc.) who browse headings are not viewing the complete set of resources available. This is a particular problem for ebooks, as there are several large collections from major publishers/platforms (Oxford, JSTOR) that are managed in the NZ on our behalf by our consortium.

    We want a setting in between the two existing options, which would include all IZ records AND the NZ records "Available for" the institution, and which would be used for the Primo VE Browse Search. This setting would allow staff to review the headings of all pertinent records, physical and electronic, within Browse Bibliographic Headings, and enable end users to access the same set of resources from the Primo VE Browse Search.

    An example of the gap for our end users:

    Browsing for the subject "Jewish wit and humor–History and criticism" yields 16 results:
    https://wrlc-gu.primo.exlibrisgroup.com/discovery/search?query=Browse:%20Jewish%20wit%20and%20humor%20History%20and%20criticism.&sortby=author&vid=01WRLC_GUNIV:01WRLC_GUNIV&mode=browse&browseQuery=Jewish%20wit%20and%20humor--History%20and%20criticism&browseScope=subject.1&innerPnxIndex=-1&fn=BrowseSearch&docCount=16&browseParams=%7B%22headingType%22:%22SUBJECTS%22,%22vocabularyCode%22:%22LCSH%22,%22normalizedValue%22:%22jewish%20wit%20and%20humor%20history%20and%20criticism%22,%22numberOfResults%22:%2216%22,%22displayValue%22:%22Jewish%20wit%20and%20humor%20History%20and%20criticism.%22,%22sourceCode%22:%22TOPICAL_TERM%22,%22isPrefered%22:false,%22originatingSystem%22:null,%22browseType%22:%22SUBJECTS_WITH_MARC21_6XX%22,%22isGlobal%22:true,%22originatingSystemId%22:null,%22family%22:%22MARC21%22,%22recordProvenance%22:%22INSTITUTION%22%7D

    An advanced search for the same "Jewish wit and humor History and criticism" subject yields 18 results: https://wrlc-gu.primo.exlibrisgroup.com/discovery/search?query=sub,exact,%22Jewish%20wit%20and%20humor%20History%20and%20criticism%22,AND&tab=LibraryCatalog&search_scope=MyInstitution&sortby=rank&vid=01WRLC_GUNIV:01WRLC_GUNIV&lang=en&mode=advanced&offset=0

    The two 'extra' results in the search by subject are ebooks from NZ JSTOR collections.

    For consortia with Network Zones, the centralized management of electronic resources is an integral function of the NZ. However, the Alma Browse Bibliographic Headings functionality used for the Primo VE Browse Search indexes omits e-resources available to an institution via the NZ.

    Within the Metadata Editor, staff can select either 'Institution' or 'Network' when using the Browse Bibliographic Headings function. Selecting 'Institution' includes records from the IZ level, which omits anything where electronic access has been distributed to that institution from the NZ. Selecting 'Network' includes all records from the NZ level, regardless of the institution's physical holdings or electronic… more

    112 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  ·  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. Real Time Availability for Electronic Resources

    If a resource from Alma is unavailable to a end user due to a campus or IP restriction and receives the "No Full Text available" message, then update the "Online Access" green dot to "No Full Text/Red Dot" or "Sign In for access options/ Yellow dot"

    •  

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

17. Different URL:s in Resource Recommender depending on language

    When adding resources to Resource Recommender you can only use one URL. We would like to have the option to enter different URL:s depending on which language you are using in Primo. All our web pages are translated to English but now we can only point to our pages in Swedish. This would be a great enhancement to all multi-lingual universities.

    107 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…)
    9 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. Primo VE mobile device enhancement

    When using Primo VE on a mobile device, such as a mobile phone, if you change from portrait to landscape and then back to portrait, half of the page will become blank, which is not conducive to readers' viewing.

    107 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

19. More DEDUP keys

    The implementation of the FRBR keys is affected by the DEDUP keys, so it would be desirable to add a new key in the DEDUP keys that includes the label 250.

    107 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…)
    7 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. Classification Authority Record Enrichment in Primo VE

    In addition to the indexing of bibliographic metadata, Primo VE indexes preferred and non-preferred terms from 1XX and 4XX fields in related Alma authority records.
    This is not the case for classification authority records. In the old Primo, it was possible to enrich bibliographic records with additional terms available in 7xx fields of the classification record. For instance:
    153 ##$aE860$hUnited States$hLater twentieth century, 1961-$hNixon's administration, 1969-August 9, 1974$jWatergate Affair, 1972-
    750 00$aWatergate Affair, 1972-1974.

    Could you enable enrichment with 7xx fields of classification authority records in the same way fields 1xx and 4xx of authority records enrich bibliographic records in Primo VE?

    In addition to the indexing of bibliographic metadata, Primo VE indexes preferred and non-preferred terms from 1XX and 4XX fields in related Alma authority records.
    This is not the case for classification authority records. In the old Primo, it was possible to enrich bibliographic records with additional terms available in 7xx fields of the classification record. For instance:
    153 ##$aE860$hUnited States$hLater twentieth century, 1961-$hNixon's administration, 1969-August 9, 1974$jWatergate Affair, 1972-
    750 00$aWatergate Affair, 1972-1974.

    Could you enable enrichment with 7xx fields of classification authority records in the same way fields 1xx and 4xx of authority records enrich bibliographic records in… more

    105 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