Ingest subset of roughly 100-200 WV02_Pan_L1B granules into UAT

[jsrikish]

Ingest subset of roughly 100-200 WV02_Pan_L1B granules into UAT to allow verification of metadata and metrics.

ACCOUNT: [csda-cumulus-uat-1686]

To find a date range that has roughly 100-200 granules, make use of AWS Athena by doing the following:

• In the MCP IMPACT-CSDAP AWS account's console, open the Athena query editor
• Select the AwsDataCatalog Data Source and the default Database
• Run the following query to update the partitions: MSCK REPAIR TABLE maxar_transfer
• Run queries similar to the following (tweaking dt and the path pattern -- see notes below) until a count near the 100-200 range is obtained:

  SELECT * FROM "maxar_transfer$partitions" ORDER BY dt DESC
  SELECT * FROM "maxar_transfer" WHERE dt='2024-05-17-01-00' AND key like 'css/nga/WV02/1B/2009/%P1BS%' AND key like 'css/nga/WV02/1B/2009/%BROWSE.jpg%' limit 100;

This approach uses the count of *BROWSE.jpg files as a proxy for the number of granules in the date range.

NOTE: the value of dt in the query above must be set to the most recent date of the S3 inventory (likely the current date, but the day prior to the current date should always work since the most recent 3 days are retained).

NOTE: days like 2009/321 and 2009/339 (because the end date is exclusive in the rule definition) must be converted to yyyy/MM/DD for determining ISO 8601 datetime values for the start and end dates for the sample rule. This site provides conversion: https://dqydj.com/day-of-the-year-calculator/

• 2009/321 is 2009/11/17T00:00:00Z
• 2009/339 is 2009/12/05T00:00:00Z

Acceptance criteria:

• [x] define a rule named WV02_Pan_L1B___1_UAT.json that spans a period of time that includes roughly 100-200 granules (using instructions above for finding appropriate values for startDate and endDate)
• [x] load the rule into UAT

  DOTENV=.env.uat make bash
  cumulus rules add --data app/stacks/cumulus/resources/rules/WV02_Pan_L1B/v1/WV02_Pan_L1B___1_UAT.json

• [ ] trigger the rule to ingest the granules

  DOTENV=.env.uat make bash
  cumulus rules enable --name WV02_Pan_L1B___1_UAT
  cumulus rules run --name WV02_Pan_L1B___1_UAT

• [ ] verify all granules covered by the rule are successfully ingested and published by using UAT Earthdata Search: https://search.uat.earthdata.nasa.gov/search?q=WV02_Pan_L1B (value of q should be collection short name)
• [ ] verify log entries appear in Kibana:
  1. connect to NASA VPN
  2. search Kibana for the recent files&_a=(columns:!(),filters:!(),index:'75212c20-de6a-11eb-a6ea-31de6c2593f3',interval:auto,query:(language:kuery,query:''),sort:!(!('@timestamp',desc))))
  3. login with saml/launchpad
  4. confirm that the search results show the ingested files (you might need to adjust the timespan in the upper right corner of the page)
  5. Message Helen & Aaron to check for 100 granules in UAT

[hbparache]

Jayanthi to look into the size / NA

[hbparache]

Jayanthi, Madhu, and Abdelhak have been working to identify the cause of the difference in fields between metadata in prod and uat. They have a plan forward, and aim to resolve tomorrow (Wed).

[hbparache]

"units"="NA" was due to bytes not being a Unit option (wiki link) and best practices being to not later the size to an approximation. The full units/size is included in the metadata section that refers to the data itself (not URL to data)

Workflow was checked in multiple ways by Jayanthi, Abdelhak, Madhu.