Task #6363: Add the ORNL Mercury schema to the object format list - Member Nodes - DataONE Tasks

Task #6363

MNDeployment #4247: EDORA (Environmental Data for the Oak Ridge Area)

Task #6353: Add support for ORNL Mercury metadata schema to the Metacat schema catalog in each environment

Add the ORNL Mercury schema to the object format list

Added by Chris Jones about 10 years ago. Updated almost 10 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Chris Jones

Target version:

Operational

Start date:

2014-09-08

Due date:

% Done:

100%

Story Points:

Sprint:

Description

To fully support the new schema used by ORNL Mercury instance documents, we need to add the following format to the object format list:

formatId: http://purl.org/ornl/schema/mercury/terms/v1.0
formatType: METADATA

History

#1 Updated by Chris Jones about 10 years ago

I've added the object format to subversion, but am getting SQL errors in the stage environment when updating the object format list:

metacat 20140908-16:20:21: [ERROR]: DocumentImpl.writeDocumentToDB - SQL error: ERROR: update or delete on table "xml_nodes" violates foreign key constraint "xml_index_nodeid_fk" on table "xml_index" [edu.ucsb.nceas.metacat.DocumentImpl]
metacat 20140908-16:20:21: [ERROR]: DocumentImpl.write - Problem with parsing: Error in DBSaxHandler.startElement for action UPDATE : ERROR: update or delete on table "xml_nodes" violates foreign key constraint "xml_index_nodeid_fk" on table "xml_index" [edu.ucsb.nceas.metacat.DocumentImpl]
metacat 20140908-16:20:21: [WARN]: MetacatHandler.handleInsertOrUpdateAction - General error when writing eml document to the database: Error in DBSaxHandler.startElement for action UPDATE : ERROR: update or delete on table "xml_nodes" violates foreign key constraint "xml_index_nodeid_fk" on table "xml_index" [edu.ucsb.nceas.metacat.MetacatHandler]

I'm troubleshooting this now.

#2 Updated by Chris Jones about 10 years ago

Status changed from In Progress to Testing

Fixed. On the CNs, we have fairly recently set the database.usexmlindex property in Metacat to false, but when we first inserted the object format list, it was set to true. This caused a SQL foreign key constraint exception when updating the list. To fix this, I've truncated the xml_index table on all 3 CNs in the stage environment.