NDSA:August 21, 2013 Meeting Minutes
Attendees
- Bailey, Jefferson, Metropolitan NY Library Council
- Grotke, Abbie | Web Archiving Team Lead, Library of Congress, and Co-Chair of the NDSA Content Working Group | abgr@LOC.GOV | 202-707-2833 | @agrotke
- Hartman, Cathy | Associate Dean of Libraries, University of North Texas/ Co-Chair of the NDSA Content Working Group | cathy.hartman@UNT.EDU
- McCain, Edward | University of Missouri | mccaing@missouri.edu
- McAninch, Glen | Kentucky Department for Libraries and Archives | Glen.McAninch@ky.gov
- McMillan, Gail | Virginia Polytechnic Institute and State University | gailmac@vt.edu
- Moffatt, Christie | National Library of Medicine | moffattc@mail.nlm.nih.gov
- Rudersdorf, Amy | Digital Public Library of America | amy@dp.la
- Stoller, Michael | New York University | Michael.stoller@NYU.EDU
- Taylor, Nicholas | Stanford Univ. Libraries
- Wurl, Joel | National Endowment for the Humanities | jwurl@neh.gov
Agenda
Brainstorm of:
- what questions we'd like to repeat from the 2011 survey --what
- topics/issues that were brought up in survey that we might want to delve deeper into
- new questions we might ask
Discussion Notes
Kristine Hanna (IA) couldn't join us today but submitted these comments to Abbie, which she shared with group:
1) I think it would be extremely helpful to see the progress organizations have made in the last two years. Sort of a "are you better or worse off than in 2011" type of polling.
2) I keep hearing over and over gain the need to understand internal work flows, skill sets required, resources needed to initiate and sustain a web archiving program. And the answers might be different for a one person shop than with a five person team. Or they may be the same. Perhaps we could have more in depth questions around this area.
General Comments
- Michael found it comforting in reading original survey that things they were struggling with, others were struggling with too.
Possible New Areas To Explore
WORKFLOWS - would be helpful to learn more about what workflows people have in place for acquisition of web content. Multiple choice might be hard; descriptive open-ended comment field?