November 3, 2014

Call-in: 

Dial: +1 (530) 881-1400

Access Code: 651025

Moderator: Ben Goldman (Penn State)

Notetaker: Erin Faulder (Tufts)

Attendees:

• Ben Goldman, Penn State
• Adam Wead, Penn State
• Mike Giarlo, Penn State
• Erin Faulder, Tufts
• Katherine Lynch, Temple
• Michael Olson, Stanford
• Gary Geisler, Stanford
• Courtney Mumma, Artefactual
• Justin Patterson, Artefactual
• Wendy Hagenmaier, Georgia Tech
• Erik, ?  
• Matthew Farrell, Duke
• Dan ?, Northwestern

Agenda with Minutes:

1. Roll call and identify notetaker - 5 mins
2. Review and Discuss Action Items from HC2 discussion group. - 25 mins
   1. As near as I can tell, those action items were:
      1. Centralize future HAWG communications using Hydra-Community google group – CHECK
      2. Consult with Stanford to see how HAWG can support efforts of ArcLight (formerly BeadL – EAD in Blacklight)
         1. Overview of the ArcLight draft charter sent through the Hydra-Community list, Michael Olson
         2. Design process - Gary Geisler
            1. Who might be interested in ArcLight to be able to commit design resources in some form – simple (interviews at institution) to more involved
            2. Stanford has set up a mailing list for feedback: arclight-feedback@lists.stanford.edu
            3. Mike G recommends Michael/Gary email hydra-community requesting input on the process
            4. HAWG asked that they share documentation as the project develops
         3. Soliciting examples – Michael Olson
            1. They will be looking for examples of archival collections in order to understand the variety of content needing to be presented
      3. Work with Artefactual Systems to develop integration between Hydra and the Format Policy Registry
         1. Justin gave an overview of FPR – they want to develop a way forward that is more platform-neutral (Islandora is also interested)
         2. Maybe start using it where Hydra creates access derivatives because it is the most simple (HydraDerivatives gem) – look up via the rest API to look at the rules provided by the FPR to take actions
         3. Going to start a sprint to do a proof-of-concept to show off
         4. Action: Justin and Courtney to post something to google group once it gets a proof of concept
            
      4. Work on developing specifications for a Hydra API that can support archival collection management integration around the user stories we developed
         1. User stories have hit a wall, so how can we build from there?
         2. Mike G – recommends focusing on developing specific examples of this integration rather than the API
         3. Justin – Rockefeller, Michigan, and MIT interested integrating ArchivesSpace/Archivematica. Michigan may be interested in contributing with development of ArchivesSapce/Archivematica/Hydra integration (not on the call)
         4. Relation to ArcLight effort, particularly around ASpace front end – maybe bring Ohio State into the discussion about their work on front-end development of ArchivesSpace
         5. This effort is tabled for now until people are ready to do more development. If members of HAWG hear about outside entities working on development in this area, they are requested to make the rest of the group aware of it. As people do develop, request that people come back to the group with their work.
            
      5. Begin sharing institutional needs/action items beyond integration with ArchivesSpace
         1. Coordinating with Hydra Digital Preservation group – they are more of an interest group? This may be a bit of a mis-match, but there are some clear points of overlap of interest (Archivematica, BitCurator)
3. Action Item 5: what does this mean to us? - 25 mins
   1. Brainstorm: what broader archival concerns can this group help advance within the Hydra community? What issues are important to members? What is the best way for us to structure this broader focus going forward?
      1. Opportunities for meeting outside of HydraConnect?
         1. Code4Lib at Portland – Artefactual is proposing a preconference event for archives
         2. Should there be a MARAC/NEA meeting?
         3. A way to talk about the same problems despite the platform – a way to help archivists to think about the issues in a more strategic manner

4. New business

   1. Mike G. - Hydra steering group are coming up with a framework for working and interest groups since they are a way the community is coming up with new ideas. When it comes up, HAWG will need to make a choice as to which we type we fall under.
   2. Wendy – could we develop a tool-kit to help archivists to talk with IT (user stories, requirements gathering, etc)
      1. Internal-facing to hydra/archivist community – in-reach/education – webinar possibly given from Penn State?
      2. External-facing – SAA session? Outreach?

Action Items:

• Stanford and Artefactual are going to put what they shared today into writing and share via the Hydra-Community group to garner participation.
• Examine IG/WG framework when it comes out and figure out where we fit in — probably available by December — possible topic for next conversation.
• Penn State will inquire with one of our PMs to gauge her interest in conducting a webinar for the community on user stories.