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.

documents submitted to the repository must be <strong>free</strong> from any DRM, password protection,or other technical protection measures that might be used, for example, to limit or disablethe print option. Thus – in the case that authors follow the guidelines – pedocs obtains fullphysical/technical control over the digital objects as required by nestor, DINI, and TRAC.As of October 2009, a newly developed tool is used which automatically identifiesdocuments with DRM restrictions during upload. As a result, while pedocs still contains<strong>file</strong>s with such technical limitations, uploaded before the new tool was implemented 91 ,these can now be identified and further action be taken where necessary.Ingest: Quality AssuranceIntegrity: As outlined above, virus checking and cyclic redundancy checks help toascertain a submitted <strong>file</strong>'s completeness and correctness (on a technical/bitstream level),and to determine whether any errors occurred during the transmission. Currently, viruschecks are not implemented into the pedocs workflow as such, i.e. <strong>file</strong>s uploaded throughthe web interface are stored in the pedocs <strong>file</strong> system without having been checked forviruses. However, every uploaded <strong>file</strong> is opened by repository staff in order to see if it isfunctional and is thus automatically scanned by the antivirus software installed on eachcomputer.As explained above, a digital object's integrity also depends on the validity of its <strong>file</strong>format. Thus, small mistakes in a <strong>file</strong>'s code might make it harder to preserve the objectfor the long term, for example, because the behavior of corrupted <strong>file</strong>s during formatmigrations cannot be predicted. A format validation (preceded by a format identification),which ascertains that a <strong>file</strong>'s bitstream is composed exactly according to thespecifications, is thus highly important in the context of long-term preservation. pedocscarries out format validation and characterization as part of the ingest process by meansof JHOVE, which is used to generate a limited amount of technical metadata to besubmitted to the DNB as part of information packages (i.e. <strong>file</strong> format, format version,supplemented by checksum; also see below). Invalid <strong>file</strong>s will not be submitted to thelong-term archive.The completeness and correctness of the SIPs is additionally ascertained by meansof intellectual control, especially with regard to metadata. Thus, for the purpose of qualityassurance the metadata submitted by authors is sometimes modified; also, furthermetadata can be added by repository staff in order to complete the information packagestored and published on the pedocs server. This practice is explicitly mentioned in thepedocs policy and thus authors are aware of the fact that their submitted metadata maybe subject to modification.Authenticity: In the context of the Ingest functional entity, the question of authenticityof digital objects is primarily a question of the extent to which the submitting person or91 Thus, for example, the documents attached to the record 807 are both encrypted and password protected.In addition, the possibility of copying text from the <strong>PDF</strong> has been disabled. Seehttp://www.pedocs.de/volltexte/2009/807/ – 30.10.2009.32

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

Saved successfully!

Ooh no, something went wrong!