Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

\uD83D\uDDD3 Date

\uD83D\uDC65 Participants

\uD83E\uDD45 Goals

\uD83D\uDDE3 Discussion topics

Item

Notes

Objective/Audience for the session

  • Is it for developers or primarily users

  • call out for planning committee of people can make it to set content that is of interest.

  • Avalon and Hyku

  • Hands on or content that is helped by in person

  • Community build too

  • What about inviting folks interested in Samvera solutions?

  • Plenary - Share fair about what people are doing, components of Samvera stack and individual code add-ons

  • Survey of what people are interested in, with options we come up with

  • unconference elements and tracks as well

  • Midwest regional meeting and context of Princeton, anyone can attend who is interested

  • output of the regional meetings will be reported and maybe virtual

  • Not a hybrid - only in-person - focused on workshopping to help with logistics and to focus on discussion rather than just pushing information one way


What do we need to send with a save the date

do survey about interest and topics, then call out for planning committee, meet 3 times, put your name here. Local logistics team is already formed.

Start a page where we can put in a google form

https://docs.google.com/forms/d/14Za-Ug4m-STVwYvMcdav6ADGjPKENHdowaTjL234MxI/edit

✅ Action items

  •  

First Meeting Notes

Samvera Regional Meeting - Midwest - April 05

VIEW RECORDING: https://fathom.video/share/vrmT4xryC-YdLSLSoL6cZ5zwKbVYX7jQ

Meeting Purpose:

Discuss hosting a Samvera regional meeting in the Midwest to replace the national Samvera Connect conference this year. Determine location, timing, themes, and audience.

Key Takeaways:

  • The meeting will likely be held in Indianapolis on September 25-26.

  • Accessibility will be a major theme, focused on user experience/management rather than just software development.

  • Attendance goal is around 50 people.

  • 50, 40, 30 person room and maybe auditorium at IU Indianapolis hosting.

  • IU Bloomington contributing catering up to $3000. PALNI will contribute additional catering needed. PALCI might be able to as way to keep from charging conference costs.

Topics:

Regional Meeting Purpose

  • Opportunity to engage a broader audience than the national Connect conference

  • Can incorporate developer-focused sessions but also focus on users and adoption

  • Important to make it useful for attendees and structure it so they don't feel overwhelmed

Location & Timing

  • Late September/October best time period to avoid conflicts

  • Midwest location makes sense regionally; Indiana is central though some have concerns

  • Indianapolis recommended as convenient with more amenities than other Indiana options

  • Dates flexible depending on venue availability

Themes & Audience

  • Accessibility a key focus - both software and content management

  • Developer-focused sessions could be included as a track

  • Outreach to potential new adopters is another opportunity

Logistics

  • 1.5-2 days recommended for those traveling

  • 50 attendees max so smaller spaces needed, not a large plenary room

  • Budget ~$10K for catering, AV, etc. but facility may be free

Next Steps:

  • Confirm Indianapolis venue and dates

  • Refine program based on themes and audience

  • Promote meeting to potential attendees

⤴ Decisions

  • No labels