Metacat

update with latest d1_common/d1_lib (includes latest schema changes)

only handle 100 (consecutive!) docId generations per millisecond, otherwise the generated docid part is bigger than Long.MAX_VALUE and Metacat cannot fully handle that.

check previous revision when attempting to update access control with EML 2.0.x docs
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5560

remove old access rules for a data object when they are being updated by rules contained in an EML document. Now the OnlineDataAccessTest EML 2.1.0 tests pass.
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5560

construct the proper previousDocId when checking for update permission

for now, look up SystemMetadata directly from the table otherwise we won't have the latest access information. Need to refresh the in-memory copy everytime we edit the access policy via Metacat (includes EML parser)

check previous revision for permissions to update (includes data described by EML)

use correct "rev" column in xml_revisions table

refactor Metacat access handling to be on a per-revision basis so that it more closely aligns with the DataONE approach
http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5560

To avoid id generation conflicts happening at the same millisecond, append a 5 character random string to the end of the docid.