Blue-Green Product Names

[jirhiker]

We need to choose proper product names for our internal and external products.

I suggest "DataForge" for the internal product. We should rename the NMSamplelocations repo to DataForgeAPI and NMBGMRDataManager to DataForgeUI. The components of DataForge are

1. Postgres database
2. FastAPI based API
3. refine.dev based UI
4. Clerk, Auth0, Keycloak for authentication see ADR Authentication and Authorization platform #6

I suggest "Aqueduct" for the external product. We should rename DIE to AqueductIntegrationEngine or we should roll DIE into the Aqueduct code base. The components of Aqueduct are

1. dagster orchestration engine
2. dagster source connectors
3. FROST
4. data integration engine
5. geoserver

[jirhiker]

Here are more AI suggestions that I like

• GRIDS (Geologic Repository for Indexed Data & Samples)
• SampleBase, (Ooo I kinda like this. There is a familiarity to it i.e. samplebase->database, that users might find easy to adopt)

GRIDS

GRIDS is the New Mexico Bureau of Geology’s centralized system for managing geologic samples, site metadata, and spatially-referenced data. Designed for long-term data stewardship, GRIDS supports indexing, traceability, and integration of field and lab data across research and public access workflows.

Tagline

"From field to archive — organized, accessible, preserved."

[jacob-a-brown]

What about NMBGMRData? It's simple, encompasses all data (assets included), and is named after our organization. It's not very sleek though

[jacob-a-brown]

Can we continue to call it the Data Integration Engine? Aqueduct Integration Engine is a mouthful. Users would also need to know what Aqueduct is, which may not be too relevant to people outside of the Bureau (and we hope to have people adopt the DIE, such as other organizations and researchers).

[jirhiker]

The idea is to consolidate under a single product name. Do we think DIE is going to continue to be a standalone product? It seems it should be rolled into Aqueduct, mainly because I don't see much need/desire to use it as a standalone product.

[ksmuczynski]

Product name ideas (mostly acronyms):

• GEODE, NMBGMR_Geode: kind of riffs off of "geology" and "nodes" as sample locations
• ES3, NMES3: Acronym for Earth Science Sample System, or New Mexico Earth Science Sample System.
• GEOSS, NMGEOSS: Similar to the previous bullet, stands for GEOscience/GEOlogic Sample System, or New Mexico GEOscience/GEOlogic Sample System
• GEMS: Geoscience & Earth-data Management System
• ESDAC: Earth Science Data Center
• NM-CDS: New Mexico Core/Central Data System.

[jirhiker]

• ES3 --- pronounced e-ess-three or ess-3?. S3 is an AWS product
• GEOSS --- already taken. Global Earth Observation System of Systems
• GEMS --- already taken. GeMS. https://pubs.usgs.gov/publication/tm11B10, https://ngmdb.usgs.gov/Info/standards/GeMS/
• ESDAC --- pretty close to https://edac.unm.edu/

[jacob-a-brown]

ES3 is nice and simple, but certainly close to S3. What about EDS2 (Earth Data Sample System)?

[ksmuczynski]

I was thinking you'd say the letters and numbers as listed, so it'd be pronounced "E-S-3" ("e-ess-three").

[jirhiker]

I'm leaning away from anything with NM or NMBGMR in the name. This is a product that could be used by a number of other state surveys(?)

[jacob-a-brown]

That's an exciting prospect! If it's containerized (which it is!), our repo(s) could easily be reused by other state surveys

[chasetmartin]

A couple others from brainstorming:

• Bedrock
• Strata
  Since there are some corporate applications online with those names, like "Amazon Bedrock", maybe a two word combo?
• Bedrock Core
• Strata Hub
• Stratabase (exists for a couple random products online)
• Stratacore

[jirhiker]

Ocotillo