February 12, 2016


Dial: +1 (641) 715 3660
Access Code: 651025#


Facilitator: sanderson (Boston Public Library)
Notetaker:  Margaret Mellinger (Oregon Digital / Oregon State University)

Agenda & Notes

  1. Roll Call
    1. Attending
      1. newmanld (Cincinnati) 
      2. Rick Johnson (Notre Dame) 
      3. Carolyn Caizzi (Northwestern)
      4. Sheila Rabun (University of Oregon) 
      5. Margaret Mellinger (Oregon Digital / Oregon State University) 
      6. matienzo (DPLA) 
      7. Jon Stroop Princeton
      8. @steven anderson (BPL) 
      9. asconrad (Deactivated) (Royal Library)
      10. wgcowan (Indiana University)
      11. Eliot Jordan (Princeton)
      12. Simeon Warner (Cornell)
      13. John Weise (Michigan)
      14. Tom Cramer (Stanford) 
      15. Chris Awre (Hull)
      16. Drew Myers (WGBH) 
      17. Lakeisha Robinson (Yale) 
    2. Welcome New Folks
    3. Call for Agenda Items
  1. Next call
    1. Date: March 11th, 2016
    2. Facilitator: TBA
    3. Notetaker: Mark Matienzo

  2. Hydra-in-a-Box project hydrainabox.org
    1. Design requirements and specifications sub-team has coded all of the user interviews and focus groups, doing further analysis.  Stanford will work on a preliminary HyBox sprint based on Sufia 7 with the aim of getting a working prototype going by Open Repositories.
    2. Specification work happened at the Developer Congress
    3. Mark Matienzo will provide a more through update via  email. 
  3. Discuss items on Power Steering identified for discussion during Hydra Connect 2015
    1. (see https://waffle.io/projecthydra-labs/power-steering) / (see also https://github.com/projecthydra-labs/power-steering/issues), "Partner Calls"; not all items need be discussed this call; facilitator should determine based on time 
    2. Agenda up on Hydra wiki and nominations for members of Power Steering 
  4. Standing Community to-do's
    1. Reports back from meetings (if any)
      1. Developers Congress at UCSD
      2. Jon Stroop - 25 developers for 2.5 days.  Best place to get a distillation of what went on is on the wiki.  What can we share, what can we take apart and reuse.  
        More work on Sufia UI design/redesign. Jon will send out the link to the wiki. 
        1. Q: is there a step by step guide for getting Sufia running on AWS?   
          1. No, but stay tuned
      3. Geo4LibCamp 2016 (Jan. 25-27, 2016): gem GeoConcerns will be worked on at this camp
        1. Elliot (Princeton)  reported on the inaugural Geo4LibCamp - this was an unconference, organized by Darren Hardy at Stanford.   Developers, managers, and librarians attended in about equal measure. Strong focus on Hydra and Geo Blacklight.  Good opportunity to GeoConcerns Gem.  PCDM geospatial models to hydra
        2. 3rd week of march there will be a sprint on the GeoConcerns.
        3. RDF and Geospatial Metadata elements were talked about, and there was general agreement that would be a good topic for the Geospatial Interest Group
    2. Next Partner and dev-centric meetings
      1. Hydra Connect 2016 (Oct. 3-6, 2016)
        1. Regional Planning Committee met yesterday to discuss logistics, but nothing new to report at this time. Planning ongoing. 
      2. Stanford Developer Congress (March 24th-25th)
        1. https://groups.google.com/forum/#!msg/hydra-community/d9eiFQFiB7A/vPaBXukZAAAJ
        2. Mike Giarlo is the local host; this event follows LDCX and is happening in parallel with Hydra Power Steering.  An eventbrite is up, not sure of how many signups there have been. Current plan is to form the event around the interests and time dedication of those who show up -  free form at this point.  If there is a big group there will be a bit of structure and activity, so that people don't spend the first day figuring out what they want to do. Look for an email from Mike about sign up details and logistics. 
      3. Michigan Developer Congress (May or June)
        1. https://groups.google.com/forum/#!msg/hydra-community/n-niCEsGARk/IdJJqseQAQAJ
        2. Narrowed down to May dates, working on logistics and will say more soon. 
          1. There is a IIIF event in NYC May 10 -13.  There may be some overlap between this and the Dev. Congress. 
        3. A question arose about the frequency of this type of meeting. With them happening every 2-3 months is there any concern about burnout or the inability for institutions to send people? There do seem to be a lot of topics moving forward that lend themselves to collaborative development.  Getting a sense of the focus of any one of these meetings would help with planning to send people. Call for proposed topics for each of the meetings has happened as the meetings are set up.  Jon noted that it's possible that the more of these we have, the less important they may become.  
          1. Power Steering group has talked about this topic and looking at the cadence and location of these meetings.  Coordinating across the meetings. 
          2. Will there be any carryover between these meetings?  Take a look at what's happened in the previous meetings and propose that they be addressed - raise these on Hydra Tech. Build energy around specific topics in advance. 
          3. Any remote participation possible?  Up to the breakout groups.  If a topic surfaced, pull people in at that point.  
          4. Both Stanford and Michigan were open to the idea of remote participation, if enough people expressed interest - contact the organizers.  
      4. Fedora Camp at CalTech in April 

  5. Regional meetings
    1. West Coast regional meeting (Friday, February 26, 2016)
      1. https://groups.google.com/forum/#!searchin/hydra-community/UCSB%7Csort:date/hydra-community/batgj37eBJA/s5vZalm1EAAJ
      2. Adding topics of interest to the agenda, brainstorming it now. If anyone is not going to the meeting, feel free to add topics. 
    2. Hydra Europe event in April (potentially cohosted with Europeana)
      1. No further details at the moment, hopefully more details by our next call in March.
  6. Training
    1. Hydra Camp - February 22-25, 2016 - UC Santa Barabara - https://hydracamp-ucsb-2016.eventbrite.com
      1. Looks like 10 tickets remaining. 
    2. Anyone willing to host a fall Hydra Camp? Reach out to Mark Bussey
    3. Dive into Hydra, Dive Deeper into Hydra, & Blacklight opportunities at Code4Lib 2016
  7. Reports from Interest & Working Groups (Please post a 1-2 sentence note of your update before the meeting just in case someone can't make the call):
    1. Samvera Archivists Interest Group 

    2. Samvera DevOps Interest Group 

    3. Samvera Digital Preservation Interest Group
      1. Call yesterday and the conversation led to forming working groups to bring back to Connect in October.  Look at the wiki pages for the ideas that have been generated. 

    4. Samvera User Experience Interest Group

    5. Hydra Web Presence Working Group

    6. Hydra Service Management Interest Group
      1. Call yesterday.  Revisit idea of a survey to send out to community in March to see how the group might function in a way that will benefit everyone.  Don't have a call scheduled, part of the survey will be to gather information on what would work best for regular meetings. 

    7. Samvera Metadata Interest Group
      1. Samvera Applied Linked Data Interest Group ()
      2. MODS and RDF Descriptive Metadata Subgroup ()

    8. Samvera Time-based Media Interest Group

    9. Samvera Metrics Interest Group

    10. Fedora 3 to 4 Migration Interest Group

    11. Samvera Geospatial Interest Group

    12. Samvera GIS Data Modeling Working Group
      1. Scheduling a sprint for geoconcerns projects.  Targeting Open Repositories as a date for having a functional prototype.

    13. Sufia Documentation for Managers Working Group (SDMWG - "sdimwig")

    14. Sufia UI Working Group
      1. Wireframes presented at Dev. Congress in UCSD and feedback given for further work on the Sufia UI.  Lynette Rayle is doing a fantastic job on this, along with several others on the group.

    15. Hydra Triple Store Interest Group 

      Chris Awre noted that the Steering Group in January had some ideas about getting updates from groups and how to do this more efficiently.  This is a topic for a future call. 

  8. Prospective Partner Intel Sharing
    1. (details not included in notes)

  9. Any other old or new business