Metacat

handle 'archive' rest calls
https://redmine.dataone.org/issues/2678

[optionally] do not archive the xml_documents and xml_nodes to *_revisions when 'deleting' a document. This will effectively guarantee that the document/data cannot be retrieved after delete.
NOTE: D1 system metadata will persist (for now) so that the ID cannot be reused with the DataONE API but Metacat calls may allow the ID to be reused -- may need to reconsider this behavior....

optionally remove the document/data file from the filesystem completely when 'deleting' it.
https://redmine.dataone.org/issues/2677

newer d1 jars that include shared AuthUtilsmethod for isAuthorized() consistency
https://redmine.dataone.org/issues/2661

implement MN and CN.archive() method -- really just the existing delete() methods.
https://redmine.dataone.org/issues/2674
https://redmine.dataone.org/issues/2675

call MN.delete() for each replica when CN.delete() is called
https://redmine.dataone.org/issues/2676

defer to AuthUtils for flattening out the equivIdent subject list.
https://redmine.dataone.org/issues/2661

check normal access control rules for getSystemMetadata before deferring to MN replica information that may grant MNs additional access to the SM.
https://redmine.dataone.org/issues/2656

include Session-less interface methods and updated jars that define them.

use a shared ExecutorService for replicate() calls.
https://redmine.dataone.org/issues/2623