Metacat

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.

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.

clean up populator; use IOUtils library to do string<->stream conversions

move the DataONE 1.0.0-SNAPSHOT

use default fmtid if we can't find the user-supplied data mime type in our list

including newer d1 libclient that uses Foresite (and Jena) to construct/parse ORE resource maps for DataONE

cleaned up to use for populating a DataONE MN using the D1 api. Retrieves packages from a Metacat and generates system metadata for them before calling MN.create() for both data and metadata.
NOTE: you need a client certificate that the target server accepts (either DataONE-generated for testing or a CILogon one for more official use). I was only able to get the former certificate type to work with our existing MN servers

include SystemMetadata when replicating data and metadata documents -- this allows us to establish the guid-to-docid mapping that is crucial for being able to read the replicated document by guid (d1 api)

do not send <systemMetadata> with the <docInfo> replication information - this is handled by the Hazelcast shared map