| | | |
|---|
10 - 10:30 | Gathering, Icebreaker 4 Quadrant Activity | | What do you bring to the LIT team? What do we need to know about you when you are under stress? What is the greatest challenge for this group? What is something you’d like to accomplish in the year ahead?
|
10:30 - 11:45 | Review of current projects and their statuses
| Beth and all
| Review Questions What are major challenges with this project or application Do we still need this application? What would it take to get the project to maintenance Beaver Tracks - on old version of Rails. Margaret wrote to the campus map people to see if it could support campus tours. We’ll want to shut this down. Blacklilght: Sunset ONS: Wikibase migration EZDeposit 2: Sunset Kiosk Project: schedule a migration to Yodeck OD2: Quarterly meeting will discuss what it takes to get to maintenance. OD1: check with SCARC, keep DB? OSULP API: Sunset SA: Ticket Review has started DCWizard: Hui will talk with Clara. Sunset eTextbook: Sunset
Drupal sites OSUL D7: OSUP: Sunset D6 OCFRP: Need a solution for this - could be static site. Margaret wrote to Larry Landis - he still uses, as does Andrea Kuentz from Oregon Farm Bureau. RPNW: Sunset
Undocumented: Over to DX Biblio: seek another option ILLiad: moving to Rapido C4L Planet and Wiki SCARC: needs to migrate Archon: needs to be migrated to A-Space Omeka: needs upgrade OHMS: OJS: Margaret wrote to Adam Becker to see how their installation was going. Eventually we will sunset UO’s content off our instance. Western Waters: Margaret write to Anna Neatrour at Utah. EAD PDF Gen - check with SCARC (RW) Oregon Spatial Data (Sunset)
|
11:45 - 12:45 | Lunch | All | |
12:45 - 1:30 | Revisiting internal communication outages and other critical issues | Margaret | Decide on the process we will use going forward this year We notice something is down We check with one other person If the thing is down, we @ people in the channel for that thing. With details or screenshots if possible. Devs/infra respond to let us know someone is working on it. Thread the conversation. First steps are to check logs and restart things, usually. Really helpful to have the person working on the issue to give an update in the thread. If updates indicate the problem won’t be a quick fix, the person who reported the issue should communicate with the rest of the library using judgement about which Slack channel to post to, or whether a banner is warranted.
Alerting and mobilizing the right people
Fixing the issue
Decide the threshold for putting up a banner, communicating with library or campus
Holding a blameless post mortem for major things. |
1:30 - 1:40 | Break | | |
1:40- 2:30 | Revisiting external communication | Beth | How do we communicate work that is mostly invisible? How would you like us to acknowledge our successes? We could use the appreciation channel to share some successes. Communicating project status ideas so far Github Project board for all projects Gantt Chart for us Wiki page Status colors (red, green, yellow) Monthly LAMP updates with more detail
Outcome: Decision for what we want to do for the next year |
2:30 - 3:15 | What are some trends you see coming at us that we need to track for the future | Margaret | Servers moving to CEOAS Government shut down Sharepoint and Google AI For coding - in our IDEs? Cara is using it for Python scripts Marc is using it with GitHub and CoPilot Discuss hosting our own LLM Machine learning for tagging or metadata Notebook LM Guidance for AI Guidance for AI images on website (nix) AI for accessibility
Accessibility Open Access Open Science Affordability Workday (HR, Finance) CentOS 9 Windows 2025 Citrix re-evaluation Library Labubu
|
3:15 -3:30 | Wrap up and next steps | Beth and Margaret | Questions concerns when we are reorg’d how will we communicate Can we keep our same LIT channels AMD at LIT on Oct 9, 2025 Volunteer projects as a dept? Set a day when people come into the office , lunch. (Beth set this up as first thurdsays) |
3:30 - 4:00 | OSU Creamery | | |