/
February 20, 2015

February 20, 2015

Jun 16, 2017

Connect

Dial: +1 (530) 881-1400
Access Code: 651025

Attendees

Facilitator: Steven Anderson (Boston Public Library)

Notetaker: Mike Giarlo (Penn State)  Rick Johnson (Notre Dame)

  • Steven Anderson (BPL)

  • Anders Conrad (Royal Library of Denmark)

  • Dean Krafft (Cornell)

  • Mike Friscia (Yale)

  • Jon Stroop (Princeton)

  • Mike Morocco

  • Mark Notess (Indiana U.)

  • Will Cowan (Indiana U.)

  • Karen Cariani (WGBH)

  • Carolyn Caizzi (Northwestern U.)

  • Julie Rudder (Northwestern U.)

  • Glen Horton (Cincinnati)

  • Matt McVey (Tufts U.)

Agenda & Notes

  1. Roll Call

    1. Welcome New Folks  

    2. Attending

    3. Call for Agenda Items

  2. Next Call

    1. Date: March 13th

      1. Facilitator: Anders Conrad

      2. Notetaker: Mike Giarlo (volunteered in absentia   )

  3. Financial & Legal Services Proposal

    1. Progress report?

      1. Nothing new to report besides the email that is circulating. Please comment as +1, or -1 if you have not already

  4. Standing Community to-do's

    1. Reports back from meetings (if any)

      1. Code4lib

        1. 25 developers at Hydra meeting

          1. Spent a lot of time talking about the semantics of the word "Works" in Hydra::Works.  Looking for alternative.

          2. Looking at projecting model for Hydra:Works into Fedora 4

          3. Planning for updating ActiveFedora to better align with new API patterns in Fedora 4

          4. Some discussion by some interested in migration from DSpace to Sufia

    2. Next Partner and dev-centric meetings

      1. LAMDevConX, 23-25 March 2015

      2. Hydra Developers Congress 26-27 March 2015

        1. Focus likely on Fedora 4 and ActiveFedora, and other continuing threads from Code4Lib

      3. Hydra Power Steering 26-27 March 2015

        1. Look to Tom Cramer's email to hydra-partners for call of nominations for Hydra Power Steering Meeting:  2015 Hydra Power Steering Participants nominations

          1. Email post here: https://groups.google.com/forum/#!topic/hydra-partners/HC5JOHtIrxc

      4. Hydra Europe Symposium 23-24 April 2015

        1. Meeting at London School of Economics co-located with HydraCamp to have both hands-on training and discussion

      5. NE States Regional Meeting 7 May 2015

        1. Planning call happening February 25th at noon

      6. Open Repositories 8-11 Jun 2015

      7. Hydra Connect 3 - FYI: Minneapolis in late September or early October, dates tbc

    3. Training

      1. Hydracamp, 9-13 March 2015 at Yale Library

      2. Hydracamp, London 20-23 April 2015

        1. See Europe Symposium notes above

    4. Reports from Interest & Working Groups

      1. Archivists Working Group (no updates)

      2. Digital Preservation Working Group (no updates)

      3. User Experience Group (no updates)

      4. Connect 3 structure WG (CfP announced 1/5)

      5. Web presence WG (CfP announced 1/5)

        1. Have had a couple meetings, have done some work regarding personas work list on main Hydra wiki page:  Hydra Web Presence Audiences and Information Needs

        2. Interim report planned for power steering

        3. New website targeted by Hydra Connect 3 in the fall

      6. Service Manager IG (being formed?)

        1. Draft of scope and objectives Hydra Service Management Interest Group

        2. First meeting recently this month

        3. Proposal submitted to OR for service manager concerns

      7. Page viewer/page turner IG

        1. Met yesterday for first time, reviewed scope of ideas that will be covered soon

      8. Metadata Working Group (CfP announced 02/19)

        1. Announcement went out on list yesterday.  Wiki is here:  Samvera Metadata Interest Group

        2. Sign up on the wiki if you are interested

  5. Prospective Partner Intel Sharing

  6. Any other old or new business

    1. A reminder to please send monthly updates to the hydra-community list (rather than hydra-partners) unless they contain "sensitive" information.

    2. Question about Hydra being solution for digital preservation

      1. Carolyn Caizzi - (not necessarily full preservation solution at NU)

      2. Anders Conrad - Depends on definition of digital preservation, was raised at Power Steering group; suggests involving Digital Preservation Working Group

      3. Jon Stroop - Not sure what preservation solution really looks like and has more to do with policies that are implemented.  Hydra is a convenient or community based solution for implementing policies.   If you do not have great policies, and infrastructure is loosely thrown together than not doing preservation.  Work not done with just Hydra and Fedora.

      4. Karen Cariani - Can be used for variety of things and can do preservation

      5. Anders Conrad - Auditing and premis is one step to have Fedora be more preservation oriented, many people also require tools for managing checksums, etc at file layer to be full preservation solution

      6. Julie Rudder - Hydra 4 does not immediately support preservation but need to put in work to do that, metadata people 

      7. Mike Friscia - From IT side can figure out ways to do preservation

      8. Rick Johnson - We have separated preservation storage from Fedora and Hydra

      9. Anders Conrad - Separate module for reading files and sending to specialized bit archive