Stacey van Groll

My feedback

  1. 2 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 am going to remove my own vote from this, as this was actually fixed as a defect in the July 2020 Release (new case querying this: 00853757).
    I'm going to leave this here, rather than deleting it, as an example of the broad issue of Ex Libris incorrectly pointing customers to the Idea Exchange after labelling a case as an 'enhancement', when it was actually a bug that plagued our site for almost 5 years. We should have been supported with better troubleshooting and case handling soon after our 2016 Implementation when we first encountered the problem.

    Stacey van Groll shared this idea  · 
  2. 6 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  · 

    Hi Christian - welcome to our user community!
    Does the Primo VE Resource Recommender not meet this need? It is described as matching to exact query: https://knowledge.exlibrisgroup.com/Primo/Product_Documentation/020Primo_VE/050Other_Configuration/010Resource_Recommender_for_Primo_VE

  3. 50 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  · 
  4. 16 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  · 

    This is a parity issue in development, as not an issue for Primo via Back Office.

  5. 12 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  · 
    An error occurred while saving the comment
    Stacey van Groll commented  · 

    It is worth noting as well that Publishing Information is also not available to staff even with the 'Read only' type of Administrator role, despite the data itself being 'read only'.

    Stacey van Groll shared this idea  · 
  6. 4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  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  · 

    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.

  7. 2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Primo » 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)
    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.

  8. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Primo » 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)
    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

  9. 40 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  ·  Alma » 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)
    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.

  10. 62 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  · 

    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.

  11. 28 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  · 

    Also for CZ into IZ as well please!

  12. 265 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 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'm not seeing 'the' highlighted in my Primo, Lacey.
    Can you provide a link to your environment?

  13. 2 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  ·  Alma » 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)
    An error occurred while saving the comment
    Stacey van Groll commented  · 

    There is some small coverage of this in the Events subject area like Courtesy and Overdue notices, but I agree that it's sorely lacking. Letter information is often a key part of workflows, such as for Purchase Requests query as part of the KPIs for Acquisitions and it's a big gap not to include this within all relevant SAs (rather than more in the separate Events).

  14. 78 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  · 

    That NERS submission was delivered with the ability to set preference of delivery category, such as assigning SFX at a lower preference.

  15. 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  · 

    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.

  16. 608 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  · 
  17. 4 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  ·  Alma » Analytics  ·  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 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.

  18. 104 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  · 

    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.

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

  19. 10 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  ·  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)
    Under Review  ·  Dana Moshkovits responded

    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?

  20. 139 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 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  · 

    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

Feedback and Knowledge Base