Stacey van Groll
My feedback
171 results found
-
1 vote
An error occurred while saving the comment -
4 votes
An error occurred while saving the comment Stacey van Groll commented
Could you advise an example or if this is in a specific area?
I went to check it and the Details display is as expected with double dash eg alma991000002559707081 with
Germany -- Economic conditions
Germany -- Politics and government -- 1789-1900 -
152 votes
Hello all,
Alma currently support publishing of a set of records with the enriched related records information. For more information please refer to Related Records Enrichment section (MARC only) section in the online help page.
Are you aware of this existing capability? Is this not sufficient for your needs?
Stacey van Groll supported this idea ·
-
38 votes
An error occurred while saving the comment Stacey van Groll commented
I think that this idea has strong similarity (but some differences) to my own idea targeted for CDI facet restrictions:
https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/42521581-remove-restriction-on-number-of-primo-facets-value -
15 votes
An error occurred while saving the comment Stacey van Groll commented
Ex Libris have previously declined this concept, with reasoning here: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/37969432-portfolio-link-checker
-
43 votes
An error occurred while saving the comment Stacey van Groll commented
This is a parity issue with VE only having the Zero Results message and not the broad range of informative feedback messages which are in Primo using Back Office.
Although it does sound like there is worse behaviour on VE in not showing any results at all, because BO will still display some local results typically.
It could also be that the results do vary further for other messages for BO, and perhaps they aren't all relevant for VE, given the lucene vs solr aspect.
But definitely there are some instances like for this submission where there are definitely limits in place for VE and yet it has no messages to advise patrons.
See the "Partial results found." message on this page to meet this example: https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/Primo/End_User_Help_-_New_UI/Feedback_Messages
-
38 votes
Stacey van Groll supported this idea ·
-
59 votes
Stacey van Groll supported this idea ·
-
180 votes
An error occurred while saving the comment Stacey van Groll commented
I think this is a limitation by sheer performance load. With the current situation, the data is quantifiable (and yet Primo VE is still so much slower than Primo on BO). There would logically be a greatly more significant system demand if sites were allowed to control their own search and facet data, adjusting the indexing dramatically. I suppose this is the price of the 'real time indexing'. I'd love to be proven wrong.
Stacey van Groll supported this idea ·
-
6 votes
An error occurred while saving the comment Stacey van Groll commented
Hi Kathleen,
This is a defect, rather than an enhancement, per OLH that 1 million rows is supported.
It was meant to be fixed in June per my case:
"June 2022 Analytics SF: 06047995
The number of rows that were possible to export in formatted Excel format was limited. This was expanded to 1,000,000 rows."I reported back to my case after the release that the behaviour remained the same. It was checked and advised that the application found to be incomplete.
The fix is now scheduled again for August.
-
105 votes
An error occurred while saving the comment Stacey van Groll commented
This would of course be a nice feature for Primo sites overall, not just those on VE as per the tagged category.
I've added a lateral link by local field into main Primo for all records in Collection Discovery, mapped to a local 'Collection' facet to meet this need for a good connection point into main Primo, in returning all results in the collection.
But it requires for a user to open a record and find the lateral link, whereas this is a very nice idea to add a button which would be much more visible.
-
1 vote
Stacey van Groll shared this idea ·
-
122 votes
An error occurred while saving the comment Stacey van Groll commented
I raised this with Ex Libris Senior Management in August 2020, after being told in a case response that I should have reported to the appropriate team, rather than using the 'Report to Ex Libris' function: "We would like to recommend reporting similar issues to CDI Support team in the future - according to the product where the issue is replicated."
I used the 'Report to Ex Libris' function because I had directly correlated an issue in a CDI record in Primo from a specific Alma Electronic Collection, and all through the CDI rollout it was marketed to customers clearly and repeatedly that a significant component of the reasoning for the move of index management into Alma was for the benefit of integrated platform functionality.
Why should we have to log into the separate SalesForce platform and go through the many dropdown arrows to submit a new case, and copy and paste a great deal of information such as record IDs, when we can directly identify a particular portfolio or collection as the root cause of an issue?
When reporting via Alma, we have none of these pain points, all of the record information is included in the case automatically on our behalf and we have only to add some simple information such as example permalinks and issue description.
What we have is an attempt at an integrated system of products, trying to match with SalesForce support teams that are rigidly segregated by product.My response was: "… it is a completely acceptable workflow for us to submit cases within Alma via 'Report to Ex Libris', when we can identify a direct correlation with the CDI collection within Alma." and "… if it is desired for us to try to determine if the issue is Alma data or CDI data, then it would be up to Ex Libris to add another dropdown option to the 'Report to Ex Libris' page, as we would be more than happy to choose CDI or Alma."
But here we are now, almost two years later in June 2022 at time of writing, and this aspect of "CDI via Alma" integration still has no sign of being in place in Alma.
Stacey van Groll supported this idea ·
-
22 votes
An error occurred while saving the comment Stacey van Groll commented
The display is by ISBN/ISSN/LCCN according to OLH (some of the pages don't mention LCCN, while others do).
In such cases where the image is wrong in Alma, perhaps check to see if the identifier is correct in the bibliographic record?
-
0 votes
An error occurred while saving the comment Stacey van Groll commented
Hi Ana - Apologies if I'm not misinterpreting the full scenario, but shouldn't this be covered by the Interested In Letter, triggered if you have selected to "Notify upon cancelation"?
Notify upon cancelation - When selected, Alma sends an email to the user when the order is canceled. An email is sent only if this is selected and an email address is configured for the user. This option is clear by default. To control whether it is selected or not, use the po_ line_notify_interested_users_upon_cancelation customer parameter (Configuration Menu > Acquisitions > General > Other Settings).
-
1 vote
An error occurred while saving the comment Stacey van Groll commented
What a poor first experience for you!
I haven't used it yet myself, and I'm a bit shocked it would create a blank case when an analyst hasn't even engaged. -
59 votes
An error occurred while saving the comment Stacey van Groll commented
I agree with Manu that this is a defect if Primo is not making the data meaningful for UI.
The normalisation rules should adjust for this, in adjusting the date to cover the range.
For example, if you check the PNX of a record with 199-, it can be seen to be adjusted to 1990 for sort and search, while it will display as 199- per the source record permitted cataloguing.
As another example with 260 ##$a[Vancouver :$bDuthie Books,$c199-?-1994], the range will be <startdate>19900101</startdate> <enddate>19941231</enddate> -
326 votes
An error occurred while saving the comment Stacey van Groll commented
I'm not an expert in authorities nor music works, but I think many of these UI problems are only in Primo VE, and not Primo (managed via Back Office)
* Record counts: Primo VE presents "20+ records", where Primo display the accurate record count eg 560 records (bar minor FRBR/Dedup variations)
* Records returned: Primo VE returns hits outside the author heading such as 600, where Primo presents from the author heading, in an author Browse Search, which I believe covers the left-anchored aspect also
* References: I'm not seeing any sign that Primo VE supports See or See Also references in Browse Search. Primo supports See but not See Also references in Browse Search
* Fields: I won't try to dive into all the subfields mentioned, but Primo sites have the ability to adjust the Browse rules as they see fit, such as if there is a subfield which they'd like to add to Browse Search
Harvard has a lovely Browse Search on Primo via Back Office, labelled in main menu as 'Starts with / Browse': https://hollis.harvard.edu/primo-explore/browse?vid=HVD2&browseQuery=bizet,%20georges&browseScope=author&innerPnxIndex=-1&numOfUsedTerms=-1&fn=BrowseSearch -
64 votes
An error occurred while saving the comment Stacey van Groll commented
I have just had one of our staff ask after this, as it is very unnecessarily time-consuming to have to click in and out of the email address entries repeatedly just to see the key field of Description.
I completely agree with the submission in not wanting to create user accounts for this to try to solve what seems to be a very simple fix to add the option to the cog icon display to allow users to display the Description if they want to. -
175 votes
An error occurred while saving the comment Stacey van Groll commented
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:
An error occurred while saving the comment Stacey van Groll commented
This feature is even more important with CDI.
I have complaints because users are getting results returned on the basis of one of their terms being only in the reference list in a URL of a citation.
In sum, completely irrelevant to their query, as nowhere else in the record metadata or the true full text of the work.
If you could force Primo (actually CDI) to only return results for your search terms when in close proximity, this would drastically improve this currently very poor situation.An error occurred while saving the comment Stacey van Groll commented
I've submitted this for Primo NERS 2020.
Title: Add a proximity search operator
Request ID: 6682
Description: A proximity operator allows a researcher to specify that their search terms are present in records within a specified number of words from each other.
Summon already incorporates this feature, performed by enclosing search terms in quotation marks and using tilde and the number distance, for example "yeast bread"~10 finds material where "yeast" and "bread" appear within 10 words of each other.
See https://knowledge.exlibrisgroup.com/Summon/Product_Documentation/Searching_in_The_Summon_Service/Search_Features/Summon%3A_Boolean%2C_Phrase%2C_Wildcard_and_Proximity_Searching#proximity
Primo’s search algorithm incorporates an out-of-the-box assignment of higher ranking to records where search terms are closer together, but a proximity search operator gives a researcher explicitly more control over precise targeting of their search, which would also help to build greater understanding and confidence that the results will meet their needs and aren’t just from a mysterious “black box”.
With CDI coming soon to Primo, along with the massive increase in records, this trust building will be even more important to support researchers with tools to help sift through billions of results.
This tool should primarily support PNX and equivalent record metadata (both Primo via Back Office and Primo VE deployment models), but ideally would also incorporate standard existing extensions to remote data where available, including table of contents, abstracts, and full text.
See Idea Exchange submission: https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/19308214-proximity-search-operator-for-fulltext-search-in-pStacey van Groll supported this idea ·
An error occurred while saving the comment Stacey van Groll commented
I would love to see this in Primo, for full text and for record metadata, which are both available in Summon.
Our site was on Summon when I was studying myself and I constantly used this functionality for my research and assignments, as a key strategy to improve ranking of results for several keywords.
It is a vital tool for topic searches for beginner and more advanced researchers alike, to help sift through the hundreds of millions of results, by improved targeting of results and moving them into prominent position.
You can loan to the new patron without checking in from the original patron, if you allow staff to Override the Block Preference for 'Item is currently on loan by another patron'.