NDSA:June 18, 2012 Standards Working Group Notes: Difference between revisions

From DLF Wiki
No edit summary
No edit summary
Line 32: Line 32:
{|-
{|-
| July 18-August || Staffing survey goes out  
| July 18-August || Staffing survey goes out  
|-
| Week of August 20 || Close out survey, collated data, generate graphs
|-
| Week of September 4 || 1st draft of text for poster (action team works off-line)
|-
| September 13 || WebEx for 2nd draft of poster
|-
| Week of September 17: Polish up final draft of poster text, copy edit, finalize graphs/images
|-
| September 24-26 || Poster is printed
|-
| September 27 || Poster is done and ready to transport to iPres
|-
| October 1-5 || iPres conferenc
|}
|}



Revision as of 13:51, 18 June 2012

Action Items

  • People are encouraged to send brief updates on conference attendance and summaries to the email list.


Workshop/Conferences/Cool Stuff to Share

  • Linda attended Screening the Future Conference in CA which dealt with audio/visual content. It was organized by the PrestoCentre Foundation, in collaboration with the University of Southern California Shoah Foundation Institute and Digital Repository. Some of the Master Classes were good and others not so much. One take-away is that a number of university's are setting up digital preservation services not just for themselves, but opening them up to external organizations. These appear to be robust back-up services. For example, if you are a UCS faculty, you can pay per TB for 20 years. For an external party it is $4200 for 1 TB for 5 years. The tapes are loaded onto a robotic system and they run fixity checks every 6 months. They will migrate the media every 2 years. The backup includes 2 copies on campus at USC. A party could pay for a 3rd copy to be stored at Clemson University. CDL PPT is on-line (https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&ved=0CFMQFjAB&url=https%3A%2F%2Fwiki.ucop.edu%2Fdownload%2Fattachments%2F163610649%2FScreening-the-future-UC3-cost-model.pptx%3Fversion%3D1%26modificationDate%3D1337056116485&ei=WnLfT-zRHoLa6gHI0ayhCw&usg=AFQjCNH_7sqLGB2Na3LxsG9MG-B1oYEywg&sig2=Ec91h9vj7_bQyLxN8rEJnA). CDL was $1400 per TB per year for internal folks.
  • Mat Shultz and his colleagues from MetaArchive where in Boston recently to attend several conferences. One was Digital Directions (where Katherine talked about community sourcing). He was at another that focussed on the lifecycle and preservation needs of e-thesis and dissertations. MetaArchive.org/imls can check out the Wiki. Conferences were really interesting.
  • MetaArchive is also looking into new grant project to look at preservation of digital newspapers.


MetaArchive, Distributed Preservation, and OAIS:

  • Matt Shultz spoke about the framework MetaArchive is working on to help apply OAIS to distributed digital preservation environments.
  • This work was started on the tail of MetaArchive's TRAC self audit from 2010.
  • MetaArchive has spoken with other distributed preservation organizations such as LOCKSS based groups and Chronopolis, and also the Library of Congress and everyone encouraged them to put together a working group and action team within this standards group, lead by MetaArchive and Educopia (MA parent institution), to poropose a framework for applying OAIS to a distributed environment.
  • They began in early 2011 and have posted work to the NDSA Wiki (http://www.loc.gov/extranet/wiki/osi/ndiip/ndsa/index.php?title=DDP_OAIS_Frameworks), including:
    • statement of purposes
    • white paper porposal as a starter document for advancing this set of work
    • Started use case and gap analysis
  • They are working closely with Els at the KB (who is leading Danish National Bit Repository).
  • Work on the white paper has ramped up in past couple of months and they will have it finished ahead of the July NDSA meeting where time has been set aside to pull together interested parties to wrangle over the white paper.


Status of Preservation Staffing Survey

  • Andrea, Meg and Jimi are working on a poster proposal for iPres meeting. They have not heard back yet.
  • The survey is just about ready to go. May want to tweak some language at the front about preserving the data in the survey.
  • The proposed schedule for circulating the survey and analyzing the data is as follows:
July 18-August Staffing survey goes out
Week of August 20 Close out survey, collated data, generate graphs
Week of September 4 1st draft of text for poster (action team works off-line)
September 13 WebEx for 2nd draft of poster
Week of September 17: Polish up final draft of poster text, copy edit, finalize graphs/images
September 24-26 Poster is printed
September 27 Poster is done and ready to transport to iPres
October 1-5 iPres conferenc


* Thinking about circulating it around July 18th , to accomodate vacations. * Gives us a month to put it out -- till mid-August. * A month or so to analyze it. * Put together poster by 1st week of October. * We'll need to think about how to do the analysis, once we get the results back? * Do we have a predetermined list of whom to distribute it too? No. * * NDSA list and probably others. * We want it to go to anyone who does digital preservation. * All records labels meeting in Helsinki in a month and trying to transfer NDIIPP stuff to ddex.net. * Everyone add to a list of places to send over the next months (list will be on the Wiki)

* Looking at letter ... we think it looks good. * * We probably want to add something about archiving the survey results. * We'll also need to change the language at the top of the survey. * We were not intending to share the data back to the institutions, though it will be publicly available -- we should reinforce that in the email. * Could also add that on request, we will send you a copy of your institution's data. Its possible to print out your results at the very end, but "it's awful". * Andrea will add some text in.

* Who will adjuticate responses? * * Some done for us. * What more analysis do we want to do on it? Perhaps we need an action group to do more detailed analysis?

* Will send it out to our list and then the rest of us can send to appropriate places (be sure to replace the "[YOUR NAME]" text.