I've been thinking about how we communicate with audiences - about explaining what we're up to, about perpetual beta and iterative development versus traditional models of heavily reviewed authoritative publication... so I've been looking out for some good examples of information written for the public about cultural heritage technology experiments.
The headings below are straight from the top of my head - please add your own headings (and feel free to tidy them up if they get cumbersome) and your own examples.
What are we doing?
Rather than defining a set of services, we want to remain flexible and embrace the notion of “perpetual beta,” mirroring the collaborative, dynamic processes used in e-research and e-scholarship. To that end we are kicking off an e-Research task force which will employ several information-gathering strategies, ranging from brown bag discussions to a public planning wiki, and work together across disciplines and professional roles (e.g., scholar, librarian, IT professional) to identify themes and develop a plan of action.
Why are we doing this?
What's influencing this?
How can you get involved?
[What else?]
Comments (0)
You don't have permission to comment on this page.