Metacat

use "lastname, firstname" convention throughout

include more descriptive data file name for title of data records

include publisher given name correctly

create docid-guid mapping during replication if it does not exist. we were [incorrectly] assuming that there would be SM coming with the document info that would fill this information in, but for traditional non-MN Metacat deployments there is no SM to provide a mapping. In this case we use the docid as the guid.

include certificate export SSL options as an example (used heavily for DataONE and Metacat Replication)

stream the replication "update" response rather than building up a complete list in a stringbuffer. prompted by findings on t he CN: https://redmine.dataone.org/issues/3141

make sure data objects correctly use force replicate with action "insert"
https://redmine.dataone.org/issues/3138

correct the update statement for setting archived flag on SM where document revision does not exist in the xml_documents table

sleep before updating and deleting test documents - otherwise their index entries may not be fully written and this causes errors (update and delete first attempt to remove index references, but if they are not in the DB yet then they are not removed but then they do get added and the FK constraints make the delete fail). Since we know indexing occurs in a separate thread with a configured delay, we just use this same delay in our testing.

when updating a document on a remote server, we still need to use the previous docid to check that the user has permissions to do so (rather than the new id that is obsoleting the old id). This was discovered by M Servilla at LTER.