Data Landing Zone
The Data Landing Zone is a bulk upload area for workbook files. Drop one or many files at once; Octigen matches each file to the collections you have configured and ingests the data automatically.
Use it when you receive a regular batch of reports (for example monthly fund workbooks) and want to populate several collections without uploading to each collection separately.
How matching works
Each data collection can define an input filename pattern (wildcard), for example:
| Pattern | Matches |
|---|---|
Q*.xlsx | Q1-2026.xlsx, Q4-2025.xlsx |
Growth of 10k*.xlsx | Growth of 10k.xlsx |
PerfAll.xls | That exact filename |
If the collection also pins a sheet name or index, the landing zone matches that sheet inside the workbook. One physical file can therefore fill multiple collections when each collection targets a different sheet (common for multi-sheet quarterly workbooks).
Matching uses the same rules as manual upload: parameters are extracted from filenames or row values according to each collection’s parameter mappings.
Upload flow
- Open Data → Data Landing Zone.
- Drag files onto the upload area, or click to browse.
- Wait for the per-file report.
For each file you see:
| Status | Meaning |
|---|---|
| Matched | File matched one or more collections; data was ingested |
| Reimported | Same parameters as an existing object; data was replaced |
| Ambiguous | Multiple collections could match; none ingested automatically |
| Unmatched | No collection’s pattern fit this file |
| Failed | Parse or upload error (details in the report) |
Expand a successful match to preview ingested data or open the target collection.
Configuring collections for landing zone
For reliable automatic matching, set on each collection:
- Filename pattern - Wildcard that identifies files for this collection
- Sheet - When the data is not on the first sheet
- Skipped header / footer rows and columns - When titles or footnotes sit above or beside the real table (see Data Collections)
- Parameters - So ingested objects get the right keys (
valuation_date,portfolio_id, row-based filters, etc.)
Collections without a filename pattern never match in the landing zone - they still work for manual upload on the collection page.
Ambiguous matches
Ambiguity happens when two or more collections share a pattern that fits the same file (and sheet). Resolve by tightening patterns, pinning distinct sheets, or using more specific filenames.
Upload the file manually on the collection page if you need a one-off override.
Reimport and duplicates
When a new file resolves to the same parameter values as an existing object, the landing zone reimports (replaces) that object. This is the intended way to refresh monthly data without deleting objects first.
Best practices
- One pattern per logical feed - Each collection should match a predictable file or sheet.
- Test with one file - Upload a single workbook first; fix ambiguous or unmatched results before dropping the full batch.
- Keep filenames stable - Changing naming conventions breaks pattern matching until you update the collection.
- Use skip settings - Files with title rows or side margins parse correctly only when skip rows/columns are set on the collection.
Next steps
- Data Collections - Patterns, parameters, and parsing options
- Transformations - Shape matched data for slides
- Data Overview - How data flows into presentations