Peta Hopkins

My feedback

  1. 42 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Peta Hopkins supported this idea  · 
    An error occurred while saving the comment
    Peta Hopkins commented  · 

    Yes please. I support this idea. All admins should be able to work on a single list of institutional styles.
    Given that shared user accounts are a security issue, having a separate generic admin account has its own problems that should be avoided.

  2. 18 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
    Peta Hopkins commented  · 
    An error occurred while saving the comment
    Peta Hopkins commented  · 

    Another use case:
    We have a view that is specific only to a small cohort of psychology students/staff for a very small collection of Psychology Tests. They get to see all the resources recommended to everyone, but it would be helpful if we could recommend specifically for them.

    Also there is another very similar idea that should be considered for merging with this one.. https://ideas.exlibrisgroup.com/forums/308176-primo/suggestions/37796875-resource-recommender-customizable-for-each-view

  3. 34 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
    Peta Hopkins commented  · 

    That's great news to see it under review.

    An error occurred while saving the comment
    Peta Hopkins commented  · 

    Bonus idea - if they need to run the Prevent FRBR/Dedup job on records, make it simple for them to quickly push a bib record into an itemised set from repository search (... menu) and/or metadata editor (tools menu).

    Peta Hopkins shared this idea  · 
  4. 309 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Alma » Other  ·  Admin →
    An error occurred while saving the comment
    Peta Hopkins commented  · 

    Yes please. A bit like an in-place change log.

    Peta Hopkins supported this idea  · 
  5. 365 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  Alma » Other  ·  Admin →
    An error occurred while saving the comment
    Peta Hopkins commented  · 

    My suggestion for prioritising is...

    Revise the table UX design and use that for all *new* tables, and is consistent especially for similar types of tables. This should include consideration of search/filter/sort/grouping/paging/export-import/changing order mechanism (eg drag n drop) options that can be applied as appropriate and consistently across similar types of tables (Discovery Labels are in groups for particular functions vs Leganto Labels which is a ginormous long list of 1800 rows)

    Then start working on tables that typically have the most rows and/or "pages" as in the letters configuration, and that are viewed/updated most frequently by customers.

    Any existing, complex table that is related to a new feature release should be considered for a makeover. It is such an anticlimax to get excited by a new feature, and then have to configure it in a table that is challenging to use.

    An error occurred while saving the comment
    Peta Hopkins commented  · 

    More tables that can be exported, edited and reimported would give us some flexibility too.

    Peta Hopkins supported this idea  · 
  6. 19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Alma » Other  ·  Admin →
    An error occurred while saving the comment
    Peta Hopkins commented  · 

    I support this idea, though I have no votes left.

  7. 38 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
    Peta Hopkins commented  · 

    No votes left, but I support improvements that make the quick links more useful.

  8. 10 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
    Peta Hopkins commented  · 

    My previous comment could stand some clarification. The Leganto CiteIt bookmarklet grabs data from the page, populates a form for the user to create a citation in a reading list, and shows if the Library already has availability.

    A similar bookmarklet (or maybe a multipurpose bookmarklet that does both Leganto & Resource Sharing - what do you want to do with this citation) that populates with metadata from the page, checks if the Library has availability (shows link to the user) or not (shows the necessary ILL form fields including copyright statement and submit button)

    An error occurred while saving the comment
    Peta Hopkins commented  · 

    Yes please. Cite It functionality to check if already held and provide availability, if not show the Resource Sharing request link.

    Wish I had some votes left.

  9. 8 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
    Peta Hopkins commented  · 

    I've run out of votes. But yes that would be very helpful to do this easily from within the publishing profile rather than work with normalization rules.

    We are looking at the same kind of problem as we rethink our publishing method for the national bibliographic database.

  10. 785 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  Primo » Primo VE  ·  Admin →
    Peta Hopkins supported this idea  · 
  11. 25 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
    Peta Hopkins commented  · 

    This sounds like a worthy idea to meet regional ontologies

    Peta Hopkins supported this idea  · 
  12. 66 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
    Peta Hopkins commented  · 

    I have not votes left, but there is definitely a use for making global changes either as free text or with regex when there are hundreds of representations affected by some change.

  13. 67 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
    Peta Hopkins commented  · 

    Oh Yes please! If some reasons need to be reserved for Alma usage, then perhaps an "Additional Reasons" table that sites have complete control over could work. This model is used in some Course Reserves (Leganto) configuration.

    Even if we can't change the code for the reserved reasons, can we at least change their labels ourselves.

    This seems to be such an anomaly from the rest of Alma configuration.

  14. 56 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
    Peta Hopkins commented  · 

    We would use a form for registrations if there was one available (Alma or Primo). But we do not have the resourcing to build one for the few types of users that it would apply to here.

    Peta Hopkins supported this idea  · 
  15. 108 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Alma » Analytics  ·  Admin →
    Peta Hopkins supported this idea  · 
  16. 91 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Peta Hopkins supported this idea  · 
  17. 11 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
    Peta Hopkins commented  · 

    Nice idea too. Keep the trail of the request handling all in the one system.

  18. 8 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
    Peta Hopkins commented  · 

    The less clicks the better :)

  19. 106 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
    Peta Hopkins commented  · 

    It would be helpful to direct them to this when they submit requests for things that we have already supplied to them.

  20. 122 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
    Peta Hopkins commented  · 

    I've run out of votes, but would certainly support having more flexibility with the resource sharing request form.

    We have a use case right now where we would like to add a link to an FAQ about the service into the form.

← Previous 1 3 4

Feedback and Knowledge Base