NDSA:Content Team To-Dos

From DLF Wiki
Revision as of 15:39, 30 January 2012 by Abgr (talk | contribs) (Created page with ' ==BACKGROUND DOCUMENT== As we prepare for working together on Content Teams, Abby Rumsey recommended CWG might want to read (or reread) the Blue Ribbon Task Force report [ http:…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

BACKGROUND DOCUMENT

As we prepare for working together on Content Teams, Abby Rumsey recommended CWG might want to read (or reread) the Blue Ribbon Task Force report [ http://brtf.sdsc.edu/biblio/BRTF_Final_Report.pdf] executive summary (p1) and also the sections on the four content domains and recommendations for stakeholders to take action – how archives can be there before (to help them create archival content) and when donors are ready to hand-off content in need of preservation.


DEVELOPING CASE STUDIES

1. Content teams decide categories of content that are important in their groups (ie. Blogs of NGOs, legal blogs, citizen science sites, local newspaper websites, etc.)

2. Develop one or more case studies that could be shared broadly to get others thinking about the topic. Show why things are at risk. Encourage the cultivation of relationships. Content team members could share experiences they’ve had, document successes and failure in negotiating such relationships around content they know and care about.

Case studies ideally would define:

  • Rationale for collecting – why is this at risk, what value does the content have?
  • Pitch to donors – how did you or do you plan to build your approach?
  • Barriers for users/creators – what challenges did you/might you face?
  • Actionable items – what can we do next, as a community (or individual institution)?

UNT will provide a sample from a recent experience they've had that could serve as a useful model.

3. Share results with broader CWG members, for discussion and feedback. Ultimately, we'll want to share more broadly to raise awareness about risk and value of content.