2023-01-10 FOLIO Implementers Meeting Notes

02:30

Calendar

• The calendar Invite ran out last year. We determine that a human has to create the calendar event and send it from their own account--TARA will do this.

  • Peter lets us know that using the calendar invite from Zoom will cause it to expire after 50 occurrences. This is why it is better to send it from our own accounts. Peter renews all the meetings in Zoom, but not the invites.

06:00

The Wiki

• Tara notes that the wiki is out of date and asks if we should take on the task of updating it

  • We are reminded that anyone can update the wiki.

  • We want to add a list of "starter sets" of Slack channels for new/onboarding users to our onboarding page. We think this work may cross over into another group's work

    • Julie thinks that the idea of the onboarding group is that there will be a set of slides that anyone could use to bring someone into the project.

      • Update: after our meeting, Julie asks on the product council slack. Sharon Wiles-Young replies "the Onboarding working group is on track to present our Onboarding slides to the PC at the January 26th PC meeting." (https://folio-project.slack.com/archives/CTYQZ7PF1/p1673371815136839)

  • Many of the sub-sections appear to be outdated. No one in this group appears to be using sections like "Active Implementation Sub-Groups"--these appear to be fully out of date.

  • TARA will work on cleaning up the wiki so that FOLIO Implementers can criticize her choices.

    • Once it is cleaned up, we can decide what it would be useful to put in the wiki.

10:00

Ideas for future meetings

10:00

Workflows/Use Cases

• Tod mentions that it is useful to see institutions presenting workflows/use cases. Finding effective ways to share solutions would be an awesome goal in 2023.

  • Tara asks if "conversation starters" might be a way to approach this--some libraries will still need to see very basic workflows.

  • Julie suggests examining slack channels for larger/vague topics that may be arising there.

  • Tod suggests "what are you trying to accomplish" as a framing question. Tara remembers a session on materials tracking. Perhaps goal-based discussions might be productive?

14:00

Course Reserves

•  Ian asks about the current ways that folks are using course reserves

  • What works, what is misleading, and what isn't there?

  • Julie notes there is no PO for course reserves, which is why this is at a full stop.

  • Ian notes that getting statistics out is challenging. There are also challenges cleaning up at the end of semesters (residual linkages). Tara and Peter note that it sounds like our experiences with Course reserves processes differ significantly, based on Ian's description. As such, it might be useful to compare notes/best practices.

    • Tod asks if we might start with the group who commissioned it. Peter believes this was Simmons.

  • After some discussion, we agree that a "current state of Courses" and "how are you actually using Courses" would still be useful.

    • TARA will follow up on getting this scheduled.

21:00

Framing Discussions

• Tod talks about ways to frame discussions so that they don't get bogged down in details, losing sight of the end goal.

  • Tod is playing with presenting things with a vision--where do we want to go with this?

  • This may or may not be for Implementers, but it is a great framing question. Julie notes that this is a great cross-topic topic. Julie asks if Tod is going to present findings? Tod notes that he's not doing this so formally, but will report back. If he gets a good result he'll let us know. Two specific topics he notes deal with settings and translations. "In the face of working code, if the fit's not the fit that we want but it's there, what's the balance there?"

    • Julie notes that this is a Product Owner skill that she as well wonders about. Julie could talk about it from that perspective.

34:00

Documentation

• Julie has an idea: she wants to know about how documentation is solved for each institution.

  • Julie's institutions need documentation at different levels--hosting, network, migrations, day-to-day work, set-up, the ecosystem, etc.

  • Julie will reach out to others who are live or who are going live--she is interested in the larger goals.

38:00

Upgrades

• Ian asks about libraries are managing upgrades. Specifically--how do individual libraries manage documentation, testing, communications, integrations, workflows. How do you make sure that the upgrade is successful?