2022-09-07 Planning meeting notes

Goals

Identify co-chairs

Identify timeframe

Paul Moeller from CU Boulder willing to co-chair. Thank you Paul!

Add'l co-chair needed. Might depend on timing of when it is.

Erin and others from Duke have limited capacity.

There are folks who wanted to be here today but couldn't make it - can we see if any of those folks would be willing to co-chair. 

We may have to identify another structure if a co-chair can't step forward to join Paul.

Fortunately we have a good infrastructure / Zoom license.

Hoping for a lightweight plan to move forward this fall.

The plan was to pitch three half-days (giving morning, mid-day, afternoon to cover West Coast, Mid, East Coast.)

JS: A three-day commitment this fall would mean moving really quickly.

Is there a Zoom component, Slack component, wiki component, others

EN: Can we list the pieces of planning that need to happen?

JS: Example of Ivy Plus Discovery Days

• time to decide on what we want to cover. e.g., survey potential participants to find common themes.
• are we going to have the same stuff three days in a row, or break things up
• will sessions build on each other or be independent.
• set up schedule, breaks. find notetakers, virtual facilitators, timekeepers.
• identify what to do after - gathering participant feedback, action points, etc.

JS: should we break up three days into a half day for three weeks?

JW: Another piece is administration of planning process. Things like communication tools, meeting schedules.

This group has a specific niche interest - we are all R1 libraries implementing the same software. We can be pretty aligned with our interests. Session per SIG, per high-level process.

EN: We have the jamboard link to get topics as well, from the kickoff.

JW: Goal for today is to figure out the communication of this group.

Slack seems to be a common communication channel, so it makes sense to create a channel in the FOLIO Slack workspace to facilitate unconference planning.

EN volunteered to facilitate setting up the channel for planning. 

JW: Pivoting back to discussion of scheduling. 3 half-days in one week vs 3 half days spread out over 3 weeks. Non-identical sessions should be in a single week.

JW: What do we hope to accomplish?

EN: Get more participants in the community. Coalesce around priorities for ARLEF resources.

Juleah: I'd love to be able to connect with people on the East Coast - important to get cross-pollination of ideas. 

JS: Discuss ability of community members to get tools connected to FOLIO, like Lehigh's Order app. Because the ARLEF libraries have similar use cases, maybe we can muster our efforts towards that.

JW: Hearing a sense of a path towards shared development.

PR: What are other libraries doing - integrations are a great way to connect and get their input. Example of National Library of Australia and discussion around ArchivesSpace. BoF type sessions.

PM: I like the BoF idea as well. Bring in topics that could be shared pain points to particular sessions.

JS: Also a "One Positive Thing."

JW: Opportunity to think about how we can find support and funding as a coalition of institutions.

Jamboard link: https://jamboard.google.com/d/12Cb9fDqB20Al5c5ykShaKKiR9n6K05JOraP9HkgJ_-A/viewer?f=2

JW: Anything we haven't mentioned yet that is important?

JW will send a follow-up email with the channel information. We will use channel to discuss next meeting and next steps.