735 results found

1. Quicklink display options on full record

   In Primo VE, any quicklinks associated with records show both at the top of the full record display and in the Links section of the record. CSS can be used to hide quicklinks from the Links section, but often results in a blank Links section on the record.

   It would be helpful to have options to show quicklink at the top of the full record display, but hide them from the Links section. This would help improve the usefulness of the Links section of the record.

   15 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

2. Allow customization of CDI resource types in Resource Type Filter Bar

   We are using the Resource Type Filter Bar with general satisfaction, with one major problem. Since Articles and Magazine Articles are separate CDI resource types now, and it isn’t possible to select more than one resource type pre-filter (in Simple or Advanced Search) -- it’s not possible to allow the user to search within both types of articles. There are some magazine articles that seem good to exclude, but there are others that are scholarly sources, even Peer Reviewed, and I fear our users may miss them. Ideally, we might want to enable the search within both types and allow the user to post-filter as desired. Initially, I thought we might be able to create a local resource type to combine Articles & Magazine Articles, but of course that can't be done in Alma, since these are CDI types. I would like to advocate for a combined Article type option (including both Journal and Magazine articles) within the CDI especially for use in Resource Type filtering, AND/OR the ability to customize the Resource Types in the Filter Bar by combing two or more types or other local configurations, including CDI-only resource types.

   We are using the Resource Type Filter Bar with general satisfaction, with one major problem. Since Articles and Magazine Articles are separate CDI resource types now, and it isn’t possible to select more than one resource type pre-filter (in Simple or Advanced Search) -- it’s not possible to allow the user to search within both types of articles. There are some magazine articles that seem good to exclude, but there are others that are scholarly sources, even Peer Reviewed, and I fear our users may miss them. Ideally, we might want to enable the search within both types and allow… more

   15 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

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

4. Allow an institution (IZ) (Alma/Primo VE) to exclude in retrieval 7XX fields with $5 from another institution within the same Network Zone

   In our Network Zone, we work with unique bibliographic records shared by several institutions. The MARC21 7XX subfield $5
   is used to indicate local information specific to each IZ.

   Currently, in Alma and Primo VE searches, 7XX fields containing a $5 from other IZs are included in retrieval and affect
   the Dedup and FRBR grouping processes within an IZ. We can only hide these fields from user display by configuring Primo VE rules.
   As a result, records retrieved in a Primo VE view of one IZ may include data that are strictly local to another institution and may
   even influence FRBR version grouping, producing less relevant or confusing results for users.

   Requested Enhancement:
   We request the addition of a configuration option (at the IZ and/or NZ level) that allows:
   Excluding from search indexing and deduplication/FRBR logic any 7XX fields whose $5 does not correspond to the specific IZ, or
   At least preventing such fields from being used in retrieval and grouping criteria, while maintaining their local character.

   Benefit:
   This enhancement would respect the cataloging meaning of subfield $5, increase result relevance for each institution, and reduce undesired
   effects in the presentation of versions in Primo VE.

   In our Network Zone, we work with unique bibliographic records shared by several institutions. The MARC21 7XX subfield $5
   is used to indicate local information specific to each IZ.

   Currently, in Alma and Primo VE searches, 7XX fields containing a $5 from other IZs are included in retrieval and affect
   the Dedup and FRBR grouping processes within an IZ. We can only hide these fields from user display by configuring Primo VE rules.
   As a result, records retrieved in a Primo VE view of one IZ may include data that are strictly local to another institution and may
   even influence… more

   15 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Additional Function:Excludes unnecessary resource types in Specialized Search Scopes for CDI

   ■Idea
   When configuring "Specialized Search Scopes for CDI"　https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/040Search_Configurations/010Configuring_Search_Profiles_for_Primo_VE
   in Primo VE, currently only 5 CDI resource types can be selected, so we want to change the system that unnecessary resource types can be excluded.

   ■Context
   Regarding "Exclude eBooks from CDI Results - Phase 2 (NERS #6702)", In Phase 1, all books were excluded from search, but after Phase 2, some books remain in the search results.

   To exclude books for this reasons,we would like to set the "Specialized Search Scopes for CDI" with limited number of CDI resource types.
   But the maximum number of resource types that can be selected is too few, so we would like the system to be changed so that unnecessary resource types can be excluded.

   This function allows scopes to be more limited to specific resource types.

   ■Idea
   When configuring "Specialized Search Scopes for CDI"　https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/040Search_Configurations/010Configuring_Search_Profiles_for_Primo_VE
   in Primo VE, currently only 5 CDI resource types can be selected, so we want to change the system that unnecessary resource types can be excluded.

   ■Context
   Regarding "Exclude eBooks from CDI Results - Phase 2 (NERS #6702)", In Phase 1, all books were excluded from search, but after Phase 2, some books remain in the search results.

   To exclude books for this reasons,we would like to set the "Specialized Search Scopes for CDI" with limited number of CDI resource types.
   But the maximum number of resource types that can be… more

   14 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

6. Request physical book when e-book is also available at home or other libraries

   No request or resource sharing option is available when the home library has an e-book. There are many scenarios where a patron may need a physical book and they should have the ability to request one from Primo.

   14 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

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

7. Language field in Brief Record Display ought to use the Language codes Labels (VE)

   For institutions with multi-lingual collections, the out-of-the-box Language field can be a useful addition to the record display. When Language is added to the Full Record display, the "Language codes Labels" code table is used to convert the abbreviated codes used in metadata records into generally understood language names–e.g. the code 'gle' displays as 'Irish'.

   When the Language field is added to the Brief Record display, however, the labels are NOT used and the code is displayed as-is. Ex Libris recognizes this as a defect (case #06659538) but a solution is not part of the current development work plan. We are dismayed, as we hoped to add this field to our brief record display to remedy student difficulties demonstrated during usability interviews. The Language field is included in our Full Record display, but it is less visible there than it would be in the Brief Record.

   Scenarios where having the language label in the Brief display would be helpful for users:

   1. Students can have trouble distinguishing which titles are foreign language material because the metadata is primarily or solely in English. This sort of confusion can lead to item requests for material that a student cannot read and thus cannot use, which wastes the time of the student during their research, wastes the time of library staff who processed the request, and sometimes costs the library money for postage/fees incurred to process the request. For online resources, this confusion leads to inflated usage statistics that can be misleading for calculating cost per use and making renewal decisions. Image: eng metadata jpn contents

   2. Titles can be in a different language than the contents of the text while the record metadata is in a third language. Numerous older titles, for example, are in Latin, which can be misleading about the linguistic nature of their contents. This confusion has similar impacts as described in the first scenario. Image: eng metadata latin title irish text

   3. The Language facet is not sufficient to distinguish the primary language of the material from the presence of supplemental text in that language, like subtitles on a film. Patrons who are seeking resources in specific languages can be frustrated by this. For example, the film Parasite remains in search results after the English language filter is applied, even though the dialogue is in Korean and French while English is only present as subtitles. In those same filtered results, you can see the film Transfer, which is in German and French. Image: eng filter koreanFrench dialogue

   Since the code is displayed in the Brief Record, we cannot add it for our users–it would cause more confusion than it would resolve. The out-of-the-box Language field needs to be fixed so the "Language codes Labels" code table is invoked for the Brief Record, as it is for the Full Record.

   For institutions with multi-lingual collections, the out-of-the-box Language field can be a useful addition to the record display. When Language is added to the Full Record display, the "Language codes Labels" code table is used to convert the abbreviated codes used in metadata records into generally understood language names–e.g. the code 'gle' displays as 'Irish'.

   When the Language field is added to the Brief Record display, however, the labels are NOT used and the code is displayed as-is. Ex Libris recognizes this as a defect (case #06659538) but a solution is not part of the current development work plan. We… more

   •  

   •  

   •  

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

8. Add a “Scholarly” Search Results Facet

   Adding a "Scholarly" search results facet to Primo VE or the future NDE, in addition to the existing "Peer-Reviewed" facet, would be beneficial, similar to Summon's “Scholarly & Peer-Reviewed” facet.

   Not all peer-reviewed articles are scholarly, so having both facets would enable users to refine their searches according to their specific needs.

   This shouldn’t require huge effort since Summon is also an Ex Libris product, and resources for implementation should be readily available.

   14 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

9. "Feedback Tool" for the New Primo UI: possibility to define the e-mail field as a mandatory field

   We have been using the feedback tool for a few weeks now and have unfortunately received many requests where the users did not provide an e-mail address.
   As a result, we have no way to ask a question or explain the reported behaviour (as it is correct).

   Therefore, we would be glad if the e-mail field can be defined as a mandatory field in the Primo back office.
   A user can of course still enter a fake e-mail address, but then this is a deliberate action.

   Thank you in advance!

   13 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

10. "Feedback Tool" for the New Primo UI: Configuring the Feedback Letter - please support multilingualism

    There are already pre-defined labels for the e-mail in different languages (e.g. default.report.emailTextNoEmail) but they are currently non-functional :-(

    Configuring the Feedback Tool for the New Primo UI
    https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/Primo/New_Primo_User_Interface/Additional_Features_for_the_New_UI/Configuring_the_Feedback_Tool_for_the_New_Primo_UI
    "Note: Only the en_US descriptions are supported for email labels, and no translations are provided if configured in the table."

    According to Production Management, implementation is not planned for the time being and we should raise an idea.
    So, please vote for this idea ;-)

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

11. Bulk search results export

    In a recent user survey, students provided feedback they would like the ability to export all or a large number of their search results. Currently they are limited to a maximum of 50 results at a time. Users reported they had worked to create a search strategy and were disappointed they could not obtain a full list of their search results, and were forced to move to searching individual databases instead.

    13 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

12. Hide collections

    Right now public Primo collections need to be deleted in order to hide them from public view; correspondingly, if a collection is suppressed from Discovery when it is created, it cannot be unsuppressed. It would be useful to be able to simply hide and unhide collections easily, for things like making changes, or themed collections whose time have passed.

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

13. Fulfillment Network - Restrict the ordering of books from the other institution when there are books loanable in the home organization

    *This is for the Fulfillment Network, not AFN.
    We are in a small consortium, just two institutions. Now we are trying to use direct requesting function of the Fulfillment Network, not AFN. In this case, we found that there is no option which restricts the ordering of books from the other institution when there are books loanable in the home organization.

    13 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Person Entity - Ability to Opt Out from Wikidata

    We propose adding an option to opt out of using Wikidata as a data source for the Person Entity feature in Primo at the institution level and the individual entity level.

    We have received complaints that the data provided by Wikidata for the Person Info Card and Person Page is incorrect or misleading for certain individuals. Currently, the only way to address these issues is by editing the Wikidata entries directly, which is not a sustainable solution and is dependent on the timeliness of weekly updates. To provide a recent example: we updated a Wikidata entry to correct the occupation data displayed for an individual. The new data was not reflected in Primo VE for several weeks. Ex Libris advised this may be due to further processing times from the Wikidata servers prior to their call data being updated.

    Justification:
    1. Updating Wikidata entries directly is not a sustainable solution and is also dependent on the timeliness of weekly updates.
    2. It takes several weeks before updated data is reflected in Primo VE.
    3. Reliability of Wikidata where everyone can update it.
    4. Relying on complaints is not the right approach and can/will lead to reputational damage to the institution.
    5. Manual workarounds can lead to technical debt.

    We propose adding an option to opt out of using Wikidata as a data source for the Person Entity feature in Primo at the institution level and the individual entity level.

    We have received complaints that the data provided by Wikidata for the Person Info Card and Person Page is incorrect or misleading for certain individuals. Currently, the only way to address these issues is by editing the Wikidata entries directly, which is not a sustainable solution and is dependent on the timeliness of weekly updates. To provide a recent example: we updated a Wikidata entry to correct the occupation… more

    13 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Being able to choose "emailing and printing exporting actions" fields

    The print and export options are currently limited.
    It would be a lot of help if we could choose the fields that are being exported to excel (or at least add the location field there), and which are being printed. Currently, in the print version there a lot of fields (all of the get it fields) and it takes a lot of space in a printed list for a patron. 4-5 pages for 15 results. The minimum is that there will be a long version and a short one to print, but better of if we could choose which fields to print or configure them up-front.

    The print and export options are currently limited.
    It would be a lot of help if we could choose the fields that are being exported to excel (or at least add the location field there), and which are being printed. Currently, in the print version there a lot of fields (all of the get it fields) and it takes a lot of space in a printed list for a patron. 4-5 pages for 15 results. The minimum is that there will be a long version and a short one to print, but better of if we could choose which fields… more

    13 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Research Assistant Usage Statistics

    Having activated the Proquest/Ebook Research Assistant capabilities it is good practice for institutions to be able to report on impact - has the functionality aided user access to material - increased length of time on site - increased usage of holdings. The FAQ state https://support.proquest.com/s/article/ProQuest-Research-Assistant-FAQs?language=en_US
    Q: Are there usage report that I can download to view usage of the Research Assistant at my institution?

    A: Currently we do not provide a report that libraries can download to assess usage of the Research Assistant at their institution. We are looking at the possibility of adding such reports to the ProQuest Administrator Module in the future but we do not have a timeframe for the availability of these reports yet. We will update this FAQ document as soon as we have a release date for the reports.

    Clarity on the timeframe?

    Having activated the Proquest/Ebook Research Assistant capabilities it is good practice for institutions to be able to report on impact - has the functionality aided user access to material - increased length of time on site - increased usage of holdings. The FAQ state https://support.proquest.com/s/article/ProQuest-Research-Assistant-FAQs?language=en_US
    Q: Are there usage report that I can download to view usage of the Research Assistant at my institution?

    A: Currently we do not provide a report that libraries can download to assess usage of the Research Assistant at their institution. We are looking at the possibility of adding such reports to the ProQuest Administrator… more

    13 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  ·  Analytics  ·  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. Copy text from digital viewer

    When reading documents in the digital viewer, it would be nice to have the ability to copy text directly from the page. You can do this if you download the document. I was attempting to do this with a larger file that mentioned other reports I wanted copy the name of a report to view/search for in the catalogue; however, the digital viewer does not allow users to select text from the document.

    13 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Create a facet for Abstracts (or Conference Abstracts)

    Abstracts are currently classified as Journal Articles, which causes confusion as readers are expecting to be able to read the full text of a published article that does not exist. Creating a facet for Abstracts would allow them to be correctly classified and would improve the user experience

    12 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

19. Give more weight to PMID in one-word PMID searches [Primo VE]

    In Primo VE, if a user wants to search for an article with a one-word PMID search (such as 22878467), the search will also match to articles in a journal with the ISSN 2287-8467, due to ISSN fuzzy matching. The issue arises in the brief result listing: currently the ISSN is given more weight than the PMID, pushing the relevant result to the very end of the list.

    In the above mentioned case, the user gets 18 results in total where the 18th is the one the user is interested in. Everything before it are articles from the journal with the ISSN 2287-8467: https://helka.helsinki.fi/discovery/search?query=any,contains,22878467&tab=DefaultSlotOrder&search_scope=CentralIndex&vid=358UOH_INST:VU1&lang=en&offset=10

    Another wilder example, where the PMID result is the 228th out of 229 results: https://helka.helsinki.fi/discovery/search?query=any,contains,22879099&tab=DefaultSlotOrder&search_scope=CentralIndex&vid=358UOH_INST:VU1&lang=en&offset=220

    If PMID could be given more weight when the ISSN is fuzzily matched, I reckon the relevant result would be the first one, thus making the process better for the user.

    edit:

    Alternatively, allow us to opt out from fuzzy matching for ISSN.

    In Primo VE, if a user wants to search for an article with a one-word PMID search (such as 22878467), the search will also match to articles in a journal with the ISSN 2287-8467, due to ISSN fuzzy matching. The issue arises in the brief result listing: currently the ISSN is given more weight than the PMID, pushing the relevant result to the very end of the list.

    In the above mentioned case, the user gets 18 results in total where the 18th is the one the user is interested in. Everything before it are articles from the journal with… more

    12 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

20. Remove resource sharing links from records for electronic and print books, but not chapters

    It is currently not possible to create a GES or DLR that would prevent RapidILL resource sharing links from appearing on CDI records for electronic and print books. The only way to do so is by removing them from ALL books, which would also exclude the link from book chapters. "Exclude CDI ebooks" helps by removing some of these records from results, but there are exceptions with e-books in database type collections. This more granular functionality is highly needed, as requests for entire books cannot be granted through RapidILL and must be cancelled.

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