35 results found

1. Increase Primo search capability to support major common search expansions on synonyms.

   Salesforce case #00583901 refers (unpublished)

   Ex Libris advises that, due to performance considerations, Primo search is unable to support the search expansion for the spelling variants that include the use of 's' or 'z' within a word. This is a common trans-Atlantic spelling variation, and omitting it has a significant impact on search results.

   Example: a search for the terms “practice globalisation” produces 441,248 results, but by changing the 's' in globalisation to a 'z', Primo produces an additional 12,000 search results.

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

2. ORCID iD Integration in Info Card for Contributor Page in Alma

   Background: In August, ExLibris implemented the Info Card feature for contributor pages in Alma, which appears under specific conditions related to linked authority records. This enhancement has significantly improved the visibility of contributor information.

   Current Conditions for Info Card Display:

   • A person is linked to an LC Names authority for a personal name.
   • A person is linked to a Name authority that exists in VIAF and can be linked to an LC Name authority for a personal name.
   • Information on the person exists in LC Names and Wikidata, with at least two fields containing information beyond the name of the person.
   • Wikidata cache is updated in Alma on a weekly basis.

   Enhancement Request: We propose an additional feature to further enrich the Info Card functionality. Specifically, we request that when an ORCID iD in the form of a URI is present in either the LC name authority record or Wikidata for the author, the following should occur:

   • Display the ORCID iD URI: The ORCID iD URI should be prominently displayed in the Info Card.
   • Make the ORCID iD URI Resolvable: The URI should be clickable and resolvable directly within the Info Card in both Alma and Primo.

   Benefits: Integrating ORCID iD URIs will enhance the discoverability of author contributions and facilitate seamless access to their research profiles, thereby improving the overall user experience.

   Thank you for considering this enhancement to the Info Card feature. We believe this addition will greatly benefit users and contribute to the ongoing development of Alma and Primo.

   Background: In August, ExLibris implemented the Info Card feature for contributor pages in Alma, which appears under specific conditions related to linked authority records. This enhancement has significantly improved the visibility of contributor information.

   Current Conditions for Info Card Display:

   • A person is linked to an LC Names authority for a personal name.
   • A person is linked to a Name authority that exists in VIAF and can be linked to an LC Name authority for a personal name.
   • Information on the person exists in LC Names and Wikidata, with at least two fields containing information beyond the name of the… more
   202 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   AdminAdina Marciano (Admin, Ex Libris) responded

   Thank you for the suggested idea. We see its value and will consider it in the future. This development requires integration with third-party providers, and we will need to investigate the possibility of this development.

3. Display license information for Open Access and Open Educational Resources

   Please add license information for resources and collections that are known to be open access or open educational resources, making it clear what licence applies. This applies both in CZ records and CDI. We would like to make it clear to our users when a title is made available under a particular licence terms.

   176 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  ·  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
   AdminTamar Ganor (Admin, Ex Libris) responded

   Hello,

   This idea will be transferred to the Primo forum as it will require product development to support this metadata.

   Kind regards,

   Tamar Ganor

   Content Product Manager

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

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

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

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

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

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

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

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

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

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

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

   171 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Enable the Hebrew Acronym file in CDI

   I would like the Hebrew Acronym file to work in the same manner for local and remote records and enable the correct retrieval of records with any of the many Hebrew words that are comprised of initials (eg פלמ"ח, תנ"ך, תשנ"א, אדמו"ר, בג"ץ, רמב"ם, מפא"י…….).

   Currently, searching a term either with or without the " sign will retrieve the term both with and without the quotation sign (") but ONLY for local records. Until this will work in CDI, many remote records will not be retrievable when searching terms that can be written in both ways (with or without the " sign).

   I would like the Hebrew Acronym file to work in the same manner for local and remote records and enable the correct retrieval of records with any of the many Hebrew words that are comprised of initials (eg פלמ"ח, תנ"ך, תשנ"א, אדמו"ר, בג"ץ, רמב"ם, מפא"י…….).

   Currently, searching a term either with or without the " sign will retrieve the term both with and without the quotation sign (") but ONLY for local records. Until this will work in CDI, many remote records will not be retrievable when searching terms that can be written in both ways (with or without the… more

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

6. [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

   •  

   117 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

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

   117 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

8. Primo Central Index ( PCI ) - more granularity in excluding content from activated resources - e.g. exclude from index by resource type

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

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

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

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

   100 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. replace "Do not show as Full Text available in CDI even if active in Alma" with a pair of show local / show CDI checkboxes

   To avoid duplicates when we have both local portfolios and CDI records, we can rely on the "Do not show as Full Text available in CDI even if active in Alma".
   Enabling this feature will show in Primo local IZ portfolios, and is very good when local records are rich and CZ records are limited/poor.
   Sometimes however CDI records are richer and provide indexing at chapter level. In such a case we would like to hide IZ local portfolios and show CDI records instead.
   It would be therefore useful and clearer to replace the "Do not show as Full Text available in CDI even if active in Alma" with a pair of checkbox:

   show local IZ records YES/NO
   show CDI records YES/NO

   To avoid duplicates when we have both local portfolios and CDI records, we can rely on the "Do not show as Full Text available in CDI even if active in Alma".
   Enabling this feature will show in Primo local IZ portfolios, and is very good when local records are rich and CZ records are limited/poor.
   Sometimes however CDI records are richer and provide indexing at chapter level. In such a case we would like to hide IZ local portfolios and show CDI records instead.
   It would be therefore useful and clearer to replace the "Do not show as Full Text… more

   100 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  ·  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. Embargoed resources displaying in Primo

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

    60 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Author/Title Index in Browse Search

    Author/Title Index in Browse Search
    Please include an Author/Title index which searches headings combining author/creator name and uniform title. The index usually includes:
    * 100/240
    * 110/240
    * 111/240
    * 700 where $$t is present
    * 710 where $$t is present
    * 711 where $$t is present
    * 800 where $$t is present
    * 810 where $$t is present; and
    * 811 where $$t is present

    60 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. CDI records: please provide us the ORCIDs in the PNX record in a usable form

    Unfortunately, we have received the following case response: "We have reviewed your request with our content operations team and determined that our system is currently not designed to provide the functionality you requested, so the next step is to pursue this as an enhancement."
    So we hope to get support for our proposal in the Alma community.

    We are currently working on making the ORCID more visible in our Primo (incl. linking to the ORCID entry of an author).

    We are glad to see that CDI records already contain the ORCIDs in the PNX record.
    Unfortunately, they cannot be used for normalization, because:
    - the XML fields <creator>/<creatorcontrib> list all authors of a record and the extra field <orcidid> lists the ORCIDs
    - however, the connection between these fields is missing

    It is not possible to find out which ORCID belongs to which author.
    Please provide us the ORCIDs in the PNX record in a usable form, so that we can create a link for those people who have an ORCID entry.

    Thank you in advance!

    Some PNX record examples:

    (1) TNcdiwebofscienceprimary000288028600012CitationCount
    Benefit of atrial septal defect closure in adults: Impact of age
    Humenberger, Michael ; Rosenhek, Raphael ; Gabriel, Harald ; Rader, Florian ; Heger, Maria ; Klaar, Ursula ; Binder, Thomas ; Probst, Peter ; Heinze, Georg ; Maurer, Gerald ; Baumgartner, Helmut
    OXFORD: Oxford Univ Press
    European heart journal, 2011, Vol.32 (5), p.553-560

    11 authors, 3 ORCIDs

    PNX record:
    <creator>Humenberger, Michael ; Rosenhek, Raphael ; Gabriel, Harald ; Rader, Florian ; Heger, Maria ; Klaar, Ursula ; Binder, Thomas ; Probst, Peter ; Heinze, Georg ; Maurer, Gerald ; Baumgartner, Helmut</creator>
    <creatorcontrib>Humenberger, Michael ; Rosenhek, Raphael ; Gabriel, Harald ; Rader, Florian ; Heger, Maria ; Klaar, Ursula ; Binder, Thomas ; Probst, Peter ; Heinze, Georg ; Maurer, Gerald ; Baumgartner, Helmut</creatorcontrib>
    (...)
    <orcidid>0000-0002-6902-126X ; 0000-0003-1147-8491 ; 0000-0002-9043-7657</orcidid>

    (2) TNcdicrossrefprimary101093eurheartj_ehq377
    Atrial septal defect: Waiting for symptoms remains an unsolved medical anachronism
    Berger, Felix ; Ewert, Peter
    OXFORD: Oxford Univ Press
    European heart journal, 2011, Vol.32 (5), p.531-534

    2 authors, 1 ORCID

    PNX record:
    <creator>Berger, Felix ; Ewert, Peter</creator>
    <creatorcontrib>Berger, Felix ; Ewert, Peter</creatorcontrib>
    (...)
    <orcidid>0000-0001-7881-1557</orcidid>

    (3) TNcdipubmedcentralprimaryoaipubmedcentralnihgov6194635
    Adherence to inhaled therapy and its impact on chronic obstructive pulmonary disease (COPD)
    Humenberger, Magdalena ; Horner, Andreas ; Labek, Anna ; Kaiser, Bernhard ; Frechinger, Rupert ; Brock, Constanze ; Lichtenberger, Petra ; Lamprecht, Bernd
    LONDON: Springer Nature
    BMC pulmonary medicine, 2018, Vol.18 (1), p.163-163

    8 authors, 2 ORCIDs

    PNX record:
    <creator>Humenberger, Magdalena ; Horner, Andreas ; Labek, Anna ; Kaiser, Bernhard ; Frechinger, Rupert ; Brock, Constanze ; Lichtenberger, Petra ; Lamprecht, Bernd</creator>
    <creatorcontrib>Humenberger, Magdalena ; Horner, Andreas ; Labek, Anna ; Kaiser, Bernhard ; Frechinger, Rupert ; Brock, Constanze ; Lichtenberger, Petra ; Lamprecht, Bernd</creatorcontrib>
    (...)
    <orcidid>0000-0003-3365-3449 ; 0000-0001-7746-3335</orcidid>

    Unfortunately, we have received the following case response: "We have reviewed your request with our content operations team and determined that our system is currently not designed to provide the functionality you requested, so the next step is to pursue this as an enhancement."
    So we hope to get support for our proposal in the Alma community.

    We are currently working on making the ORCID more visible in our Primo (incl. linking to the ORCID entry of an author).

    We are glad to see that CDI records already contain the ORCIDs in the PNX record.
    Unfortunately, they cannot be used… more

    60 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Consortia environment: inheritance for open access collections

    Open access collections that are activated in the NZ are not inherited by the IZs.

    Given the number of open access collections and the possible number of IZs, it can be a tedious task to activate a large number of OA collections for each IZ.

    We would like to see that OA collections can be inherited just like regular subscription collections.

    PS - copied from https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/19695103-consortia-environment-provide-inheritance-for-ope, to open it for voting again.

    52 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

14. Advanced search functionality for the Newspaper Search

    Please provide advanced search functionality for the Newspaper Search. Users would like to limit searches by criteria such as publication name.

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

15. Allow fields available in the CTO to be used in General Electronic Services (GES)

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

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

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

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

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

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

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

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

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

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

    33 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Ensure that CZ & CDI Metadata is Linked Data Ready

    I was advised by the Linked Data Group to post this idea here because I submitted the following for the LOD Working Group webinar in December:

    Broader strategic and commercial alliances required to ensure that data is ready to be linked?

    To engender confidence in CZ and make it linked-data ready, why don’t the Company do business with e.g. Backstage Library Works for authority control clean-up and maintenance?

    Metadata is a global commodity so all stakeholders have responsibility for creating, sharing, enriching and maintaining it, and of course there are costs for all of these elements which we could share.

    Isn’t this the best way to ease the burden on libraries and leverage our metadata improvements for mutual and sustainable benefit?

    I note that this document alludes to the Company taking a lead in creating a new open metadata platform and preserved data in an open format.
    https://knowledge.exlibrisgroup.com/Alma/Product_Materials/010Roadmap/Linked_Open_Data

    Preserving metadata is not the same thing as maintaining it because metadata evolves e.g. authorities are deleted, changed and new ones created.

    In light of this I would ask that the Company explore strategic commercial partnerships to ensure that any metadata that they manage (knowledgebases, platforms) is properly maintained.

    Jane

    I was advised by the Linked Data Group to post this idea here because I submitted the following for the LOD Working Group webinar in December:

    Broader strategic and commercial alliances required to ensure that data is ready to be linked?

    To engender confidence in CZ and make it linked-data ready, why don’t the Company do business with e.g. Backstage Library Works for authority control clean-up and maintenance?

    Metadata is a global commodity so all stakeholders have responsibility for creating, sharing, enriching and maintaining it, and of course there are costs for all of these elements which we could share.

    … more

    16 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

17. Fix Core Flaw: (VE / NDE) Holdings Configurations Must Apply to All Locations, including Temporary Locations

    Description:
    This request is being submitted at the direction of the support team, although it addresses a critical flaw in core functionality, not a new enhancement or feature.

    The flaw exists in Primo VE and Support will not confirm that the flaw will not be carried over into the Next Discovery Experience (NDE).

    Problem:
    Primo VE effectively ignores the configurations for holdings field display when an item is moved to a temporary location. Only the default holdings statement automatically generated from the item records is displayed. Due to other known issues, this auto-generated statement presents potentially inaccurate information to library patrons.

    Expected Outcome:
    The core function of a discovery system is to accurately reflect the library's holdings. We expect configurations for metadata display to apply to all items, regardless of whether they are in a temporary or permanent location. The launch of the NDE presents the ideal opportunity to correct this long-standing flaw, ensuring the new product is built correctly from the start and can offer a more reliable user experience than competing discovery platforms.

    References:

    Support Ticket: 07849390 (original) / 07956870 (cloned) - Inconsistent Holdings Display Configuration in Primo VE - Permanent vs. Temporary Locations

    Configuration Documentation: https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/080Configuring_Delivery_Services_for_Primo_VE/Configuring_Holdings_Display_Fields_for_Primo_VE

    Description:
    This request is being submitted at the direction of the support team, although it addresses a critical flaw in core functionality, not a new enhancement or feature.

    The flaw exists in Primo VE and Support will not confirm that the flaw will not be carried over into the Next Discovery Experience (NDE).

    Problem:
    Primo VE effectively ignores the configurations for holdings field display when an item is moved to a temporary location. Only the default holdings statement automatically generated from the item records is displayed. Due to other known issues, this auto-generated statement presents potentially inaccurate information to library… more

    15 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

18. Keywords entered should be carried over from the basic search field to the advanced search field

    In Primo NDE keywords entered should be carried over from the basic search field to the advanced search field as in Primo VE

    13 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  ·  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
    Under Review  ·  AdminYael (yael.shahar@clarivate.com, Ex Libris) responded

    We will revisit this and will consider adding this to support user continuity

19. unpaywall - collection separation

    in the webinar : Yes, We’re Open! Open Access in Knowledgebases and Discovery 20231211 1501 1 1 (https://www.youtube.com/watch?v=WhZ34Y1Rzdo) Christine Stohn mentioned that Ex Libribs we interested in feedback to find out how people wanted UnPaywall content to be available, e.g. split up by version.

    I would therefore like to proposed that the UnPaywall Collection be split into 3 separate collections, Submitted version, author accepted versions and Version of Record/Published version.

    This would not only enable us to only enable the versions we want and avoid those we don't, but also allow us to potentially signpost the version types to our users/make then aware BEFORE they follow the link through that it may not be the version that they are anticipating.

    in the webinar : Yes, We’re Open! Open Access in Knowledgebases and Discovery 20231211 1501 1 1 (https://www.youtube.com/watch?v=WhZ34Y1Rzdo) Christine Stohn mentioned that Ex Libribs we interested in feedback to find out how people wanted UnPaywall content to be available, e.g. split up by version.

    I would therefore like to proposed that the UnPaywall Collection be split into 3 separate collections, Submitted version, author accepted versions and Version of Record/Published version.

    This would not only enable us to only enable the versions we want and avoid those we don't, but also allow us to potentially signpost the version types… more

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

20. Allow Digital Viewer to use different View than Primo

    When viewing digital representations in the Digital Viewer, Alma-D uses the same Primo VE View; however, this can cause some difficulties when configurations ideal for Primo don't translate well to the Viewer.

    For example, we have a pop-up chat icon in Primo VE for patrons to chat with librarians; because this is configured in View, it's also present in the Digital Viewer, but the icon ends up obscuring parts of the representation's image and metadata.

    We'd like to be able to point the Digital Viewer to a different View entirely than the one Primo VE is currently using.

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