Explanation of possible errors in a discovery report

The following list includes all possible errors that could be found in a discovery report, along with suggestions of what steps to take upon seeing the error. Having trouble finding the errors in your report? Try out Namoi Dushay's Jupyter Notebook.

dor_connection_error

There is a problem connecting to the Digital Object Repository. Try running your discovery report a second time. If you are still getting this error, contact the repository manager. It could be a sign that there is a problem with the network.

dupes

The discovery report has found multiple files in the object folder that have the exact same name (including extension). All files within the same object must have unique names.

Please check the object folder listed in the manifest.csv. Content must be staged for accessioning in a single-level (flat) folder structure, and it should not be possible to include more than one file with the same name in the same folder. This error is a sign that the object folder listed in the manifest may contain one or more subfolders, which would make it possible to have two files with the same name, as they could be in different folders within a hierarchy.

empty_files

At least one file in the object is empty. You can identify which file by checking its size in a file viewer: it will show a size of 0 bytes.

Note that if the content is expected to include an empty file - an exceptional situation, but possible - you can go ahead and run preassembly even if you see this error. However, the error is usually a sign that there is a problem with the file that should be resolved before accessioning.

empty_object

The druid's object folder has no files or all of the object's files are empty.

It is permissible to have an item with no files. If this is what you intended, you may ignore this error and run preassembly. If not, check the folder. It's possible some files were never copied into the correct location.

filename_no_extension

At least one file has no extension (the extension is the part after the last period in the filepath, e.g. pdf or jp2).

Note that this error message can be interpreted as a warning. Files are not required to have extensions (e.g. some communities will name "read me" files simply README). However, it is far more common for files to have extensions and this error is a sign that there could be a problem with the content. Please verify that the content is named and structured correctly if you see this error.

item_not_registered

The object must already be registered. This error will occur if you enter a value in the "druid" column on the manifest.csv that does not match an existing druid. One possible cause of this error is a typo in the druid column.

missing_files

This error means that the folder corresponding to the particular druid either:

• has no files whatsoever
• is missing files listed on the file_manifest.csv (this error only occurs if you are using the file_manifest.csv)
• has files but the system can't read all of them (system-level permissions problem)

It is permissible to have an item with no files. If this is what you intended, you may ignore this error and run preassembly. Otherwise, check for the following:

• Does the folder have files?
• Is every file you want to accession in the folder?

If the answer to both questions is yes, and you are using a file_manifest.csv, check your manifest to see if it lists files that you did not mean to accession.

If you are not using a file_manifest.csv and the folder has files in it, please contact the Repository Manager as there may be a problem with the file permissions.

Errors That Only Occur When Using a File Manifest

empty_manifest

There are no files listed in the manifest.

files_found_mismatch

The number of files in the manifest does not match the number of files found in the object folder.

missing_media_container_name_or_manifest

The manifest.csv file wasn't found. Both a manifest.csv and a file_manifest.csv are required when using a file manifest.