SAA 2016 Meeting

Owned by Bill Branan
Jun 16, 2017
3 min read

August 2, 2016, Atlanta, GA

Introduction from Ben:

Full text of comments: https://docs.google.com/document/d/1iGpBiszYGE_HF0-_00mpIEJ4uVN-RwO6K_o9imNA8_k/edit?usp=sharing

Attendees:

  • Joy Novak -- Washington U -- using Hydra for video streaming -- Avalon -- interested for digital preservation and serving special collections with finding aids and digital collections

  • Eira, Cincinnati -- hydra institution -- faculty repository -- product co-owners -- hydra head for visual resources for digitized, video, and bornd

  • Marcie -- tech services archivist at Cornell

  • Adrienne -- Tufts -- 7 hydra heads -- focused on migrating to fedora 4

  • Nathan T, Cincinnati -- also plans to implement ArchivesSpace over the next year -- integrations with Aspace and Hydra -- Archivematica coupling

  • Missed Name, Ohio State special collections -- product owner for digital collections system -- hydra/fedora -- sufia 7 introducing complex objects -- replicating hierarchy in digital collections -- finding aids

  • Nik Dragovic -- Emory -- requirements gathering for Hydra repo -- will also involve archival and born digital material

  • Elizabeth -- univ archivist at Oregon St -- user of Hydra -- Oregon Digital -- migrating from Dspace to Hydra for institutional repo

  • Erin, Cornell -- hydra for digital collections -- figuring out how to integrate hydra aspace archivematica

  • Mike, Umich -- integration project -- early design process to support ArcLight project -- user stories - development work around arc light

  • Samantha Cross - corporate archivist

  • Nicholas, Stanford -- interested in intersections of Hydra and web archiving and LOCKSS

  • Cliff Hight, Kansas, just here to check things out

  • Princeton -- born-digital, other digitized content

  • Bethany Scott -- University of Houston -- developing new repo based on Hydra in a Box for digital collections

  • Karen, graduate of Pratt -- part of linked jazz research team

  • Sherri Berger -- CDL -- aggregate content coming out of hydra heads

  • Laura Alagna, Northwestern -- 2 apps -- sufia IR coming

  • Glynn, Stanford -- interested in finding aids

  • Celia, Swarthmore -- 3 college consortium anticipating HinaB

  • Doreva -- PA Digital, DPLA, hydra aggregator, Temple, oral history repo using hydra, HinaB, sufia

  • Sarah, Chem Heritage, migration to sufia 7, ArcLight

  • Sam Meister, Educopia, intersection with educopia members, integration of tools, research and development across institutions, working on ETF workflows in sufia

  • Adam, Boston College, not hydra but hope to be, HinaB

  • Farrell, Noah, Duke, born digital, fedora 3 to 4, Aspace members

  • Lora, Johns Hopkins, migrating from Dspace to Dspace, ETd to Sufia, digital preservation, Archivematica

  • Seth, Clayton State, keeping pulse on digital in archives

  • Christie, GWU, implementors not partners, IR, ProQuest to Hydra migration of Etd

  • Rachel Trent, GWU

Notes

  • Themes: landscape of repositories for different needs, integration, formats, migration of apps, sharing of code/solutions, planning with a repository ecosystem and the role of archivists within that, which preservation solutions are part of that, finding aid delivery.

  • This is a lot -- too much? How might archivists focus their needs?

  • How interested is the community in developing needs for us? A (Ben): I think a lot based on my time in the hydra community, but how do we articulate those needs?

  • Local priorities are an issue too.

  • Should there be focus groups for archivists needs? Formal data gathering is a useful way to get things moving in Hydra.

  • Question: where do archivists fit into larger repository planning efforts?

  • Hydra is a lot of different things to different people. Different institutions implement in different ways. Pragmatic, maybe we need to pick one archival solution and organize around it. But also need to consider how other solutions fit into that.

  • Huge overlaps, but huge diversity of needs. Interested in making this group the best partners that archivists can be for software development. GWU is doing a pretty hardcore agile development process. There’s also a need for us to push our individual needs within institutions to drive more community dialogue.

  • Interest in a larger systems integration affinity group.

  • Maybe this group needs to continue to be a place for us to continue checking in on needs, and keeping the dialogue going. We are, after all, still just an interest group (that can spin off working groups as needed).

  • Could look at collectively writing user stories -- how to organize this effort? Don’t write user stories just for the hell of it -- needs to be a context.

  • Sharing, mapping, modeling workflows helps us better understand needs for systems integration.

  • Pre-conference day on agile development, user stories, workflows, data modeling, etc.

  • If we organize around this, are people interested?

  • Who is going to Hydra Connect? Maybe 4-5

  • “Archives for Developers” -- finding better ways for developers to learn more about we do. Getting the communication flowing both ways.

  • Digital Preservation interest group -- how we get more engagement with this group and other affinity groups in Hydra.

  • The existence of this group is a huge symbolic help for local conversation and expressing our needs.

  • Community stewardship -- building out what the community is, now defining the work, agenda, etc.

  • Looking to get a session on archives together for HydraConnect (erin, nathan interested). Virtual options