Information Technology Reference
In-Depth Information
AIP
XFDU Manifest
RORRI
CPID
Data File
RIN
Fig. 14.20
Using a remotely stored RIN
introduces the risk of possible loss of access to the RIN network but reduces
the amount of storage space and hence the cost of archiving large data sets. The
RIN can much more easily change and evolve in line with the community as its
knowledge changes.
An intermediate case would be to keep a local cache of the Registry/Repository's
RIN, updated periodically. This would remove the risk of loss of access to the
RRORI.
Of course a combination of the described implementations maybe required based
on the level or risk in the network model and the perceived degree to which the
designated community might change. As this section is focused on the idea of
RIN resource reuse, the following details the building and implementation of RIN
enabled packaging solutions.
14.11.8 Using CPIDs to Reference a RIN from an AIP
Persistent Identifiers have been discussed in
Sect. 10.3.2
; here we look at a practi-
cal example, although the persistence of this particular implementation cannot be
guaranteed.
When a RIN is referenced from an AIP, the RIN becomes, logically, a part of that
AIP, therefore it is important to discuss how this might be implemented. Because
each piece of RepInfo has its own RepInfo, one need only point using CPIDs to the
immediate dependencies and the whole RIN can be accessed.
The mechanism to connect the XFDU packages built by CASPAR and their data
assets to the RIN in RORRI uses the attributes of the XFDU metadataReference
type. For instance in the example below we have a “metadata” object categorised
and classified using OAIS terminology as semantic RepInfo, the reference is to a
RepInfo object stored within RORRI identified by a URI, the location type has been
listed as CPID and the XML identifier is set to the CPID value. At the point of pack-
age construction, the CASPAR packaging component, given the data and a CPID,
