- Purpose
- Keep a body of written or uploaded material in a place where members can find it and revise it.
- Operational principle
- If a member writes a document or uploads a file, it exists in the workspace with a name and a body; when they revise it, others find the revised body under the same name.
- State
name: Document -> one Namecontent: Document -> one BodydocumentType: Document -> one Typeauthor: Document -> one UsercreatedBy: Document -> one Userversion: Document -> opt Versionpath: Document -> opt Path
- Actions
createDocument A member writes a document, giving it a name, a type and a body.editDocument A member revises a document; the new body replaces the old under the same name.uploadFile A member adds a finished file as a document, with a name, a type and a path.
- Misfits
- A revision replaces the body, so what the document said before is gone unless something else kept it.
- An uploaded file and a written document look alike in a list but behave differently when opened, and the concept does not say which is which.
- A document's name is the only handle on it; two documents with the same name are told apart by nothing the concept holds.
- Also called
- files, docs, pages
- Appears in
- Google Drive, Notion, Dropbox, Confluence