NDSA:Open Source Software

References

• Four use cases (Harvard): File:Use case.pdf

1. We need to choose software solutions, potentially open source, for a project.
2. We learn of an opportunity to participate in an existing project to collaboratively develop an open source software product.
3. We see an opportunity to initiate the development of a collaborative open source software product.
4. We have locally-developed software that could be made open source.

• Decision Support Tools. Code4Lib wiki. [1]
  • Includes advantages, disadvantages and costs of using OSS, and links to other relevant documents

• Reflections on open source software projects and digital stewardship
  • Post about SIMILE Exhibit: Lessons Learned for Sustainable Open Source Software for Libraries, Archives and Museums
  • Post about Omeka: Growing Open Source Communities: Omeka, End Users, Designers and Developers

Working Title

25 Questions to ask when considering open source software for digital stewardship and preservation

Goal

Refine a set of questions or a decision tree that we provided to help guide decisions around open source software’s use in digital preservation and digital stewardship.

Process

We work off of Andrea’s set of questions, refine them and tweak them if we like. Then we set up a series of calls with people we identify as having some particular insight and or expertise. We send them the revised document before hand, and then give them a chance to comment on the initial set of questions. They can offer stories of times when a given issue was particularly important, make suggestions for how they would prioritize these issues, remark on what they think should also be included or if there are some things that don’t need to be included. We take significant notes on each of the calls and post those up on the wiki as we go. So, we would have monthly calls with one expert a month for, say five or six months. After each call we would tweak our document in light of the previous calls and organize our notes to keep track of things we will want to talk about in a final report that accompanies the final revised set of questions. At the end of this process we would have a set of organized questions that partners could use as a tool, we would then also produce a report that explained why these were particularly important questions based on our own experience and including commentary from those involved in the process.

Schedule

Here is a quick schedule I would suggest for working on this:

1. January we identify, contact, and schedule our conference call speaker/commenters
2. Feb through June we do monthly calls with speakers, taking notes and iteratively revising our set of questions.
3. July we share the questions and something reflecting on their development at the NDIIPP/NDSA partners meeting.
4. Aug-September, we draft the final report doc
5. October-December we would disseminate the resulting products and start planning our next project.