80 results found

1. Combining searches from search history into a new search

   My colleagues misses the functionality from our previous discovery system to combine searches in the search history list into a new search in an easy way, e.g. S1 AND S3

   95 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…)
   26 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
   AdminYael (yael.shahar@clarivate.com, Ex Libris) responded

   This is currently not planned to be developed. We might evaluate it again in the future.

   Currently we are removing the "Under review" status.

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

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

4. new option/checkbox: "expand my results with synonyms"

   The Primo Search Engine includes synonyms by default to expand the result list. This often leads to results which are fuzzy and hardly explainable.

   Instead of including synonyms by default we want to see an option to include synonyms by explicit user decision.

   This option ("expand my result using synonyms") could be included into the facets section or should be visible close to the search button.

   77 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

5. "Remember all filters" should be selected by default

   We want "Remember all filters" to be selected by default. It confuses our users who expect that their filters will remain while they change their search, only to find that they had to click "Remember all filters" first. We'd rather them have to de-select "Remember all filters" if there's a reason they don't want to retain them in their searching.

   Relates to https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/34854556-make-facets-sticky-by-default-for-the-session, where the "default" part was never instituted.

   76 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

6. Natural language search in NDE should support customized local resource types

   Some of our consortium members who are testing Primo NDE have discovered that our custom resource types do not work with Ask Anything (the natural language search) in Primo NDE. For example:

   The search "i need print books about water" returns only ebooks. Due to our custom "print books" resource type, only e-books remain in the OTB "books" resource type in Primo.

   The search "i need audiocassettes on bach" returns only audio CDs, as we have custom resource types for other audio formats (audiocassettes, lp records, etc.).

   The search "i need videocassettes on figaro" returns only streaming videos, as we use custom resource types for physical video formats (videocassettes, DVDs, Blu-Ray, etc.).

   In general, none of the custom resource types is selected - instead, the natural language search appears to default to the OTB resource types (if there is one).

   Users who interact with our catalogs on a daily basis are used to seeing resource type labels that are often customized to our collections. So it's understandable that they will use those resource type names in their natural language searches. NDE's natural language search should be able to transform those phrases into searches for the accurate resource type - especially since the customized resource types appear in (working) facets that are available for Primo users who are not employing natural language search.

   Some of our consortium members who are testing Primo NDE have discovered that our custom resource types do not work with Ask Anything (the natural language search) in Primo NDE. For example:

   The search "i need print books about water" returns only ebooks. Due to our custom "print books" resource type, only e-books remain in the OTB "books" resource type in Primo.

   The search "i need audiocassettes on bach" returns only audio CDs, as we have custom resource types for other audio formats (audiocassettes, lp records, etc.).

   The search "i need videocassettes on figaro" returns only streaming videos, as we… more

   72 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  ·  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. Optimize call number Advanced Search

   Currently you can conduct an advanced call number search, but there are a few issues with it:

   -It doesn't properly search the entry as a call number like the Browse function does. It treats it like a regular word which results in severely incomplete results. For example, if I do advanced search > call number > contains > MT, I receive 90 results, though we have 3,578 items with call numbers that begin with MT.

   -The only way to see a mostly accurate number of holdings is to search partial numbers + an asterisk. For example, MT* returns most of our 3,578 items. Most users would not think to search with an asterisk.

   -When limiting an Advanced Search by Call Number, the only limiters available are Contains and Is(exact). Starts With appears to be an option until you click on it, and then Call Number changes to Title which becomes unavailable to change. Starts With would be the best and most logical limiter for users for a call number search, but it's not available.

   -The Contains limiter does not appear to function correctly. For example, I receive results when searching Advanced Search > Call number > Contains > M1003 .H64, but no results when I search M1003 .H.

   (I submitted ticket 00523629 regarding these requests, and was advised to post them to the Idea Exchange.)

   Currently you can conduct an advanced call number search, but there are a few issues with it:

   -It doesn't properly search the entry as a call number like the Browse function does. It treats it like a regular word which results in severely incomplete results. For example, if I do advanced search > call number > contains > MT, I receive 90 results, though we have 3,578 items with call numbers that begin with MT.

   -The only way to see a mostly accurate number of holdings is to search partial numbers + an asterisk. For example, MT* returns most of… more

   71 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  ·  User Functionality  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Displaying the pre-filters used, as the used facets are dispalyed

   It would be very useful to display the pre-filters used in Primo New UI (from both simple search screen - as of May release and advanced search screen). Pre-filters used should be displayed in the brief results list just as the facets used are displayed, at the top of the column. Thus the patron can always see and be aware of all the active filters in the session

   62 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

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

9. Reconcile top-level facet selection (one by one vs. multiple)

   Currently, if you select top-level facets one by one (e.g. "Peer-reviewed Journals" then "Full Text Online"), you get different results than if you select both facets at once (using the checkboxes and clicking "Apply Filters".) The first applies a boolean AND and the second applies a boolean OR.

   Ex Libris support has confirmed that this intended and expected behavior.

   This functionality seems confusing to both our patrons and staff. I think I can see the argument if this occurs within certain other facets (e.g. Resource Type), but because this happens with top-level facets that do not otherwise seem like the same sort of facet (e.g. "Peer-reviewed Journals" and "Full Text Online"), our patrons and staff have been finding this to be unexpected behavior.

   Requesting that this functionality be revisited, especially when it comes to top-level facets.

   Currently, if you select top-level facets one by one (e.g. "Peer-reviewed Journals" then "Full Text Online"), you get different results than if you select both facets at once (using the checkboxes and clicking "Apply Filters".) The first applies a boolean AND and the second applies a boolean OR.

   Ex Libris support has confirmed that this intended and expected behavior.

   This functionality seems confusing to both our patrons and staff. I think I can see the argument if this occurs within certain other facets (e.g. Resource Type), but because this happens with top-level facets that do not otherwise seem like the… 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…)
   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

10. Primo does not work with some date formats used for old material and rare books.

    Primo does not work with some date formats used for old material and rare books. The biggest problem is that Primo only recognises 4-digit dates and does not accommodate date searches for pre-1000 dates that have 3 digits or less. This issue greatly inhibits searches for a significant number of users of archives and rare material collections.

    Primo also does not work well with dates in square brackets that include text and unknown dates that have a question mark or dash instead of the wildcard character ‘u’ - e.g. [i.e. 1973], [between 1772 and 1802?], 195? or 195-. These are all valid date formats that follow international bibliographic standards and are frequently found in bibliographic records. It would be beneficial to our users if these issues could be addressed and fixed.

    Primo does not work with some date formats used for old material and rare books. The biggest problem is that Primo only recognises 4-digit dates and does not accommodate date searches for pre-1000 dates that have 3 digits or less. This issue greatly inhibits searches for a significant number of users of archives and rare material collections.

    Primo also does not work well with dates in square brackets that include text and unknown dates that have a question mark or dash instead of the wildcard character ‘u’ - e.g. [i.e. 1973], [between 1772 and 1802?], 195? or 195-. These are… more

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

11. Alternative Coverage & Newspaper Search in PCI/CDI

    We rely on PCI alternative coverage for maintaining the best discovery layer as this enables full text access to results obtained from known-item searches and topic searches. Using both PCI alternative coverage and the Newspaper Search together present challenges. Using both of these options together result in too many false positives; false positives disappoint users and erode their trust in our discovery system.

    Please consider including the Newspaper Search with the regular Primo Central updates that are compared against our institutional electronic holdings file so the Availability statements are correct. As we look ahead to the introduction of CDI, please consider including the Newspaper Search with the regular CDI updates in comparison against our institutional electronic holdings file as well.

    We rely on PCI alternative coverage for maintaining the best discovery layer as this enables full text access to results obtained from known-item searches and topic searches. Using both PCI alternative coverage and the Newspaper Search together present challenges. Using both of these options together result in too many false positives; false positives disappoint users and erode their trust in our discovery system.

    Please consider including the Newspaper Search with the regular Primo Central updates that are compared against our institutional electronic holdings file so the Availability statements are correct. As we look ahead to the introduction of CDI, please… more

    58 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  ·  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. Allow admin to select in what order Resource Types are displayed

    Currently the Resource Types can only be arranged alphabetically or by count (how often the type appears in search results). We would like to be able to preference certain types above others (for example, books, ebooks, articles...over things like Text Resources. So that for any search, the Resource Types are always arranged the same way and in a way that is most helpful for users.

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

13. List of Stop Words in Catalan

    Alma/Primo clients in Catalan cannot use the Full Text Indexing utility in Primo VE with all its functionality because there is no Stop Word List implemented in Catalan.

    Because of this and the 10,000 terms limit per indexed file, the included PDFs are not fully indexed.

    https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/Go_VE/Step_3%3A_Configuration/040Go_VE%3A_Converting_Primo_Data_Configuration_to_Primo_VE/060Go_VE%3A_Full_Text_Indexing_in_Primo_VE

    We are 17 university libraries and a national library (Biblioteca de Catalunya) that form part of the University Union Catalogue of Catalonia (CCUC); 2 university libraries from València (Universitat Jaume I and Universitat d’Alacant); and 62 collaborative institutions with special libraries.

    We contribute to the visibility of more than 12 million documents and resources.

    We need Full Text Indexing utility in Primo VE to work with a list of Catalan stop words.

    List:

    ---

    on aqui alla alli dins fora sobre sota davant darrere rere amb sense contra en entre a de des per
    quan aleshores abans despres durant mentre ja encara
    com aixi tambe tampoc si no i o ni pero perque nomes potser
    que aixo allo quelcom aquest aquesta aquests aquestes aquell aquella aquells aquelles algun alguna alguns algunes altre altra altres mateix mateixa mateixos mateixes
    qui quin quina quins quines qual quals ell ella ells elles se hi ho ne li lo la les los jo nosaltres vosaltres me em nos vos
    quant tan tant tanta tants tantes poc poca pocs poques molt molta molts moltes tot tota tots totes
    un una uns unes el la els les al als del dels seu seva seus seves teu teva teus teves meu meva meus meves
    es eren fou foren sigui siguin seria serien estar esta estan estava estaven haver ha han havia havien tenir tenen tenia tenien sembla semblen
    --/--

    Alma/Primo clients in Catalan cannot use the Full Text Indexing utility in Primo VE with all its functionality because there is no Stop Word List implemented in Catalan.

    Because of this and the 10,000 terms limit per indexed file, the included PDFs are not fully indexed.

    https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/Go_VE/Step_3%3A_Configuration/040Go_VE%3A_Converting_Primo_Data_Configuration_to_Primo_VE/060Go_VE%3A_Full_Text_Indexing_in_Primo_VE

    We are 17 university libraries and a national library (Biblioteca de Catalunya) that form part of the University Union Catalogue of Catalonia (CCUC); 2 university libraries from València (Universitat Jaume I and Universitat d’Alacant); and 62 collaborative institutions with special libraries.

    We contribute to the visibility of more than 12 million documents and… more

    53 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

14. Sort purchase requests in Primo, by newest

    It would be really helpful if user were able to sort their purchase requests in Primo by purchase-request creation date newest. Now Primo shows their purchase requests sorted by oldest, normally the user wants to see the follow up of the most recent.

    53 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

15. Article level records from Alma should populate resource sharing form correctly

    Article records from CDI will populate the Primo VE resource sharing form correctly, as a document delivery option for when there is no full-text available.
    However, when it comes to article level records from Alma, the Journal title is incorrect (instead, the article title is entered into this field) and other information is missing, like publication year, volume, etc. Overall the article is not recognized in the Context Object as an article, but instead treated as a journal - thus omitting all fields not relevant to a journal record.
    Example:
    
    1 - Go to: https://kbdk-kgl-psb.primo.exlibrisgroup.com/permalink/45KBDK_KGL/1pioq0f/alma99124396529705764. See that the resource type is Article (this is expected) in the brief results and in the full display.
    2 - Check the PNX and see that in the adddata section that:
    format = journal
    genre = article
    atitle = High-protein diet during pulmonary rehabilitation in patients with chronic obstructive pulmonary disease
    jtitle = Danish medical journal [online]
    3 - However, when you check the CTO:
    rft.stitle > High-protein diet during pulmonary rehabilitation in patients with chronic obstructive pulmonary disease
    rft.jtitle > High-protein diet during pulmonary rehabilitation in patients with chronic obstructive pulmonary disease
    rft.genre > journal
    rft.object_type > JOURNAL
    4 - See the following screenshot of the resource sharing form: the Journal Title is incorrect and other information like the publication year, volume is not included.
    https://www.screencast.com/t/rA9G9rcuh

    This has of course been reported as a defect (case # 06707109), but is deemed by ExLibris to be an enhancement request.

    Article records from CDI will populate the Primo VE resource sharing form correctly, as a document delivery option for when there is no full-text available.
    However, when it comes to article level records from Alma, the Journal title is incorrect (instead, the article title is entered into this field) and other information is missing, like publication year, volume, etc. Overall the article is not recognized in the Context Object as an article, but instead treated as a journal - thus omitting all fields not relevant to a journal record.
    Example:
    
    1 - Go to: https://kbdk-kgl-psb.primo.exlibrisgroup.com/permalink/45KBDK_KGL/1pioq0f/alma99124396529705764. See that the resource… more

    53 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

16. Add a pre-filter for Peer-reviewed Journals

    Our students would like the option to pre-filter their searches to articles published in Peer-reviewed journals. The current Primo configuration only allows this filter as a refining facet after searching.

    51 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

17. Ability to share favorites

    We'd like to see a more robust favorites area, with more options for configuration. One thing in particular we'd like would be the ability to organize lists of favorites, then to share those with other users. This has been brought up by librarians who'd like to work on lists collaboratively and then share those lists with students or instructors.

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

18. "Did you mean" has no option for selecting, "No."

    A librarian submitted the following question:

    "If you do a search in the catalog for Andrew Lyght (he's an artist), you get the message "Do you mean Andrew Light?" and a whole bunch of results that have lyght spelled "light". There is no option to say "No, I mean Lyght."

    I think the Google-like functionality of "did you mean..." is a good
    direction to go in, but there needs to be an option to respond to that question, especially when what the catalog is guessing is wrong. Overall, this isn't a helpful implementation as it currently works."

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

19. Combine permalinks with citations in Primo

    In Primo, the ability to copy citations is very useful, as is the ability to copy permalinks for individual records. When helping a patron via virtual reference (chat or email), it is cumbersome to, first, open and copy the citation, and second, open copy the permalink. It would make more sense to either hyperlink the citation with a stable link, or include the permalink after the citation in the same window.

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

20. Do not interpret words in phrase searches as Boolean operators

    At ETH Library, we use UDK classification. The UDK notations are always in capital letters, and some contain words as “AND” or German “UND”. “AND” and “UND” are defined as Boolean operators in our Primo VE. This leads to the following problem: when a user clicks on an UDK notation that contains such a word (e.g. on “PFLANZEN + BÄUME + BLUMEN (MOTIVE IN KUNST, LITERATUR UND FILM)” in this record: https://eth.swisscovery.slsp.ch/permalink/41SLSP_ETH/lshl64/alma990015558430205503), a search for “subject equals exact phrase” in the advanced search is triggered. Although a phrase search is performed, the word UND is interpreted as a Boolean operator, and therefore the search returns 0 results.
    We think that the search in Primo VE should be improved so that no word in a phrase search is interpreted as Boolean operator. Since it is not possible for a phrase to contain a Boolean operator, the current search behavior is a bug and should be fixed.

    At ETH Library, we use UDK classification. The UDK notations are always in capital letters, and some contain words as “AND” or German “UND”. “AND” and “UND” are defined as Boolean operators in our Primo VE. This leads to the following problem: when a user clicks on an UDK notation that contains such a word (e.g. on “PFLANZEN + BÄUME + BLUMEN (MOTIVE IN KUNST, LITERATUR UND FILM)” in this record: https://eth.swisscovery.slsp.ch/permalink/41SLSP_ETH/lshl64/alma990015558430205503), a search for “subject equals exact phrase” in the advanced search is triggered. Although a phrase search is performed, the word UND is interpreted as a Boolean… more

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