Quality

docuteam packer offers various possibilities for quality assurance and control.

Preview

In order to evaluate files of a SIP efficiently, docuteam packer offers the possibility of a preview. This can be found in the detail view of the SIP under the tab "Preview".

In order to use this functionality, the affected formats must be stored in the configuration file filePreviewConfigurator.properties (as PUID (PRONOM Unique Identifier), MimeType or by extension). This file can be found at docuteam-packer/config.

File Migrations

In docuteam packer individual files can be migrated to another file format directly from the detail view of a SIP. This is recommended for fine-grained control of migrations.

In order to perform a migration, the desired object can be right-clicked and the option "Convert files" selected. The action must be confirmed. In addition, it must be specified whether the original should be kept or deleted after the migration.

If the original is kept, a new folder will be created and the original and the migration result will be appended below it. The metadata is transferred from the original to the parent element, but not to the migration result element.

To perform a migration, a corresponding instruction must be stored. It consists of the specification of the source format, the desired target format, and the application that is to perform the migration.

The configuration for format migrations is defined in the file migration-config.xml. It is located at docuteam-packer/config.

The file consists of two parts:

• the first part specifies the tools for format migration.
• the second part lists all the formats to be migrated and specifies the tool to be used.

Examples for the definition of applications in migration-config.xml:

<config>
	<application
		id="1"
		name="OpenOffice"
		executable="Class:ch.docuteam.converter.OOConverter"
		parameter="{[arg1]}#{[arg2]}" />

	<application
		id="2"
		name="ImageMagick"
		executable="C:/Apps/ImageMagick/magick.exe"
		parameter="-compress#none#{[arg1]}#{[arg2]}" />
...
</config>

id denotes the ID of the application that is referenced in the second part for the configuration of the format migration. executable contains the Java class or the path to the executable file of the tool. parameter can contain specific options of the tool. Additionally, {[arg1]} and {[arg2]} reference the input and output files.

Examples for the definition of migration instructions in migration-config.xml:

<config>
...
	<puid
		name="fmt/123"
		applicationID="2"
		targetExtension="tif"
		targetPronom="fmt/353" />

	<extension
		name="pdf"
		applicationID="1"
		targetExtension="pdf"
		targetPronom="fmt/354" />

	<mimeType
		name="image/tiff"
		applicationID="2"
		targetExtension="tif"
		targetPronom="fmt/353" />

</config>

A file format migration instruction can be defined via 3 tags, depending on the property a format is to be migrated from: PUID, file extension or MimeType. PUID stands for PRONOM Unique Identifier and is an established identifier for specific file formats. name denotes the value of the property. For example, if you want all files that have a PUID fmt/123 (Encapsulated PostScript File Format) to migrate to a Tiff, you specify the value "fmt/123" in the name attribute. The tool to be used for this is defined by the applicationID. The value of this ID must have been defined in the first part of the migration-config.xml. In this case it is the tool with ID 2, i.e. Image Magick. Finally, the attributes targetExtension and targetPronom are used to specify the values for the target format. targetPronom refers to the PUID of the target format. In the example, a Tiff is to be created with the PUID fmt/353.

Submission Agreements

Submission agreements allow you to check whether objects with unwanted file formats are in a SIP by specifying permitted file formats and to delete them directly. In addition, further information can be stored in the submission agreement, such as information on the archive or on individual deliveries.

The submission agreements are stored as XML files at docuteam-packer/agreements. When creating a SIP, the desired submission agreement can be selected via the drop-down menu.

In the detail view of a SIP, the desired submission agreement can be applied for a review via the menu item "SA" > "Review or Assign...". By clicking the "Play" button, a check is performed and all objects whose file format is not explicitly listed in the submission agreement under fileFormats are listed. Afterwards you can select whether the objects should be deleted or marked.

If the submission agreement does not contain a tag fileFormats all file format are allowed.

In the following example, only JPEG files with PUID fmt/43 (PRONOM Unique Identifier), the MimeType image/jpeg or the file extension jpg are accepted:

<fileFormats strict="true">
	<puid>fmt/43</puid>
	<mimetype>image/jpeg</mimetype>
	<extension>jpg</extension>
</fileFormats>

Verify checksums

If you want to check the integrity of the files contained in a SIP, you can perform the "Package" > "Check Checksums" action in the SIP detail view. The checksums are calculated for each file individually and compared with the checksum of the file stored in the metadata (mets.xml). The execution as well as the result (successful or unsuccessful) is recorded in the metadata as a PREMIS event.

Remove duplicates

The menu item "Package" > "Remove Duplicates" opens a dialog that displays identical files if existing. The identity is determined using the checksum. Listed files can be deleted using the dialogue box. It is not possible to delete all files with the same checksum.

Delete disposed elements

The action "Package" > "Delete disposed elements" requires that a corresponding level has been defined for the disposal in the levels.xml. If this is the case, elements of this level are deleted by this action.