Missing dataset names for L2, L3 data noticed by SPDF

[mmshaw]

From @andrkoval on 9/4/2026:

For IMAP datasets, the dataset name (recorded in Logical_source_description ISTP global attribute) normally includes both IMAP, instrument name, and the data type itself (combination that completely identifies dataset). However, for some datasets either “IMAP" or the instrument name is missing. For example, for all MAG datasets there is no “MAG" in the dataset name, e.g., Logical_source_description = "IMAP Mission Normal Rate Instrument Level-2 Data in Geocentric Solar Ecliptic Reference Frame.” for imap_mag_l2_norm-gse dataset (and also includes unnecessary "." at the end of the name). Also, for some SWAPI and SWE L3 datasets there is no "IMAP" in the name. Could you please check the dataset names (including future ENA datasets). The second in-situ release, which you plan by 9/29, would be a good time to update those (and please let us know of such updates).

[mmshaw]

@jtniehof did you already do any work on this e.g., for the SWAPI and SWE L3s that I should note?

[jaredclaypoole]

I addressed the MAG description issue at least partially in merged PR #3400.

[bryan-harter]

For @lacoak21's knowledge:

You can see the issue if you go to https://cdaweb.gsfc.nasa.gov/, select "IMAP" and "Submit". You get a boatload of products listed here.

The issue is that the MAG datasets say:

IMAP Mission Normal Rate Instrument Level-2 Data in Geocentric Solar Ecliptic Reference Frame. - Prof. David J. McComas (Princeton University)

But other instruments contain the instrument name in that description, like:

IMAP SWE Instrument Level-2 Science Data - Prof. David J. McComas (Princeton University)

Jared's fixes should actually solve the MAG one, but we should just double check that is actually the case.

And then the other issue is that SWAPI and SWE L3 don't include the word "IMAP" in that descriptor field, so that just needs to be added in for those products.

And then in general, just take a look at the descriptors on that page and ensure they are all consistent. At a brief glance I don't see anything too obvious.

Thanks!

[lacoak21]

@jtniehof and @bryan-harter I dont think I can fix the l3 issue from imap_processing unless I am mistaken.