SAP coordination: pre-meeting technical orientation

### What
Determine whether and how the SAP portal (ResearchDataGov.org) can harvest metadata from Data.gov, and what format or mechanism would work best.

### Why
The single-submission model only works if the SAP portal can pull from Data.gov rather than collecting separate agency submissions. We need to know what their technical constraints are before we can finalize the pilot design.

### Done When
- [ ] Data.gov harvest mechanisms documented (data.json, API endpoint, filtered query options)
- [ ] SAP team has confirmed their portal's ability to harvest from an external source
- [ ] Format and frequency requirements from the SAP side are documented (e.g., JSON-LD, DCAT, polling interval)
- [ ] Any blockers or gaps are captured with a recommended path forward

### Notes
- Data.gov currently supports harvest via agency data.json feeds and a catalog API
- The SAP team may not be technical -- Reid may need to walk them through options and provide example payloads
- If the SAP portal cannot harvest natively, a lightweight intermediary script may be needed (scope TBD)