feat: rename project to OcotilloAPI and update CLI command references

Author: jirhiker

README.md

@@ -1,4 +1,4 @@
-# NMSampleLocations
+# NMSampleLocations aka OcotilloAPI
 
 [![Code Format](https://github.com/DataIntegrationGroup/NMSampleLocations/actions/workflows/format_code.yml/badge.svg)](https://github.com/DataIntegrationGroup/NMSampleLocations/actions/workflows/format_code.yml)
 [![Dependabot Updates](https://github.com/DataIntegrationGroup/NMSampleLocations/actions/workflows/dependabot/dependabot-updates/badge.svg)](https://github.com/DataIntegrationGroup/NMSampleLocations/actions/workflows/dependabot/dependabot-updates)
@@ -9,7 +9,8 @@
 **Geospatial Sample Data Management System**  
 _New Mexico Bureau of Geology and Mineral Resources_
 
-NMSampleLocations is a FastAPI-based backend service designed to manage geospatial sample location data across New Mexico. It supports research, field operations, and public data delivery for the Bureau of Geology and Mineral Resources.
+OcotilloAPI is a FastAPI-based backend service designed to manage geospatial sample location data across New Mexico. It 
+supports research, field operations, and public data delivery for the Bureau of Geology and Mineral Resources.
 
 ---
 
@@ -197,4 +198,39 @@ Notes:
 - All `Update` schema fields are optional and default to `None`
 - All `Response` schema fields are defined as `<type>` if non-nullable and `<type> | None` if nullable
 - All raised exceptions should use the `PydanticStyleException` as defined in `services/exceptions_helper.py`
-- Errors handled by the database should be enumerated and handled in a database_error_handler in each router's file
+- Errors handled by the database should be enumerated and handled in a database_error_handler in each router's file---
+
+## 📦 Ocotillo CLI
+
+The `oco` command exposes project automation and bulk data utilities.
+
+```bash
+# Display available commands
+oco --help
+
+# Bulk import water level data from a CSV
+oco water-levels bulk-upload --file water_levels.csv --output json
+```
+
+The bulk upload command parses and validates each row, creates the corresponding field events/samples/observations, and prints a JSON summary (matching the API response shape) so the workflow can be automated or scripted.
+## 🧪 Testing
+
+```bash
+# Run unit tests
+pytest
+
+# Run Behave BDD specs
+behave tests/features
+```
+
+> Tests require a local Postgres/PostGIS instance. Set `POSTGRES_*` values in `.env`, run migrations, and ensure the database is reachable before running the suites.
+
+## 🔄 Data Transfers
+
+Legacy or staging datasets can be imported using the transfer utilities:
+
+```bash
+python -m transfers.transfer
+```
+
+Configure the `.env` file with the appropriate credentials before running transfers.

pyproject.toml

@@ -1,7 +1,7 @@
 [project]
-name = "nmsamplelocations"
+name = "OcotilloAPI"
 version = "0.1.0"
-description = "Add your description here"
+description = "FastAPI backend and CLI for managing Ocotillo groundwater locations, wells, assets, and bulk water-level data transfers."
 readme = "README.md"
 requires-python = ">=3.13"
 dependencies = [
@@ -99,6 +99,10 @@ dependencies = [
   "uvicorn==0.38.0",
   "yarl==1.20.1",
 ]
+
+[project.scripts]
+oco = "cli.cli:cli"
+
 [tool.alembic]
 
 # path to migration scripts.

tests/features/water-level-csv.feature

@@ -44,7 +44,7 @@ Feature: Bulk upload water level entries from CSV via CLI
       | water_level_notes  |
     When I run the CLI command:
       """
-      bdms water-levels bulk-upload --file ./water_levels.csv --output json
+      oco water-levels bulk-upload --file ./water_levels.csv --output json
       """
     Then the command exits with code 0
     And stdout should be valid JSON
@@ -71,7 +71,7 @@ Feature: Bulk upload water level entries from CSV via CLI
       | data_quality          |
     When I run the CLI command:
       """
-      bdms water-levels bulk-upload --file ./water_levels.csv
+      oco water-levels bulk-upload --file ./water_levels.csv
       """
     Then the command exits with code 0
     And all water level entries are imported
@@ -82,7 +82,7 @@ Feature: Bulk upload water level entries from CSV via CLI
     Given my CSV file contains extra columns but is otherwise valid
     When I run the CLI command:
       """
-      bdms water-levels bulk-upload --file ./water_levels.csv
+      oco water-levels bulk-upload --file ./water_levels.csv
       """
     Then the command exits with code 0
     And all water level entries are imported
@@ -97,7 +97,7 @@ Feature: Bulk upload water level entries from CSV via CLI
     Given my CSV file contains 3 rows of data with 2 valid rows and 1 row missing the required "well_name_point_id"
     When I run the CLI command:
       """
-      bdms water-levels bulk-upload --file ./water_levels.csv
+      oco water-levels bulk-upload --file ./water_levels.csv
       """
     Then the command exits with a non-zero exit code
     And stderr should contain a validation error for the row missing "well_name_point_id"
@@ -108,7 +108,7 @@ Feature: Bulk upload water level entries from CSV via CLI
     Given my CSV file contains a row missing the required "<required_field>" field
     When I run the CLI command:
       """
-      bdms water-levels bulk-upload --file ./water_levels.csv
+      oco water-levels bulk-upload --file ./water_levels.csv
       """
     Then the command exits with a non-zero exit code
     And stderr should contain a validation error for the "<required_field>" field
@@ -130,7 +130,7 @@ Feature: Bulk upload water level entries from CSV via CLI
     Given my CSV file contains invalid ISO 8601 date values in the "measurement_date_time" field
     When I run the CLI command:
       """
-      bdms water-levels bulk-upload --file ./water_levels.csv
+      oco water-levels bulk-upload --file ./water_levels.csv
       """
     Then the command exits with a non-zero exit code
     And stderr should contain validation errors identifying the invalid field and row
@@ -141,7 +141,7 @@ Feature: Bulk upload water level entries from CSV via CLI
     Given my CSV file contains values that cannot be parsed as numeric in numeric-required fields such as "mp_height" or "depth_to_water_ft"
     When I run the CLI command:
       """
-      bdms water-levels bulk-upload --file ./water_levels.csv
+      oco water-levels bulk-upload --file ./water_levels.csv
       """
     Then the command exits with a non-zero exit code
     And stderr should contain validation errors identifying the invalid field and row
@@ -152,7 +152,7 @@ Feature: Bulk upload water level entries from CSV via CLI
     Given my CSV file contains invalid lexicon values for "sampler", "sample_method", "level_status", or "data_quality"
     When I run the CLI command:
       """
-      bdms water-levels bulk-upload --file ./water_levels.csv
+      oco water-levels bulk-upload --file ./water_levels.csv
       """
     Then the command exits with a non-zero exit code
     And stderr should contain validation errors identifying the invalid field and row