Debbie Campbell

My feedback

  1. 10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Debbie Campbell supported this idea  · 
  2. 164 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
    Debbie Campbell commented  · 

    My comment below originated as a separate Idea Exchange post, and it has been combined into this other Idea Exchange post, I assume by Ex Libris.

    I do not think the two topics are the same, and I am not sure they should have been combined.

    I am advocating for a job that can look at "empty" linked user records, aka, linked user records where the purge date may still be in the future, but, where the user record no longer has an active transaction.

    The idea this was rolled into was asking for a way to schedule a purge job to run automatically, based on that purge date. This idea that it was rolled into is also making no distinction between local and linked user records.

    Please note: If these two separate ideas can be solved in development at the same time, then it is okay to combine them into this one idea. But I do not want my original intention of my post to be lost within this combination.

    An error occurred while saving the comment
    Debbie Campbell commented  · 

    In Alma, Linked User records saved to another institutions IZ as part of a collaborative network are eligible for deletion following the same parameters as that IZ's home patron records:
    1) Linked users can be manually deleted in Alma; statistics are not maintained.
    2) Linked users can be purged using the Alma purge job; the criteria is the patron record's purge date.

    Alma is making the assumption that the user at Institution A will perpetually (as long as the user is an active/eligible user at Institution A) want to maintain their linked user accounts in all other instititions that are a part of the collaborative network (Institutions B - infinity).

    This causes issues in large consortia using Alma collaborative networks:
    1) Patron Identifiable Information is being maintained in the collaborative network IZs (outside the patron's home institution) for longer than is needed for transactions.
    2) While Primo VE now contains an "activity" indicator to show a patron that they have a transaction with another institution, the overall list of institutions where the patron's record is maintained can be too long to be manageable. Patrons are also confused as to why a library would still be listed on their account, when they have no current activity at that other institution.

    In our previous system, Voyager, there was a Circulation server job that was set to automatically "Purge Universal Borrowing (UB) Patron Stub Records (Circjob 29)" (aka- Collaborative Network Linked User Records) after the record was no longer in use by a transaction at the institution. We ran the job every night.
    https://knowledge.exlibrisgroup.com/@api/deki/files/77521/Technical.pdf?revision=1

    The server job would identify linked user records and then check for the existence of fines/fees, holds, reqeusts, charged/checked out, or lost materials. If the system job found that the linked user record was "empty" aka, had no active transactions at the institution that should be used to prevent the record from deletion, the job would automatically purge the linked user record. The job did NOT delete a linked user record if it was still in use by a transaction. The server job retained the patron's statistics for reporting purposes, but the purge served to allow anonymization.

    Please add a scheduled "purge empty linked user records" job to Alma that can be scheduled by each institution. Ideally, it should offer the institution the ability to select to run the job daily, weekly, monthly, or yearly.

    Debbie Campbell supported this idea  · 
  3. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Alma » User Management  ·  Admin →
    Debbie Campbell shared this idea  · 
  4. 90 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
    Debbie Campbell commented  · 

    This would be a helpful enhancement- so many times libraries are creating/editing internal records at the circulation desk for community patrons, alumni, etc, and it would be ideal to then be able to give the patron a temporary password, that they are prompted to change on next login. Please make this functionality possible for Primo VE as well.

  5. 81 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Debbie Campbell supported this idea  · 
    Debbie Campbell shared this idea  · 
  6. 31 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
    Debbie Campbell commented  · 

    Yes please. Many of our institutions have materials cataloged that they want to display in their IZ for their local patrons to know are available, but, they do not necessarily want to have the records show in the NZ for all of the consortia's members to locate on a search.

    Common examples include materials such as headphones, dry erase markers, professor's copies of reserve materials, and certain kits or equipment.

    Debbie Campbell supported this idea  · 
  7. 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
    Debbie Campbell commented  · 
  8. 127 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
    Debbie Campbell commented  · 

    Patrons of the libraries in our consortium frequently used this functionality in our prior OPAC. They would use it if it were available in Primo VE as well.

    (I would use it too.)

    Debbie Campbell supported this idea  · 
  9. 47 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
    Debbie Campbell commented  · 

    Yes, it would be so helpful if this functionality were built directly into Alma.
    1) refresh on renewal attempt by patron or by library staff
    2) a job that can call home to the linked user's home record and refresh the copy saved to the item's IZ.

    Debbie Campbell supported this idea  · 
  10. 228 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Debbie Campbell supported this idea  · 
  11. 103 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Debbie Campbell supported this idea  · 
    An error occurred while saving the comment
    Debbie Campbell commented  · 

    This issue has become more important for our member libraries in that, with the COVID-19 pandemic, more of our libraries are using "contactless pickup" where the material needs to be checked out to the patron before placing it in a remote-retrieval site (such as lockers).

    Without knowing the patron's institutional affiliation, library staff are unable to check out the item to the patron.

    Debbie Campbell shared this idea  · 
  12. 19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Debbie Campbell supported this idea  · 
    An error occurred while saving the comment
    Debbie Campbell commented  · 

    Yes, I agree, this functionality would be very valuable for consortia using Alma, especially Alma's AFN functionality.

    Voyager (the system we are migrating from), had "Universal Policy Definitions" in which we could determine cumulative totals of delinquency a patron could assess across the consortium, before they were blocked from further circulation activity.

    For example, we could set it so that a the patron could have no more than 3 lost items total from any/all of the other institutions in our consortium. If they reached the consortial aggregate threshold (whether that was three items lost at one institution, or one item lost at each of three institutions), they were blocked from further circulation activity in ALL of the other consortial member institutions, with the option for them to also be automatically blocked at their home institution as well.

    With Alma's Consortial Block functionality currently only being one-directional-- a patron blocked at HOME with a network block is blocked at the other network member institutions, but not the reverse-- it will be significantly more difficult for our institutions to encourage and monitor appropriate patron behavior.

  13. 86 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Alma » Analytics  ·  Admin →
    Debbie Campbell shared this idea  · 
  14. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Debbie Campbell shared this idea  · 
  15. 69 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Primo » Other  ·  Admin →
    Debbie Campbell supported this idea  · 
  16. 220 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
    Debbie Campbell commented  · 

    I would appreciate this enhancement for Primo VE.
    It is much easier for patrons to browse the list of available courses/instructors to review a reserve list than to remember the correct words in order to search.

    Debbie Campbell supported this idea  · 

Feedback and Knowledge Base