647 results found

1. Make the New Primo UI more CSS friendly

   While the new Primo interface gave us more power to extend functionality via JavaScript it does not do the same for modifications via CSS due to the lack of properly marked up content.

   In some parts of the New UI the content is well described, often with custom HTML elements, but there are also many places, often in the higher levels in the DOM tree, where better described selectors (preferably through classes) are needed.

   For example, there is currently no selector that show the current system that is being displayed. The <prm-explore>-element could have the current system being shown as a class (search, fulldisplay, openurl, jsearch, account, login etc).

   In the search results the <div.list-item-wrapper> element is used on the parent level. Here the markup would be greatly improved by adding the media-type such as article, book, text_resource etc. Allowing us to style based on media-type.

   It's the same with facets. There's currently no way to target a specific Facet Group with CSS. The first real identifying selector is on the span[translate="facets.facet.facet_XXX"] that is several children down. Having this as a class or other attribute on either the repeating parent <div> or the <prm-facet-group> would help.

   In My Account the <md-tab-content> could use the same treatment. Here the section could be added as an attribute, e.g. overview, fines, blocks_messages etc.

   These are just a few examples where better selectors would be helpful. The best would be if the entire UI got the treatment with better selectors and modifications via CSS in mind. While JavaScript is powerful it is not the correct tool for everything.

   While the new Primo interface gave us more power to extend functionality via JavaScript it does not do the same for modifications via CSS due to the lack of properly marked up content.

   In some parts of the New UI the content is well described, often with custom HTML elements, but there are also many places, often in the higher levels in the DOM tree, where better described selectors (preferably through classes) are needed.

   For example, there is currently no selector that show the current system that is being displayed. The <prm-explore>-element could have the current system being shown as… more

   93 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  User Interface  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Default 'Has Activity' instead of 'All Institutions' in My Library Card

   The new ability to toggle between "All Institutions" and "Has Activity" in the My Library Card feature is helpful. It would be more helpful if the default were "Has Activity" instead of "All Institutions" (or if libraries could configure which of the two options they would like to be the default in their PrimoVE instance). Patrons need to know information about where their current loans originate from, and are not usually looking for a list of all the libraries they've ever borrowed from. Most do not even notice the ability to toggle between the two options, so the default should be the option that most patrons are looking to make use of.

   The new ability to toggle between "All Institutions" and "Has Activity" in the My Library Card feature is helpful. It would be more helpful if the default were "Has Activity" instead of "All Institutions" (or if libraries could configure which of the two options they would like to be the default in their PrimoVE instance). Patrons need to know information about where their current loans originate from, and are not usually looking for a list of all the libraries they've ever borrowed from. Most do not even notice the ability to toggle between the two options, so the default should… more

   93 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   8 comments  ·  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. 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

   •  

   •  

   94 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. Adding 'Issue' as a new resource type in Primo Central

   Resource types used in Primo Central are limited to 23 (book, article, journal, image...) [See pdf "Primo Central Index Resource Types" in the Documentation Center].

   For digitized journal issues, the type in use is 'journal'. Archive collections like HathiTrust may contain tens of thousands of digitized journal issues; institutional repositories may also contain complete issues… This is finally confusing for end-users for who see issues labelled as journals and for whom filtering by resource type has become useless.

   Adding a 24th type 'Issue' for this material would be welcome! ‘Journal’ would thus only remain for real journal records.

   93 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…)
   Under Review  ·  8 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

5. Authenticated "Authentication note" field

   Make the content of the "authentication note" field (electronic collection editor and portfolio editor) only visible to our legitimate end-users by means of authentication: preferably via sso, another option would be via ip. That way we can register and manage all our username/password information for e-sources from within Alma. And get rid of the in-house solution (according to the Alma-L mailing list other institutions, like us, developed solutions involving a link to an authentication protected page).
   Currently the authentication note has the same functionality as the "public note" field. It is displayed to anyone searching in our Primo. There also is no distinction (label) from the actual public note field in the Primo display.

   Make the content of the "authentication note" field (electronic collection editor and portfolio editor) only visible to our legitimate end-users by means of authentication: preferably via sso, another option would be via ip. That way we can register and manage all our username/password information for e-sources from within Alma. And get rid of the in-house solution (according to the Alma-L mailing list other institutions, like us, developed solutions involving a link to an authentication protected page).
   Currently the authentication note has the same functionality as the "public note" field. It is displayed to anyone searching in our Primo. There also… more

   92 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  ·  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. Search Limiters for Accessibility Features

   As a cataloger, I would like to propose a new option to filter search results for items with accessibility features (captions, audio descriptions, large print, etc). We are in the process of adding 041 subfields (mostly p and q), and 341 and 532 fields to our records in order to help users more easily identify items intended for those with hearing or visual disabilities. Ideally, this feature would utilize that input based on the presence of indicators in the 341 or 532 fields (i.e., 0 and 1) or controlled vocabulary terms to create search facets or indications (similar to the use of the 506 to indicate Open Access). Ultimately, our aim is to make access to our collection more inclusive, and this feature would go a long way towards achieving that goal.

   As a cataloger, I would like to propose a new option to filter search results for items with accessibility features (captions, audio descriptions, large print, etc). We are in the process of adding 041 subfields (mostly p and q), and 341 and 532 fields to our records in order to help users more easily identify items intended for those with hearing or visual disabilities. Ideally, this feature would utilize that input based on the presence of indicators in the 341 or 532 fields (i.e., 0 and 1) or controlled vocabulary terms to create search facets or indications (similar to the… more

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

7. Option to deactivate the Resource Sharing Request Service for records without physical item of electronic/digital services

   Dear colleagues,
   this idea is for adding the option to deactivate the Resource Sharing Request service in Primo VE for some groups of records without physical item of electronic/digital services, without having to deactivate the Resource Sharing Request rule in Discovery Interface Display Logic.

   This deactivation should be applicable only to local records (catalogued in Alma) and the single institutions should be able to decide if enable it or not.

   We would like the same behavour that exists for Primo also for Primo VE (for example, indicating to Primo VE that when the availability is "no inventory" ILL must be disabled, while when the availability is "no electronic" the possibility of requesting Resource Sharing must can be activated).

   Dear colleagues,
   this idea is for adding the option to deactivate the Resource Sharing Request service in Primo VE for some groups of records without physical item of electronic/digital services, without having to deactivate the Resource Sharing Request rule in Discovery Interface Display Logic.

   This deactivation should be applicable only to local records (catalogued in Alma) and the single institutions should be able to decide if enable it or not.

   We would like the same behavour that exists for Primo also for Primo VE (for example, indicating to Primo VE that when the availability is "no inventory" ILL must be… more

   91 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   5 comments  ·  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. Customise Purchase Suggestion Form material type list

   The Purchase Suggestion Form in Primo VE currently offers a drop-down menu of all possible material types, including things like Ephemera, Toys, and Vinyl LP, which we don't want to turn off as a material type option but we also don't want to offer as a purchasing possibility. At the moment there's no way to switch off material types from that dropdown without removing them as an option for new items completely. We would like an option to customise this purchase suggestion form material type list with more flexibility.

   91 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

9. Hide digitization button when items of a title are on loan / unavailable

   We would like to suggest the option to hide the digitzation button when all items of a title are on loan / unavailable.
   Currently, titles can be requested for digitization while all items corresponding to a title are on loan or unavailable, which can result in significant waiting periods between requesting a title for digitization and the fulfillment of said request.
   Therefore, we propose that the digitization button only appears when an item is available for the title in question. This would benefit patrons, since they can assume that if a request can be made, it will be processed right away.

   We would like to suggest the option to hide the digitzation button when all items of a title are on loan / unavailable.
   Currently, titles can be requested for digitization while all items corresponding to a title are on loan or unavailable, which can result in significant waiting periods between requesting a title for digitization and the fulfillment of said request.
   Therefore, we propose that the digitization button only appears when an item is available for the title in question. This would benefit patrons, since they can assume that if a request can be made, it will be processed right… more

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

10. Add target_url to DisplayCTO output

    There is a feature in Primo VE to debug OpenURLs. You add to the OpenURL the parameter &displayCTO=true, e.g. https://uzb.swisscovery.slsp.ch/discovery/openurl?institution=41SLSP_UZB&vid=41SLSP_UZB:UZB&id=pmid:24881163&sid=Entrez:PubMed&displayCTO=true

    Now you find between the metadata and the inventory a button "DISPLAY CTO". If you click there, you get an XML file with the metadata details that are available to Primo VE at the moment as well as data for the online services Primo VE will offer the user. However, one important information is missing: The target URL the service will link to is not displayed.

    If you, however, use the debug URL of the Alma Link Resolver: https://slsp-uzb.alma.exlibrisgroup.com/view/uresolver/41SLSP_UZB/openurl?svc_dat=CTO&debug=true&debug=true&id=pmid:24881163&sid=Entrez:PubMed

    You get in every service record a field <target_url>. There you find the exact URL that will be called, when the service is chosen.

    This is crucial and should be added to the displayCTO feature in Primo VE.

    There is a feature in Primo VE to debug OpenURLs. You add to the OpenURL the parameter &displayCTO=true, e.g. https://uzb.swisscovery.slsp.ch/discovery/openurl?institution=41SLSP_UZB&vid=41SLSP_UZB:UZB&id=pmid:24881163&sid=Entrez:PubMed&displayCTO=true

    Now you find between the metadata and the inventory a button "DISPLAY CTO". If you click there, you get an XML file with the metadata details that are available to Primo VE at the moment as well as data for the online services Primo VE will offer the user. However, one important information is missing: The target URL the service will link to is not displayed.

    If you, however, use the debug URL of the Alma Link Resolver: https://slsp-uzb.alma.exlibrisgroup.com/view/uresolver/41SLSP_UZB/openurl?svc_dat=CTO&debug=true&debug=true&id=pmid:24881163&sid=Entrez:PubMed

    You… more

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

11. Sorting of multiple copies according to item policy "available for loan"

    Our library for medicine offers a large number of copies of some standard works. Some of them are not borrowable because they belong to the reference collection (item policy 63). Other copies have the item policy "available for loan, 1 day" (item policy 59) or "available for loan, 28 days" (item policy 01).
    Example; https://slsp-network.primo.exlibrisgroup.com/permalink/41SLSP_UBE/hnud4r/alma99116892929105511

    In the details display (get it), the items that can be borrowed for 28 days are displayed last and are very difficult for users to find.
    Ideally, the filter function should be adapted to contain the option "available for loan", so that patrons can choose the loan status themselves. If this ist not possilble, borrowable copies should be displayed first by default. This will enhance visibility and make it easier for patrons to find the items they want.

    Our library for medicine offers a large number of copies of some standard works. Some of them are not borrowable because they belong to the reference collection (item policy 63). Other copies have the item policy "available for loan, 1 day" (item policy 59) or "available for loan, 28 days" (item policy 01).
    Example; https://slsp-network.primo.exlibrisgroup.com/permalink/41SLSP_UBE/hnud4r/alma99116892929105511

    In the details display (get it), the items that can be borrowed for 28 days are displayed last and are very difficult for users to find.
    Ideally, the filter function should be adapted to contain the option "available for loan", so that patrons can choose… more

    89 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

12. Find alternate ISBNs in the available record to force an available syndetic cover image.

    I've learned that the book cover images from Syndetics in Primo comes from the first Addata: ISBN PNX field which comes from the first subfield a in the MARC 020 field.

    Often, we have the electronic version of a book that uses a different ISBN in the first MARC 020 |a

    Small presses/publishers may have only sent Syndetics a print ISBN image and that image is available from Syndetics. Since often the print ISBN is in the MARC 020 field already - but not necessarily in subfield a or in the first position - it means that the default book image displays in the catalogue instead of a cover image.

    Can you do something so that the system cycles through all of the ISBNs in a record until it finds an image? For example all of the ISBNs in the MARC 020 could be listed in the Addata: ISBN and then the system can systematically go through them until it finds one with an image to use?

    That would be better than contacting Syndetics with a requeest to copy the printISBN image for use with an e-isbn and prevent us from listing incorrect ISBNs in the MARC 020 |a field just to force a book cover to display

    Thanks for considering. Sandra.

    I've learned that the book cover images from Syndetics in Primo comes from the first Addata: ISBN PNX field which comes from the first subfield a in the MARC 020 field.

    Often, we have the electronic version of a book that uses a different ISBN in the first MARC 020 |a

    Small presses/publishers may have only sent Syndetics a print ISBN image and that image is available from Syndetics. Since often the print ISBN is in the MARC 020 field already - but not necessarily in subfield a or in the first position - it means that the default book… more

    88 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    4 comments  ·  Integration with other systems  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

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

    88 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. Add 245 subfield c to Primo display

    Please add the 245 subfield c to the display in Primo. It does display in Alma. In the example below, you are not able to determine the author/creator's responsibility for the work - Author vs. forward vs. photographer.

    https://cmog.primo.exlibrisgroup.com/discovery/fulldisplay?docid=alma991302983504126&context=L&vid=01CORNING_INST:01CORNING_INST&search_scope=MyInstitution&tab=LibraryCatalog&lang=en

    We would love to have more granularity in general for what fields/subfields display in Primo for our specific institution.

    Thank you!

    87 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    9 comments  ·  User 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

15. Cambiar la prioridad de las portadas en Primo VE

    Las portadas de Primo se intentan extraer desde el servicio de Syndetics y Google, si el servicio de Syndetics tiene una portada disponible se muestra esta y no la de Google. Por este motivo, por ejemplo, en alma se visualiza una portada de Google y en Primo una de Syndetics.

    Primo VE no tiene la opción de desactivar o cambiar la prioridad de las portadas, por lo que para solucionar este problema se necesitaría que se pueda activar o desactivar la prioridad de las portadas.

    Esperamos que esta idea resulte de interés a todos los usuarios de PRIMO VE y que contribuyan con sus votos a solucionar este inconveniente en la visualización de las portadas.

    Las portadas de Primo se intentan extraer desde el servicio de Syndetics y Google, si el servicio de Syndetics tiene una portada disponible se muestra esta y no la de Google. Por este motivo, por ejemplo, en alma se visualiza una portada de Google y en Primo una de Syndetics.

    Primo VE no tiene la opción de desactivar o cambiar la prioridad de las portadas, por lo que para solucionar este problema se necesitaría que se pueda activar o desactivar la prioridad de las portadas.

    Esperamos que esta idea resulte de interés a todos los usuarios de PRIMO VE y… more

    87 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

16. Enable authority Record Enrichment in Primo VE on local subject fields

    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. However, this works only in the generic advanced search Subject field.

    We need Primo VE to enable authority record enrichment on local fields as well.

    Indeed, we have configured local subject fields that are more specific than the default Subject field. These enable searching only on specific subject vocabularies. But configuring such fields does not include the enrichment capability.

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

    86 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. collection discovery

    Currently grid items in Collection Discovery can show title, resource type and thumbnail. We would like to add creator/author and or creation/publication date if possible. My suggestion is to add configuration for changing what is displayed in the item grid elements in Collection Discovery.

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

19. Journal Search: Consider the NZ activation for e-resources with Inventory Management Groups in the IZ

    Our consortium activates Open Access e-collections in the Network Zone so that they are available in every IZ of the network. Electronic collections for Open Access e-resources are activated without any Inventory Management Group assigned to it. It should display for every IZ and every Inventory Management Group within the IZ.
    Some of the licensed e-collections in the IZs also cover e-resources that are activated in the NZ as Open Access. (Journals can have partial Open Access) The IZs are using Inventory Management Groups, and the local views are assigned to the campuses of the specific Inventory Management Groups. The Journal Search is activated in the views.

    Issue
    The Journal Search records in affiliated views are filtered by the view affiliation and the corresponding Inventory Management Group. If there is an e-resource activated both in IZ and NZ, the current mechanism overrides the Inventory Management Groups of the NZ with the configuration set in the IZ. Therefore, only the licensed coverage of an e-resource is considered for the Journal Search, but not the Open Access part activated in the NZ. This results in incomplete search offer in the Journal Search of the views affiliated with a campus / library.

    Example
    View A affiliated with a campus A
    View B affiliated with a campus B
    View C with no affiliated campus

    E-resource
    Activated in IZ for campus A for licensed coverage
    Activated in NZ without restrictions for the Open Access coverage

    Searchable in Journal Search of campus A – correct, the title is licensed in campus A
    Not searchable in Journal Search of campus B – incorrect, the title is not licensed in campus B, but OA coverage from NZ should apply
    Searchable in Journal Search of view C – correct, no campus affiliation
    Example from productive environment
    View A: https://slsp-rzs.primo.exlibrisgroup.com/discovery/jsearch?query=any,contains,2052-1499&tab=jsearch_slot&vid=41SLSP_RZS:VU06&lang=en&offset=0&journals=any,2052-1499
    View B: https://slsp-rzs.primo.exlibrisgroup.com/discovery/jsearch?query=any,contains,2052-1499&tab=jsearch_slot&vid=41SLSP_RZS:VU07&lang=en&offset=0&journals=any,2052-1499
    View C: https://rzs.swisscovery.slsp.ch/discovery/jsearch?query=any,contains,2052-1499&tab=jsearch_slot&vid=41SLSP_RZS:VU15&lang=en&offset=0&journals=any,2052-1499

    Our consortium activates Open Access e-collections in the Network Zone so that they are available in every IZ of the network. Electronic collections for Open Access e-resources are activated without any Inventory Management Group assigned to it. It should display for every IZ and every Inventory Management Group within the IZ.
    Some of the licensed e-collections in the IZs also cover e-resources that are activated in the NZ as Open Access. (Journals can have partial Open Access) The IZs are using Inventory Management Groups, and the local views are assigned to the campuses of the specific Inventory Management Groups. The… 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…)
    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

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

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