-
Notifications
You must be signed in to change notification settings - Fork 6
Closed
Milestone
Description
Designs:
-
Immutable Storage: Ensure that once a dataset version is "frozen," it becomes immutable, meaning it cannot be altered or deleted. This maintains the integrity and authenticity of the data.
-
Versioning
-
Need to make sure its associated metadata and etc are also frozen
- Extractor Metadata is versioned right now tied to file version
- Double check if it's also applicable to dataset
-
Try Zenodo and screen capture
- upload file which version does it start
- how does update works
- "current" you can edit
- once a DOI is minted you can not change
-
Mongodb:
- Have a separate immutable collection for frozen documents. Once data is finalized, move it to these collections, and restrict write operations on them to enforce immutability.
- ? Same collection with Version field
- Set proper "read-only" access on document level (try how hard it is; low priority)
https://studio3t.com/knowledge-base/articles/mongodb-read-only-mode/
https://www.mongodb.com/docs/manual/core/collection-level-access-control/ - Regular backup of the frozen dataset - the whole mongo instance separate ticket
-
MinIO
- Look into object locking and retention policy in MinIO https://min.io/docs/minio/linux/administration/object-management/object-retention.html
- Data replication and regular backups
-
Checksum Verification (do we need that?)
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
Done
Status
Done