Define supported spatial metadata standards of H2.0

[rshewitt]

User Story

In order to understand what information harvester 2.0 is responsible for processing, datagov wants to define the supported spatial metadata standards of harvester 2.0

Acceptance Criteria

[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]

• [ ] GIVEN what spatial metadata standards are currently in catalog \ AND what the current harvester supports WHEN a discussion happens \ THEN a list of supported metadata types is produced \

Background

• What spatial metadata standards are currently supported in harvester 1.0?

  • ISO 19115 Metadata ( ISO 19139 NGDC XSD )
  • FGDC minimal validation
  • FGDC CSDGM Version 2.0, 1998 ( FGDC-STD-001-1998)
  • FGDC CSDGM Biological Data Profile (FGDC-STD-001.1-1999)
  • FGDC CSDGM Metadata Profile for Shoreline Data (FGDC-STD-001.2-2001)
  • FGDC Extension for Remote Sensing (FGDC-STD-012-2002)

• What spatial metadata standards are in catalog?

  • ISO19115-2 (291017 datasets)
  • FGDC-STD-001-1998 (5262 datasets)
  • ISO19139 (2219 datasets)

• What spatial services do we NOT want to support in harvester 2.0? ( not a metadata standard but relevant )

  • CSW
  • geoportal
  • ArcGIS

• What could a transformation pipeline look like for harvester 2.0 with the data we currently have?

  • ISO19115-2 ---------\
  • FGDC-STD-001-1998 ---[ ISO19139 NGDC we're here currently on catalog ] --- [ ISO19115-3 --- DCATUS this is h2.0 ]
  • ISO19139 -------------/

Security Considerations (required)

[Any security concerns that might be implicated in the change. "None" is OK, just be explicit here!]

Sketch

[Notes or a checklist reflecting our understanding of the selected approach]

[rshewitt]

noaa takeaway: do we want to support s3 as a harvest source? s3 bucket urls can't be authenticated. waf will have a .gov TLD so that's why we can process them