Stacey van Groll
My feedback
198 results found
-
245 votes
Hello all,
As planned, we are moving forward with this ingestion. You will see a zero-title database in the KBs, as we work towards indexing this content in CDI.
Best,
Rael
Stacey van Groll
supported this idea
·
-
19 votes
An error occurred while saving the comment -
4 votes
An error occurred while saving the comment Stacey van Groll
commented
Hi Mary - I've written a CKC on how to identify troublesome collections like this: https://knowledge.exlibrisgroup.com/Primo/Community_Knowledge/How_to_-_Find_Central_Discovery_Index_(CDI)_records_for_specific_collections_in_Primo
You can then move the collection into expanded search by ticking the box to 'Do not show as Full Text on CDI...', and remove it completely by checking Not Active in CDI Search Activation Status. It's good to report these also to Ex Libris though in a case. -
2 votes
An error occurred while saving the comment Stacey van Groll
commented
This behaviour should be available to change in your institution by the 'Find GetIt services based on standard identifiers only' setting added in the March 2020 Release. Prior to this release, a title / author match is done when there is no standard identifier, but with that release, a site can choose to swap to only matching by standard identifier.
-
4 votes
An error occurred while saving the comment Stacey van Groll
commented
Perhaps try using Gabriele Hofler's Primo PNX bookmarklet instead? It has XML output and makes it much easier to activate PNX view with one click, rather than having to add text to the URL.
https://github.com/gabriele-h/PrimoNUIShow -
40 votes
An error occurred while saving the comment Stacey van Groll
commented
We'd want the option to do this by Fulfillment Unit though, rather than only an off or on setting at the institution level, as things like loans for 2 hours that circulate quickly and that users actively wait for need a time stamp.
-
62 votes
An error occurred while saving the comment Stacey van Groll
commented
Commenting to note that such functionality should be for the Primo UI in general, regardless of deployment model ie for both Primo on Back Office and Primo VE via Alma, with the expectation that development is for functional parity for all customers.
-
27 votes
An error occurred while saving the comment Stacey van Groll
commented
Also for CZ into IZ as well please!
-
78 votes
An error occurred while saving the comment Stacey van Groll
commented
That NERS submission was delivered with the ability to set preference of delivery category, such as assigning SFX at a lower preference.
-
642 votesStacey van Groll
supported this idea
·
-
121 votes
An error occurred while saving the comment Stacey van Groll
commented
Hi Gran - Thanks very much for clarifying the intent of the idea. I agree that the Blocks display in Blocks + Messages are very limited at the moment, and it would be good to have them all displayed there for user information. This would also help in making up for the 2 block limit for nonrenewal reasons in the Loans tab. I will add a vote in support.
An error occurred while saving the comment Stacey van Groll
commented
User specific blocks and loan specific blocks are both displayed, but the key is the design decision to only display 2 blocks maximum.
The user specific blocks display first and then the loan specific, in a certain order. I had a case querying this and asked for the details were added to the OLH:
1. The following patron blocks are checked first to see if all loans are blocked for renewal. Alma will return the first two reasons found and will not perform any further checks.
a. Patron is expired.
b. Check if patron overdue recall limits were exceeded.
c. Fetch patron's active blocks.
d. Check if patron overdue limits were exceeded.
e. Check if a patron's cash limits were exceeded.2. The following loan-specific checks are performed next. Alma will return the first two reasons found for that loan.
a. Validate that the item is renewable.
b. Check if the user has a patron role for this library or the whole institution.
c. Validate that the current date is before the maximum renewal period expires.
d. Check that the item does have any holds.We changed the first code table display from 'Cannot renew this item' to 'Cannot renew this item. Reasons include:' to try to establish the user expectation that there may be more than the 2 displayed reasons.
-
177 votes
Hi all,
We would like to update that we are planning to add this functionality to the Primo Next Discovery Experience User Interface.
We are currently evaluating it together with the Alma team.
More details on the plans for the new interface can be found here:
Best regards,
Yael.
An error occurred while saving the comment Stacey van Groll
commented
For visibility in Primo, there are a couple of benefits that make it appreciated:
1. Some staff are more comfortable with the Primo UI, rather than certain aspects of Alma like Manage Purchase Requests facets, and they are already actively using Primo for many activities when they may also like to check on a past purchase request. The speed of being able to do so from within the UI they're already typically actively using, especially as some will have no need to log into Alma on many days, is also a plus
2. There is the Primo feature from Requests of being able to click on the title and go directly to the full record, which is a quick workflow to find the record in discovery, grab a permalink, etc. Although I have set up Analytics reports for purchases which include the URL to the Primo record both from within Analytics and after export, this does again require them to navigate to the report. If they, for example, get a query from a user about a purchase request submitted on their behalf, they can quickly go to Primo, Requests, find the title, click on the entry, and go from there.
These aspects will inevitably be particular to workflows of different sites. As an example, we mediate all purchase requests through liaison librarians rather than offering the option for users to submit requests directly, And we also choose to publish all orders straight away to Primo, rather than waiting for receipt, so that users can see that requests have been actioned and anticipate addition to the collection.
As such, the visibility for these librarians of all the resources they've requested directly in Primo is a positive experience.
I can understand that sites without these sort of workflows might wish to remove these entries for non library staff users, but it's important that changes to UI take all usage variations into consideration, hence my alternate suggestion.An error occurred while saving the comment Stacey van Groll
commented
Our librarians quite like that their purchase requests are visible in Primo.
Perhaps, instead of removing them, a dropdown option could be introduced to Requests for all Requests History, as there currently exists in Loans for Historic Loans.
This would also fulfill this request: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/38591101-my-account-previous-historic-requests -
45 votes
An error occurred while saving the comment Stacey van Groll
commented
I actually thought this was likely to be a deliberate design feature (although I've never asked). The half panel display on either side suggests to me that there are more resources available, rather than just the ones on screen, reinforcing the user expectation established with the bars on either side with the arrows. Up to 100 records will be displayed, combined to the left and right, with the open record in the middle, so it's correct that the list is not complete.
-
66 votes
An error occurred while saving the comment Stacey van Groll
commented
Could you share the use case of why this would be useful? For staff this information is available in the equivalent form within Alma, and I can't think why a user would care how many times an item was loaned.
-
5 votes
An error occurred while saving the comment Stacey van Groll
commented
I agree that you should have the ability to configure this, just as Primo Back Office does.
Did Ex Libris ask you to submit this entry though, as it seems to me there might be a bug here?
The search initiates on Potter, Harry, 1954- even though the $$Q is without the date:
<creator>Potter, Harry, 1954- author.$$QPotter, Harry</creator>
And then the search fails to match with the facet term, even though the search data appears to be the same as the facet in UI, but is different in the underlying data:
<search><creator>Potter, Harry, 1954- author.</creator>
<facet_creatorcontrib>Potter, Harry,</facet_creatorcontrib> -
2 votes
An error occurred while saving the comment Stacey van Groll
commented
There are many potential root causes of this, but it depends on a number of factors.
Is this on Primo BO or Primo VE?
Are you using the out of the box EasyBib styles or the GitHub styles?
Is it an issue via records directly in Primo from PCI, or via the services page into Primo from an external source? -
4 votes
An error occurred while saving the comment Stacey van Groll
commented
Hi James - Did Ex Libris classify this as an enhancement rather than a defect, and direct you here? This is not right if yes, as if a subject heading lateral link with a hyphen requires quotation marks in order to function as expected to return results, then it should be included in the query by the system at the point of initiating the action.
I see that your search also functions as expected when removing the hyphen and leaving a space.
I have checked this on our Primo Back Office site, set also to exact phrase action, and it is working as expected with both the initial lateral link and also when initiating the search again after removing the hypen and leaving a space, which is expected with the Search Engine Configuration option also of Remove Hyphens as the default.
It seems clear that this is a defect with Primo VE that should be fixed. -
54 votes
An error occurred while saving the comment Stacey van Groll
commented
Hi - This can be done by adding Loan Status to the fields in the Loans List. It will show with data such as Normal, Renewed, Recalled, etc.
-
3 votes
An error occurred while saving the comment Stacey van Groll
commented
You can change this message, in the Error Messages Code Table in the Primo Back Office. Are you in Primo VE and not have access to this table? I didn't realise that this was yet another missing element, which is not good as we have made many tweaks to poor wording, or wording which does not match our standard terminology.
Ours is:
Partial results found
Your initial search is too broad due to the use of ? or * wildcards. The results below are only a partial results set due to limits on possible combinations
WE SUGGEST:
Reduce the number of "?" and/or "*" in your search
Increase the number of letters used in wildcard words -
25 votes
Hello,
We are in contact with the provider discussing the Alma CZ enrichment. Some additional work is needed for the provider to support the CZ requirements.
At this time we are setting this request to “Accepted”, pending the completion of this work on the provider side.
Best,
RaelStacey van Groll
supported this idea
·
This is a parity issue in development, as not an issue for Primo via Back Office.