DOI and other links broken in spase://NASA/NumericalData/RBSP/B/EFW/L3/MGSE/PT11S

[berniegsfc]

The following links are broken in spase://NASA/NumericalData/RBSP/B/EFW/L3/MGSE/PT11S:

• https://doi.org/10.48322/p4ze-4247
• https://cdaweb.gsfc.nasa.gov/cgi-bin/eval2.cgi?dataset=RBSPB_EFW-L3&index=sp_phys
• ProductKey (RBSPB_EFW-L3) when used with https://cdaweb.gsfc.nasa.gov/hapi

Did the new link checker report these? The old vspo validator would have.

@scottb77 @tressahelvey

[berniegsfc]

This is not a significant problem. I just stumbled upon it somehow while testing hdpws's spase.xslt.

[rweigel]

Also

https://cdaweb.gsfc.nasa.gov/WS/cdasr/1/dataviews/sp_phys/datasets/RBSPB_EFW-L3/clientLibraryExample/

[berniegsfc]

The problem is that the dataset is not yet public in cdaweb (it's only in a test dataview). The links that depend upon the cdaweb ProductKey will work when the dataset is made public in cdaweb. I didn't mention the .../clientLibraryExample link because it's not actually in the SPASE xml file. As mentioned in the //AccessInformation/AccessURL/Description

Note: this AccessInformation element was added by HDPWS

BTW, HDPWS also adds cdaweb hapi AccessInformation elements when they are found to be missing (and adds cdaweb filenaming templates when they are missing).

[tressahelvey]

Will the DOI issue be resolved when it moves out of TEST? Thank you. From: berniegsfc ***@***.***> Sent: Wednesday, July 31, 2024 10:42 AM To: hpde/NASA ***@***.***> Cc: Helvey-Kasulke, Tressa L. (GSFC-672.0)[ASRC FEDERAL SYSTEM SOLUTIONS] ***@***.***>; Mention ***@***.***> Subject: [EXTERNAL] [BULK] Re: [hpde/NASA] DOI and other links broken in spase://NASA/NumericalData/RBSP/B/EFW/L3/MGSE/PT11S (Issue #14) CAUTION: This email originated from outside of NASA. Please take care when clicking links or opening attachments. Use the "Report Message" button to report suspicious messages to the NASA SOC. The problem is that the dataset is not yet public in cdaweb (it's only in a test dataview). The links that depend upon the cdaweb ProductKey will work when the dataset is made public in cdaweb. I didn't mention the .../clientLibraryExample link because it's not actually in the SPASE xml file. As mentioned in the //AccessInformation/AccessURL/Description Note: this AccessInformation element was added by HDPWS BTW, HDPWS also adds cdaweb hapi AccessInformation elements when they are found to be missing (and adds cdaweb filenaming templates when they are missing). - Reply to this email directly, view it on GitHub<#14 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AZ3W6XANLQWF25KLG3KVBO3ZPDZSFAVCNFSM6AAAAABLYGOJS6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRQGY4DMMJYGE>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[scottb77]

HI Tressa For https://hpde.io/NASA/NumericalData/RBSP/B/EFW/L3/MGSE/PT11S.html The cite as link works https://citeas.org/cite/https://doi.org/10.48322/p4ze-4247<https://citeas.org/cite/https:/doi.org/10.48322/p4ze-4247> even though the doi link does not work. https://doi.org/10.48322/p4ze-4247 The RBSP-A version works https://hpde.io/NASA/NumericalData/RBSP/A/EFW/L3/MGSE/PT11S.html https://doi.org/10.48322/4k9n-gs06 My guess is that, both had to be created at the same time. I could not find either on datacite. Scott From: tressahelvey ***@***.***> Date: Wednesday, July 31, 2024 at 12:11 PM To: hpde/NASA ***@***.***> Cc: Boardsen, Scott A. (GSFC-674.0)[UNIVERSITY OF MARYLAND BALTIMORE CO] ***@***.***>, Mention ***@***.***> Subject: [EXTERNAL] [BULK] Re: [hpde/NASA] DOI and other links broken in spase://NASA/NumericalData/RBSP/B/EFW/L3/MGSE/PT11S (Issue #14) CAUTION: This email originated from outside of NASA. Please take care when clicking links or opening attachments. Use the "Report Message" button to report suspicious messages to the NASA SOC. Will the DOI issue be resolved when it moves out of TEST? Thank you. From: berniegsfc ***@***.***> Sent: Wednesday, July 31, 2024 10:42 AM To: hpde/NASA ***@***.***> Cc: Helvey-Kasulke, Tressa L. (GSFC-672.0)[ASRC FEDERAL SYSTEM SOLUTIONS] ***@***.***>; Mention ***@***.***> Subject: [EXTERNAL] [BULK] Re: [hpde/NASA] DOI and other links broken in spase://NASA/NumericalData/RBSP/B/EFW/L3/MGSE/PT11S (Issue #14) CAUTION: This email originated from outside of NASA. Please take care when clicking links or opening attachments. Use the "Report Message" button to report suspicious messages to the NASA SOC. The problem is that the dataset is not yet public in cdaweb (it's only in a test dataview). The links that depend upon the cdaweb ProductKey will work when the dataset is made public in cdaweb. I didn't mention the .../clientLibraryExample link because it's not actually in the SPASE xml file. As mentioned in the //AccessInformation/AccessURL/Description Note: this AccessInformation element was added by HDPWS BTW, HDPWS also adds cdaweb hapi AccessInformation elements when they are found to be missing (and adds cdaweb filenaming templates when they are missing). - Reply to this email directly, view it on GitHub<#14 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AZ3W6XANLQWF25KLG3KVBO3ZPDZSFAVCNFSM6AAAAABLYGOJS6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRQGY4DMMJYGE>. You are receiving this because you were mentioned.Message ID: ***@***.***> — Reply to this email directly, view it on GitHub<#14 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGMCOOSFAITLAHMAV3Q3QQLZPEEB5AVCNFSM6AAAAABLYGOJS6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRQHA4DCMBWGM>. You are receiving this because you were mentioned.Message ID: ***@***.***>