-
Notifications
You must be signed in to change notification settings - Fork 34
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
Representing Recoverability of Unallocated Files #251
Comments
This is being tracked in OC-119. |
Transfer UCO CP-43 Representing Recoverability of Unallocated/Unavailable Files to https://github.com/ucoProject/UCO/tree/Feature-CP-43 |
Submitted pull request to resolve this issue and satisfy requirements in CP-43 |
Transcribed CP43 examples to https://github.com/casework/CASE-Examples/tree/uco-issue-251/examples/illustrations/recoverability |
A follow-on patch will generate Make-managed files. References: * ucoProject/UCO#251 Signed-off-by: Alex Nelson <[email protected]>
References: * ucoProject/UCO#251 Signed-off-by: Alex Nelson <[email protected]>
References: * ucoProject/UCO#251 Signed-off-by: Alex Nelson <[email protected]>
References: * ucoProject/UCO#251 Signed-off-by: Alex Nelson <[email protected]>
Discussing with @ajnelson-nist we decided that RecoveredObjectFacet is a more suitable name for this. I am making edits to PR in preparation for Solution vote. |
Implement 2018 approved CASE change proposal that is listed on caseontology.org website:
https://caseontology.org/resources/references/Representing%20Recoverability%20of%20Unallocated%20Files%20using%20CASE%20UCO%2031Jan2018.pdf
See UCO CP-43 - Representing Recoverability of Unallocated Files
The text was updated successfully, but these errors were encountered: