Project Data and Cooperation¶
This methodology serves as a checklist for gathering data and access credentials from the client before implementation begins. It is designed for Project Managers and AI Agents analyzing requirements and preparing development specifications.
The goal is to ensure all necessary keys, data, and contacts are available for smooth integration and migration processes.
Gathering Methodology¶
Every project requires a specific set of data. The list below covers the most common scenarios. For each item, you must define: 1. Source: Who provides the data (Client / Vendor / IT Dept). 2. Format: What the data looks like (API Key, XLSX, SQL Dump). 3. Status: Requested / Delivered / Verified.
1. Integrations and API (External Systems)¶
Connecting to third-party systems is a critical part of most projects. Without these details, integration cannot be implemented or tested.
| Area | Service / System | Requirements Checklist | Note |
|---|---|---|---|
| E-shop | Shoptet | E-shop ID, API Access Token |
Rights must be set in the API add-on. |
| WooCommerce | Consumer Key, Consumer Secret, Site URL |
Read/Write permissions required. | |
| PrestaShop | Webservice Key, Site URL |
Enable relevant resources (GET, POST...). | |
| Accounting | Pohoda (mServer) | IP Address/URL, Port, IČO (Reg. No), Username, Password |
Often requires VPN or Public IP. |
| Abra Flexi | Instance URL, Username, Password, Company ID |
||
| Money S3 | XML Export or Direct DB Access | API is often limited; file exchange is common. | |
| Shipping | PPL / DHL | Client ID, Client Secret, Number Ranges |
Request both Test and Production credentials. |
| Zásilkovna (Packeta) | API Key (Password), API Label |
Distinguish between Client API and Carrier API. | |
| GLS / DPD | Username, Password, Customer ID |
Often require specific label formats. | |
| Banks | Fio Banka | API Token (Read-only) |
For downloading statements. |
| Komerční banka | Certificate, API Keys |
Complex authorization (PSD2). | |
| Specialized | Signi (Signatures) | API Key, Contract Template ID |
Specify if Sandbox or Production. |
| SmartEmailing | Username, API Token |
For contact synchronization. | |
| Raynet / Pipedrive | API Key, Instance URL |
For migration or bi-directional sync. | |
| ARES / Registers | Public Sources | Usually no key needed, but beware of IP limits. |
2. Data Migration (Legacy Data)¶
Transferring data from the old system. Data quality and cleanliness are key here.
| Entity | Typical Format | What to Check / Specifics |
|---|---|---|
| Directory (Clients) | XLSX, CSV, SQL | First/Last Name separation, ID validation, Duplicates, GDPR consents. |
| Contacts | XLSX, CSV | Link to Company (Company ID), Emails, Phones. |
| Product Base | XLSX, XML Feed | Codes (SKU/EAN), Prices (with/without VAT), Stock Cards, Categories, Images (URL). |
| Open Orders | XLSX, JSON | Order Status, Order Items, Link to Customer. |
| Invoices (History) | SQL Dump, PDF | Often only unpaid (receivables) are migrated, or full history for stats. |
| Stock Levels | XLSX (Inventory) | Exact quantities at launch date, Stock prices (purchase). |
File Requirements: * Encoding: UTF-8 (preferred), Windows-1250 (Czech Excel). * Structure: The first row must contain column headers. * Mapping Table: If statuses change (e.g., "Done" -> "Closed"), the client must provide a conversion map.
3. Infrastructure and Access¶
Technical background for application hosting and developer access.
| Access Type | Purpose | Required Details |
|---|---|---|
| Hosting / Server | App Deployment | IP Address, SSH Port, Root/User login, SSH Key (preferred). |
| Database | Direct Data Access | DB Host, DB Name, User, Password, Port (usually 3306/5432). |
| DNS / Domain | Email & Web Setup | Access to registrar (GoDaddy, Namecheap...) or DNS admin contact. |
| SMTP (Emails) | Sending Notifications | SMTP Server, Port (465/587), Username, Password, SSL/TLS. |
| IMAP (Emails) | Incoming Mail Pairing | IMAP Server, Port (993), Username, Password. |
| VPN | Internal Network Access | Config File (.ovpn), Certificates, Login Credentials. |
| Remote Desktop | Windows Server Mgmt | RDP Address, Username, Password (TeamViewer/AnyDesk as backup). |
4. Business Assets (Design & Content)¶
Visual identity and system settings.
- [ ] Logo: Vector format (SVG, AI, EPS) or high-quality PNG (transparent background).
- [ ] Colors: Brand manual or HEX codes of primary colors.
- [ ] Document Templates: Invoice, Delivery Note, Quote templates (PDF or Word).
- [ ] Email Signatures: HTML code or signature example for users.
- [ ] User List: First Name, Last Name, Email, Phone, Role/Position, Access Rights.
- [ ] Numbering Series: How should invoice numbers look? (e.g.,
2024001,INV-2024-001).
5. Tech Support Contacts¶
For smooth communication during technical issues.
- Internal IT Admin: Name, Phone, Email.
- Network/Server Admin: Name, Phone, Email (if external).
- Accounting System Vendor: Contact for the company managing Pohoda/Abra.
- Web/E-shop Vendor: Contact for e-shop developers (for API integrations).