Error logs

If files fail to upload, an error log will be generated. You can access these files through the confirmation email sent by Metadata Hopper and through the Administration section.

Error logs include all errors found by the system. This is delivered in an xml file, with comments for the specific errors that occurred. You can edit the error log file to fix any error and then resubmit the file.

Below you will find details on specific errors.

Missing Required Elements

In this case, the system could not find one or more elements that it required for upload. You will need to add the element with a value to your metadata file.

Consider the following example, for a set of rules that require an identifier element.

Original

<title>Text</title>
<subject>Subject</subject>

Revised

<title>Text</title>
<identifier>Number</identifier>
<subject>Subject</subject>

Missing Required Value

While all required elements were found, not all of the elements had a value.

Consider the following example, for a set of rules that require a Title element.

Original

<title>Text</title>
<identifier/>

Revised

<title>Text</title>
<identifier>Number</identifier>

Duplicate Records

This occurs when the file you are trying to upload already exists in the system. Please search Metadata Hopper for the object you are trying to upload.

If you are trying to upload a new version of an existing object, you will need to use the Replace Object function.

Media File Not Found

This error occurs when the system is unable to match a media file (such as an image file or a pdf) against a metadata file. This may be because:

  • The element you specified for your media file source is incorrect
  • The file names specified in your metadata file do not match the media files. You may want to check that your media files do not have any suffixes or prefixes that are not included in the metadata file or that the media files have been renamed by another system.
  • The media file is not in the same directory as the metadata file
  • The media file is not in an accepted format. See Accepted file formats for more information.

If you need any help determining why this error occurred, please contact your portal manager.

Media URL Not Found

This error occurs when the system is unable to find a media file (such as an image file or a pdf) at the address specified in the metadata file. This may be because:

  • The element you specified for your media file source is incorrect
  • The file names specified in your metadata file do not match the media files. You may want to check that your media files do not have any suffixes, prefixes that are not included in the metadata file or the media files have been renamed by another system.
  • The media file is not in an accepted format. See Accepted file formats for more information.
  • The media file is no longer at the address specified
  • The server that the media file is on is down

If you need any help determining why this error occurred, please contact the portal manager.

Failed XML Validation

Your file may fail XML validation if it is not well formed. This means it does have correct XML syntax.

Some common XML syntax errors include:

Having no closing tag

An XML element must always have both opening and closing tags.

Incorrect

<persname>Smith, John

Correct

<persname>Smith, John</persname>

Opening and closing tags do not match

The opening and closing tags for an XML element should always match.

Incorrect

<persname>Subject</subject>

Correct

<subject>Subject</subject>

An XML may have only one root element

The very first element that appears at the beginning of an XML document is called the root element. This element serves as a parent element and all other elements in the XML document live underneath this parent element. There may only be one root element in each XML document.

Incorrect

<record>
<title>Title 1</title>
</record>
<record>
<title>Title 2</title>
</record>

Correct

<collection>
	<record>
		<title>Title 1</title>
 	</record>
 	<record>
 		<title>Title 2</title>
  	</record>
</collection>

Metadata file not found

This means that Metadata Hopper could not find a file to extract metadata from. Please check that your metadata file is in the directory you specified for upload and is in XML format.

Multiple XML files

This means that the rules selected specified one file to extract metadata from but the directory specified contains more than one. Check to see if more than one XML file exists among the files selected for upload.