Monday, May 11, 2015

Lessons learned in developing digital preservation tools the right way (and the wrong way).

Lessons learned in developing digital preservation tools the right way (and the wrong way). Paul Wheatley.  iPRES 2014 - Proceedings. October 2014.
There have been difficulties with creating digital preservation tools in the past, including poor technology choices, half measure in adopting open source applications, limited project funding, gaps in capabilities, poor support, and others. The wish list of tools from several years ago hasn't changed much. "Why can't we have digital preservation tools that just work?" But there have been new approaches which focus more on practical applications, sharing ideas with others and engaging with existing projects.

Lessons learned  in developing digital preservation tools:
  • Be agile in the development. Develop, demo, and get feedback from users. Get crude results first, then perfect and polish later.
  • Re-use, don't re-invent. There are often tools outside of the preservation community.Try existing solutions first.
  • Keep it small and simple. Modularize in the face of growing requirements. Make it so the tool can be integrated into others' workflows.
  • Make it easy to use, build on, re-purpose, and maintain. Share the source and package for easy install.
  • Share results, knowledge; learn from others.Let others know what you are doing.

The poster includes:
  • Engage with the community
  • Build on existing work
  • Design for longevity
  • Ally with a more long lived organization as a custodian


No comments: