Stacey van Groll

My feedback

  1. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Alma » Link Resolver  ·  Admin →
    Stacey van Groll supported this idea  · 
  2. 126 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  · 
  3. 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  · 
  4. 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 →
    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>

  5. 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 →
    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?

  6. 105 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Stacey van Groll commented  · 

    I have voted for this idea as I would like to be able to interrogate our live data about our users directly in our LMS as needed. For example, as an admin, I typically need to do testing for various system configurations and issues, and have had the need to find some current users by key elements. I have been prevented from doing this quickly and easily by Alma limitations of user search, and have been forced into the significantly more laborious process of loading Analytics, which often has caching delays and also disrupts other reports I might be running on historical data. This then needs even more back and forth checks between Alma and Analytics to find accounts which have not changed in the preceding day after ETL, as this data is not current. It does not seem unreasonable that library staff should be able to use our LMS to find our own data in ways that are practical to our daily work, and this is just one example.

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

  8. 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 →
    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.

  9. 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 →
    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.

  10. 252 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Primo » Primo VE  ·  Admin →
    Stacey van Groll commented  · 

    I believe that the earlier idea referenced is incorrectly marked as Complete.
    I have added a similar comment to this on that idea, noting that the content of the request was clearly for AND, and yet the development in-system is OR, in that only one field can be used.
    In this way, it is also not correct that this functionality is marked as Complete on the Primo VE Feature Alignment page when it is also there as AND: "Local Resource Type Normalization for MARC Leader and Fixed Fields".
    It is not right that a clear request can be submitted, be accepted and Planned with no indication it would be limited, and then the community waits for release six months, only to find that it is not what was asked for or what was promised.
    Then the whole cycle starts over again with the idea here.

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

  14. 58 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  · 
  15. 98 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  · 
  16. 372 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Stacey van Groll commented  · 

    Wow! This submission picked up 212 votes in only 2 days, including my own.
    Thanks for adding this, as I had a recently closed SalesForce case with exactly this issue, with a direction that this is an enhancement to current design.

    Stacey van Groll supported this idea  · 
  17. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Stacey van Groll commented  · 

    You can change this message, in the Error Messages Code Table in the Primo Back Office. Are you in Primo VE and not have access to this table? I didn't realise that this was yet another missing element, which is not good as we have made many tweaks to poor wording, or wording which does not match our standard terminology.
    Ours is:
    Partial results found
    Your initial search is too broad due to the use of ? or * wildcards. The results below are only a partial results set due to limits on possible combinations
    WE SUGGEST:
    Reduce the number of "?" and/or "*" in your search
    Increase the number of letters used in wildcard words

  18. 114 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Stacey van Groll commented  · 

    Very happy to lend University of Queensland support. We definitely would like to be able to acknowledge the correct Austlang languages in the existing Language features of Primo, as standard and expected.

    Stacey van Groll supported this idea  · 
  19. 29 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  · 
  20. 91 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Stacey van Groll commented  · 

    Can I suggest that Ex Libris move this one to the Content Idea Exchange?

← Previous 1 3 4 5 6 7

Feedback and Knowledge Base