Metacat

do not allow blank node references to be used.
https://redmine.dataone.org/issues/2362

only generate system metadata when the call comes from the legacy Metacat API, not the D1 API.
https://redmine.dataone.org/issues/2362 (I think this was the culprit)

Get ReplicationPolicy correctly generated:
-tweak the regular expression for getting the pref/blocked node list for default replication policy.
-set blocked list (had mistakenly been two calls to set pref list)

actually, let's set the serialVersion during the MN.create() call so that the HZ map and the backing store have the same information immediately. Also, this is how the docs specify it.
http://mule1.dataone.org/ArchitectureDocs-current/design/SystemMetadata.html

remove ID mapping when a create()/"insert" call fails so that subsequent calls do not return an IdentifierNotUnique error. In this case it was due to invalid XML.
https://redmine.dataone.org/issues/2341

use RC-3 DataONE jars and fix compilation error that arose. https://redmine.dataone.org/issues/2351

CNodeService.listChecksumAlgorithms() was returning null rather than the list. Fixed.

Update D1NodeService to reflect new ObjectFormatCache signature.

1. lookup and use the guid when processing obsoletes/obsoletedBy entries -- had previously been assuming localId==guid but now that we have introduced DOIs as part of the Metacat upgrade process, we may have DOIs for the guid that map to localIds.
2. base ORE guids on the localid of the data package they are describing and not on their DOI -- otherwise we might mash up the DOI prefix (or other id scheme that we are unaware of). By using resourceMapPreix + localId we are sure to have a valid localid and guid for the ORE map we create and add to the system

use updated authorization policies as discussed in:
https://redmine.dataone.org/issues/2277
and
http://epad.dataone.org/20120131-authn-authz-questions