UC-5.7
Revision as of 12:59, 4 September 2009 by Evelyn McLellan (talk | contribs)
Main Page > Requirements > OAIS Use Cases > UC-5 Preservation Planning > UC-5.7 Develop Migration Plans
UC-5.7 Develop Migration Plans[edit] | |||
Summary | |||
Number | UC-5.7 | ||
Name | Develop Migration Package | ||
Context | UC-5 Preservation Planning | ||
Sub-Use Cases | None | ||
Overview | Develop Packaging Designs and Migration Plans receives migration goals from Administration>Establish Standards and Policies, develops and tests migration package (migration plans, IP designs, and migration software) and sends migration package to Administration>Manage System Configuration. New IP designs are also sent to Administration>Audit Submission and Administration>Negotiate Submission Agreement. | ||
Actors |
| ||
Description | |||
Preconditions | UC-1 Ingest | ||
Trigger | Administration>Establish Standards and Policies sends migration goals to Develop Packaging Designs and Migration Plans (Step ?? of UC-4.5) | ||
Successful outcome | Develop Packaging Designs and Migration Plans sends migration package to Administration>Manage System Configuration and sends IP designs to Administration>Audit Submission and Administration>Negotiate Submission Agreement. | ||
Steps |
| ||
Exceptions | |||
Documentation | |||
Citations | OAIS Page 4-14, section 4.1.1.6 "The Develop Packaging Designs and Migration Plans function develops new IP designs and detailed migration plans and prototypes, to implement Administration policies and directives. This activity also provides advice on the application of these IP designs and Migration plans to specific archive holdings and submissions. This function receives archive approved standards and migration goals from Administration. The standards include format standards, metadata standards and documentation standards. It applies these standards to preservation requirements and provides AIP and SIP template designs to Administration. This function also provides customization advice and AIP/SIP review to Administration on the application of those designs. If this function encounters submissions that are not covered by existing standards and procedures, it can send issues to Develop Preservation Strategies and Standards and receive advice, including new standards, to assist in meeting the new submission requirements. The migration goals received by this function tend to involve transformations of the AIP, including transformations of the Content Information to avoid loss of access due to technology obsolescence. The response to the migration goals may involve the development of new AIP designs, prototype software, test plans, community review plans and implementation plans for phasing in the new AIPs. This process may call on expertise or resources from other functions within Preservation Planning, such as prototype development from the Monitor Technology. This effort also will require consultation from the other functional areas and from the Designated Community. Once the migration plan, associated AIP designs, and software have been tested and approved, this function will send the entire migration package to Administration, which will schedule and perform the actual migration." | ||
Diagrams | |||
Notes | |||
|