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).
All of these changes were fixed in imap_processing except for the SWAPI and SWE l3 dataset issue.
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).
All of these changes were fixed in imap_processing except for the SWAPI and SWE l3 dataset issue.