Stacey van Groll
My feedback
171 results found
-
318 votes
An error occurred while saving the comment An error occurred while saving the comment Stacey van Groll
commented
Some user-focused reasons to vote:
* Do you get queries from confused users who have searched in specific fields like Subject, Title, and Author, and then get results that have no sign of their search terms in those fields?
* Do your users wonder why they don’t see features like lateral links to find more records in these results, and don’t get the expected data they searched also exported to EndNote?Stacey van Groll
shared this idea
·
-
21 votesStacey van Groll
shared this idea
·
-
18 votes
An error occurred while saving the comment Stacey van Groll
commented
Hi Moshe,
I don't think such workflows for rejected requests are unknown to Ex Libris. It's necessary for monitoring, tracking, and resolving requests in a variety of scenarios, such as those which were cancelled while In Transit. This then hinders other workflows such as deleting a Library. Alma should not just 'disappear' a request as if it never existed, and we need visibility of all requests in Alma. This should already be the case under the 'All' filter selection, which is a defect. But it would also be helpful as this submission suggests to specifically add also a 'Rejected' filter. I am well aware from a case open for years that this filter was about to be released, and was even in Release Notes for May 2021, and then was pulled last minute.Stacey van Groll
supported this idea
·
-
103 votes
An error occurred while saving the comment Stacey van Groll
commented
I suggest to merge and rename to CDI this submission: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/43803426-customize-cdi-activations-by-resource-types
-
139 votes
An error occurred while saving the comment Stacey van Groll
commented
It is really unfortunate that the new pagination option to display up to 50 results by user selection in May 2021 was not included in Collection Discovery, which keeps the same Load More Results.
This also adds a design inconsistency across Primo interfaces.
The design is that it will only apply to Collection Discovery if a user sets this already for the session in main Primo and then happens to navigate into Collection Discovery.
As it is a very common user pathway to provide direct links to specific collections, such as promoting content in a web page by direct link to a collection, this means that a user is guaranteed to bypass main Primo and then miss out on the opportunity to set an increase in page numbers. -
53 votes
An error occurred while saving the comment Stacey van Groll
commented
Doesn't that CSS code just hide the suggestion, Manuela? The DYM index is taking effect on the results in Primo VE, right? So the results would still be highlighted as 'light', using the original example.
I often think that the downfall of this feature is what seems to be the unnecessary complexity, so it is almost impossible to explain.
For example, if I test this on one of my local data sources with Hmong consumers, I get two results with among and consumers highlighted. If I choose the suggestion for 'among consumers', then I get 19 results, some of which have among and consumers also clearly in the data, including the title. But the key is that the two which showed up originally have apparently been triggered by the Levenshtein distance aspect of the distance between the two words (it's not documented what that is specifically that I can find), whereas in the other records the words among and consumer are further apart.
Try explaining that to a user!
And there's also the issue that only the local index is used to build the index from title and authors, which drastically reduces the value because it's missing out on more unique and newer terms that might only be in emerging research topics which only have articles thus far in CDI, which are actually more likely for users to misspell and need help with. -
69 votesStacey van Groll
supported this idea
·
-
9 votesStacey van Groll
supported this idea
·
-
92 votes
An error occurred while saving the comment Stacey van Groll
commented
I believe this was added on Primo via Back Office with the New UI in 2016/2017, by adding request.date to mapping configuration.
-
44 votes
An error occurred while saving the comment Stacey van Groll
commented
I believe this is technically possible by a different manner of running a Delete and Reload pipe. This can now be scheduled with NERS delivery of '6184: Make it possible to override Start Harvest date for Delete and ReLoad pipes' in May 2020. I run this process monthly, which seems sufficient for our 3 OAI data sources.
-
72 votes
An error occurred while saving the comment Stacey van Groll
commented
It's disappointing that this idea has so few votes when Evidence-Based Practice is such a focus, and this is vital data on user engagement with different types of formats ie electronic vs physical.
I have long contemplated putting in a submission for yet another gap of no actions recorded in Primo Analytics for View It services clicks.
These are partially recorded in Alma Analytics for Link Resolver, but completely missing for any Link in Record links for either remote PCI/CDI or external local sources. So few votes here makes me think I shouldn't bother,but at the same time it amazes me that this gap hasn't been filled already as standard.Edit: I'll take the plunge, here's an idea for the View It clicks
Primo Analytics - Add Actions for clicks on View It links, for both Link in Record and Link Resolver
https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/41480614-primo-analytics-add-actions-to-be-recorded-for-cStacey van Groll
supported this idea
·
-
135 votes
An error occurred while saving the comment Stacey van Groll
commented
There's no label just for 'Primo', Lisbeth, as this enhancement channel was designed before Primo VE existed. It applies to all flavours of Primo regardless of deployment model. My impression is that it only needs a Primo VE tag if Primo on Back Office already has the functionality, but Primo VE does not. I have seen incorrect entries for this though, as someone on a Primo VE site might not know that a idea isn't possible in Back Office either.
-
42 votes
An error occurred while saving the comment Stacey van Groll
commented
Have you considered use of the category tree? I understand completely if the submission is only for Subject headings, as would be found in the Subject facet in main Primo, but perhaps you might not be aware of the option to add a category tree. We use this for a curated list of subject categories and then have a second tier for 'Key Resources', as many other commenters have described as being desirable. This makes for a different search experience to main Primo, as offering our users a list designed just for a focus area for our university with databases chosen by the expert liaison librarian supporting that areas, which helps also to not just replicate the Primo search in two different places, as each offers a distinct feature.
-
44 votes
An error occurred while saving the comment Stacey van Groll
commented
Agreed - there should be holistic design as standard.
-
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.
-
23 votes
An error occurred while saving the comment Stacey van Groll
commented
Also for CZ into IZ as well please!
-
75 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.
-
119 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.
-
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.
The set of 3 ideas which would drastically improve irrelevant and meaningless CDI results, by restoring and adding search tools which empower our users to target their search and their results, and and fixing the design decisions which make these tools very necessary:
https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/41092123-remove-cdi-constant-expansion-of-results
https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/43998315-make-consistent-the-use-of-cdi-record-data-in-prim
https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/19308214-proximity-search-operator-for-fulltext-search-in-p