When you join the meeting, rename your Zoom name to your name + SILS group (Mouseover your participant window, click on the […] dots dropdown to the right of “mute”, choose Rename.)
Ben, Lena, Christine will be watching chat today.
0
All
2
Quick announcements (shared via Slack)
Confluence is back up! (still feeling some post-traumatic stress from its disappearance)
3
SILS co-chairs update
5
Günter
Thank you for overcoming so many obstacles this year!
2021 will be a very busy year with all campuses involved in test load and beyond
4
Timeline review (recurring)
0
Lena, Christine
Skipping since it was covered in the Townhall yesterday.
Point to the rollup decision page from the FAQ. Xiaoli would be happy to create a FAQ/some context for the link.
Starting in February, PPC and FGs should be able to supply tips, why are you seeing x, how does it work, etc.
Send FAQs as you have them. It’s a living document.
Aiming for mid-January to refresh the document from the vanguard period to the new test load period. Please add one FAQ by mid-January to the google doc.
6
RLF records
Why? why now?
Current practices with RLF records are: suppress, don’t suppress, or delete.
If we maintain those practices, how will that impact discovery and fulfillment for end-users?
Does maintaining current diverse practices add complexity and expense?
Can we use Alma analytics/metadata to count what we own for ARL statistics rather than maintaining physical records?
What are the impacts of our decisions on end-users?
Is it possible/desirable to standardize a policy/practice on how we manage RLF records?
If we were to standardize, what would the timing be for this?
Without a RLF CKG, how do we include RLFs in future discussions about RLF records?
Is this issue so political [because of ARL record counts] that it needs to be sent to an escalation leader group? If so, which group? TSELG and ASCELG?
30
Christine, chairs from RM, FF & Discovery
Liz and Sarah W talked about how they came to their decision.
Scope = Test Load.
Why? They were aware of dependencies with FF and Discovery and special collections considerations. And, they didn’t know all the issues at the time.
The phantom issue is a big one.
Reconstructing a bib is a bigger deal than removing it later.
Joe and Liz R on fulfillment decisions
Decision happened at the end of vanguard. Based on seeing the experience of canceling a request. More work will be needed in test load phase.
Additional current practice that happens at CDL (beyond suppress, don’t suppress, etc). Maintain shelving locations at CDL for Melvyl, Request. RLF records in your local catalog must be marked as non-lending. Special code in Request that removes these records from ILL.
3 considerations in the decision and they are listed in priority order.
Suppressing is the number 2 priority.
Make the shelving locations “non-requestable” to avoid getting requests for items that are not lendable.
They haven’t considered special collections in FFFG.
RMFG specified in their decision, you must designate “offsite at an RLF” not just “offsite”.
There’s a need to mediate special collection requests from RLFs. Not sure how this will work with systems like Aeon. Investigating in test load.
Jess & Josephine from Discovery on the impacts on end-user:
looked for user pain points.
consulting with partner FGs on usability.
2 other groups were looking at RLF materials - how would a user engage with a serial title with split issues is one example.
Questions from J & J:
Which campuses suppress or don’t suppress? Liz M will survey members for Test Load.
Will RLF get their own IZ? Not for go-live but the RLF Configuration group is working on that decision.
How do records get into the RLF? Currently, it’s done differently by NRLF and SRLF. Proof-of-concept to see what’s possible during Test Load would be great per Lynne G.
Xiaoli: RLF is not just workflow or technology – there’s a political component. If it’s political, it may be beyond the FGs to make this decision.
Xiaoli: Only records with OCLC numbers are allowed into the NZ. Many special collections don’t have OCLC numbers. How does this affect discovery and resource sharing? Does it need to go to an escalation group? Some pieces could be handled well by the FGs. Others would get escalated.
Xiaoli: Workflow testing - current workflow to RLF has a lot of redundancies. Can we make RLF materials shelf-ready? Bar code so they can be scanned in easily? Can campuses provide this service to RLFs to reduce the RLF work? It would mean using the same bar code system. This may not be MVP, but could be considered post go-live.
Per Lynne, bar codes are not as much of an issue if you use Caiasoft (the inventory management system used at both RLFs. Using this software means that the barcode is no longer the “address” for where a book lives in the stacks).
RLFs are open to making things smoother and understanding where the value add is.
User experience: The test load is a good opportunity to see what the patron experience is.
We are now in one system with all records available in one place.
Next steps…do testing and revisit this conversation. Consider adding RLF testing to Confluence so it’s more public. (Discuss in PPC)
Per Josephine, NA07 will be in the new URL for your primo VE instance in test load.
7
Parking Lot
Capture important topics for future discussion
8
Total
50/50
Future agenda items
The SILS mission is to transform library services and operations through innovation and collaboration. The future is shared!
Question? Contact AskSILS-L@ucop.edu