There are number of issues related to the RO metadata synchronized with DataONE. Those can categorized according to SEAD versions as follows.

SEAD 2.0 Beta
1. Bad default values appear in some FGDC files (early beta1 publications) sent to DataONE.
Ex: https://search.dataone.org/#view/seadva-dfaaf2bb-94f1-4938-bcc8-416a24964ee7
This has been fixed in latest objects like IFRI.
https://search.dataone.org/#view/seadva-066a5d98-e937-4458-adc7-3159cc82786d
However older ROs need to be fixed.

2. Old seadva-# identifier has been used for DataONE FGDC files.
Ex: seadva-dfaaf2bb-94f1-4938-bcc8-416a24964ee7 in https://search.dataone.org/#view/seadva-dfaaf2bb-94f1-4938-bcc8-416a24964ee7
We can use the SEAD 2.0 RO identifier instead of this old identifier for FGDC files. However, either one is relevant for external users. I think DataONE should display the DOI as the 'Identifier' in their UI. Still we need to get this clarified from them.

SEAD 1.5
3. In all SEAD 1.5 ROs synchronized with DataONE, SEAD VA landing page URL has been used as the 'onlink' in the FGDC file instead of the DOI.
Ex: In https://search.dataone.org/#view/seadva-HsuLeslie029090a9-11b8-4fc1-bf76-bb5a8153363f 'onlink' in FGDC is set to http://seadva.d2i.indiana.edu:8181/sead-access/#entity;http://seadva.d2i.indiana.edu:8181/sead-wf/entity/2348
This should be fixed by setting the DOI, as we might migrate all 1.5 ROs into 2.0 and discontinue 1.5.

Before SEAD 1.5
4. In NCED ROs published (not sure how these were published. may be scripts, manually etc) before SEAD 1.5 deployment, the 'onlink' in the FGDC points to the NCED repository. Again those should be fixed by adding DOIs.
Ex: In https://search.dataone.org/#view/sead-Bode-Collin-32a51798-22d1-48e9-8b13-05e5243b54e4 'onlink' is set to https://repository.nced.umn.edu/browser.php?dataset_id=22.

All SEAD ROs synchronized with DataONE can be found here.
https://search.dataone.org/#data/query=datasource:%22urn%3Anode%3ASEAD%22/page/0

Main issue in fixing these issues is that, as far as I know, our level of membership with DataONE does not allow updates to already synchronized metadata. There might be a workaround for that, but we need to discuss with them on that. Probably the best solution for above issues could be removing the synchronized FGDC files and let new ones get through during the republishing process. However, at this point we are not sure whether that is a possibility.