[2ff88f42] Update GEMINI.md with Notion Tooling Documentation
This commit is contained in:
23
GEMINI.md
23
GEMINI.md
@@ -122,6 +122,29 @@ To ensure the stability and accuracy of the metric extraction logic, a dedicated
|
||||
|
||||
These tests are crucial for preventing regressions as the parser logic evolves.
|
||||
|
||||
## Notion Maintenance & Data Sync
|
||||
|
||||
Since the "Golden Record" for Industry Verticals (Pains, Gains, Products) resides in Notion, specific tools are available to read and sync this data.
|
||||
|
||||
**Location:** `/app/company-explorer/backend/scripts/notion_maintenance/`
|
||||
|
||||
**Prerequisites:**
|
||||
- Ensure `.env` is loaded with `NOTION_API_KEY` and correct DB IDs.
|
||||
|
||||
**Key Scripts:**
|
||||
|
||||
1. **`check_relations.py` (Reader - Deep):**
|
||||
- **Purpose:** Reads Verticals and resolves linked Product Categories (Relation IDs -> Names). Essential for verifying the "Primary/Secondary Product" logic.
|
||||
- **Usage:** `python3 check_relations.py`
|
||||
|
||||
2. **`update_notion_full.py` (Writer - Batch):**
|
||||
- **Purpose:** Batch updates Pains and Gains for multiple verticals. Use this as a template when refining the messaging strategy.
|
||||
- **Usage:** Edit the dictionary in the script, then run `python3 update_notion_full.py`.
|
||||
|
||||
3. **`list_notion_structure.py` (Schema Discovery):**
|
||||
- **Purpose:** Lists all property keys and page titles. Use this to debug schema changes (e.g. if a column was renamed).
|
||||
- **Usage:** `python3 list_notion_structure.py`
|
||||
|
||||
## Next Steps
|
||||
* **Marketing Automation:** Implement the actual sending logic (or export) based on the contact status.
|
||||
* **Job Role Mapping Engine:** Connect the configured patterns to the contact import/creation process to auto-assign roles.
|
||||
|
||||
Reference in New Issue
Block a user