NDSA:Tuesday, January 31, 2017: Difference between revisions

From DLF Wiki
NickK (talk | contribs)
No edit summary
 
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
=== Agenda ===
== Attendees ==
* Carol Kussman
* Ed Busch
* Martin Kong
* Leah Prescott
* Bonnie Gordon
* Euan Cochrane
* Juan C. Romero
* Antonio Guillermo Martinez
* Andrew Berger
* David Pcolar
* Nicole Scalessa
* Sibyl Schaeffer
* Megan Rohleder
* Nick Krabbenhoeft
 
== Agenda ==
* Digital Media Log application overview - Bonnie Gordon
* Digital Media Log application overview - Bonnie Gordon
* LibSafe overview - Juan Romero
* LibSafe overview - Juan Romero
Line 9: Line 25:
** Staffing survey working group
** Staffing survey working group


=== Minutes ===
== Minutes ==
==== Digital Media Log application overview - Bonnie Gordon ====
=== Digital Media Log application overview - Bonnie Gordon ===
* Ruby-on-Rails worfklow app built to support inventory/imaging digital storage media included in archival collections
* Ruby-on-Rails worfklow app built to support inventory/imaging digital storage media included in archival collections
* Retrieves contextual data from ASpace API and exports JSON for storage with AIP
* Retrieves contextual data from ASpace API and exports JSON for storage with AIP
* https://github.com/RockefellerArchiveCenter/dm_log
* https://github.com/RockefellerArchiveCenter/dm_log
==== LibSafe overview - Antonio Guillermo Martinez ====
 
=== LibSafe overview - Antonio Guillermo Martinez ===
* LibNova is a digital preservation system builder since 2009 with US offices since 2016
* LibNova is a digital preservation system builder since 2009 with US offices since 2016
* Presented case study in implementing a digital preservation system for 1 PB of data for Madrid City Hall
* Presented case study in implementing a digital preservation system for 1 PB of data for Madrid City Hall
Line 22: Line 39:
** Scaled ingest processes across cloud servers to account for increased demand during initial ingest
** Scaled ingest processes across cloud servers to account for increased demand during initial ingest
** System checks fixity every month, requires 2 weeks to finish hashing
** System checks fixity every month, requires 2 weeks to finish hashing
=== Review Infrastructure Interest Group description on website ===
* The group agreed to deemphasize the discussion of the Levels of Preservation on the Infrastructure page and to describe as a past project
* It was also suggested to add links to members' current NDSA activities
=== Fixity working group ===
* Created 2 subgroups
** Survey subgroup designing, deploying, and contextualizing results
** Vendor information subgroup to gather information about how to vendors generate and use fixity information
=== Staffing survey working group ===
* Created Google Group to coordinate activity
* Currenlty refining previous survey questions based on results from the last iteration
* Plan to publish report by next September 2017

Latest revision as of 14:56, 31 January 2017

Attendees

  • Carol Kussman
  • Ed Busch
  • Martin Kong
  • Leah Prescott
  • Bonnie Gordon
  • Euan Cochrane
  • Juan C. Romero
  • Antonio Guillermo Martinez
  • Andrew Berger
  • David Pcolar
  • Nicole Scalessa
  • Sibyl Schaeffer
  • Megan Rohleder
  • Nick Krabbenhoeft

Agenda

  • Digital Media Log application overview - Bonnie Gordon
  • LibSafe overview - Juan Romero
  • Review Infrastructure Interest Group description on website: http://ndsa.org/working-groups/infrastructure/
    • What do we want to keep? Revise?
    • Which of the projects listed do we want to push forward?
  • Updates from working groups:
    • Fixity working group
    • Staffing survey working group

Minutes

Digital Media Log application overview - Bonnie Gordon

LibSafe overview - Antonio Guillermo Martinez

  • LibNova is a digital preservation system builder since 2009 with US offices since 2016
  • Presented case study in implementing a digital preservation system for 1 PB of data for Madrid City Hall
    • Used Level 4 of the NDSA Levels of Preservation as a reference to define system functions
    • Connected preservation storage system to access/discovery interface (Blacklight [1])
    • Used automated classifier to recognize and organize 98% of data staged for ingest
    • Scaled ingest processes across cloud servers to account for increased demand during initial ingest
    • System checks fixity every month, requires 2 weeks to finish hashing

Review Infrastructure Interest Group description on website

  • The group agreed to deemphasize the discussion of the Levels of Preservation on the Infrastructure page and to describe as a past project
  • It was also suggested to add links to members' current NDSA activities

Fixity working group

  • Created 2 subgroups
    • Survey subgroup designing, deploying, and contextualizing results
    • Vendor information subgroup to gather information about how to vendors generate and use fixity information

Staffing survey working group

  • Created Google Group to coordinate activity
  • Currenlty refining previous survey questions based on results from the last iteration
  • Plan to publish report by next September 2017