Database POC for basic rec site info

[FM-SM]

This ticket is to do the first part of the data migration from the FTA database into a new database. It may include a subset of the full data set as we are scoping the first data work to public data.

Full migration?
Copy/paste of data so we can start using it?
Access to prod database?
ETL or some sort of update pattern?

Acceptance Criteria:

• ...

Development Checklist:

• ...

Notes:

From refinement Nov 19:

• likely reorganize the database structure from current state (regardless of db chosen)
• maybe use test data and do some verifications
• could start with ~10 fields and do a POC to get our data structured to get an idea of what we want to build
  • use "view rec site" designs to drive these selections
• Do a POC and potentially do an ETL or something to show updates to the data?
  • mitigates the update process for users as they would be updating in FTA and then we could use an ETL or something to update our POC database (would mean that we need a connection to prod data - so we could start this in test?)
• Using this POC as a starting place to start getting our tech set-up for a data register
• this would be an epic level ticket - need to be broken down in refinement
• need to identify what fields to include - minimal viable data
• this concept leads us to think a mono repo for something like rec-resource-registry to capture a data register for rec sites & trails data
  • then this could link to other products and tools via api

[JLWade]

delete ticket