679 results found

1. Open Access Indicator for Unimarc records

   Open Access Indication in Primo VE is currently supported for Marc21 and Dublin records : https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/030Primo_VE_User_Interface/Open_Access_Indication_in_Primo_VE
   Please support Unimarc record, too !

   134 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

2. Add more than 7 lines – Advanced searches only include a maximum of seven search criteria lines

   Could we have the capability to include more than seven lines in the advanced search function? In Summon, Web of Science and numerous other platforms, there is an unlimited possibility to select more lines.
   Given that our users frequently search using both Danish and English keywords, the seven-line limit is often reached when both languages are used in an 'OR' search.

   8 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

3. Primo default language

   When opening discovery, the language showed is the default one set in the Alma configuration. Many website today are capable to adapt the default language depending on the language set in the browser or the ip adress or other technologies.
   The current idea propose to investigate and eventually apply the technologies that allows an automatic adjustment of the primo default language.

   1 vote

   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  ·  Edit…  ·  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. Support for Numeric Subfields (e.g., $0, $1) in MARC to PNX Mapping in Primo VE

   Currently, numeric subfields such as $0 and $1 are excluded from Primo VE’s standard MARC to PNX mapping. This prevents institutions from displaying and passing on crucial metadata, such as authority IDs, in/from the Primo VE UI.

   Please map at least subfields $0 and $1 to PNX
   This would greatly benefit libraries that rely on authority control and linked data, ensuring that identifiers like VIAF and GND IDs can be used for enhanced metadata display and linking within Primo VE as provided for by the MARC standard .

   Use Case Example:
   A record with multiple subject headings (650 fields) includes corresponding $0 subfields containing GND IDs.
   Currently, these IDs are not accessible, meaning they cannot be displayed or linked to external authority services.
   With the proposed enhancement, institutions could properly map these identifiers to custom fields and improve metadata accuracy and display options.

   By mapping numeric subfields to PNX, Ex Libris would significantly enhance Primo VE’s ability to support linked data and authority control, aligning it better with modern metadata standards.

   Currently, numeric subfields such as $0 and $1 are excluded from Primo VE’s standard MARC to PNX mapping. This prevents institutions from displaying and passing on crucial metadata, such as authority IDs, in/from the Primo VE UI.

   Please map at least subfields $0 and $1 to PNX
   This would greatly benefit libraries that rely on authority control and linked data, ensuring that identifiers like VIAF and GND IDs can be used for enhanced metadata display and linking within Primo VE as provided for by the MARC standard .

   Use Case Example:
   A record with multiple subject headings (650 fields) includes… more

   26 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. Sort Favorites by Call Number

   Allow sorting of "My Favorites" by Call Number. Currently, you can only sort "My Favorites" by Date Added, Author, and Title.

   7 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  ·  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. Allow the resource type - " Trade Journals " as an option under Primo's Resource Types!

   Allow the resource type - " Trade Journals " as an option under Primo's Resource Types!

   10 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

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

8. Improve call number Browse search

   To improve the user experience in Primo VE, we propose modifying the call number browsing feature to show a few call numbers both before and after the searched call number, providing better context and making it easier to locate desired items.

   5 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

9. Provide option to remove 490 field from Browse Index

   We would like the option to remove the 490 series description field from the Browse index. Because we use 490 for series description and 8XX for the authorised form of series in the same record, the browse series feature in Primo counts one record twice. If we could have the option to remove this from the Browse index, this would solve the problem. It would need to be optional as it is clear that some Primo Libraries rely on the 490 for this purpose.

   22 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

10. Customize brief display of fees in user account - Primo VE

    On the overview page in the fees tile it displays 4 lines of information. If a user need more information they have to click on the entry to do so. One of the pieces of information in the drill down is if the fee was transferred to an outside entity such as bursars. Given there is a Pay Fees button even if transferred fees are present on this tab it would be nice to be able to have more lines display or at the least be able to order the display so what we feel is most important shows in brief display. That way with this easy to see designation and a relabel of the button (which we have done) users can know if fees can be paid using the button or if they should go somewhere else.

    On the overview page in the fees tile it displays 4 lines of information. If a user need more information they have to click on the entry to do so. One of the pieces of information in the drill down is if the fee was transferred to an outside entity such as bursars. Given there is a Pay Fees button even if transferred fees are present on this tab it would be nice to be able to have more lines display or at the least be able to order the display so what we feel is most important shows in… more

    •  

    •  

    4 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

11. Change CDI handling of Language data for Primo

    CDI Language data in handled in ways which have undesirable impact on patrons in Primo, such as:
    • A default language is applied to all records in a CDI feed for use in Primo in the Language field display, search, and facet. This may be done when the CDI provider feed has no record-specific Language information available automatically and the provider has not otherwise advised that all the records are in a specific known language and confirmed that this Language can be applied to the records in CDI
    • Records may be allowed to merge into a CDI logical record even when the Language data differs across participant records. All of the participant record Language values are then included in the Language facet bar ‘outlier’ languages stripped out, and then one Language value may be selected to display in the record according to library full text activations, even if it contradicts the Language facet value

    It is understood that the CDI is a massive index and that strategies such as collection level normalisation rules are necessary in order to manage this scale of data.
    However, it is feared that the experience of individual users is inappropriately de-prioritised and lost in these decisions focused on “acceptable” percentages of impact, which may seem tiny relative to the size of the index, but may be significant to actual people using our discovery layer.
    The practical reality is that such handling of Language information at a broad scale in CDI causes a negative impact for people using Primo, as the information is clearly incorrect and features cannot be used as expected.
    It may be argued that patrons are unlikely to encounter such issues on a regular basis, but this also ignores common knowledge of human nature that even one or two experiences of being presented with clearly false information is enough to build distrust in all future experiences.

    For example, the Language facet cannot be used when a patron is specifically trying to target results in a certain language, when they know in advance or learn from initial results that their search term may return records for multiple languages with different meanings.
    ISSUE
    “Persona” has different meanings in Spanish and English and the patron wants the English variation.
    STRATEGY
    With a search by “personas school principals” the patrons deliberately selects to include only the Language facet value of English and exclude the Language facet value of Spanish.
    BUT
    Ex Libris has applied Language facet value of English broadly as a default in the CDI provider feed and/or has artificially selected a Language from participant records to display in the record regardless of the Language in the facet.
    RESULT
    The patron sees in their results many records stating English when they are clearly in Spanish in both the metadata and full text.
    Examples (screenshots attached):
    • cdicrossrefprimary105944reopvol30num1201925194
    • cdiunpaywallprimary1014295idonlinev15i583330
    • cdijstorprimary_40654076
    OUTCOME
    This patron may then submit a complaint to the library or simply decide that their library provides a poor service and stops using our discovery layer in favour of other options.

    When opening a case to report such patron complaints with examples of unexpected incorrect information in Primo, it is advised that this behaviour is expected and that current handling was chosen over other options to mitigate the impact of insufficient provider CDI metadata in Primo.
    This could be by including a Language information in the records of ‘No linguistic content’ or ‘Undetermined’ to ensure a facet count matched to a result count, not allowing records to merge when there are Language differences, and not presenting Language facet values which do not match Language display values.

    Ex Libris considers it a “resolution” to such cases for defect reports to document this behaviour, shifting responsibility to their library customers to explain to complaining patrons.

    This approach focusing on quantity over quality does not centre the individual user as a person, and disregards the harm to the professional reputation of libraries, degrading the trust our patrons place in our services and which we are responsible to provide for our institutions, to support teaching, learning, and research.

    Now that such behaviours have been documented over time as “expected”, this issue moves from hope it is resolved as a defect, to a product enhancement request that Ex Libris change the current design decisions causing this problem.

    This submission requests that Ex Libris reconsider and change these practices with the individual user in mind, committing to align Language data across display, search, and facets and to consistently present only accurate Language information in the Primo discovery layer.

    CDI Language data in handled in ways which have undesirable impact on patrons in Primo, such as:
    • A default language is applied to all records in a CDI feed for use in Primo in the Language field display, search, and facet. This may be done when the CDI provider feed has no record-specific Language information available automatically and the provider has not otherwise advised that all the records are in a specific known language and confirmed that this Language can be applied to the records in CDI
    • Records may be allowed to merge into a CDI logical record… more

    •  

    1 vote

    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  ·  Edit…  ·  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. Improve Primo linking to limit dead/inaccurate links

    To prevent user confusion, frustration, and access delays, we would like Ex Libris' Primo to mirror a feature that LibKey calls "Entitlement Confirmation," which would help prevent delivering dead links to end users, especially when Metadata in the CDI is lacking or incorrect.

    Delays between publishing and availability, especially with third-party databases (like EBSCOHost), happen often and can vary in length due to the nature of aggregation. The proposed change would confirm if content is available before indicating to end users that it is. This saves user and staff time and effort, streamlining the process and managing expectations while providing exemplary service.

    To prevent user confusion, frustration, and access delays, we would like Ex Libris' Primo to mirror a feature that LibKey calls "Entitlement Confirmation," which would help prevent delivering dead links to end users, especially when Metadata in the CDI is lacking or incorrect.

    Delays between publishing and availability, especially with third-party databases (like EBSCOHost), happen often and can vary in length due to the nature of aggregation. The proposed change would confirm if content is available before indicating to end users that it is. This saves user and staff time and effort, streamlining the process and managing expectations while providing… more

    18 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

13. Disabling automatically generated links for related records if the associated NR is disabled.

    Primo VE is capable to automatically create links to related records via MARC 7xx fields.
    As these links where not working well for us, we were looking to turn them off with a NR, by setting “set pnx."display"."relation" to "N/A"” for 776 specifically.
    Unfortunately, this turned out not to work in all cases. As Ex Libris explained this is because
    - in the related records, they differentiate between child records and parent records
    - for child records, as the specific relation field is included, Display NR takes effect
    - for parent records, as the specific relation field is not included, and the opposite link is added automatically, Display NR cannot have any effect

    This means we can only disable links from child to parent records but not the other way around. What we would like to see is that, if a relation from a child to a parent record is supressed, the automatically added opposite link should also be supressed.

    Primo VE is capable to automatically create links to related records via MARC 7xx fields.
    As these links where not working well for us, we were looking to turn them off with a NR, by setting “set pnx."display"."relation" to "N/A"” for 776 specifically.
    Unfortunately, this turned out not to work in all cases. As Ex Libris explained this is because
    - in the related records, they differentiate between child records and parent records
    - for child records, as the specific relation field is included, Display NR takes effect
    - for parent records, as the specific relation field is not included,… more

    88 votes

    Vote 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

14. NZ/IZ linking in consortia

    Background: MARC 776 is used to establish a link between related records (Also available in another form:). If a link cannot be established, a title search is started instead.

    In a consortial environment, there is an issue with this: Primo VE is only able to establish a link if both the linking and the linked-to title are available locally. This happens because Primo depends on Alma functionality for related records to establish a link and Alma is building them within institution scope only (Network is considered just another institution in this regard). This means that as soon as only the linking title is available in an IZ, a title search will be started.

    To give an example: We have a journal with the main title “Recht” (Law), which links to an electronic version of the same title. In IZ that do not have the electronic version, a title search for Recht/law will be started instead, leading to over 27’000 results – from a link that promised to lead to a different version of the same title. See also pdf below.

    This behaviour makes 776 largely unusable for consortia, where it would be important for that our patrons are able to find resources that are not available locally as well or where we’d at least want a system that can recognize if something is locally available and only displays the link in this case.

    Background: MARC 776 is used to establish a link between related records (Also available in another form:). If a link cannot be established, a title search is started instead.

    In a consortial environment, there is an issue with this: Primo VE is only able to establish a link if both the linking and the linked-to title are available locally. This happens because Primo depends on Alma functionality for related records to establish a link and Alma is building them within institution scope only (Network is considered just another institution in this regard). This means that as soon as only the… more

    • 

    144 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

15. Author/Title Index in Browse Search

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

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. PressReader

    PressReader uses Webhook functionality to enable direct search of its content within Primo VE.

    In Brief Search Results the link displays as "check for available services'. This is not configurable (Salesforce #07245690).

    In the Full Record Screen the default text 'Link to Resource' is used.

    This is sourced from Links and General Electronic Services Labels.

    Can there please be a separate label, created specifically for PressReader, with text configurable by the library?

    Screenshots attached

    Thank you!

    • 

    3 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  ·  Edit…  ·  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. Add ability to display item status in locations list in Get It section

    Currently, the locations list displays a holdings summary for each location. To view the status of held items, users must click into each location's details. It would streamline the user journey if the item status (item in place, on loan, on order, etc.) could be displayed within the locations list itself, in addition to the holdings summary.

    1 vote

    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

18. Suppress blank yellow box in "View It" section

    Currently, when there are no online access links in the "View It" section on the full details page, a blank yellow box appears. Can this be suppressed when there are no links to display?

    We receive numerous problem reports each year from students who are confused. Thank you!

    •  

    3 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

19. Influence the algorithm in the display format for hits on large broad subject searches where local repository records appear.

    In our library we have decided that Primo should also display records from a local repository. This is a database of references to research publications produced by our researchers at our university. It is not always the case that we have electronic access to the titles in this local database. And it's not always the case that we own the physical works.
    So we would like to have the titles in our catalogue, but we are well aware that at best they are reference titles that have to be obtained/borrowed.
    We are planning to display more local repositories through our Primo (students' theses and the like).

    It would actually be super user friendly if we could influence the algorithm in the display format for hits on large broad subject searches where local repository records appear.
    Namely, that your own repositories that are available to Primo can be both prioritised and, most importantly, deprioritised in the display format.

    So we want to propose the idea that each individual library can control the display of its own local small repositories in Primo.

    In our library we have decided that Primo should also display records from a local repository. This is a database of references to research publications produced by our researchers at our university. It is not always the case that we have electronic access to the titles in this local database. And it's not always the case that we own the physical works.
    So we would like to have the titles in our catalogue, but we are well aware that at best they are reference titles that have to be obtained/borrowed.
    We are planning to display more local repositories through our… more

    9 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

20. Make "Subject is(exact)" a precision search that returns results based on exact subjects

    Currently in legacy Primo, a Subject is(exact) search returns items that do not have the specified terms in the visible records, but returns matches from the CDI metadata that is not presented in the record. For clarity of functionality, returning only results that include the specified terms would be preferable. (Similar to NERS 8871 which was focused on the Title fields.)

    (An alternative would be to increase transparency of results so that the CDI metadata that constitutes a match is visible to end users.)

    1 vote

    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  ·  Edit…  ·  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