Minnesota Recordkeeping Metadata Standard:
Preservation History Element
ELEMENT 17: PRESERVATION HISTORY
| Definition: | The dates and descriptions of all actions performed on a record after its registration into a recordkeeping system which ensure that the record remains readable (renderable) and accessible for as long as it has value to the agency or department, and to the community at large. | ||||||||||||||||||
| Purpose: |
To act as a tool for preservation management. To provide a history of all preservation actions carried out on a single record over time. To provide evidence that an agency took all due care to keep its records of value both readable and accessible. |
||||||||||||||||||
| Rationale: | Agencies are required under Minnesota Statute 15.17 to "carefully protect and preserve government records from deterioration, mutilation, loss, or destruction." | ||||||||||||||||||
| Obligation: | Optional | ||||||||||||||||||
| Applicability: | Migration from one data format to another is generally applicable at record level only (unless a series is comprised of records that are all in the same format). Movement of records from one hardware platform/software environment to another, or one medium to another, is applicable at both the record and record series levels. |
||||||||||||||||||
| Use Conditions: |
Use each time a preservation action is performed on a record—e.g. add information to this element whenever a record is migrated from one format to another or moved to a new medium. If used, this element should be used in conjunction with element 13. FORMAT, which provides information on which preservation strategies should be based. It may also be used in conjunction with element 18. LOCATION. The current details about the format and medium of the record shall always be recorded in element 13. FORMAT, sub-elements 13.2 Data Format, 13.3 Medium and 13.4 Extent. Some preservation actions which involve moving or copying from one medium to another may result in changes to details held in element 18. LOCATION. This element should also be used in conjunction with element 1. AGENT to document the agent responsible for performing or authorizing the preservation action (see Comments under 17.3 Action Description for information on linking to/capturing agent details). This element shall be linked to elements 12. AGGREGATION LEVEL and 14. RECORD IDENTIFIER. |
||||||||||||||||||
| Repeatable: | No | ||||||||||||||||||
Sub-Elements (Name, |
|
||||||||||||||||||
| Comments: | This element could be implemented as a history 'log'. As such, it would need to incorporate linked information about agents and (depending on the implementation) the records themselves. Which particular information about agents and record IDs/titles etc. is incorporated into this log is a system design decision that must be made by the agency. |
17.1 ACTION DATE/TIME
| Definition: | The date and time at which a defined preservation action on a record takes place. |
| Purpose: |
To provide system validation of preservation actions carried out on records. To restrict or facilitate access to records based on dates pertaining to particular preservation actions. |
| Obligation: | Mandatory |
| Use Conditions: | The system shall assign the date/time of the event when the corresponding Action Type (sub-element 17.2) is selected by the agent from a pick list of the assigned values—i.e., the selection of the event by the agent is the trigger for the date/time to be generated by the system. |
| Assigned Values: | - |
| Default Value: | Current system date/time. |
| Repeatable: | Yes |
| Assigned By: | System-assigned. |
| Schemes: | ISO 8601 standard for date/time encoding. |
| Comments: | - |
17.2 ACTION TYPE
| Definition: | A preservation action carried out on a record. | ||||||||||||||||||||||||
| Purpose: | To provide a finite (but extensible) set of defined preservation actions which can be used to describe how the record was maintained in a readable and accessible state over time. | ||||||||||||||||||||||||
| Obligation: | Mandatory | ||||||||||||||||||||||||
| Use Conditions: | - | ||||||||||||||||||||||||
Assigned Values: (Value Name, |
|
||||||||||||||||||||||||
| Default Value: | - | ||||||||||||||||||||||||
| Repeatable: | Yes | ||||||||||||||||||||||||
| Assigned By: | Assigned by an authorized agent from a pick list of the assigned values. | ||||||||||||||||||||||||
| Schemes: | Minnesota Recordkeeping Metadata Standard | ||||||||||||||||||||||||
| Comments: | Each time a particular action is carried out, it will change the current values displayed in one or more other sub-elements (refer to each event for specific details). Details of the old values shall be entered under sub-element 17.3 Action Description. |
17.3 ACTION DESCRIPTION
| Definition: | The specific details of the action. |
| Purpose: | To ensure the visibility and auditability of agency preservation management decisions and actions. To ensure accountability for records readability and accessibility. |
| Obligation: | Mandatory |
| Use Conditions: | - |
| Assigned Values: | - |
| Default Value: | - |
| Repeatable?: | No |
| Assigned By?: | Authorized agent. |
| Schemes: | Free text, agency-defined schemes |
| Comments: | The previous value of the particular record status being changed by the event may be recorded in this sub-element. This may be the information relating to the old format, medium and extent, which shall be taken from element 13 FORMAT, sub-elements 13.2 Data Format, 13.3 Storage Medium and (if used) 13.4 Extent, or it may be information relating to the location of the record, stored under element 18. LOCATION, sub-elements 18.1 Current Location or 18.3 Home Storage Details. It is strongly recommended that this information be structured in some way rather than being entered as free text. Use of templates will enable the information to be entered in a structured way, as well as allowing certain pieces of information to be automatically generated by the system rather than manually entered by the agent—e.g., required information about the agent could be automatically assigned to the template. Information about the agent performing the action shall be associated with the action itself. A decision will need to be made by individual agencies as to whether this association is implemented through links to separately held agent information, or whether agent information is automatically captured through the use of templates and stored as part of the Action Description. |
17.4 NEXT ACTION
| Definition: | The next preservation review, check, or action that the record needs to undergo. | ||||||||||||||||||||||||||
| Purpose: | To act as a tool for preservation planning and coordination. To enable searches on all records which next require a particular action. |
||||||||||||||||||||||||||
| Obligation: | Optional | ||||||||||||||||||||||||||
| Use Conditions: | May be used in conjunction with 17.5 Next Action Due. | ||||||||||||||||||||||||||
Assigned Values: (Value Name, |
|
||||||||||||||||||||||||||
| Default Value: | - | ||||||||||||||||||||||||||
| Repeatable: | No | ||||||||||||||||||||||||||
| Assigned By: | Authorized agent. | ||||||||||||||||||||||||||
| Schemes: | Minnesota Recordkeeping Metadata Standard | ||||||||||||||||||||||||||
| Comments: | - |
17.5 NEXT ACTION DUE
| Definition: | The date that the next preservation action is due. |
| Purpose: | To act as a tool for preservation planning and coordination. To enable searches on all actions due within a particular time period. |
| Obligation: | Optional |
| Use Conditions: | Use in conjunction with sub-element 17.4 Next Action. |
| Assigned Values: | - |
| Default Value: | - |
| Repeatable?: | No |
| Assigned By?: | Assigned by the system and calculated on the current date after an authorized agent selects from a pick list of set time periods (e.g., "3 months", "6 months", "1 year", "2 years", "5 years", etc.), or manually entered by the agent. |
| Schemes: | ISO 8601 standard for date/time encoding. |
| Comments: | This sub-element could be used to generate reminders at set (agency-defined) times before the action due date arrives. |
PRESERVATION HISTORY Examples
| 17.1 | Action Date/Time | 1998-06-14 | Scheme: ISO 8601 |
| 17.2 | Action Type | Microfilmed | |
| 17.3 | Action Description | Microfilmed at Dakota Microfilm per schedule |
| 17.1 | Action Date/Time | 2002-06-11T20:00-6:00 | Scheme: ISO 8601 |
| 17.2 | Action Type | Integrity Checked | |
| 17.3 | Action Description | Integrity checked per schedule | |
| 17.4 | Next Type | Check Integrity | |
| 17.5 | Next Action Due Date | 2003-06-11T20:00-6:00 | Scheme: ISO 8601 |
Minnesota Recordkeeping Metadata Standard: Version 1.1, July 2002.



