Bug #5531
closed
Remove/make optional the DataONE MN registration that occurs during Metacat configuration
Added by ben leinfelder almost 13 years ago.
Updated almost 13 years ago.
Description
Right now when I [re]configure Metacat I hit the DataONE CN in an attempt to register myself as a MN. This should be optional.
There is now a separate admin configuration screen for dataone:
you can bypass it in the same way you can bypass geoserver configuration. No configuration values will be changed, except that your installation of Metacat will know that you have bypassed that section. You can return to it in a reconfiguration at any time.
-You can update the values. After they are written to the configuration file, a call will be made to the CN.register() or CN.updateNodeCapabilities() methods - depending on whether it is a new registration or an update. We determine this by examining the existing node list for a matching ID. One problem with this approach is that if you happen to choose a NodeId that already exists in DataONE during your initial registration (during which your input is ignored and a nodeId is actually generated for you) then you will incorrectly attempt to update that node (that you probably do not own).
Original Bugzilla ID was 5531
Also available in: Atom
PDF