mike-gangl
commented
7 months ago closing this as done-enough; will need documentation updates outside of the jupyter notebook eventually.
Closed mike-gangl closed 7 months ago
mike-gangl
commented
7 months ago closing this as done-enough; will need documentation updates outside of the jupyter notebook eventually.
Custom Metadata
An algorithm developer creates data products which have required and optional custom metadata. The metadata for output products is needed for rich metadata search in the U-DS Data Catalog.
Acceptance Criteria
Algorithms are required to create a stac catalog for all products they want to output from their algorithm (catalog.json)
Algorithms are required to create a stac item for each "granule"
Algorithms specify required metadata in each stac item (Start, stop time)
Algorithms specify optional metadata data in STAC item (label, quality flag?)
Stage-out process reads catalog.json and finds files for stage-out
Stage-out process move files to an S3 location or to a collection's specific S3 location if specified in the workflow
Stage-out process updates the STAC file to reference their S3 location
Stage-out outputs a STAC catalog of the output files in their Unity storage areas
Data Catalog task takes in catalog.json
For each stac item, a CNM is constructed with assets listed in the STAC item, along with the STAC item json itself
U-DS ingest reads the sTAC item catalog for required and optional metadata
Required Metadata are searchable via the DAPA endpoint
Optional Metadata are searchable via the DAPA endpoint
Documentation on how to register and provide custom metadata
Required metadata (Needs to be worked):
Start Time / Stop Time OR Sol/SCLK? Creation Time
Optional Metadata
Bounding coordinates? cycle, Pass
Custom (Project) Metadata (examples) Cloud Cover
Work Tickets
Link to work tickets required to implement the epic
Dependencies
Other epics or outside tickets required for this to work
Associated Risks
links to risk issues associated with this epic