Issue | Description of Issue | Status w/ExL | Campuses Reporting |
Source Record 856 URLs auto-mapping to VE Additional Services | Several CSU colleagues have reported source record MARC 856 field URLs being automatically mapped to the Additional Services section in VE's full record display. Though the genuine access URL appears correctly in the Get It area, the proliferation of non-access URLs in Additional Services will certainly cause user confusion and generate plentiful unnecessary problem reports. A clear example may be viewed here: https://csu-fullerton.primo.exlibrisgroup.com/permalink/01CALS_FUL/oe38cr/alma991013283172802908 | Primo VE's full record display Links section offers links cataloged in 856 $u as long as 1st indicator =4. | Fullerton, Sonoma, SLO, Northridge |
Local field data remains in the PNX local_field even after the local field is removed from Primo VE | when removing a local field used for searching, will the content be removed from the search->local_fields section of the PNX record?
http://library.csus.edu/bookplates/winter Gift of Kevin Winter" ], | created Salesforce case 00937039 for tracking purposes. | Sacramento |
Issues with Everything search and complex phrase queries | A couple of campuses have noticed extreme slowness in returning results from queries consisting of 4 or more words using the standard "DN and CDI" search profile. One campus observed that this search contains e-inventory from all campuses, which is not desirable and also could be contributing to the performance issue. They created a search profile containing "physical items from NZ + e-resources available to me + CDI" and searches using this profile are much quicker. | There are multiple issues here. One concerns Esploro records being returned in search results even when Esploro is disabled. This will be fixed in April release. The issue of 4 or more word search phrases causing slowness is being looked into as of Mar 9. | All campuses are affected |
Primo VE gap - Public Access Model doesn't support HTML | Access model, displays HTML. We have self-created HTML Public Note for access Model display in the full record display. This displays fine in the current Primo (OneSearch), but Primo VE shows the HTML only. | SalesForce case 00937205 created - fix in Development | CSULA |
Appearing-Disappearing Held by Library facet | Intermittent situation where Held by Library facet randomly appears while searching in VE. It happens with both of our current search slots (one is DN+CDI, the other is NZ physical + local E + CDI). The appearance/disappearance of the facet happens during switches between search slots, between simple and advanced, and when starting a new search, but it is completely unpredictable and random. | Salesforce case 00936448 created - fix planned for Q3 2021 | SLO, Northridge, likely others |
Available for "Held by library" facet does not limit results down to what is physically held by institution but rather includes inventory from other CSU libraries | On traditional Primo, we've always been able to do a search that included the physical inventory of all campuses, and then use a top level facet to limit to materials available only in our specific institution library. | The Availability facet values cannot be adjusted, but you can enable the Institution facet and push it up the page to just below the Availability facet. | SLO |
Limit to identifier fields shows in record display | Our librarian found out that the following record shows different identifier in full display details section in Primo and Primo VE. | Each Display field or local field can process up to 19 output rows. If this limit is exceeded, only the first output row is displayed. Salesforce case 00936909 created to track issue | |
local scope for external data source | We have an external data source of DC records that represent all of our institutional repository holdings systemwide. I have configured the import profile to bring all of them in and have tested a view to search across the entire set of records with no issues. | This should be possible using a local field, but you currently cannot map a DC field to a local field without use of a MARC field. SalesForce case 00929849 has been created to track a fix. | CO |
Facets are missing numbers | Facets in VE do not show number of records available under each facet, as they do in Primo. | Primo VE does not include numbers for their facets as they are inaccurate. See | All |
There are no numbers on the Availability facet | I noticed in the Primo VE documentation and in our Primo VE that there are no numbers (of records) next to the Availability facet as there is for our Primo NUI. I noticed other live Primo VE also do not show number of records. Is this a forthcoming enhancement? | Indeed, the Availability facet in Primo VE doesn't display record count. The top level facets are used for filtering the results at a very high level based on inventory across both the local and central index. These facets do not display numbers, in order to make sure we do not show even the slightest inaccuracies related to calculating very large number of records taking into account local and central data and also taking into account both Dedup and FRBR functionalities which impact the numbers users see. | |
Newly configured facets require an Ex Libris reindexing of all records | According to the Notes located on {+}https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/050Display_Configuration/040Configuring_Local_Display_and_Search_Fields_for_Primo_VE+, new display fields used for search/faceting that are configured using norm rules require that reindexing be done. Only Ex Libris can run this job. | Ex Libris has responded on multiple occasions that they would only like to reindex the records once prior to going live, due to the system load that the process creates. They have said that they would be willing to run reindexing on a small subset of records that could be used to test rules. This seems to be a "case-by-case" offer but worth pursuing to those who might want to create substantial local facet fields. | All |
It does not seem to be possible to use the Purchase Request form in the link menu without also displaying it as a Request service for titles. | Hiding the Purchase Request using Display Logic causes the link to the Purchase Request form in the links menu to give an error message saying "This form cannot be displayed." We want to enable the form from the Links menu, but not have the Suggest a Purchase link appear next to other requesting options in item/title records. | This is by-design in Alma. I see that Alma Product Management recently evaluated this area and concluded that changing the mechanism would require an enhancement request. | Sonoma |
Link box appears even if it's empty | Even when there are no links to display, the Links box appears, which makes it look like something is wrong and the links are just not loading. The Links box should not be displayed if there are no links to display. | I'm experiencing this as well on out testing environments. | Sonoma, Northridge |
ILLiad GES and Display Logic | GES is set so that it is never disabled, but the display logic is set so that if a full text service exists, the GES should be hidden. | There is a known issue where a Display Logic rule doesn't hide the GES in Primo VE. I've added your example to our internal report, and have logged Support ticket 00943256 for tracking. | Sonoma, San Jose, SLO, San Bernardino |
Hold and Booking Request Form | trying to customize the Discovery->Getit Configuration->Hold and Booking Request form and I am unable to get some fields to display on the form. I enabled the Comments, Not Needed After, and Manual Description fields for public display. The Comments and Not Needed After fields show on the form, and I was able to change the label for the Comments to match our Primo label: Mailing Address:(Only for Delivery). However the Manual Description field is not displaying on the request form. What does this field display? Is there a way to add instruction text to the request form in Primo VE? | When requesting items that aren't cataloged, either a free-text manual description field or structured description fields can be filled-in. | Sacramento, Northridge and anyone that uses extra text on the request forms |
LC Classification Facet | We noticed that while we have a subjects facet, there doesn't appear to be an option to add the LC Classification for subject headings as a facet. We found this idea exchange about adding it and a comment about it: Adding LC Classification facet is planned for Q4 2019 as part of the feature alignment plans. | The current plan for this is Q1 2022. | SJSU, Northridge |
# of results not displaying for facets using EBSCO | SJSU is not seeing # of results for Resource Type facet, subject facet, database facet, etc.when searching in the SJSU collections (My Inst and CDI and EBSCO API). We added the EBSCO API to this search profile yesterday. What needs to be done to correct this? | See {+}https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/Primo_VE_(English)/040Search_Configurations/010Configuring_Search_Profiles_for_Primo_VE+ under the "Details Fields for Other Searches" heading: | SJSU |
Configuration for Request this item | We want to edit the content of the "Request this item" box (example record permalink: https://csu-chico.primo.exlibrisgroup.com/permalink/01CALS_CHI/bbjidc/cdi_gale_healthsolutions_A606636759 ) to match the box in our Primo. Where is this box configured? an example from CSUN. I found the labels eventually except for the equivalent of c.uresolver.getit2.holding_list.empty.guest_user = Sign in, and you'll see a link to request the item. | This text is configured in the Discovery Interface Labels code table for Primo, and in the ViewIt Labels code table for VE. | Northridge, Chico, probably all |
Library Guides import normalization | I have a successful discovery import profile for our Library Guides. I want to give them a resource type of "Library Guide" and then make that a facet. | There's some sort of software glitch here. I'll get VE development to manually fix it. I'll update once restored. | San Bernardino |
VE settings reverted back to OOTB | On Friday, I noticed that our Primo VE display had somehow reverted back to what I presume are OOTB settings. This happened last month (April 7th), too. I reported it then here. Somehow, after I reported it, later that day, the issue seemed to resolve itself. | This can happen when there's an invalid norm rule that did not display an error upon Saving, but could not be compiled. Upon removing or correcting the faulty rule will bring back all local_fields and modified Display fields. Most invalid rule statements will result in a compilation error highlighted in red, and not allow you to save the rule. There are situations where the system is unable to detect the issue, allowing the rule to be saved, but failing when run on the VE records themselves. VE Development are aware of this, but I'm not sure anything can be done about it. | Sacramento |
Invoke automatic search when search slots/scopes are switched | In Primo Back Office for Primo, there is a setting "Invoke automatic search when tabs are switched. Whether auto-search is enabled when users switch between tabs on a view. This field is checked/enabled by default." Documentation for that is here. This is a nice user experience feature since the search is automatically repeated without manually selecting "search" when switching between scopes. We had to manually select search again when we changed the search slot in Primo VE. Is it our understanding that this is not available in Primo VE? Will this functionality be available at a later date? | We haven't received similar requests for this functionality in VE in the past. | |
CDI Scope question | The Central Discovery Index (CDI) consists of more items than articles, and we want to keep a variety of items turned on in CDI. All of these items and formats are available in our “everything” scope. We also have a need to just search for Articles. In our current instance of Primo, we made a work around by filtering the search results to be limited to “articles. In Primo VE, is there going to be a better way to do this? Will it be possible to have a scope which only searches articles from the CDI? | I don't see any current plans to develop such an option for CDI search. |
Manage space
Manage content
Integrations