FontAwesome and Bootstrap are imported locally rather than via CDN. Updated the docs screenshots to the new style.
Pull the external stylesheets in by <link> rather than @import for faster page load
Matched the admin config pages to the default metacatUI theme. Changed the background image of the docs and config pages to a big cat for some metacat branding.
Redesigned the /admin configuration pages to better match our new MetacatUI design. Looks good in both /context/admin view and the #external view using metacatUI
use sleeker "?" icon for the admin help links
correct typo for "dataone.mn.services.enabled" property on the admin screen checkbox
Globally change the property 'dataone.memberNodeId' to 'dataone.nodeId'. This is more useful for both MNs and CNs implemented in Metacat. Also, change D1NodeService.getLogRecords() to return log entries with the actual node id rather than the IP address (looks like a cut/paste error)....
include member node id text field now that the CN is not assigning random Ids.https://redmine.dataone.org/issues/2308
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....
Show "Update" button if this MemberNodeId is already registered with DataONE, otherwise use the "Register" label
Updated configuration documentation in admin guide for Metacat DataONE section. Changed links in configuration utility to point at the Admin guide.
Modify admin configuration to include default replication policy. Extensively revised the DataONE configuration page, including new wording for intro, improved tooltips throughout, new arrangement of sections, and other cosmetic changes.
Remove ability to edit NodeID from D1 configuration page. Fix update of contactSubject and dataone.ore.generated property name.
store D1 configuration properties in the main backup so that they persist between upgrades.
add description about what becoming a Member Node entails
configure synch schedule in the admin screenhttps://redmine.dataone.org/issues/1933
DataONE MN registration/configuration is now its own configuration page in the admin interface.http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5531