Project

General

Profile

Bug #7022

Fatal processing error when updating an object with incorrect sysmeta

Added by Bryce Mecum over 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
05/06/2016
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:

Description

Jessica used the R package today to update an object with new bytes via the D1 REST API call for MNStorage.update(). She received this error back from Tomcat:

<?xml version="1.0"?>
<error>Fatal processing error.</error>

She showed me what she had for her input to the call and I found that the sysmeta formatId was EML 2.1.1 instead of text/csv which was the correct format ID for the object. This was a bug in my code that she was running that I've since addressed.

I expected a more useful error that directly addressed the mismatch in format ID and the file being uploaded.

Why did this action cause a "Fatal processing error"? It seems like the sysmeta format ID being set to EML should've triggered the EML validation routine which should have returned a validation error.

Also available in: Atom PDF