Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device.
Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Waiting for Privacy Group to determine what data can be shared in the form
AFN Billing (broad topic, might need to be redefined/split up into various smaller topics?)
Document how each campus takes payment from other UC patrons
What solutions can we recommend?
Low/Medium
In
Progress
Point patrons in the right direction for who to talk with at each campus. Don’t know what else we can do with AFN billing unless we’re on the same system…
Linked page on website for how to pay/improving each campus' communication to patrons.
Stability for billing across campuses?
Do we each have a well running machine?
bringing billing “in house” and switch to something like PayPal…?
Non-Alma Billing
In
Progress
In relation to billing. we haven’t worked out items that are backlogged in VDX (along with items that are still going thru VDX). are we still billing for those items or calling a wash? also items that go into a black hole and never reach their destination or are lent but never come back. unity issue (develop process for tracking these items? I think we discussed this in the past? circle back with RS OST)? who’s responsible? how do we move forward?
Subteam working with UCs to close out VDX bills by end of year, and recommend practice for in-transit too long items
Recall Policies (established at each campus and share info out, similar to communication/who to contact matrix)
Document practices at each campus
Medium
Not Started
Only the owning institution can recall the item. Not sure what’s there to agree on re: policies since it’s all on the owning institution. We can discuss a “best practices” but there’s not much to harmonize otherwise.
what’s the trend? what’s the practices?
make patrons aware of various policies from other campuses
Anonymization survey
Identify from each campus what information is anonymized in Alma. I know what we anon, but not about the rest of the campuses. in particular find history and attachments.
AFN User Blocks (coord. with RS OST?)
High
3/31/2026
In Progress
2025
ExL put AFN blocks on their 2025 roadmap, we’ll wait for them to make the next move and then revisit this item.
Completed testing of manual Network Blocks
Testing of Network Loan & Request Blocks in progress
Harmonization of AFN Policies and Procedures
High
2026
In Progress
2025
Part of this on hold until AFN block case is finalized.
Patrons may be charged for an item vs. being blocked.
AFN Analytics
Medium (RS OST currently working on this, F might be consulted as needed)
Complete
Done- will not happen
Discussed 3/27/23. May be reviewed at a systemwide level. Holding on any action for the time being.
It has been determined that cash limit block harmonization among the UCs is difficult at best and not actually pertinent to the potential use of AFN consortial blocks across the UCs. Each UC may continue with their own costs and place the block at the time an AFN bill is generated. The issue of potential harmonization decisions of cash limit blocks has been deferred to and is in the purview of the SILS Fulfillment OST.
Possibly purging user records? See if we can standardize this in some way.
UCB purges at end of June. Expired accounts with no activity (2 years) and no fines/fees. have not purged any AFN accounts since two years hasn’t yet elapsed.
Do some testing to see if network users are removed (if removed at home campus).
purge date/expiration date on accounts.
Is it possible to harmonize on when and how we purge??
Determined no need to harmonize dates. Committed to purge network accounts once a year.