Information Technology Reference
In-Depth Information
17.10.3.2 AIP Roles
While all AIPs are built around a digital asset that needs to be preserved, some fill
additional functions in the preservation system, such as transformation modules,
fixity modules, or even serving as another AIP's RepInfo. To handle these “spe-
cial AIPs” properly, a preservation system needs to somehow mark them as such.
For this reason, PDS supports various AIP roles, which are indicated upon ingest
through the packageType attribute of the XFDU manifest's informationPackageMap
element. An AIP that also serves as another AIP's RepInfo should thus be marked as
follows:
<informationPackageMap packageType
=
"ContentRepInfo">
...
</informationPackageMap>
Other roles include FixityModule for AIPs containing ingest modules for fixity
calculation, CategoryRepInfo for classifying RepInfo objects, etc. An AIP that is not
“special” is indicated by packageType
=
“Standard”, or, as the packageType attribute
is optional, by not adding the attribute.
17.11 Authenticity Manager Toolkit
Chapter 13
is devoted to Authenticity and some useful tools. Therefore in this
section we focus only on the interfaces.
17.11.1 AUTH - Authenticity Manager Interfaces
Component name
CASPAR Authenticity Manager
Component acronym
AUTH
Authentication is a process. In order to manage this process,
it's necessary to describe:
1. the procedure to be followed (per object type),
2. its outcome (per object),
3. the evolution of the procedure and its outcome
over time.
In this perspective, the Authenticity Management
responsibilities is to manage/monitor Protocol (Procedure)
for Authenticity in order to:
Component description
