2018-05-01 Program Committee


Connection Info:

Attendees

AgendaĀ 

  1. Welcome
  2. Volunteer for note taker _______ ? facilitatorĀ arouner
  3. Additions/changes to agenda?
  4. Scheduling future meetings
    1. Change next meeting (scheduled for June 5) to not conflict with Open Repositories (June 4-7, 2018)
      1. New date for June meeting:
    2. Dates for additional meeting frequency (starting July) as we near the Connect
      1. Additional dates for July +
    3. Committee members known time-off or missing for future meetings (can write in after meeting)
  5. Review/confirm conference schedule by days: additions or corrections?
    1. Monday - partner meeting
    2. Tuesday - workshops
    3. Wednesday -Ā Main Conference Day 1
    4. Thursday - Main Conference Day 2
    5. Friday - Unconference
  6. Facilities / Rooms available for conference - info provided by host committee
    1. https://docs.google.com/spreadsheets/d/1pTncHSl5JFXu8ORCReAyo0sbU-4MX7aangzr136SHrE/edit#gid=0
  7. ReviewĀ communication timeline
    1. Andrew has/will update to adjust to target of earlier Connect
  8. Review and discuss workshop proposals:
    1. Carolyn Cole (cam156@psu.edu) ā€“Ā Rails Testing Featuring RailsBridgeĀ Ā (half-day workshop)

    2. Nabeela Jaffer ()Ā ā€“ Managing Samvera-based Projects and Services
    3. EsmĆ© Cowles () & Adam WeadĀ () ā€“Ā Introduction to Valkyrie (half-day workshop)
    4. Chris Colvard ()Ā ā€“Ā Enhanced media playback in a Hyrax app using Avalon components (half-day workshop)
    5. Lynette Rayle -- Collection extensions workshop
    6. Rob Kaufman ()Ā ā€“ several possible workshops:
      • Keeping your Samvera application up to date ~ we'd talk through upgrade strategies, workflows, best practices and common pitfalls

      • Samvera as an API ~ discuss tools and capabilities for building external interfaces (React apps, mobile apps) that use Samvera as an API and data source
      • Rails Features ~ 5.2 is almost out, and 5.3 or 6 preview will be out by the time the conference comes around (this is similar, but updated from out 2017 workshop)
      • Real world TDD ~ A look at test driven development with Rspec, with an eye toward the balance between best practices and what is really practical
  9. Soliciting and commissioning content (seeĀ Suggestions for Samvera Connect 2017 Program)
  10. Review tools and processes forĀ planningā€“who is familiar with and/or has admin access to these?
    1. Waffle board for organization and tracking of sessions and speakers
      1. https://waffle.io/samvera-labs
    2. Ā Google drive
      1. Chris volunteered to clean up?
      2. Link:Ā program planning and structure of past Connect conferences
    3. Sessionizer for timetabling unconference sessions
      1. https://github.com/curationexperts/sessionizer
      2. Script run (originally created by Peter Binkley) to scrape wiki and put into GitHub repo (above)
      3. Aaron Collier will check with Justin Coyne and Erin Fahy about sessionizer use and scripts.
    4. Slack channel?
  11. Review of past Connects
    1. Useful documents from last year
    2. program planning and structure of past Connect conferences
    3. Feedback from past Connects (documents inĀ Drive) - Q&A
  12. Next steps
    1. Solicit proposals for panels
    2. What else needs to be done next?


Meeting Notes

  1. Welcome
  2. Volunteer for note taker: Chris Diaz; facilitator:Ā arouner
  3. Additions/changes to agenda?
  4. Scheduling future meetings
    1. Change next meeting (scheduled for June 5) to not conflict withĀ Open RepositoriesĀ (June 4-7, 2018)
      1. New date for June meeting: June 12th, same time
    2. Dates for additional meeting frequency (starting July) as we near the Connect
      1. Additional dates for July + (twice per month)
    3. Committee members known time-off or missing for future meetings (can write in after meeting)
  5. Review/confirm conference schedule by days: additions or corrections?
    1. Monday - partner meeting
    2. Tuesday - workshops
    3. Wednesday -Ā Main Conference Day 1
    4. Thursday -Ā Main Conference Day 2
    5. Friday - Unconference
  6. Facilities / Rooms available for conference - info provided by host committee
  7. ReviewĀ communication timeline
    1. Andrew has/will update to adjust to target of earlier Connect
  8. Review and discuss workshop proposals: all of the workshop proposals look great; however, we ought to solicit workshops for metadata librarians and new adopters. We should also make an effort to have a non-technical introduction to Valkyrie.
    1. Carolyn Cole (cam156 at psu.edu) ā€“Ā Rails Testing Featuring RailsBridgeĀ Ā (half-day workshop)

    2. Nabeela Jaffer ()Ā ā€“ Managing Samvera-based Projects and ServicesĀ (length?)
    3. EsmĆ© Cowles () & Adam WeadĀ () ā€“Ā Introduction to Valkyrie (half-day workshop)
    4. Chris Colvard (cjcolvar atĀ indiana.edu)Ā ā€“Ā Enhanced media playback in a Hyrax app using Avalon components (half-day workshop)
    5. E. Lynette Rayle (elr37 at cornell.edu) -Ā Collection Extensions WorkshopĀ (length?)
    6. David Wilcox (dwilcox atĀ duraspace.org) - Fedora WorkshopĀ (length?)
    7. Richard Green - Intro to SamveraĀ Ā (length?)
    8. Rob Kaufman ()Ā ā€“ several possible workshops:
      • Keeping your Samvera application up to date ~ we'd talk through upgrade strategies, workflows, best practices and common pitfallsĀ [first choice of committee]

      • Samvera as an API ~ discuss tools and capabilities for building external interfaces (React apps, mobile apps) that use Samvera as an API and data sourceĀ [second choice of committee]
      • Rails Features ~ 5.2 is almost out, and 5.3 or 6 preview will be out by the time the conference comes around (this is similar, but updated from out 2017 workshop)
      • Real world TDD ~ A look at test driven development with Rspec, with an eye toward the balance between best practices and what is really practical
  9. Soliciting and commissioning content (seeĀ Suggestions for Samvera Connect 2017 Program)
  10. Review tools and processes forĀ planningā€“who is familiar with and/or has admin access to these?
    1. Waffle board for organization and tracking of sessions and speakers
      1. https://waffle.io/samvera-labs
    2. Ā Google drive
      1. Available here
      2. Link:Ā program planning and structure of past Connect conferences
    3. Sessionizer for timetabling unconference sessions
      1. https://github.com/curationexperts/sessionizer
      2. Script run (originally created by Peter Binkley) to scrape wiki and put into GitHub repo (above)
    4. Slack channel?
      1. #samvera-connect (private channel)
  11. Review of past Connects
    1. Useful documents from last year
    2. program planning and structure of past Connect conferences
    3. Feedback from past Connects (documents inĀ Drive) - Q&A
  12. Next steps
    1. Solicit proposals for panels
    2. What else needs to be done next?