HOLLIS Known Issues and Enhancement Requests

Owned by Corinna Baksik
Last updated: Jan 26, 2024

Enhancement Requests

Please vote for these enhancement requests in Ideas Exchange

NERS enhancement requests 

Some NERS requests are also in Ideas Exchange list above. Those are not repeated here.  

2024

  • Primo VE Facet for physical availability, configurable for locations / policy (NERS 8756)
  • Primo VE: Sort - customize per view, define local options (NERS 8755)
  • Primo VE: Browse cross-references and usage / scope notes (NERS 8750)
  • Primo VE: Change dynamic preferred record selection, support separate preferences for FRBR and Dedupe (NERS 8749)
  • Primo VE: Subject linking - allow users to choose level of subdivision searched (NER 8767)

2023

  • 8150. Primo VE: add support for complex XML external data sources
  • 8151. Primo VE: PrimoVE: support full-text extensions for local data sources
  • 8152 Primo VE: improve support for diversity and equity through automatic handling of non-Latin data in 880 fields
  • 8153 Display non-Latin script fields in CDI, important for equity and inclusion
  • 8170 Primo VE: increase facet display for languages (diversity equity and inclusion)

Past requests that did not make it through 2nd stage

  • 7714 - Music discovery - Name/Title Browse Searches for authorized headings
    • Previous requests for similar functionality not successful. 
    • Rejected from 2022 ballot. ExL response: As most of the development here is in Alma (a new Browse index must be built and this will require new infrastructure), this request should be submitted through Alma NERS next year. Normally we'd leave this in the Primo list since it is the "product of entry," this is an extreme example that may take more than 100 development days. 
  • 6583 - FRBR group static preferred record presentation per Advisory Group report
  • 6584 - Dedupe preferred record and data elements per Advisory Group report
  • 6638 - Email alerts for failed pipes / indexing in Primo Back Office

Local development in backlog

  • Aligned local resource types with CDI
  • HGL long layer list roll-up (for > 20 layers, "See more" button) (JIRA)

Known Issues 

  • Paging through results
    • Due to restrictions placed by data providers, you cannot page past 2,000 total article results. 
  •  Facets
    • In the search results, when records are clustered, facet values are only generated for the preferred record (the one displaying) and not the non-preferred record(s) in the cluster. The exception is the Library facet and Online facet, which will represent all records in the cluster. Case 00671459. No resolution - ExL rejected enhancement request as it would require major technical redesign. 
  • View It
    • (Local issue): when there is SKC as well as NET link for full-text, the NET link doesn't show up in View Online, only SKC. Can't get to full-text link. Example 002208174. Note: SKC was never designed to co-exist with full-text links. 
    • When a record has both a portfolio and a NET holding the local URN does not display in View Online. It does still show in the holdings.  (e.g. 990114346890203941, 990043194890203941). This is a non-standard scenario specific only to local handling of certain ebook sets such as MOML. 
  • Browse
    • A precomposed character may not always file with the corresponding decomposed character, causing some headings for same entity to appear separately in browse list. (Case 00717725). Problem only presents itself if controlled headings are not consistently coded. 
    • The call numbers in related holdings are present in the Browse list as if they were the call number for the record to which the holdings are related. (In addition to the actual holdings on the record). No resolution expected - would require an enhancement request. Case 00910405
    • Normalization of numbers in the browse list needs to be refined (e.g. sorting for B-1 Bomber, B-15 Bomber, B-2 Bomber)   Case ?
    • Browse search does not properly normalize hyphens. (Case 00489259). E.g "Tel-Aviv" and "Tel Aviv" are handled differently. Users must try both forms. 
  • Finding aids:
    • A limited number of EAD files which are very long are not fully indexed. Only the first ~80K words are indexed. There is not a solution for this issue in the current system architecture. (Affects a few dozen finding aids). 


Known Issues for Images (whether in HOLLIS or HOLLIS Images) - resolution not scheduled 

  • For HOLLIS Images only: 
    • Search results lack system feedback where applicable, e.g. "Showing expanded results. Your search resulted in few or no hits."  (JIRA LTSP-258)
  • Restricted images may not display in full view even when you are logged into HOLLIS. Workaround: use link to open image in separate tab. The Image Viewer will ask you to login and will set a cookie that will be recognized for the rest of your session, meaning HOLLIS will display the full size restricted images. (JIRA LTSMPS-22)
  • Restricted image metadata discrepancies: there will be some anomalous behavior in cases where there is a discrepancy between the image metadata from JSTOR Forum and the DRS access flag. These are exceptional cases that must be resolved through JSTOR Forum or through DRS. Behavior will be follows:
    • If the JSTOR Forum metadata indicates that the image is unrestricted but the DRS access flag is set to restricted then:
      • If you're off campus and not signed in, you will see a HarvardKey form embedded where the image should be. Proceed to sign in to see the image.
    • If the JSTOR Forum metadata indicates that the image is restricted but the DRS access flag is set to unrestricted then:
      • If you're off campus and not signed in, you will see instructions indicating that you must first sign in to view the image.  Process to sign in to see the image. Non-Harvard affiliates will not be able to see the image unless they come to campus to use an in-library device or obtain the direct link to the image. A direct link to an image can be found by opening the record in HOLLIS and clicking View Source (MARC). This will open a page with the source record in XML where the URNs to images may be found.
  • Thumbnail grids may load slowly. (JIRA LTSMPS-23)