| ##### Exporting profiles

Welcome to DROID | Load and save profiles | Filter your results | Summary reporting

DROID can export all open profiles (which are not currently running) to a CSV file. To export a profile, press the Export button, or select the File / Export all... menu item. This will bring up the export dialog window:

The profiles you have open are listed in the export window. If a profile is empty, or in the process of running, it will be greyed out. Select all the profiles you want to export into a single CSV file by checking the boxes next to them. If any of your profiles have active filters, then the results will also be filtered. Each profile can have different filters defined and enabled.

You can also select whether the export should produce one row per file, or one row per format. When exporting one row per file, each row in the CSV file will represent a single file, folder or archival file profiled with DROID. If exporting one row per format, each row in the CSV file will be a single format identificaiton made by DROID. Since a file can be identified as being more than one possible format, this option will produce CSV files with multiple rows for the same file (but with different identifications for it).

When you are happy you want to export your profiles, press the Export profiles... button. This will bring up a standard file-save dialog, in which you can specify where you want your CSV file to be saved.

## CSV File Columns

### ID

This is a unique number assigned to each file, folder or archival file processed by DROID.

### PARENT_ID

This is the id of the archival file or folder in which this file is contained.

### URI (Uniform Resource Identifier)

This provides a standard, cross-platform way of describing where resources are located. URIs are described in more detail in "Information collected by DROID".

### File path

The file system location of the resource being profiled, if the resource was directly in a file system. Some files are not inside a file system - for example, files inside a zip file. In this case, the file path will be blank, as there is no file path to the resource.

Please note that file paths are platform dependent (they are different on windows and unix). DROID will write out file paths for the system on which it is currently running. This means that if you profile files on a unix machine, then export the profiles on a windows machine, the file paths will be written out as if they were windows file paths, and vice versa.

### Name

The file name of the resource being profiled.

### Method

This field gives the method by which a resource identification has been made. DROID can recognise resources by several methods:

- Extension - the file format was identified only by its filename extension. This method may not be very reliable, as the filename extension may be wrong. It is only used when DROID cannot identify a resource by another method, and cannot usually identify what the version of a file format is, only its broad type.
- Signature - the file format was identified by finding a file format signature inside the file itself. This method is more reliable than filename extensions, and can identify the precise version of a file format.
- Container - the file format was identified by finding embedded files and patterns within them. This method is as reliable as signature identifications, and can be more reliable.

### Job status

This field gives the identification status of a resource. It can have several values:

- Not done - the resource has not yet been profiled.
- Done - the resource was processed with no errors.
- Access denied - the operating system refused to give DROID read permissions to the resource.
- Not found - the resource was moved or deleted before DROID could read it.
- Error - an error occurred while trying to profile a resource. For example, if DROID is prevented from reading a file due to the user not having read permissions to it, this will result in a profiling error for that file.

### Size (bytes)

The size in bytes of a file. Only files have a size - folders do not. However, note that some files can contain other files inside them, for example zip files. In this case, the zip file has a size (as it is a file), and so do the files inside it. The size reported in all cases is the uncompressed size of each file, as it would appear if extracted from the container file.

### Type

DROID categorises the files and folders it profiles as being one of three types:

- File
- Folder
- Archival file (e.g. zip)

### Extension

The filename extension of a file, which is the last part of a filename following a full stop. Only files have extensions, as they indicate the type of the file. Even if a folder has a full stop in its name, it will not be assigned an extension.

### Last modified

The date and time on which a resource was last modified. This is the only resource date-time available to DROID, as the Java 6 platform on which it runs will not report any others (e.g. creation date-time). More file system information will be available via the Java 7 platform, which is not yet available at the time of writing. This would also require DROID to be modified to take advantage of the new file system interfaces in Java 7.

### MD5 hash

If you have enabled hash generation in the preferences, then this column will contain the MD5 hash for each file and archival file processed. See "Detecting duplicate files" for more information on hashes.

### PUID

The PRONOM Unique IDentifier (PUID) identifies the precise file format of a profiled file. When a resource has been identified, it is assigned a PUID. A unique identifier exists for every file format that DROID can recognise, and these identifiers are maintained in the PRONOM technical registry database, hosted at the UK National Archives.

### Mime type

The mime-type of an identified file format is a high level format identifier assigned by the Internet Assigned Numbers. It is widely used in email and other internet protocols to identify the type of resource. Not all file formats identified by DROID have an assigned mime-type, and different PUIDs assigned by DROID can have the same mime-type

### Format Name

The name of an identified file format, as listed in the PRONOM technical registry against its PUID.

### Format Version

The version of an identified file format, as listed in the PRONOM technical registry against its PUID. Not all file formats have a defined version, so this field can be blank even when a file has a PUID.

Welcome to DROID | Load and save profiles | Filter your results | Summary reporting

######