681 results found

1. Set default of language in vocie search

   When in voice search using customized languages (not UI supported languages because it influences the language options in My Account) it is not possible to set a default language: https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/050Display_Configuration/010Configuring_Discovery_Views_for_Primo_VE#Defining_a_View
   I suggest it should be possible to set the default language of Voice Search (as once was possible in earlier versions of VE)

   •  

   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

2. "Peer reviewed" for academic books

   Currently, there is a limiter in discovery to "Peer-reviewed articles" but using this limiter does not bring results from books even by the most celebrated academic publishers. While this information arrives from vendors, there should be a way to search peer-reviewed publications that would exclude magazines but include both peer-reviewed journals and books (or book chpaters) by any academic press.

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

3. Ability to create URL redirects for deleted collections

   Alma offers institutions the ability to create collections to facilitate discovery and access to groups of related resources. In addition to being displayed on the Collections Lobby page, collections can be made accessible via direct links on websites, research guides, or course syllabi. However, when a collection is deleted, any links or bookmarks to that collection are broken. To avoid this, customers should have the ability to configure redirects for collection page URLs that can be used to route visitors to another page.

   Related documentation:

   https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/050Inventory/050Managing_Collections

   https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/130Configuring_Advanced_Search_Interfaces_for_Primo_VE/Configuring_Collection_Discovery_for_Primo_VE

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

4. Expand "full text"

   Currently "full text" is limited to first 65K characters of an article or of a complete [!] book (along with chapter abstracts only). Thus tweak results to full text is misleading. For articles, entering from google scholar may circumvent the problem partially. For books, true research now requires search full text (possibly not available or only available in snippet view) in google books for finding the required source and pages, then searching the discovery for the book for electronic access, similar to finding a physical book.
   True full text is strongly required.

   0 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

5. Do not index preprint articles in CDI until they are published

   Preprint articles are showing up in EBSCOhost collections via CDI records before the articles are published. This makes things confusing for users when they find an article that is not actually available yet.

   Please consider working with this provider to distinguish this content and/or not index them in CDI until the articles are published. Thank you!

   2 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  ·  Integration with other systems  ·  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. Articles not yet made available

   I would love to see some regulations or procedure set in place for articles not yet published from being published in primo. I understand this is a vastly complex issue but curious if anyone else has had these issues as well.
   Per Ex Libris
   Ex Libris's goal is to reflect the provider’s content and metadata and cannot directly make changes in our databases without the provider making these changes. If the provider has sent us a record for an article that is not yet published, or not yet assigned to a specific volume/issue, you will see it as a search result on CDI, but the availability indication and/or linking behavior will not always work correctly.

   I would love to see some regulations or procedure set in place for articles not yet published from being published in primo. I understand this is a vastly complex issue but curious if anyone else has had these issues as well.
   Per Ex Libris
   Ex Libris's goal is to reflect the provider’s content and metadata and cannot directly make changes in our databases without the provider making these changes. If the provider has sent us a record for an article that is not yet published, or not yet assigned to a specific volume/issue, you will see it as a search… 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…)
   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. Unpaywall - displaying both GETPDF and Interloan links for some resources

   This suggestion has been logged at the suggestion of Ex Libris in response to our Salesforce Ticket #07049766 .

   Unpaywall content sometimes displays both GETPDF and "Interloan" links. This confuses users, who regard the Interloan link as the safer option, and place an interloan request when they can directly access the PDF full text via the GETPDF link.

   There are overhead costs to managing this problem and redirecting the users to the correct link.
   Example record in Primo VE with both GETPDF and "Interloan" links:
   https://tewaharoa.victoria.ac.nz/permalink/64VUW_INST/1m9iv9v/cdi_openaire_primary_doi_211a156b24c44785a740e56954ab1501

   Ex Libris has reviewed this case and requested that it be placed in the Idea Exchange to gather additional input from the wider community and to decide on the scheduling of a fix.

   Your endorsement and support will be warmly welcomed.
   Thank you

   Ngā mihi
   Brenda Norton
   Brenda Norton RLIANZA | Library Systems and Discovery Librarian |
   Systems and Integration Development | Te Pātaka Kōrero |Phone +64 4 463 6185 | E-mail Brenda.Norton@vuw.ac.nz

   This suggestion has been logged at the suggestion of Ex Libris in response to our Salesforce Ticket #07049766 .

   Unpaywall content sometimes displays both GETPDF and "Interloan" links. This confuses users, who regard the Interloan link as the safer option, and place an interloan request when they can directly access the PDF full text via the GETPDF link.

   There are overhead costs to managing this problem and redirecting the users to the correct link.
   Example record in Primo VE with both GETPDF and "Interloan" links:
   https://tewaharoa.victoria.ac.nz/permalink/64VUW_INST/1m9iv9v/cdi_openaire_primary_doi_211a156b24c44785a740e56954ab1501

   Ex Libris has reviewed this case and requested that it be placed in the… more

   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…)
   2 comments  ·  Primo VE  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

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

9. Person Entity – Option to hide or suppress the Person Page and Person Info Card at the individual level

   We propose adding the option to allow institutions to hide or suppress the Person Page and Person Info Card at the individual level.

   We've received complaints that some person entities display incorrect information on their pages. As updating information directly at the data source (Library of Congress, Wikidata, or Wikipedia) is neither sustainable nor predictable in terms of when data changes will be reflected, we propose providing an option for institutions to exclude specific person entities from being displayed in Primo.

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

   We propose adding the option to allow institutions to hide or suppress the Person Page and Person Info Card at the individual level.

   We've received complaints that some person entities display incorrect information on their pages. As updating information directly at the data source (Library of Congress, Wikidata, or Wikipedia) is neither sustainable nor predictable in terms of when data changes will be reflected, we propose providing an option for institutions to exclude specific person entities from being displayed in Primo.

   Justification:
   1. Updating Wikidata and other data sources entries directly is not a sustainable solution and is not predictable… more

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

10. Resource Recommender Banner: allow multiple, randomised Banners

    We find the Resource Recommender Banner in Primo VE incredible useful for promoting exhibitions, programs and other library events, but the click through rate on the Banner is extremely low.

    One of the reasons for this, I suspect, is the static nature of the banner - once activated, the same image appears every time a search is conducted and it quickly just becomes "noise" on the catalogue that is either ignored or dismissed.

    We'd like to see this feature further developed to allow for multiple banners to be active at once (say, up to 5) and then have a different, randomly selected banner displayed each session. This would allow libraries to use the banners to promote more than one thing at a time (e.g. an exhibition, new Collection Discovery additions, research guides, etc) and increase the "noticability" of the banners by having something different displayed over subsequent catalogue visits.

    As an additional enhancement, it could also be useful to "boost" one of the active banners so it appears more often than the others so something can have higher prominence.

    We find the Resource Recommender Banner in Primo VE incredible useful for promoting exhibitions, programs and other library events, but the click through rate on the Banner is extremely low.

    One of the reasons for this, I suspect, is the static nature of the banner - once activated, the same image appears every time a search is conducted and it quickly just becomes "noise" on the catalogue that is either ignored or dismissed.

    We'd like to see this feature further developed to allow for multiple banners to be active at once (say, up to 5) and then have a different,… more

    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…)
    2 comments  ·  Primo VE  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Using FRBR local key to force certain similar records to FRBR in a group

    When having records with the same title (245 a) and also very similar subtitles (245 b) or section titles (245 p) or section numbers (245 n) you may want to FRBR them (and no others) in certain (sub)groups by using FRBR local key.

    Examples:
    In one group:

    245 a Sveriges rikes lag p Processrätt I
    245 a Sveriges rikes lag. n 3, p Processrätt I
    245 a Sveriges rikes lag. n 4, p Processrätt I

    And these in another group:

    245 a Sveriges rikes lag p Processrätt II
    245 a Sveriges rikes lag. n 3, p Processrätt II
    245 a Sveriges rikes lag. n 4, p Processrätt II

    Not as now being FRBR-ized with other records also if the regular FRBR rules returns a match.

    When having records with the same title (245 a) and also very similar subtitles (245 b) or section titles (245 p) or section numbers (245 n) you may want to FRBR them (and no others) in certain (sub)groups by using FRBR local key.

    Examples:
    In one group:

    245 a Sveriges rikes lag p Processrätt I
    245 a Sveriges rikes lag. n 3, p Processrätt I
    245 a Sveriges rikes lag. n 4, p Processrätt I

    And these in another group:

    245 a Sveriges rikes lag p Processrätt II
    245 a Sveriges rikes lag. n 3, p Processrätt II
    245 a… 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…)
    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

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

13. Resource Type Filter Bar buttons: users expect them to unclick if they change the search scope dropdown

    Users raised that they would like the Resource Type Filter Bar buttons to reset themselves to "All" when they repeat their search in a different dropdown scope.

    This is especially relevant when the new combination of search scope and resource type doesn't give any hits, e.g. searching the print catalogue scope with the button clicked to see only electronic articles.

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

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

15. Open Access articles to display in full text results

    Currently, if only displaying CDI results with full text, articles tagged as open access aren't included. These are only displayed if the user toggles to show results with no full text.

    Ideally, articles tagged Open Access would also be included when displaying results with full text. The tag would need to bypass the link resolver process so those results are also included.

    This would reduce the number of users putting in ILL requests when they didn't realised the article was available OA.

    20 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Add 'Review articles' as an option for the Resource Type Filter Bar

    Currently, the only option we can set is 'Reviews' for the Resource Type Filter Bar, but that is not the same as 'Review articles', which are a CDI document attribute used as a facet, as described here:

    https://knowledge.exlibrisgroup.com/Primo/Content_Corner/Central_Discovery_Index/Documentation_and_Training/Documentation_and_Training_(English)/CDI_-_The_Central_Discovery_Index/CDI_Document_Attributes

    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

17. Interaction between Unpaywall and View-it Section

    In some cases the Unpaywall API returns a link but the View-it section of the record shows "No full text available". Customer support explained the beahviour as follows:

    "Currently the Unpaywall API used by the Alma ViewIt checks for a direct link to the PDF of the article. In some cases, Unpaywall's API might return a link to a landing page - a webpage in which details on the resource appear as well as option for download. In that case, the ViewIt will not present a link.
    The Primo 'Get PDF' link uses a different mechanism, which does support links to Landing Pages - this is why you see the link in the "Get PDF" Primo functionality, but in the Alma ViewIt."

    It would be great if The ViewIt section could receive the Unpawall link and display it. Or maybe the View-it section could be supressed in these cases, so that only the "View online" and "Get PDF" links remain.

    The current situation where "View online" and "Get PDF" are being displayed alongside "No fulltext available" in the View-it section is confusing for patrons.

    In some cases the Unpaywall API returns a link but the View-it section of the record shows "No full text available". Customer support explained the beahviour as follows:

    "Currently the Unpaywall API used by the Alma ViewIt checks for a direct link to the PDF of the article. In some cases, Unpaywall's API might return a link to a landing page - a webpage in which details on the resource appear as well as option for download. In that case, the ViewIt will not present a link.
    The Primo 'Get PDF' link uses a different mechanism, which does support links… more

    0 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

18. Primo VE item filter by ChronJ item field

    In Primo VE, in the Get it section, button "location item filter" we can see and filter the items associated to an specific holding. Sometimes, for example with daily newspapers, there are lots of items associated to a holding.
    We have the issue's year codified in chronI field, following ExLibris recommendations, month in chronJ field and day of the month in ChronK field.

    If users want to reach, say, an issue dated July 16th, they should select the corresponding year and Primo VE loads the first ten issues of the year, starting in January. Now, user should be clicking many times “Show more ítems” button to load ten issues more and so on, so it will be cumbersome to reach finally July’s issues.
    So, adding chronJ to filter item functionality would be very useful for daily newspapers users.
    Thanks

    In Primo VE, in the Get it section, button "location item filter" we can see and filter the items associated to an specific holding. Sometimes, for example with daily newspapers, there are lots of items associated to a holding.
    We have the issue's year codified in chronI field, following ExLibris recommendations, month in chronJ field and day of the month in ChronK field.

    If users want to reach, say, an issue dated July 16th, they should select the corresponding year and Primo VE loads the first ten issues of the year, starting in January. Now, user should be clicking many… 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…)
    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. Change newspaper indexing from weekly to daily

    The CDI indexes newspaper content, like Proquest Newsstream, once a week. We would like to see newspaper specific content, that have daily issues updated in Primo on a daily basis. Patrons conducting newspaper searches in Primo report missing content, but need to redirect them to the individual databases for daily news.

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

20. Display portfolio public notes in brief record display

    We add important public notes to portfolios, with access instructions for users. Currently these only display on the full record screen.
    Users often miss these instructions. It would improve the user experience to also include these notes in the brief record display, where they have a greater chance of being noticed.

    6 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