METAMATER Overview
 

The purpose of MetaMater is to add to image metadata and create corresponding files alongside the images which reflect this metadata, and are uniquely keyed to match the images.

 

An important part of the process is the creation of a checksum for each image that is recorded in the metadata, and further creation of a checksum on the resultant metadata file.

This ensures the integrity of the data and means that images can be checked for modifications.
 

The metadata included is entirely customisable to match the requirements of the organisation.

 

It is always saved in a standard CSV file format in the same folder structure as the images, and can then easily be imported into a database.
 

The output images are named according to a pattern specified in the configuration and image format conversion is available during the process.

Summary of functions

 

There are 3 Main Tabs for the 3 main tasks performed using MetaMater:

 

1) Operational
This tab is used for processing a batch of images.
It shows the current values that will be applied to the next image saved, and is where the values of manually input fields are entered on a per-batch basis.
 

Each batch is started by the "New Batch" button. The images are then processed together or in groups, and at the end the batch is finalised and the final metadata checksum is taken.
 

There are other utilities to allow marking of linked (left and right) images. These can then be cross-referred withing the metadata.
 

A second tab within the Operational section allows viewing of the values just applied to
the last image saved.

 

2) Configuration
This section allows general program configuration and definition of fields to appear in embeded and external metadata. The field values can be fixed, user-specified at run-time,or automatically created from the image or other fields.

 

The configuration is split into 5 parts:
 

a) Global Configuration
This allows loading and saving of configuration files and specifying of general configuration options such as root output paths and file-naming patterns.
b) Acquisition CSV
This section allows specification of all fields to be saved in the main metadata CSV file, alongside the images.
c) Embedded XML
This allows specification of a chunk of XML that can be saved in the specific XML section of JPeg2000 output files.
d) Environment CSV
This is a single entry file created for a batch from fields specified in this section.It is designed to reflect the environment in which the captures are originated.
e) Calculation Only Fields
These are fields created to be used by other fields, often to form a concatenated field for file naming or to concatenate fixed text to other fields.
It is also useful for storing fields that are used in some configurations or batches,but not in all.

By using this facility a master configuration can be created containing all possible fields, and they can be transferred  in or out of the calculated field section as they are used, to prevent the need for defining them in multiple separate configurations.

 

3) Image QC
This allows a preview of the last image saved, and will also open any other image selected.