Page Comparison

• Copied by arouner.

Connection Info:

...

• Aaron Collier (Stanford)
• Chris Diaz (Northwestern)
• Hannah Frost (Stanford)
• Brian McBride (Utah–host committee)
• Margaret Mellinger (Oregon State)
• Jennifer Moore (WUSTL)
• John H. Robinson, IV (UCSD)
• arouner (WUSTL)
• Emily Stenberg (WUSTL)
• David Wilcox (DuraSpace) 
• Richard Green (Steering)

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 morning - workshops: parallel themed or targeted tracksTuesday afternoon - plenary
   3. Wednesday morning - parallel themed or targeted presentations
   4. Wednesday afternoon and 
   5. Thursday - unconference and WG/IG meetings
   6. Friday- Main Conference Day 1
   7. Thursday - Main Conference Day 2
   8. 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 () – IManaging  – 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
   Getting under way
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 and introductionsNote taker and facilitator 
2. Volunteer for note taker: Chris Diaz; facilitator: arouner
3. Additions/changes to agenda?
4. Scheduling future meetings
5. Review of Connect week schedule—Brian McBride
6.  program planning and structure of past Connect conferences ( use waffle board to plan) 
   
   1. Monday - workshops: parallel themed or targeted tracks
      1. Last year we did not have to recruit people to submit proposals
      2. Finalize the workshops first, so people can make travel plans
      3. Last year, we added an intro to community
      4. Fedora workshop is popular every year
   2. Tuesday morning - plenary
      1. feedback suggests: people love the lightning talks
   3. Tuesday afternoon - poster session
      1. We ask all the partners to bring a poster
      2. There was some negative feedback about the noise and space
   4. Wednesday morning - parallel themed or targeted presentations
      1. concurrent lightning talks - how many concurrent tracks can we have? 6 rooms are available - doesn't mean we have to have 6 tracks. The rooms are on 2nd and 9th floor.
      2. Plan out lightning talks ahead of time or let people sign up on that day?
   5. Wednesday afternoon and Thursday - un-conference and WG/IG meetings
      1. We will have to contact the IG and WG. Last year, some committees did not have any updates. At virtual connect, we used a template and asked chairs to put update based on 3 questions: What has been done, what is the future and who are the chairs and meeting times.
      2. Recruit people for presenting 
      3. Un-conference is for providing an opportunity to work any cool ideas/topics. 
      4. Not sure if everyone has a good idea about what un-conference session is. We need to better advertise it
7. Soliciting for workshops
   1. Richard requested (previously) we address this first (presumably so people can make travel plans etc.)
   2. Topics to suggest in CFP:
      1. Intro to Hyrax
      2. Fedora
      3. RSpec rspec.info
      4. Software Carpentry
      5. Valkyrie
      6. Collections Extensions Collection Extensions Requirements Working Group
      7. (Library) Publishing with Samvera
      8. Contributing to Samvera documentation
      • • (especially using jekyll https://jekyllrb.com)
   3. Timeline for workshop CFP messaging:
   • • Draft CFP for workshops / send to committee–4/03 
     • EMAIL CFP for workshops (Partners, Community & Tech?) 4/4
     • EMAIL REMINDER 4/15
     • DEADLINE for submissions 4/27
   1. more
8. Review of meeting times for this committee (Samvera program committee)
   1. Will need to go to meeting alternate weeks beginning in July
   2. Scheduled meetings (first Tuesday, 10-11 am CST):
   • • April 3
     • May 1
     • June 5–will need to reschedule due to conflict with OR 2018 conference (June 4-7, http://www.or2018.net) 
     • July 3
     • August 7 
     • September 4
9. Facilities / Rooms available for conference - info.provided by host committee
10. Getting under way
    1. Change next meeting (
    not asked)
11. Why are we all here?
    1. Richard,  Steering Group liaison
       1. Brian as Host Committee liaison
    2. Everyone else, to design and commission the program for an excellent SC2017!
1. Karen created the timeline based on previous notes. 
2. Call for Mentors and Mentee is new and is moved earlier in the timeline. Last year was the first time.
12. 1. 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)
13. 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
14. Facilities / Rooms available for conference - info provided by host committee
15. Review communication timeline
    1. Andrew has/will update to adjust to target of earlier Connect
16. 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
17. Soliciting and commissioning content (see Suggestions for Samvera Connect 2017 Program)
18. 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
    (
    2. 1. https://waffle.io/samvera-labs
    /samvera-connect)
    4.  Google drive
       1. Available here
       2. Link: program planning and structure of past Connect conferences
    5. 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)
    6. Slack channel?
       1. #samvera-connect (private channel)
19. Review of past ConnectsReview feedback
    1. Useful documents from last year
20. Progress so far:  call for suggestions (2) 
21. Scholarships?
    1. one program committee member can be liaison for the scholarship committee 
22. 1. program planning and structure of past Connect conferences
    2. Feedback from past Connects (documents in Drive) - Q&A
    3. Feedback suggests: Full conference dinner is not necessary
    4. Host committee is planning some dine arounds
    5. Opt-in for first time badge ribbons
23. Slack channel
    1. do we want to have a slack channel - yes! Question is where to host it?
24. Next steps
25. CFP for workshops
    1. Draft CFP for workshops and send to committee for review 4/03–Andrew
    2. EMAIL CFP for workshops 4/4
26. Review communication timeline –All 
Review recommendations from last year's Samvera Connect program committee (from committee members and from attendee feedback) 
 for  (see Suggestions for Samvera Connect 2017 Program)Next steps
1. Solicit proposals for panels
2. What else needs to be done next?