DOI value is wrong in OMNI NumericalData Descriptions

[berniegsfc]

The DOI value in the OMNI NumericalData descriptions (e.g., ResourceID = spase://NASA/NumericalData/OMNI/HighResolutionObservations/Version2/PT1M) is a landing page URL (https://doi.org/10.48322/mj0k-fq60) instead of simply the DOI value (10.48322/mj0k-fq60). This is inconsistent with previous values like in spase://NASA/NumericalData/ISEE2/MAG/PT4S and fails validation by web services that accept DOI values as input.

[berniegsfc]

Just because a DOI is displayed as a URL doesn't mean it should be stored in the SPASE XML file as a URL.

[tressahelvey]

Hi @berniegsfc
I just reviewed several SPASE records which appear to have the DOI formatted as a URL.
Since this ticket is years old, I'm going to close it. If you have new comments, please let me know.
Thank you.

[rweigel]

The SPASE documentation says it should be a DOI. So either the existing SPASE records you looked at are wrong, or the documentation is.

[berniegsfc]

Todd and I recommended against using the URL in the XML but were overridden years ago. I have since created a "computed" value/index in the HDP database to standardize (non-url form) the value for use as a db index and other uses by software. My solution doesn't help software outside the HDP DB environment. It's not to important for this discussion, but note that the CDAS WSs which have supported DOIs for a long time (when cdaweb had < 10 datasets and spase DOI values were non-url), still returns non-url values to clients (> 15 years backward compatibility).

[rweigel]

I guess the documentation is wrong then.

[berniegsfc]

The documentation is the way it was originally done. Aaron, and maybe others, decided to change it years ago (but years after some values and s/w expected it the other way). Just minutes ago, I had to change some xslt/javascript code that was calling citation.doi.org because they changed to no longer allowing the https://doi.org/ value in an HTTP doi query parameter. I understand why some wanted to make it a url but it has created more trouble. The spase group forgot to update the documentation when they made the change.

[tressahelvey]

@sffung @lfb12345
Hello Shing and Lee,
The documentation needs to be changed for the above issue.
Let's discuss at next SMWT meeting.

Thank you. Tressa