NDSA:Tech Community Engagement: Difference between revisions
| Line 8: | Line 8: | ||
*Make it easy for LAMs to preserve the content produced by your users – enable preservation through your API. | *Make it easy for LAMs to preserve the content produced by your users – enable preservation through your API. | ||
*Don't push off all the costs of preservation to libraries, archives and museums | *Don't push off all the costs of preservation to libraries, archives and museums | ||
*Make sure you have a broad group of the community at the table when you discuss future IT strategy. | |||
==What Do We Have to "Offer" the Tech Community?== | ==What Do We Have to "Offer" the Tech Community?== | ||
Revision as of 18:24, 2 August 2012
Back to the Public Awareness page.
Back to the NDSA:Outreach Working Group Home.
What Would We "Ask" of the Tech Community?
- Make it easy for LAMs to preserve the content produced by your users – enable preservation through your API.
- Don't push off all the costs of preservation to libraries, archives and museums
- Make sure you have a broad group of the community at the table when you discuss future IT strategy.
What Do We Have to "Offer" the Tech Community?
- resources to educate the Tech Community about digital preservation and long term data viability
- guidelines for entering into digital preservation partnerships with libraries and archives
- collaborative opportunities to look at how to include digital preservation partnerships into terms & conditions
- forums for discussion, scholarship, and industry best practices for digital preservation
- The prestige of collaborating with memory institutions.