ResourceName values are not descriptive enough

[berniegsfc]

The /Spase/NumericalData/ResourceHeader/ResourceName value in most, if not all, CNES documents are not descriptive enough. One example is spase://CNES/NumericalData/CDPP-AMDA/MAVEN/MAG/mav-mag-pds. See attached screenshot of how they are displayed in the Heliophysics Data Portal.

[tressahelvey]

Hello Daniele, Was it your intention to name your SPASE records as indicated in the screen shot? It has been pointed out that they are not descriptive enough. I have added Lee and Shing to this notice as well. Please let us know if you'd like to discuss the issue. Thank you. Tressa

[myriam62]

Hi, We use the ResourceName to build the tree in AMDA ( for example you can see 0.03 sec, 1 sec, 4s). A fuller description is given in other fields. If this is a problem, we can think of another solution.

Best regards, Myriam

[berniegsfc]

AMDA should use the //TemporalDescription/Cadence value instead of the //ResouceName for cadence values.

[myriam62]

The cadence is well defined in TemporalDescription/Cadence. We need to display the name of the dataset in a tree and we use the ResourceName to do this.

[berniegsfc]

Having a ResourceName value like you have make your SPASE XML files un/less usable in other systems like HDP. If your SPASE files are only to be used in AMDA, then the current values are fine.

[BaptisteCecconi]

I agree with the comment from @berniegsfc. The SPASE records are not only for CDPP/AMDA, they can be used by other tools to discover CDPP/AMDA resources. If the ResourceName is cryptic, then it is a bit useless. I understand that CDPP/AMDA has a direct mapping between ResourceName and the AMDA tree display. There is some value in this, of course, but not to the detriment of external usage.

So I suggest to change a bit the mapping and include more information in the SPASE ResourceName.

[sffung]

ResourceName should be a "full name" sufficient for identifying a resource uniquely. It should be a brief, textual description (see definition in SPASE dictionary) that corresponds to the ResourceID. Cadence can be included as a part of the ResourceName, but by itself cadence is not a full name of a resource (see an example for an MMS product: [https://hpde.io/NASA/NumericalData/MMS/1/FIELDS/FGM/Burst/Level2/PT0.0078125S.html]

[myriam62]

I understand what you mean. We will complete the descriptions for the ResourceName as soon as possible.

[sffung]

Hi Myriam,

Great, thanks! While we’re at it, I think we’ve also found other issues relating to the CDPP SPASE repository that are inconsistent with the SPASE registry. Lee Bargatze has been tasked to document some of our findings. We’d like to have a meeting (on Teams or Webex when we have a clearer picture) to discuss how we may resolve them.

Shing

From: myriam62 @.> Reply-To: hpde/CNES @.> Date: Wednesday, March 6, 2024 at 3:42 AM To: hpde/CNES @.> Cc: "Shing Fung (GSFC-6750)" @.>, Assign @.***> Subject: [EXTERNAL] [BULK] Re: [hpde/CNES] ResourceName values are not descriptive enough (Issue #5)

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.

I understand what you mean. We will complete the descriptions for the ResourceName as soon as possible.

— Reply to this email directly, view it on GitHubhttps://github.com/hpde/CNES/issues/5#issuecomment-1980351990, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJUI6GV4XPK7766WDLDVHDLYW3JHVAVCNFSM6AAAAABDMFOZR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBQGM2TCOJZGA. You are receiving this because you were assigned.Message ID: @.***>

[tressahelvey]

Hello Myriam, We are checking on the status of the modifying the ResourceName. Do you have a target date for completion? Thank you.

[myriam62]

The ResourceNames has been modified. Best regards.

[tressahelvey]

Closing Ticket