Major README overhaul with complete deployment and configuration guide.
Moved old docs to tests/ folder for archive.
README.md UPDATES (880 lines - completely rewritten):
✓ Table of contents with navigation
✓ Complete overview of all 4 workflows + daily report
✓ Detailed authentication section (OAuth2 vs mTLS)
✓ Box-config.json location explanation
✓ Server deployment step-by-step guide
✓ Database setup (Docker + native PostgreSQL)
✓ Cron job examples for all workflows
✓ Comprehensive troubleshooting section
✓ Security checklist
✓ Monitoring and log rotation details
✓ Common SQL queries
✓ File structure diagram
KEY SECTIONS ADDED:
1. What's Included - All 5 scripts explained
2. Quick Start - Local setup guide
3. Server Deployment - 6-step process with commands
4. Workflows - Detailed process for each (A1→A2, A5→A6, B1→B2, A2→A3, Daily Report)
5. Authentication - OAuth2 vs mTLS with examples
6. Configuration - All .env variables documented
7. Database - Schema, setup, queries
8. Monitoring - Logs, emails, database queries
9. Troubleshooting - Common issues + solutions
10. File Structure - Complete directory tree
BOX-CONFIG.JSON LOCATION DOCUMENTED:
✓ Must be one folder up from Python-Version
✓ Referenced as ../Box-config.json in config.yaml
✓ Server deployment instructions include copying both files
✓ Troubleshooting section explains file not found errors
MTLS DOCUMENTATION:
✓ Different base URL explained (dev-auth.app-api.ferrero.com)
✓ --auth-pfx flag usage
✓ Whitelisted IP requirement noted
✓ Certificate testing commands
REORGANIZATION:
- Moved old DEPLOYMENT.md → tests/DEPLOYMENT.md (archive)
- Moved old WORKFLOW_DIAGRAMS.md → tests/WORKFLOW_DIAGRAMS.md (archive)
- New DEPLOYMENT_GUIDE.md is the current deployment doc
- README.md is now comprehensive one-stop documentation
Changes:
- Python-Version/README.md (completely rewritten, 880 lines)
- Moved 2 old docs to tests/ folder
- Added test files to tests/ folder
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Box Metadata Extraction Fixed:
Template Name:
❌ Was: 'Ferrero-DAM-Metadata' (with dashes and caps)
✅ Now: 'ferrerodammetadata' (lowercase, no dashes)
Field Names:
❌ Was: 'CreativeX Score', 'CreativeX URL'
✅ Now: 'creativexScore', 'creativexUrl' (camelCase)
Test Results with File 2035459900168:
✅ Template found successfully
✅ creativexScore: 90
✅ creativexUrl: https://www.bbc.com✅ Metadata extraction working!
A2→A3 workflow will now:
1. Download file from Box
2. Read ferrerodammetadata template
3. Extract creativexScore and creativexUrl
4. Update CREATIVEX fields in asset representation
5. Upload to DAM with CreativeX data
Test: Upload a file to Box with ferrerodammetadata template applied
and the A2→A3 script will extract and use those values!
🤖 Generated with Claude Code
Implementation Complete:
✅ Box metadata extraction method
✅ Retrieves from 'Ferrero-DAM-Metadata' template
✅ Extracts 'CreativeX Score' and 'CreativeX URL'
✅ Updates CREATIVEX LINK field in asset representation
✅ Integrated into A2→A3 workflow
Testing Note:
File 2035459900168 does not have metadata template applied yet.
To Test:
1. In Box, select a file in folder 348526703108
2. Right-click → More Actions → Metadata
3. Apply template: Ferrero-DAM-Metadata
4. Fill in:
- CreativeX Score: 85
- CreativeX URL: https://creativex.com/report/12345
5. Run A2→A3 script
6. Check logs for: 'CreativeX URL from Box: ...'
7. Verify CreativeX fields in uploaded DAM asset
Implementation ready - awaiting file with metadata template for testing.
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
Created a2_to_a3_upload_polling.py:
- Polls Box folder (348526703108) instead of webhook
- Works locally (no need for public URL)
- Single-run mode (process one file and exit)
- Can be run via cron every 5 minutes
Why Polling Instead of Webhook:
- Webhooks require public URL (doesn't work on localhost)
- Polling works everywhere (local and server)
- Same functionality, different trigger mechanism
Database Fix:
- Don't create new columns (dam_asset_id, upload_status)
- Use existing schema: tracking_id, derivative_filename, file_extension, status
- Simplified store_derivative_asset() to use existing columns only
- Database now compatible with existing schema
Test Results - A2→A3 Polling:
✅ Polls Box folder 348526703108
✅ Finds V2 files with tracking IDs
✅ Downloads from Box
✅ Loads master metadata from PostgreSQL
✅ Builds 27 MVP fields
✅ Updates Description, State, Language from filename
✅ Uploads to DAM successfully (Asset ID: 214924)
✅ Stores derivative record
✅ Processes one file and exits
Both Scripts Working:
✅ A1→A2: Downloads from DAM → Box (folder 348304357505)
✅ A2→A3: Uploads from Box → DAM (folder 348526703108)
Cron Setup:
*/5 * * * * python scripts/a1_to_a2_download.py
*/5 * * * * python scripts/a2_to_a3_upload_polling.py
Complete automation ready for production!
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
Changes:
- Downgraded boxsdk to 3.x (compatible API)
- Created .env file with all credentials
- Fixed requirements.txt versions
Python automation now ready for testing:
✅ Virtual environment created
✅ All dependencies installed
✅ Box connection working
✅ Database connection working
⚠️ DAM OAuth (same creds as PHP, might be temp server issue)
Next steps:
1. Test DAM connection (may need to retry)
2. Run A1→A2 script
3. Monitor logs
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
