Metacat

do not subset the list for MS generation testing -- at least not as the default in svn!

only run ORE generation for EML docs -- no need to run this for all documents (yikes!)

use IdMan method to find docids that do not already have system metadata records -- this lets us re-run without re computing system metadata for every entry (in case the process is interrupted). I haven' been using this option because I wanted to continually regenerate all SM for everything in my test DBs, but we are so close to release that I want to get this in there.

for testing: limit and randomize the docs to generate metadata for

FOR TESTING ONLY: limit number of records to 100 so that we can get an estimate

update the memberNodeId in existing system metadata only after the register/update is successful with the CN -- we can avoid unneeded SM updates in cases when the register/update fails because we gave the CN bad info that it rejects.
https://redmine.dataone.org/issues/2308

include member node id text field now that the CN is not assigning random Ids.
https://redmine.dataone.org/issues/2308

refactor D1-specific upgrade utilities into their own package

generate SystemMetadata during D1 registration (not 2.0.0 upgrade). This process runs in a thread and updates a metacat.properties value when it is complete.

dataone configuration and registration enhancements:
-include flag to disable D1 services, currently only the MN side enforces this
-do not allow multiple registration attempts if we have just submitted and are awaiting Node verification by the CN.
-do not allow configuration "bypass" if D1 settings have been configured previously....