Information Technology Reference
In-Depth Information
can pull extra information from RORRI such as textual descriptions of the RepInfo
and these can be inserted into the XFDU manifest.
<
metadataObject
category=
"REP"
classification=
"SEMANTIC"
ID="REP_OTHER01">
<
metadataReference
otherLocatorType=
"CPID"
locatorType="OTHER"
href=
"http://registry.dcc.ac.uk/omar/registry/http?interface=QueryManager&method=getR
epositoryItem&param-id=urn:uuid:fe5b94c3-070c-4a9e-af7a-b355aa6b37b8"
textInfo=
"Semantic description Climate Forecast standard Names XML description"
ID=
"cpid-
fe5b94c3-070c-4a9e-af7a-b355aa6b37b8"
/>
</
metadataObject
>
Fig. 14.21
Example of addition to XFDU manifest
This method provides an entry point into the RIN, a first level dependency. Using
the CASPAR Packaging subsystem, if required it is possible to download all further
necessary RepInfo in the network for addition into an AIP.
14.11.9 Packaging Guidelines
From the experience gained and lessons learnt from the work undertaken through
the CASPAR project and the STFC we define 10 steps which we feel will facil-
itate the preservation of digital assets using information packaging. These are as
follows:
1. Understand the complexities of the digital asset to be preserved, what is it used
for currently? Why is it important?
2. Understand the Designated Community, what are their needs, what skills do
they currently use to get value from the asset
3. Perform preservation analysis in order to full understand and realise the risks
and threats to the digital asset
4. Clearly state the preservation objectives for the digital asset based on risks and
costs involved - remember that depositors should also have some input into this
5. Use preservation network modelling to determine the scope and complexity
of the RepInfo and PDI required for the digital asset to ensure its long term
understandability. Structural and Semantic RepInfo are both essential to ensure
the long term understandability of the asset
6. Be aware of, or discover, existing sources of RepInfo such as RORRI which
may provide the reuse of an available RIN for the digitally encoded object in
question.
7. Determine whether it is appropriate to embed the RepInfo directly with the
asset inside the package (“all-in-one”), reference a remotely stored RIN, or use
a combination.
8. If packages are to be ingested by an archive it may be necessary to formulate an
agreement between the producer and archive stating the specifics of what needs
