12.07.2015 Views

Download (PDF, 9MB, Not barrier-free file.) - Nestor

Download (PDF, 9MB, Not barrier-free file.) - Nestor

Download (PDF, 9MB, Not barrier-free file.) - Nestor

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

integrity between AIPs and their metadata. Thus, TRAC criterion B5.3 requires that“[e]very AIP must have some descriptive information and all descriptive information mustpoint to at least one AIP, such that the integrity can be validated” and suggests thefollowing evidence: “Descriptive metadata; persistent identifier/locator associated with AIP;documented relationship between AIP and metadata; system documentation and technicalarchitecture; process workflow documentation” (TRAC 2007, B5.3). Criterion B5.4requires that this referential integrity must also be maintained. 138 To achieve referentialintegrity, the nestor catalog suggests that persistent identifiers are used to identify digitalobjects and all their parts (including metadata), and/or that metadata and content objectare stored in one <strong>file</strong> or directory (cf. nestor 2008, 12.7). Similarly, DINI criterion 2.8requires that a permanent link is created between metadata and document, e.g. by meansof persistent identifiers or containers. In practice, these functions are primarily performedby the repository software; more particularly, the DBMS managing the tables containingthe information.2.4.1 pedocs Data ManagementAs just pointed out, a primary concern of the Data Management functional entity isthe referential integrity between archived information packages and their associatedmetadata (cf. TRAC 2007, B5.3). This can be achieved by saving objects and theirmetadata together in one container. pedocs does not currently use such containers butbuilds its information “packages” virtually, so to speak, by linking metadata and object viathe relational database tables.In addition, a cover sheet will be used in the future to permanently link metadata anddigital objects linked by including them in the same <strong>file</strong>. Thus, each document uploadedinto pedocs will automatically (via a PHP script) receive a cover sheet added to the <strong>PDF</strong>as its first page during the Ingest process. The workflow for this procedure is currentlybeing tested, and a number of documents have already received cover sheets (see forexample http://nbn-resolving.de/urn/resolver.pl?urn=urn:nbn:de:0111-opus-18568 –01.11.2009). It is planned that by the end of 2009 all documents contained in pedocs willhave cover sheets containing core bibliographic metadata, the URN, copyright/useinformation, as well as the logo of the publisher (where applicable) by whom the work wasfirst published. In addition, if the work was digitized by pedocs, this is also stated. Thispractice is clearly described in the pedocs policy document so that submitting authors areaware of the fact that the <strong>file</strong>s they submit will be modified in this manner. With this coversheet, the problem that currently the <strong>PDF</strong> documents are separated from their metadataonce they have been opened, printed, and/or saved on a user's computer is solved.138 Suggested evidence includes “[l]og detailing ongoing monitoring/checking of referential integrity,especially following repair/modification of AIP; legacy descriptive metadata; persistence ofidentifier/locator; documented relationship between AIP and metadata; system documentation andtechnical architecture; process workflow documentation” (TRAC 2007, B5.4).56

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!