obsidian/wiki/client-knowledge/ferrero.md
2026-04-27 18:22:09 +01:00

53 lines
2.1 KiB
Markdown

---
title: "Client Knowledge: Ferrero"
description: "Ferrero-specific context: AC Booking Tool, Box API, OMG CSV workflow"
tags: [client-knowledge, ferrero]
created: 2026-04-27
updated: 2026-04-27
---
# Client Knowledge: Ferrero
## Key Takeaways
- One active project: AC Booking Tool — browser-based, outputs CSV for OMG media booking system
- No Docker, no database — the simplest possible stack (Node.js + HTML/JS)
- Box API integration for "Send to OMG" folder saves
- CSV download works without the Node server — can open index.html directly
---
## Projects
| Project | Server | Stack | Status | Purpose |
|---------|--------|-------|--------|---------|
| [[01 Projects/ferrero-ac-creator/Ferrero AC Booking Tool\|AC Booking Tool]] | optical-web-1 | Node.js + HTML/JS + Box API | active | Generate CSV files for OMG media booking import |
---
## AC Booking Tool — Key Facts
**What it does:** Browser form for creating Ferrero communication asset bookings → export as CSV → import into OMG (media booking system)
**Two modes:**
1. **Standalone:** open `index.html` directly — CSV download works without server
2. **With server:** `node server.js``http://localhost:3456` — enables "Send to OMG" (Box API folder save)
**Box API:** Used for saving directly to a predefined Ferrero Box folder. Uses Box OAuth or service account credentials. See [[wiki/tech-patterns/box-api-integration|box-api-integration]].
**No build step:** Plain HTML/JS, no transpilation. Editing is direct.
**Deploy:** `node server.js` on optical-web-1. No Docker, no reverse proxy — runs as a direct port.
---
## OMG CSV Format
The CSV output format is dictated by OMG media booking system import requirements. Fields are Ferrero-specific (AC codes, booking dates, media channels). **Do not change column structure without confirming with client** — OMG imports are fragile to schema changes.
---
## Related
- [[wiki/tech-patterns/box-api-integration|box-api-integration]] — Box API patterns
- [[wiki/tech-patterns/nodejs-vanilla-proxy|nodejs-vanilla-proxy]] — Node.js + vanilla JS pattern