UWG Member Actions:

• UWG was asked to supply additional user stories that could help improve pathfinders such that they provide more clear instruction for new users on where and how to find and use data

  • Reach out to UWG to share stories
• UWG was asked to submit complementary/merged dataset suggestions. One suggestion was for SST and current products. Another suggestion was for Sea Ice products.
• Assuming successful entry into the cloud, UWG was asked to share what barriers or challenges they see for executing workflows and processing (to be provided back to OB.DAAC)
  • A survey will be developed to help the UWG with this and the earth data search

OB.DAAC Actions:

• OBDAAC will explore creating merged products composed of complementary datasets (for PACE to start)

Note: A dedicated team is exploring ways to produce cross-mission products as part of a broader time-series effort spanning multiple projects.

• OB.DAAC will contact NSIDC to learn about their notification mechanism used to report changes in datasets to user community

• OB.DAAC will look into feasibility of using EULA mechanism in EDL to force users to acknowledge data version;

• OB.DAAC will look into adding metadata to collections to include release notes link

Will figure out the best way to programatically do this; currently, the general information is included in documentations https://cmr.earthdata.nasa.gov/search/concepts/C3385049983-OB_CLOUD.html

• OB.DAAC will: - Haven't had time for this
  • look into requesting new metadata field for science data product stage (Std, provisional, test, special) -AND-
  • will also consider adding Science Data Product Implementation Plan as related URL to collection metadata so information about data product stage procedure is accessible from product. - unresolved
• Contact EMS for user breakdown in the past year for OB.DAAC
• OB.DAAC will investigate adding keywords for sub-products into OC and IOP collections
  • As data migrating to the cloud, keywords such as Rrs, absorption (aph. etc.) will be visible in the collection variables.
• Enable SeaBASS download reporting in EMS/the Cloud - not started
• An update on the final decision about CALIOP will be provided to the UWG in October
  • In conversation with the CALIOP team regarding achieving this database.
• SeaDAS will develop a tutorial that lets users know Windows requires subsystem for Linux (WSL 2) to run Docker (https://docs.docker.com/desktop/wsl/)
  • Tutorial videos published online -  ()
• SeaDAS is considering ways to return just the subset of data users want vs giving them all the data
  • This effort is in progress - working with the harmony team.
• OBDAAC will coordinate with ARSET if scheduling a training for pulling data from Earthdata Search rather than the Level 1 and 2 Browser seems like a viable training to request.
• OB.DAAC will obtain user statistics and share with UWG
• The 2023 UWG report will be emailed to the group.
• Mailing list is not working well. OB.DAAC will look for alternate means of communicating with UWG

Algorithm Publication Tool (APT) Actions: as APT is going to decommission as a result of web unification, the APT team stopped technical development of this tool. 

• A clear path to regaining access after account lockout is needed.
• Feedback on when documents are published is requested to be sent to collaborators

Earthdata Search Client Actions:

• There is potential for EDSC to support showing 'complementary datasets' through portals. How would this be acheived?
  • Tabled
• EDSC will investigate ways to improve sorting of search results

ESDIS Actions:

• ESDIS is working on developing a combined working group that would have at least a representative from each UWG present to discuss commonalities of needs, issues and solutions. ESWG will be considered as an opportunity for this meeting.
• ESDIS will bring issues impacting related to privatization up to HQ, specifically how it impacts Universities.

Carry-over items

OB.DAAC Actions (2023):

• Work with Earthdata to keep L1/L2 browser features, especially the granule search capability. Develop the geo-spatial/location-based search and subset capabilities.
  • Yes, there is support for both granule-level and geospatial/location-based searches by providing latitude/longitude coordinates or drawing a bounding box. The PO.DAAC subsetting capability via Harmony is also functional. Users can select specific variables.