Notes about DTs (Fort Davis insights)

[helpfultangent]

Thoughts from conversation on March 22, 2024

• Onboard internal team - training
• document pieces of architecture (use MkDocs - Lissa to create web presence for accessible documentation)

Look and Feel (Hernan)

• data registry - MS2 grandchild
• rebranding MINT
• CKANN

Collection

• internal onboarding for ingest services/use
• branding of all ingest services into one place with similar look and feel
• Registry [metadata schema - data model of corded; metadata schema]
  - metadata lives in Postgres at TACC
• Registry for outside links/api services (e.g. GAMs - MF96)
  • raw/unchanged data product from an origin agency
  • modified/improved dataset (e.g. GAMs - MF96-to-MF05)
  • hosting other peoples' data (e.g. subsidence, researchers, communities, university partners)

Storage
Available Storage Locations currently
- ArcGIS portal data store (sitestories.io on Azure)
- S3 allocation - TDIS (need to change the name of allocation - Chris; 10TB+ - loaded into it via MinIO with other application batch scripts, forms, MEEP living on TACC azure)
- sort through list of all vm and other services connected to S3 allocation
- PT2050 allocation on Corral

• metadata to be coredb lives on a virtual machine at TACC

What we want People to:
PUBLISH - large and AI ready collections (Bell Jar)
USE - models and data in interoperable formats and reusable analyses

Defining a digital object:
We want Single Stream Ingest - set up UX workflows that automate ingest with a shared interface and automate ingest and registration

• all digital elements; coredb only stores metadata digital objects
• have to ingest 2 times once for metadata and data object

Discovery (CKANN)

• look and feel
• not linked to anything, should be linked to coredb and postgis metadata registry

Authentication

• immediate term
• long-term priority

---

Storage - (PTDataX - request it's made S3 - ask Chris)

• Sitestories.io
• digital objects for Ft Davis
• metadata surveys
• Ft Davis Wildfires app - multiple data layers from various sources (Planet, pdal elevation), grid data from TNRIS, solar park burn scar perimeters
• photos and videos on our phones
• files on laptops (various like movies)
• used cloud compare
• TNRIS files
• Las files.
• Photogrammetry - point - cloud to polys; orthophotos, digital terrain and digital surface models
• Drone flight data
• Geoslam datasets

Workflows

• Need to document