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

help of JHOVE. In this context, the question remains at which point the SIPs will becreated and at which point format characterization and validation will hence be carried out.A possible scenario according to Dr. Kluge is that koLibRI will create SIPs twice a month.In establishing this routine it will be crucial to consider how files submitted to Qucosa willbe treated in the time between submission by the depositors and their processing bykoLibRI. For example, it has to be considered whether it is advisable to make these filespublicly accessible through Qucosa before their integrity was checked by JHOVE. Thus, ifan error is detected by JHOVE, it might be easier to correct it – e.g. by replacing the file –if it is still unpublished. Any other procedure might lead to conflicts with the DNB's URNpolicy, according to which a new URN has to be assigned if, for example, the MD5checksum of a publication can be shown to have changed (see above).As with pedocs and JUWEL, the “completeness and correctness” of the submittedfiles is additionally ascertained by means of intellectual control, especially with regard tometadata and the author agreement – thus, no publication takes place until the signedagreement has been received, and Qucosa staff will correct or add metadata before thedigital object is added to the repository. As authors are requested to submit a certainamount of descriptive metadata (e.g. keywords/subject terms) it might be helpful to advisethem – e.g. in the FAQ or publication guidelines – that their submitted metadata will besubject to quality control and may be modified in the process.Authenticity: As authors are not required to identify themselves by creating anaccount, they confirm that they indeed have the right to publish the work in question, andthat hence they are who they claim to be (i.e. the author of a publication) only through theauthor agreement. As mentioned above, this author agreement has to be printed andsigned, and hence exists in analog form. The procedure is therefore different from the onechosen by pedocs, which works with digital agreements (see above).Qucosa does not use secure protocols at the moment so that any information enteredinto the web submission form is submitted in unencrypted form.Ingest: Generate AIPAs in the other two repositories considered here, (pre-)AIPs are created in Qucosa,which will later form the basis for the koLibRI SIPs and the AIPs for long-term archiving.These pre-stage AIPs are saved in the Qucosa file system. The information packagescurrently contain a persistent identifier (URN) and a set of descriptive metadata. All in all,the assignment and use of URNs in Qucosa is quite similar to their use in pedocs. Thus,URNs are assigned to the record for the digital object (the so-called “front door”); thedigital object(s) described and referenced by the record is/are addressable via the URLincluded in the record. URNs and URLs are submitted to the DNB, where any changes tothe URL are registered as well. 128 The URN is displayed as preferred form of citation in the128 A considerable number of the URNs are at the moment not resolved and result in a DNB error message(see, for example, http://nbn-resolving.de/urn:nbn:de:bsz:14-qucosa-24790 – 18.10.2009). According toKluge, the problem lies with the DNB, where an interruption of the technical service provided occurred48