Skip to content

Stacey van Groll

My feedback

202 results found

  1. 61 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Rialto » Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Stacey van Groll shared this idea  · 
  2. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Alma » Link Resolver  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Stacey van Groll supported this idea  · 
  3. 299 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    14 comments  ·  Primo » Primo VE  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Stacey van Groll commented  · 

    I also had a case for this opened in May 2020 where I directly referenced this Idea Exchange submission, and will copy details relevant comments from my case log.

    In sum, I think this was a defect that was fixed in August 2022 and will reiterate my last comment that I believe anyone still seeing this should open a case.

    CDI - Different term highlighting in record display does not match query, in comparison to PCI where highlighting is complete including stop words
    * 05310266

    Analyst advised: "In case of an exact match, the title highlight should include also the stop words. This, as you mentioned, is a good way to let the user know easily they hit the right result. If the match isn't exact, the stop words shouldn't be highlighted, again in order to allow the user a quick initial navigation among the brief results. But there are are few variations to this - namely, what counts as "exact match". For example, the search for "Playing the game; is sport as good for race relations as we'd like to think" - will get the full highlight. But it can be flexible - if you change some of the words in the query to their plural/singular forms ('races', 'sports', or 'relation') you will still see the full highlight. However, CDI isn't expanding 'we' when the indexed term is 'we'd'. Development team verified that this is the expected behavior for CDI, and that in fact it was the same for PCI (which is why 'we' wasn't highlighted then). So, the basic behavior is the same." 28.4.2021 SvG

    Responded to query only item outstanding re the Idea Exchange submission included in the original case for random stop word highlighting. 29.4.2021 SvG

    Analyst advised: "Currently, there's a fix planned for both for CDI and Primo side, to prevent the highlight of stop words when they appear separately, in addition to the expected highlight of them as part of an exact match. For example, a search for "lord of the rings" will highlight, as expected, the full exact match, but also the words "off" or "the" before or after the full highlight.", and also seemed to not see the issue in the Idea Exchange entry. 29.4.2021 SvG

    Responded to point analyst to screenshot on the entry, which shows the issue. 30.4.2021 SvG

    Analyst confirmed screenshot missed, and that it seemed an issue with the separate stop words as per the planned fix and not the "exact match" highlight. 25.2.2021 SvG

    Analyst advised tentatively planned fix for May 2022, which is extended as the fix must include also changes to the search mechanism. 15.6.2021 SvG

    Analyst advised fix estimation pushed back to August 2022. 20.2.2022 SvG

    Analyst advised firm fix in August 2022 Release. 8.7.2022 SvG

    Update of fix in the August 2022 Release and case set to closing. 22.8.2022 SvG

    Responded to advise cannot confirm and added a screenshot per the described fix in April 2021 showing the same additional highlighting. 22.8.2022 SvG

    Analyst is querying with PM re: "stop words detached from the query itself are no longer highlighted, but the adjacent stop words are. " 22.8.2022 SvG

    Added comment referencing earlier updates by analyst and the desire to ensure both aspects are resolved: "to prevent the highlight of stop words when they appear separately, in addition to the expected highlight of them as part of an exact match. For example, a search for "lord of the rings" will highlight, as expected, the full exact match, but also the words "off" or "the" before or after the full highlight." 24.8.2022 SvG

    Analyst advised: "What was actually fixed in this case is that only the words in the search phrase will be highlighted, not only the 'exact match'. For example, when searching 'lord of the rings', these words will be highlighted for all phrases that contain these words adjacent to each other. Indeed, according to the release notes, previously, the text 'of the' was highlighted even though it did not begin with Lord and/or end in Rings and currently, 'of the' is highlighted only when it appears in adjecent to the search phrase." 8.9.2022 SvG

    An error occurred while saving the comment
    Stacey van Groll commented  · 

    I still cannot replicate this. I'll attach images of what I see for one of the last examples Lacey posted with custom code stripped out to clearly show no stop word underlining.
    I suggest this be opened as a case for anyone seeing it, so there can be explanation provided for what appears to be an intermittent defect.

    An error occurred while saving the comment
    Stacey van Groll commented  · 

    I'm not seeing 'the' highlighted in my Primo, Lacey.
    Can you provide a link to your environment?

  4. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Primo » Primo VE  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Stacey van Groll commented  · 

    This sounds like treating the symptom rather than the problem.
    We help our patrons with the number of results by having expanded search and search in full text toggled off by default, and the individual can chose to enable them.
    I also submitted to NERS a submission last year which is aiming for delivery in the August 2024 release: Prevent search results expansion by use of exact phrase (VE/BO) #8210

    For Browse Search, our usage is miniscule at less than half a percent of search activity, so I don't expect any comments on it because they're simply not using it. it's unfortunate though that Ex Libris choses such a strategy of hiding features to improve poor performance.

    An error occurred while saving the comment
    Stacey van Groll commented  · 

    Interesting.
    Every now and then we may have a comment, but our general impression is that it's treated like google in that nobody really cares about the number at the top particularly when doing a broad topic search, so long as relevance ranking is good. And data shows very few people go beyond the first page or two.
    In contrast, the number of results is very necessary for context and framing when targeting into more narrow topic or known item type searches where there may only be a smaller number of results and faceting may be used to target further.
    I would think patrons would be concerned to have no indication at all as to the number of results, with also limitation of 1-5 pages at the bottom of the screen (if set to 10 or 25) and 1-3 pages (if set to 50).

    An error occurred while saving the comment
    Stacey van Groll commented  · 

    Could you advise why this would be useful?

  5. 5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Stacey van Groll shared this idea  · 
  6. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Content » New provider  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Stacey van Groll shared this idea  · 
  7. 7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Stacey van Groll supported this idea  · 
  8. 58 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Stacey van Groll commented  · 

    As an accessibility issue, this should be a SalesForce case, rather than an enhancement request.

  9. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Primo » Primo VE  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Stacey van Groll commented  · 

    I hope it’s okay if I share the translated text from the word document from Hebrew to English.

    This is:
    Sort the display of the results on the left
    In Primo - the main page (with image)
    in favorites [pin] (with image)
    add:
    Date - the newest
    Date - the oldest
    Change to the order of adding to favorites [in place of the date added]

    In sum, my understanding of the request is that main Primo results has the options to sort by publication date of the resource by Date Newest and Date Oldest. Currently in Favourites there is only an option to sort by the date that the patron pinned the item to their Favourites.
    This request is to add the same options from main Primo results into Favourites, by adding the options to sort by publication date of the resource by Date Newest and Date Oldest.

  10. 102 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Content  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hello,

    After a meeting with Austlit it is clear there is more efforts required for preparing the file for adding it to CDI.

    We will have more updates during the coming months and probably have a more accurate timeline during Q3.

    Kind regards,

    Tamar

    An error occurred while saving the comment
    Stacey van Groll commented  · 

    The University of Queensland Library and AustLit are collaborating on this topic to add AustLit content to the Central Discovery Index.

    Stacey van Groll supported this idea  · 
  11. 0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Primo » Primo VE  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Stacey van Groll commented  · 

    I wanted to add another comment to note that the person I was talking back and forth with here appears to have deleted their account.
    I would expect their comments to remain in place, but they are missing now.
    So, it's looks like I'm having a bit of a crazy conversation only with myself, which wasn't the case.

    An error occurred while saving the comment
    Stacey van Groll commented  · 

    I believe this is because a provider has given that record metadata to Ex Libris in English.
    There is the record in English from ProQuest, and this matches to the ProQuest source platform showing the record metadata in English and the article in Chinese: cdi_proquest_journals_1858231693
    There is also a record which has Chinese metadata also, rather than English. This is cdi_hyweb_hyread_00440336 and I believe this is from the Chinese Electronic Periodical Service (CEPS).
    If you search by the Chinese characters, the Chinese version record will be returned in Primo.
    Basically, Ex Libris is presenting what the provider has given them, which does seem reasonable and right to me and is their standard practice to not adjust provider metadata.
    They also don’t Match & Merge when there are language variations, which does seem right to be also as that could get very messy trying to merge such varying data.
    Are you thinking that Ex Libris should add a detection factor during provider feed ingestion to identify if the record metadata is in English, but there is Language metadata stating something else like Chinese, and try to employ a translation service to transform the data to that language?

    An error occurred while saving the comment
    Stacey van Groll commented  · 

    We have access to this example content via a CDI record from ProQuest, same as yours. The metadata is in English, and it has a Language display field of Chinese.
    When navigating to ProQuest, I see this is replicated by the English metadata, Chinese Language indication, and the pdf in Chinese.
    In looking around your site, I see that you have a Language facet but in a random check of your records I can’t see any Language fields displayed in records. When using this facet to limit to Chinese after doing a search by the article title, this record appears, Have you deliberately disabled the Language display field? If not, I think it is a defect that you are not seeing the Language display field, to make clear the article is in Chinese on the source platform.

    An error occurred while saving the comment
    Stacey van Groll commented  · 

    Is there an example of this?
    Whenever I have seen this, it has appeared to be explainable by match and merge of multiple sources and the full text source content reflects the same. For example, the title in English in the source but the article in another language and in the Primo record the title is in English.
    Or is this asking instead for something like that Ex Libris step in to change the metadata themselves for the title to match the article language despite what the provider may have made available to them, such as by AI generative tools?

  12. 2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Primo » Primo VE  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Stacey van Groll supported this idea  · 
  13. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Stacey van Groll commented  · 

    I'm wondering about the nature of the solution and if it would be better enhancing the matching process en masse, rather than adding a mechanism for manual individual flagging.
    Can you advise the situation with example, which Ex Libris states currently has no technical solution? One of those instances where I wish we could still see cases so I could look up the details myself!
    Is it something like an aggregator which just randomly doesn't have a particular article?

    An error occurred while saving the comment
    Stacey van Groll commented  · 

    This seems like a metadata issue to me that would be best reported with a request for metadata correction in CDI and/or Alma, to ensure CDI records are not marked as available online per Alma coverage information when this is not true.
    It would be helpful to have the details from the stated cases to understand why the metadata correction is not possible.

  14. 79 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Primo » Primo VE  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Stacey van Groll commented  · 

    This seems like a defect rather than an enhancement, as Primo VE is marketed as indexing for changes within 15 minutes.

  15. 77 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Stacey van Groll supported this idea  · 
  16. 14 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Stacey van Groll commented  · 

    No disrespect intended as this is so beautifully detailed and clear as to this issue, but I am concerned that this would be in Idea Exchange. The premise of this platform is for enhancements, not for defects which Ex Libris has decided not to prioritise fixing.

  17. 74 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Stacey van Groll commented  · 

    Please be aware that hiding GES or service by Display Logic Rules still shows the details in the OpenURL Context Object, and only hides the details from UI.

  18. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Stacey van Groll commented  · 

    I suggest to move this submission to the Primo Idea Exchange, as submitted to Alma Idea Exchange but solely for Primo functionality.

  19. 44 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Stacey van Groll commented  · 

    It would be very welcome for this Rialto version Purchase Request form to have a configuration option to require authentication and allow to show only to specific user groups.
    Optional configuration would support those sites who currently use this feature without authentication, while also expanding potential use to sites who do need it to be authenticated.
    The flow-on benefits for authentication would be to associate the requests to the Alma user account, just as is done for the Primo Purchase Request form.
    We currently use the Primo version Purchase Request form, but it's notably less unattractive than the Rialto form, and a bit of a clunky workflow via Citation Linker.
    But it allows for us to show it only to specific authenticated staff and student user groups by Display Logic Rules, as embedded within the GetIt, and is a nicely streamlined workflow overall for staff processing.
    We can't use the Main Menu direct link option as our institution requires a standard header, and even if we could it does not allow to show only to specific user groups accounts.

    Stacey van Groll supported this idea  · 
  20. 88 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Primo » Primo VE  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Stacey van Groll commented  · 

    I agree this is very clunky for VE.
    In Primo with BO, you can see all the information easily by frame source and adding &displayCTO=true, which I added as a bookmarklet to be triggered in one click.
    In Primo VE, first you have to trigger Display CTO, which very annoyingly refreshes the display from the full record overlay to a full page, losing your place in the search results. Then the CTO display is still missing the Target URL. So then you have to find the Incoming URL, copy this, paste it into a doc, add &debug=true&svc_dat=CTO to the URL, copy the URL, paste it back into the browser.

← Previous 1 3 4 5 10 11

Feedback and Knowledge Base