Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Align behavior of server managed properties with Fedora. #971

Merged
merged 1 commit into from
Nov 13, 2024

Conversation

dlpierce
Copy link
Member

Fixes #970

Fedora's criteria for determining if a property is server managed has been more selective than Valkyrie's. Relevant docs and code:
https://wiki.lyrasis.org/display/FEDORA6x/Server+Managed+Triples
https://github.com/fcrepo/fcrepo/blob/1cae11d1bfb1fda3ddd39f0ab8c01f780f3c3432/fcrepo-kernel-api/src/main/java/org/fcrepo/kernel/api/RdfLexicon.java#L74-L75

The spec is based on the needs of the Hyrax ResourceStatus service.

Fedora's criteria for determining if a property is server managed has been more selective than Valkyrie's.
Relevant docs and code:
https://wiki.lyrasis.org/display/FEDORA6x/Server+Managed+Triples
https://github.com/fcrepo/fcrepo/blob/1cae11d1bfb1fda3ddd39f0ab8c01f780f3c3432/fcrepo-kernel-api/src/main/java/org/fcrepo/kernel/api/RdfLexicon.java#L74-L75

The spec is based on the needs of the Hyrax ResourceStatus service.
@tpendragon tpendragon merged commit 9ade54d into main Nov 13, 2024
10 checks passed
@dlpierce dlpierce deleted the fix-fedora-info-ns branch November 14, 2024 14:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Fedora adapter filters all fedora.info values
2 participants