Repository navigation
feat: read-only archival metadata from the storage layer (D3 proof of concept) - #1
Merged
Merged
Conversation
Adds the archiefmeta app: a read-only "Archive" tab in the Files sidebar with the MDTO fields classificatie, bewaartermijn, zorgdrager and identificatie. Each value carries its source and read time. - Sources behind IMetadataSource: S3 Object Lock retention and legal hold, S3 user metadata and tags (mdto-*), administrator values set with occ, and the Nextcloud file ID as a visibly non-durable fallback. - Values stored as core file metadata with EDIT_FORBIDDEN behind IMetadataStore, so a later switch to the schema API is one class. - Refresh on write, copy and move, and through occ archiefmeta:refresh. - Read-only OCS endpoint; no write endpoint. - PHPUnit unit tests, live integration test script, demo script, English and Dutch strings.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
First version of
archiefmeta: a read-only "Archive" tab in the Files sidebar that shows MDTO fields (classificatie, bewaartermijn, zorgdrager, identificatie) from the storage layer, each with its source and read time.Design: sources behind
IMetadataSource(S3 Object Lock + legal hold, S3 user metadata and tags, administrator via occ, Nextcloud file ID fallback). Values stored as core file metadata withEDIT_FORBIDDENbehindIMetadataStore, so the move to the Nextcloud 36 schema API (nextcloud/server#66355) is one class. Seedocs/architecture.md.Verified locally
COMPOSER_PROCESS_TIMEOUT=0 composer check: php -l, php-cs-fixer (nextcloud/coding-standard) 0 issues, PHPStan level 8 no errors, PHPUnit 54 tests / 233 assertions OK. Exit 0.npm run lint(eslint, @nextcloud/eslint-config) exit 0,npm run buildOK.composer audit: no advisories.npm audit: 24 low/moderate, all transitive (webdav, minimatch, eslint and vite plugins).tests/Integration/live-test.shon the vng-ol instance (Nextcloud 34.0.0.12, S3 primary storage with Object Lock GOVERNANCE 1d, external S3 mount): 25 passed, 0 failed. Evidence indocs/integration-evidence.md.s3-object-lock; tags, metadata and legal hold appear after refresh.nc:metadata-archiefmeta-*refused for owner and for a share recipient with edit rights: HTTP 500,FilesMetadataException: you do not have enough rights to update 'archiefmeta-classificatie' on this node. Stored values unchanged afterwards.docs/screenshots/.No CI is configured on this repository yet.
Known limits
identificatiefalls back to the Nextcloud file ID, labelled not durable (Stable record identity across versions, alongside hash-based file identity nextcloud/server#66499).occ archiefmeta:refresh.🤖 Generated with Claude Code