SRQ7.47 - Document Versioning: Implement Document Versioning

BLOCKS / BLOCKED BY: none

TICKET ORIGIN (PERSON / EVENT): contract requirement of version control.

RELATED SOLUTION REQ(s): Solution must provide a document version control mechanism for forms submitted (including captioned photos) and resulting versions from internal staff edits/reviews.
RELATED TICKET(s):

ISSUE DESCRIPTION / CONTEXT:

to meet current business needs related to document audit and backup.

photos/docs versioning is built into the S3 configuration (MVP1) FOR DIGITAL OBJECTS, setting how many versions of a document to keep. can make this infinite. Andrew's group does the configuration because it happens in the S3.

Digital forms (MVP2 OR MVP3) OR INFORMATION IN YOUR DATABASE become a series of attributes that are auditable in the audit trail, unless we choose to generate/print it as a digital object like a PDF (yes).

USER STORIES:

**Given** a document
**When** uploading to BCAP
or editing after the initial upload
or overwriting the same file as before
**Then** the document version is incremented by one
and previous versions can still be opened and downloaded

**AC**:

- [ ] Confirm infinite document versioning is enabled in S3 storage via the Optimize team @ NRIDS.
- [ ] Any document uploaded is versioned
- [ ] Changes are tracked and can be reverted by recalling a previous version
- [ ] For images, changes to captions and any other image-specific attributes are tracked as changes to the document version number
- [ ] Users can see and access all available versions
- [ ] Users can delete unwanted versions (is a double-check 'are you sure you want to permanently delete this file?' popup out of the box for deleting files in BCAP?)