Video Wiki Manifesto
From ActiveArchives
Pipeline: Dynamic processes, Static results
Why static results?
- Example of consultation of an archive requiring only static files
- Efficiency (static files, caching)
- Long term (imagine viewing in 10, 20 years)
- Self-containedness
- Portability
- Security is physical access
- Ecological component: ability to "work" when stored offline (the USB stick example)
But also:
- Creative/Unexpected reuse: Example of taking the titles of one film and playing them against another resource
The "self-containedness" of a resource (like an SRT file) avoids the over-determinednes of a "perfect system" that might (inadvertantly) over-constrain what can be done with a resource. Better a "dumb" system that can be "hacked" into doing many things, than a "smart" one that holds works close to particular work flows.
Database-primary access means that interventions can only occur at the "source", ie via the "proper channels" of a web framework dictated API. Pipeline access allow for intervention at any part of the process, with or without the (1) technical functioning, (2) knowledge or permission of pieces earlier on in the pipeline.
Web 2.0 and "Flickrland": Web 2.0 services are problematic as they generally work to centralize and control how resources are viewed, and act to remain the primary source for working with a material, generally discourage copying of the actual resource as a means of holding on to this centrality.
Responsible Publishing: Storing Provenance and Versions
Cite Jeni Tennison -- Responsible Publishing
Storing "static" output of a process does not however mean that the chain of events that led to its production ought to or needs to be lost. Remembering the provenance (sources) and keeping versions of changes are essential tools to complement the "static" pipeline production.
