‹header›
‹date/time›
Klicken Sie, um die Formate des Vorlagentextes zu bearbeiten
Zweite Ebene
Dritte Ebene
Vierte Ebene
Fünfte Ebene
‹footer›
‹#›
different tasks
Asset descriptor: contains information about the asset; information about every single file in the asset
builder tool builds the asset: creates asset descriptor using the xml files for the presentation systems
it's the only descriptive metadata section which is stored in DIAS data management
Only metadata from data management can be used for retrieval
The other metadata can only be accessed by export the whole as as DIP; additional metadata will be kept in Asset Descriptor
not using PREMIS as internal metadata schema
project started in 2004: no final version of premis available
contains not only preservation metadata but also technical metadata; therefore it is stored in METS' <techMD> section
URN: NBN namespace
masterCreationDate: when this asset was created
Using bulder tool à masterCreationDate and metadataCreation date is always equal, as the builder tool creates both during a single process
masterCreationDate: when this asset was created
Using bulder tool à masterCreationDate and metadataCreation date is always equal, as the builder tool creates both during a single process
fielIdentifier: diffent from ID attribute in METS
Format: in future: PRONOM; now DIAS internal system format registry: attached to the registry DIAS handles view pathes (applications which can read those files)
Two xmlData elements: one from METS-namespace; one from lmerFile namespace Import jhove namespace / result from jhove directly into lmerFile:xmlData
Jhove xmlns=„http://hul.harvard.edu/ois/xml/ns/jhove“
oldObjectIdentifier: unique identifier (DIAS internal);
purpose:
processCreator:
steps:  all steps executed during this project; element is repeatable
completionDate:
Builder creates DIAS asset: generates DIAS files
felxible tool with internal workflow engine and modules
contains not only preservation metadata but also technical metadata; therefore it is stored in METS' <techMD> section
contains not only preservation metadata but also technical metadata; therefore it is stored in METS' <techMD> section
conversion module for PREMIS/METS - UOF
Dissemination:
dissemination to storage space; from there the conversion module can read the asset descriptor
Unlimited number of FileSets and FileGrp - have to convert into one file set and one fileGrp for import; This information gets lost -> so for export all files will be in a single fileGrp premis has no element to store technical metadata; Mets techMD section is used
link to amdSec; all sub elements (techMD),(digiprovMD) belong to the appropriate file
METS attributes: as in LMER metadata -
creating application: same application, which created METS file
enviroment: document management system
<swDependency> contains information about webservers, databases etc.
single <amdSec> for every file
PREMIS data in <digiprovMD>
MIME TYPE also stored as attribute to METS file element
<format> e.g. from DIAS internal format registry
old asset version may be deleted – but asset descriptor will always be in DIAS system eventIdentifier: only internal identifier, used as a target for the link from relationship section eventDateTime: date and time, when action was finished (when the event occurs)
usage of attributes of file element within METS is identical; no conversion necessary
LMER just knows "migration" events