adding a system to track system metadata documents for dataone
Added initial implementation of getSystemMetadata and its associated REST service. Current implementation is returning a hardcoded system metadata document -- need to look up the real document for each guid and return that.
Completed main parts of CrudService.create(). Now the method writes both data and metadata objects along with their system metadata, and handles the mapping between global identifiers and local identifiers. Access control and logging still need to be dealt with to properly authenticate and then log activities.
Modify CrudService to write SystemMetadata to disk with an autogenerated localId and an autogenerated GUID. Validation depends on the DataONE schemas being setup in xml_catalog properly, so still need to check upgrade scripts to be sure these new schemas are added. Still need to handle the metadata document insert, but should be same as system metadata insert.
Added comment about MIME form processing.
Refactored schema service to call doRefresh() in constructor to eliminate code duplication.
Added note on TODO for access bug.
replication of guids now works. tested this for both forced replication and update/insert/delete triggered replication
fixed bug where guid end tag wasn't getting printed
added a method in IdentifierManager to get a guid from a docid and rev. added fields in the documentinfo replication document to pass the guid. now need to handle the guid and insert it into the table if its found
View revisions
Also available in: Atom