Document Version Control
From [[http://cpsquare.org CPsquare]], the community of practice on communities of practice.
Collects additional information around a version that is relevant to the development of a document, as distinct from the information that is appropriate in a library.Tracking versions of a document as it evolves or goes through the editing process
Uses in communities of practice
When a community does a significant amount of writing together, a version control system can be essential.
- Together/apart, Synch/Asynch:
Stuff below needs to be sorted out...
- Automatic time stamp Each time a document is revised, the date and time are recorded and made visible for others.
- Larger number of people involved.
- History of documents Labeling changes includes contextual information such as author, intention, status of the project or the document.
- Check-in / check-out A status indicator shows that someone has taken control of a file so others defer making changes.
- Multiple participants working on a document where a single-thread process will improve clarity or reduce cost.
- Subscription for modifications Email or other alerts when change in documents have occurred.
- Multiple activities make it desirable to focus on a subset of edit / change activities.