1103 results found

1. Library Card page

   I think it would more user-focused if the "Library Card" dashboard listed all of the requests and loans in one spot, regardless of the lending library. Many users are unaware of which library they've requested an item through - it would be nice if there was only one dashboard for patrons to check on the status of everything in one spot.

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

   Thank you for this idea. We are currently reviewing it and discussing it also with the Alma team.

2. Remove CDI constant expansion of results

   PCI results respect that a user knows what they want, but help with expansion when necessary, such as by stemming when there are very few results returned by the exact query. A user has autonomy also to target their results with techniques such as quotation marks, Boolean operators, and Advanced Search.

   In CDI, expansion is constant, by term inflection applied to all searches, as well as higher recall in general by design. This cannot be prevented by features such as Boolean operators, quotation marks or Advanced Search, and is illogical in conjunction with other features like 'Did you mean'.
   Note: It is recognized that these may represent different underlying mechanisms, but it is the user outcome which is key.

   Ex Libris states that CDI behaviour "does not affect precision" because of Verbatim Match Boost, which will rank more highly the exact search query, but they have designed this as also meaning "near verbatim", completely undermining this concept.

   Use case: If a user searches for ATLA, then they expect only results for ATLA and not atlas. CDI returns 7 of 10 first page results which are clearly returned on the basis of atlas by term highlighting, even at No.1, and yet also offers a "Did you mean: atlas", which barely changes the results when clicked.

   Use case: If a user searches for a DOI, then they expect only that specific resource. CDI returns dozens of results with often no indication by term highlighting or snippets to explain why. This is discovered only after a timeconsuming check on the full text to be because the DOI is in the Reference List. There is no clear pathway to the actually correct known item, and this is not consistently fixed just by ranking changes. For example, if we do not hold that article in full text, the user sees dozens of results, none of which are correct, instead of the expected pathway of the Zero results message, using the expansion checkbox, and then leveraging the metadata in the 'No full-text' citation to prefill an ILL form.

   This is the opposite of precision.

   The design should centre the user and the needs they directly express when entering their search query, allowing the choice to both target their search by the techniques above, as well as giving the option of expanding their search, which is even more important given the larger CDI index.
   One option could be returning the expected targeted results matching the user query, and then offering a suggestion similar to a clickable Did you mean or Controlled Vocabulary features, such as: "Results also referencing [query]"

   PCI results respect that a user knows what they want, but help with expansion when necessary, such as by stemming when there are very few results returned by the exact query. A user has autonomy also to target their results with techniques such as quotation marks, Boolean operators, and Advanced Search.

   In CDI, expansion is constant, by term inflection applied to all searches, as well as higher recall in general by design. This cannot be prevented by features such as Boolean operators, quotation marks or Advanced Search, and is illogical in conjunction with other features like 'Did you mean'.
   Note:… more

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

3. Possibillity to add print journal holdings to Primo holdings-file

   In Primo only the electronic holdings for e-books and e-journals are taken into consideration when determining the availability for a record/article from the central index (PCI/CDI).

   The libraries also have print/physical holdings of journals that can fulfill the needs of the end-user and that can fill gaps in the electronic coverage. If the user search for an article that the library only has as part of the physical journal holdings the availability of the article are set to "Not available" and dependig on the configuration the article might not even show up in the result-list.

   This has been adressed in another Idea:
   https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/19965871-physical-holdings-should-be-considered-in-determin

   This idea has the status of "Already supported", but it is only supported by Primo VE and in my opinion (based on the comment from Ex Libris) does not completely solve the intention of the idea.

   I understand that it might be difficult to automatically extract the correct coverage based on the existing data for the print journals.

   I therefore ask that Ex Libris provides an option/function in Alma to either upload a file in a given format with the coverage of print journals, or some other way to structure the coverage of a print journal. I believe that this was an option in SFX earlier.

   This information must then be added to the Primo holdings file and be used to determine the availablity of an article for the central index.

   This must be supported for all Primo versions and not only Primo VE.

   In Primo only the electronic holdings for e-books and e-journals are taken into consideration when determining the availability for a record/article from the central index (PCI/CDI).

   The libraries also have print/physical holdings of journals that can fulfill the needs of the end-user and that can fill gaps in the electronic coverage. If the user search for an article that the library only has as part of the physical journal holdings the availability of the article are set to "Not available" and dependig on the configuration the article might not even show up in the result-list.

   This has been adressed in… more

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

4. Display related holdings for monographs only for the 773 $w relation and not for the 8xx $w relation

   When filtering to a certain location via facets, you often get results from other locations too, which is unexpected from patrons perspective in many cases. This is caused by the current related records setting which is also taking locations with related records into account. The display is correct for analytical records without inventory (book chapters and articles), but not for the other monographical resources.

   What we wish to achieve is the following:

   When the record of a book chapter, journal issue or journal article (i.e. a record containing a 773 field with $w) is viewed in Primo, the holding of the record linked via 773 $w is displayed.

   When records contain a series link (8xx $w) or a related record (76x/77x/78x $w - exception: 773), we do wish to display a link to the related record (via system number), but not the related holding.

   Right now, the configuration does not offer the needed flexibility.

   When filtering to a certain location via facets, you often get results from other locations too, which is unexpected from patrons perspective in many cases. This is caused by the current related records setting which is also taking locations with related records into account. The display is correct for analytical records without inventory (book chapters and articles), but not for the other monographical resources.

   What we wish to achieve is the following:

   When the record of a book chapter, journal issue or journal article (i.e. a record containing a 773 field with $w) is viewed in Primo, the holding of… more

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

5. Improve indexing of in press articles in CDI

   The Central Discovery Index (CDI) includes many in press articles (i.e., articles that have been accepted for publication in a future issue). However, because these records do lack a pub date, volume, or issue number, the Alma link resolver cannot reliably determine whether an institution has access to these articles. We ask that Ex Libris improve they way in press articles are indexed in CDI so that the link resolver does not return false positives for content the library does not actually own.

   Example: https://www.screencast.com/t/iZ2jjOgWgC6v

   476 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Enable search and browse also for item call numbers, not only holdings

   Hi

   We switched to Primo VE some months ago and are really missing a call number index that shows all our call numbers, in items as well as in holdings.

   https://slidetodoc.com/three-types-of-call-numbers-in-alma-yoel

   "Item Call Number – is it in Primo VE search indexes?
   • The item call number cannot be added as a Primo VE search index.
   • Of the three call numbers only the “Holding Call Number” can be added as a Primo VE search index."

   Our call number index is set to "callnumber.4 – Shelving control number call number", our item call numbers are type 4, but they are missing in the call number index.

   https://basel.swisscovery.org/discovery/browse?vid=41SLSP_UBS:live

   ---

   Examples:

   https://slsp-ubs.primo.exlibrisgroup.com/permalink/41SLSP_UBS/mmbbsj/alma9920741170105504

   No hit in call number index search for
   UBH Bc I 50
   UBH Bc I 51
   UBH Bc I 52

   ---

   https://basel.swisscovery.org/permalink/41SLSP_UBS/mmbbsj/alma9910081250105504

   Can not be found in the call number index under UBH AL VII 42:1993

   ---

   We know that it can be done in Alma (see screenshot), but we need the function also in Primo.

   ---

   In addition to the index search, please also index the item call numbers for simple and advanced search.

   Hi

   We switched to Primo VE some months ago and are really missing a call number index that shows all our call numbers, in items as well as in holdings.

   https://slidetodoc.com/three-types-of-call-numbers-in-alma-yoel

   "Item Call Number – is it in Primo VE search indexes?
   • The item call number cannot be added as a Primo VE search index.
   • Of the three call numbers only the “Holding Call Number” can be added as a Primo VE search index."

   Our call number index is set to "callnumber.4 – Shelving control number call number", our item call numbers are type 4, but they are… more

   •  

   453 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

7. Primo VE: Allow Exclusion of Institution Zone only records from Discovery Network/NZ Scope

   In consortial environments, the Network Scope includes Institution Zone only records such as laptops, keys, etc.

   We would like the capability to exclude IZ only records from a Discovery Network scope so that we can display only records that are NZ bibs, not local IZ with no NZ bibs.

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

8. Allow reader to sort the values in a facet by A-Z or by number of records.

   Most databases such as Web of Science or Ebsco Discovery tool allow the user to determine how to sort the values in a facet (see screenshot)

   •  

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

9. Primo VE: Ability to use norm rules to specify which 856 (Marc) fields display in Links service

   In Primo Back Office (BO), it is possible to use normalization rules to specify which 856 Marc fields display in the "Links" section of the Primo full record view. (See attached screenshot.)

   We would like the same functionality in Primo VE to choose which 856 links to display based on the 856 first and second indicators and/or the subfields of the 856 field. Thank you.

   •  

   331 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…)
   16 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
   Under Review  ·  AdminNili Natan (Product Manager, Ex Libris) responded

   Thank you posting this idea. Moving it to under review for further analysis.

10. Improve Primo Search Algorithms

    When our users look for a book in the Primo Search Portal they expect that the Primo Search behaves like a Google Search, i.e. they expect that Primo finds books with titles or metadata containing words similar to those in their query. Unfortunately, the Primo Search is very sensitive to the exact spelling of the words in the query. If the search query is slightly inaccurate, the book is not found in Primo. I tried such unsuccessful search queries on www.amazon.de, and Amazon usually found the correct book: Amazon showed the correct hit on top of the list (see attachment). This shows that the search algorithms of Amazon are clearly superior to those of Primo. I feel that Ex Libris should take steps to keep up with modern search technologies.
    Some, but not all, of Primo’s shortcomings seem rather easy to fix. Primo fails to take word flexions in non-English languages into account. Since the endings of German words not only depend on plural and singular but also on the context, Primo’s search results for German queries are overly sensitive to word flexions. However, some of the English examples indicate that improving Primo’s dictionaries will not be sufficient. Over the long term, ExLibris may consider to team up with a specialized search provider.

    Similar proposals in ExLibris idea exchange
    https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/37586617-increase-primo-search-capability-to-support-major
    https://ideas.exlibrisgroup.com/forums/564566-summon/suggestions/17415091-automatically-searching-for-the-corrected-spelling

    When our users look for a book in the Primo Search Portal they expect that the Primo Search behaves like a Google Search, i.e. they expect that Primo finds books with titles or metadata containing words similar to those in their query. Unfortunately, the Primo Search is very sensitive to the exact spelling of the words in the query. If the search query is slightly inaccurate, the book is not found in Primo. I tried such unsuccessful search queries on www.amazon.de, and Amazon usually found the correct book: Amazon showed the correct hit on top of the list (see… more

    • 

    330 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Ability to edit the OTB (Out-of-the-Box) search and facet rules in Primo VE

    We would like to be able to edit the OTB search and facet rules. This is necessary for parity with PBO. There are several things that we were able to do in PBO that we cannot reproduce in VE because of the lack of this functionality. In the PBO OTB author search and facet, we were able to include dates and qualifiers from names in the LCNAF, which improved precision. In the OTB language facet, we were able to include intertitle, caption and audio description languages, which are not currently included in the VE OTB index. On the other hand, we excluded languages of accompanying material, which are currently included in the VE OTB language index. We were able to limit the OTB subject facet to specific vocabularies, such as LCSH. This improved the usefulness of the subject facet because it removed near duplicates and non-English headings. This meant that users got a more helpful variety of terms within the top twenty facets. For subjects, ideally we would be able to do different things with the OTB search index and the OTB facet index, as was possible in PBO. In PBO, we included a larger number of vocabularies in the search index than we did in the facet index.

    We would like to be able to edit the OTB search and facet rules. This is necessary for parity with PBO. There are several things that we were able to do in PBO that we cannot reproduce in VE because of the lack of this functionality. In the PBO OTB author search and facet, we were able to include dates and qualifiers from names in the LCNAF, which improved precision. In the OTB language facet, we were able to include intertitle, caption and audio description languages, which are not currently included in the VE OTB index. On the other hand,… more

    328 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Make consistent the use of CDI record data in Primo UI

    Current CDI design in Primo UI is to expose metadata from all participant records for both returning results from a search query, and in the values presented for selection in facet for filtering results, but the display of metadata within records is only by site-specific activations.
    This means that a user can search for a term in Primo, have results returned on the basis of that term, select the value for the term in a facet, but then not see the term in the record display.

    The negative impact of this design decision includes:
    * a user is confused by the Primo results list, as there is no indication as to why results were returned, even when the user has specifically targeted data such as an Advanced Search by a specific subject that is then nowhere to be found in the records displayed
    * a user can't effectively filter results by facets, because when they do so and look at the records, they can see no relationship between their actions and the resulting records
    * a user can't take advantage of lateral links, to generate an Advanced Search query of all the entries for the search term to expand their initial results set, such as all records in a specific subject, because there is no lateral link displayed in the record
    * a user is missing key data when exporting by RIS to EndNote, RefWorks, BibTex etc, such as keywords not included, as well as this information not being included in other Send to options of Export to Excel, Print, and Email

    Ex Libris design should be reviewed and made holistic and meaningful, to either:
    1. Hide all the data ie if data is hidden from display, it should also be hidden from search and facets (and any other elements)
    2. Show all the data ie if data is used in search and facets, then it should also be shown in display

    Current CDI design in Primo UI is to expose metadata from all participant records for both returning results from a search query, and in the values presented for selection in facet for filtering results, but the display of metadata within records is only by site-specific activations.
    This means that a user can search for a term in Primo, have results returned on the basis of that term, select the value for the term in a facet, but then not see the term in the record display.

    The negative impact of this design decision includes:
    * a user is confused by… more

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

13. Search Slot/Scope/Profile Usage in Primo Analytics

    We would like to be able to report the total number of searches that have been performed in each search/slot/scope/profile that we have configured in Primo. Currently the only report in Analytics that has Search Scope search information is the Zero Results Report.

    This information will provide invaluable information about our user behaviour and will help us in the customization of the Primo interface to meet the needs of our clients by assisting in decisions regarding adding or removing search profiles/scopes.

    294 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…)
    15 comments  ·  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

14. Do Not Highlight Stop Words in the Results of a Keyword Search

    There is no value to highlighting words in the search results of a keyword search that were considered STOP words when the search was conducted.

    Words such as AND, THE, OR, IN, TO, etc., provide no value on their own and should not be highlighted. Not only does highlighting them add visual noise to the search results, it sends the wrong message to users about how to construct a strong search string.

    As the screenshot shows, the highlighting is only adding noise.

    •  

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

15. course reserve

    Course Reserves:
    Requested Enhancement: Offer interface with drop-down menus for Course Title, Course Department, and Course Instructor (similar to drop-down menus in Voyager)

    Currently users can search for course reserves, but there is not a good mechanism to browse. Offering drop-down menus would easily allow users to see what was currently on course reserve by course title, department and instructor.

    Thank you for considering

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

16. Primo VE: Ability to search by publisher (advanced search or facet)

    The MARC 260b + 264b field is not included in the out-of-the-box indexing in Primo VE advanced search or facet as PUBLISHER. According to the documentation the publisher name is searchable only by general in the simple search and not in the advanced search, specific search for the publisher name. Readers want to limit the results by the name of the publisher.

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

17. Allow libraries to configure the Brief Record Display with more flexibility

    In the brief and full display pages, libraries can display information contained in data fields (such as the title, author, and creation date) from the source record. This information helps users to differentiate records quickly. In some cases, there can be a lot of information that is displayed. This is particularly the case when Contributor is added: all 7XX fields are added, and in their entirety (see for example in the attached screenshot).

    We would like an option that would allow the library to either limit the number of fields to display (for example max 3 7XX fields) or to only display fields based on the content of some subfields (for example: only display 7XX where $$e equals 'editor', 'publishing director ', 'translator', 'Director', 'film director'...).

    In the brief and full display pages, libraries can display information contained in data fields (such as the title, author, and creation date) from the source record. This information helps users to differentiate records quickly. In some cases, there can be a lot of information that is displayed. This is particularly the case when Contributor is added: all 7XX fields are added, and in their entirety (see for example in the attached screenshot).

    We would like an option that would allow the library to either limit the number of fields to display (for example max 3 7XX fields) or to… more

    •  

    268 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Primo Name/Title Browse Searches

    Primo Name/Title Browse Searches

    As frequent Primo users searching for known music items, the Alma Music Users Group would like to propose that Ex Libris create a left-anchored browse search for name/title entries found in bibliographic records. An alphabetical left-anchored browse search is particularly helpful for known-item searches that are often used for music materials and prolific literary authors.

    Currently, Primo provides browse search options for names (name portion only ($a,$q,$d)) and name/title headings used as subjects. For prolific authors, it is not unusual to find thousands of name/title headings lumped under the composers or authors name, with “20+ records” displayed adjacent to the heading. The Primo Browse Search options should include an alphabetical left-anchored “browse” listing for all name/title headings found in bibliographic records.

    The left-anchored browse name/title index search for authorized access points should include the subfields from the 700 name portion of the heading, as well as subfields from the 700 title portion of the heading ($t, $f, $m, $n, $r, $l, $k, $p, $o, $s), displayed in the order in which the fields are transcribed in the bibliographic authorized heading. The browse name/title index should also include the name/title information from the 100/240 fields, including the subfields from the 240 ($f, $m, $n, $r, $l, $k, $p, $o, $s), displayed in the order in which the fields are transcribed in the bibliographic authorized heading. In the event that the 100/240 combination cannot be included as the left-anchored browse search is developed, it is critical that these fields are added as soon as possible.

    In addition to a browse name/title search that retrieves results from the 7xx fields, the subject browse search should include name/title headings used as subject headings found in the 6xx fields.

    The browse indexes should display 4XX and 5XX cross-references and public notes such as the 680 found in authority records. Associated name and title strings must be kept together for both indexing and display. The cross-references are critical in helping the user to find items known by various titles in various languages. The 4xx and 5xx displays should be linked to redirect the patron to the appropriate section in the index.

    Benefit: Without a left-anchored browse search, there are too many false drops and omissions when searching for materials by prolific authors and composers. The left-anchored browse results in a more focused and complete search result, helping the user to quickly find all items with the same authorized access point.

    Attached is an optimal name/title display for the composer Georges Bizet.

    Primo Name/Title Browse Searches

    As frequent Primo users searching for known music items, the Alma Music Users Group would like to propose that Ex Libris create a left-anchored browse search for name/title entries found in bibliographic records. An alphabetical left-anchored browse search is particularly helpful for known-item searches that are often used for music materials and prolific literary authors.

    Currently, Primo provides browse search options for names (name portion only ($a,$q,$d)) and name/title headings used as subjects. For prolific authors, it is not unusual to find thousands of name/title headings lumped under the composers or authors name, with “20+ records”… more

    • 

    268 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

19. Can Ex_libris work with publishers to enable OA articles in hybrid journals to be discoverable ?

    Currently if we do not subscribe to a journal (normally a hybrid OA titles) which has open access articles the article access is not discoverable as available during a search of Primo - is there any way to identify these articles as being available ?

    265 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

20. Display 6XX fields with $v form subdivisions intact

    Primo VE is configured to map 6XX $v form subdivisions to a separate display field, breaking the subject string. In some cases, the form subdivision is plucked out of the 6XX, leaving the surrounding string incomplete. For example:

    600 10 $aO'Keeffe, Georgia, $d1887-1986 $vExhibitions
    displays in Primo VE as:

    Subject O'Keeffe, Georgia, 1887-1986

    Genre Exhibitions

    651 #0 $aRome (Italy) $vMaps $vEarly works to 1800
    displays in Primo VE as:

    Subject Rome (Italy)

    Genre Maps
    Early works to 1800

    And so on, for all 6XX $v form subdivisions. This cannot be reconfigured. Additionally, each occurrence of the form subdivision is displayed as a separate genre. An exhibition catalog with three artists appearing in 6XX fields would result in three genre term displays, all saying "Exhibitions".

    To preserve our subject string with form subdivisions intact, we were advised to consider adding a 9XX with the field as we want it to display and labeling that as Subject in Primo VE.This adds steps to cataloger workflow and generates unnecessary data in the records.

    This display feature should be reconsidered. Whether or not to split $v form subdivisions should at least be configurable by libraries.

    Primo VE is configured to map 6XX $v form subdivisions to a separate display field, breaking the subject string. In some cases, the form subdivision is plucked out of the 6XX, leaving the surrounding string incomplete. For example:

    600 10 $aO'Keeffe, Georgia, $d1887-1986 $vExhibitions
    displays in Primo VE as:

    Subject O'Keeffe, Georgia, 1887-1986

    Genre Exhibitions

    651 #0 $aRome (Italy) $vMaps $vEarly works to 1800
    displays in Primo VE as:

    Subject Rome (Italy)

    Genre Maps
    Early works to 1800

    And so on, for all 6XX $v form subdivisions. This cannot be reconfigured. Additionally, each occurrence of the form subdivision is displayed… more

    257 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close