Stacey van Groll

My feedback

  1. 86 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    An error occurred while saving the comment
    Stacey van Groll commented  · 

    Yes. Thank you. This was not a problem from our original implementation in 2016 and only started maybe in 2019. Presumably because Ex Libris is not continuing to manage effectively new versions of Chrome to maintain the field setting. For browser based software, this is essential, and should not be forced on the customer to try to find workarounds or disable browser functions.

  2. 60 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    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-p

    Stacey 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.

  3. 74 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    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.

  4. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Alma » Fulfillment  ·  Admin →
    An error occurred while saving the comment
    Stacey van Groll commented  · 

    Hi Dan - could you advise exactly what the job report says now for the scenario of autorenewal not occurring due to expiry date being within the renewal period, and what you'd like it to say instead? I'm not clear on that after reading the case.

  5. 529 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Stacey van Groll supported this idea  · 
  6. 128 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Stacey van Groll supported this idea  · 
  7. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Alma » Analytics  ·  Admin →
    An error occurred while saving the comment
    Stacey van Groll commented  · 

    I might be missing something, but if wanted at an admin level of control, there is already an easy way of setting the schedule configuration from Active to Inactive.

  8. 83 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    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.

    Stacey van Groll supported this idea  · 
    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.

    https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/Primo/New_Primo_User_Interface/Back_Office_Configuration_for_New_UI#Display_Reasons_for_Nonrenewable_Loans

  9. 13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Alma » Link Resolver  ·  Admin →

    Thank you for your feedback.
    Today Primo does present viewit services for resources that do not have full text indications.
    We will check with Primo if this can be changed as the Unpaywall service can appear also when there is no full text service.

    Note that this issue is not relevant to PrimoVE

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

    I think you’re being too hard on yourself with this, Deborah, as when I look at the text of your original idea, it clearly states in the first paragraph: “… this could fill about 50% of recent articles that show in Primo for us as "no full-text available".”.
    It is very obvious the use case you were making that the Unpaywall link is needed in ‘No fulltext’ scenarios, for example nui.getit.alma_tab1_nofull.
    You suggested a potential development pathway, but it is for Ex Libris to implement in a manner which fulfills the submission, if they decide to mark as Under Review, then Planned, and then Completed.
    As it currently stands, I think that the original idea should not be marked as Completed if it only appears in no fulltext scenarios for Primo VE, but not for Primo

    Dana – could you please advise how and why this is not also an issue for Primo VE? Does it perhaps appear in the ‘How to get it’, as these appear to be locked behind auth in the VE sites I checked?

  10. 127 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Primo » Primo VE  ·  Admin →
    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

  11. 45 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Primo  ·  Admin →
    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.

  12. 66 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Primo » Primo VE  ·  Admin →
    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.

  13. 25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Stacey van Groll supported this idea  · 
  14. 5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Primo » Primo VE  ·  Admin →
    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>

  15. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Primo » Primo VE  ·  Admin →
    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?

  16. 5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Primo » Primo VE  ·  Admin →
    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.

  17. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Alma » Other  ·  Admin →
    An error occurred while saving the comment
    Stacey van Groll commented  · 

    Hi, If the documentation indicates that running a job is possible for a role, but it isn't available in your Alma environment, then this is a bug which should be reported to SalesForce. It is also possible to remove the other jobs from the role by requesting this in SalesForce. For example, 'Change Physical Items job' is by TASK_CHAIN_ITEM_INFORMATION_UPDATE and so all TASK_CHAINS bar this one could be removed.

  18. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Alma » Analytics  ·  Admin →
    An error occurred while saving the comment
    Stacey van Groll commented  · 

    Have you checked the Events subject area of Analytics? I haven't done a full assessment, but I think your minimums are pretty much covered there, as security events.

  19. 42 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Primo » Primo VE  ·  Admin →
    Stacey van Groll supported this idea  · 
  20. 53 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    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.

Feedback and Knowledge Base