Matches in LOV for { <http://www.loc.gov/premis/rdf/v1#hasPreservationLevelRationale> ?p ?o. }
Showing items 1 to 8 of
8
with 100 items per page.
- hasPreservationLevelRationale type DatatypeProperty.
- hasPreservationLevelRationale comment "Examples: user pays, legislation, defective file, bit-level preservation only available for this format".
- hasPreservationLevelRationale domain PreservationLevel.
- hasPreservationLevelRationale range string.
- hasPreservationLevelRationale term_status "stable".
- hasPreservationLevelRationale definition "Definition: The reason a particular preservationLevelValue was applied to the object.".
- hasPreservationLevelRationale editorialNote "Rationale: Application of a particular preservationLevelValue may require justification, especially if it differs from that usually applied according to repository policy.".
- hasPreservationLevelRationale scopeNote "Usage Notes: This optional semantic unit records the reason for applying the preservationLevelValue. This information can be particularly important when the assigned preservationLevelValue differs from usual repository policy. For example, a repository may normally assign a preservationLevelValue of \"full preservation\" for JPEG2000 files, but detects that a particular file is defective. This may mean that the repository's preservation strategy for JPEG2000 may not be effective for this particular file, so the repository may assign a preservationLevelValue of \"bit-level preservation\" to this file, recording \"defective file\" as the rationale. Similarly, legislative requirements or contractual agreements may require a higher level of preservation to be assigned to a particular object than would be assigned to that class of object according to usual policy. In this case, the rationale for the assignment may be recorded as \"legislation\" or \"user pays\", for example. preservationLevelRationale may be repeated if more than one reason needs to be recorded.".