NDSA:Tuesday, January 31, 2017: Difference between revisions
Created page with "=== Agenda === * Digital Media Log application overview - Bonnie Gordon * LibSafe overview - Juan Romero * Review Infrastructure Interest Group description on website: http://..." |
|||
Line 21: | Line 21: | ||
** Used automated classifier to recognize and organize 98% of data staged for ingest | ** 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 | ** 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 |
Revision as of 14:40, 31 January 2017
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
- 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
- https://github.com/RockefellerArchiveCenter/dm_log
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