This guide is aimed at ensuring users prepare clean, functional datasets that will work flawlessly in the upload and tagging system. It includes guidance on structure, headers, field types, and common issues to avoid. #
Overview #
Uploading a clean, well-structured dataset is critical to unlocking Vloggi’s smart tagging and auto-completion features. This guide explains how to structure your CSV file to ensure smooth contributor lookup, data tagging, and metadata overlays.
Basic Requirements #
- Use a .csv (comma-separated values) file format
- Include one row per contributor
- Keep your file under six columns where possible
- Ensure you have a unique identifier (e.g. email, ID) in every row
- Always include a header row with clear, simple column names
Structure Example #
| ID | Name | School | State | |
|---|---|---|---|---|
| 12345 | Mia Harrison | [email protected] | Riverdale High | Texas |
| 67890 | Jack Collins | [email protected] | Skyline College | California |
| 54321 | Emily Carier | [email protected] | Lakeside Academy | Oklahoma |
Field Guidelines #
1. Unique Identifier (Key Column) #
Choose one column (e.g. Email or ID) that contains only unique values—no duplicates, no blanks. This is used to match a contributor to their record.
⚠️ Vloggi will reject your dataset if the key column has duplicates or empty rows.
2. Header Row #
Always include a header row. Use short, meaningful names (e.g. State, School, Program ID). These names will appear in dropdowns and the tag builder.
Avoid:
- Special characters (e.g. “&”, “/”, “@”)
- Long descriptions (e.g. “What state are you located in?”)
What to Avoid #
| Issue | Why it matters |
|---|---|
| Duplicate rows or duplicate values in key column | Causes lookup errors and incorrect tagging |
| Empty cells in required fields | Makes lookup unreliable or blocks matching |
| Unnecessary columns (e.g. timestamps, internal notes) | Clutters the UI and slows down search |
| Extra header rows or formatting rows | Breaks the import process |
| Using “one column per contributor” format | Not supported – Vloggi expects one row per contributor |
What to Keep #
- Include only useful fields for display, tagging, or matching (e.g. Name, School, Location)
- Retain a clear, consistent structure throughout
- If using for tagging, keep responses short: “Retail” not “Retail sales division, Eastern zone”
Optional Enhancements #
- Pre-tag your data columns: columns like State, Tier, or Department can be automatically converted into tags using the tag icon on the dataset preview screen
- Leave out private or irrelevant columns that aren’t used in the contributor experience
Test Before Use #
After uploading your CSV, preview it in the Create Dataset step. Vloggi will show you:
- Suggested key columns
- Data preview
- Warnings about duplicates or formatting errors
- Option to apply tags to specific columns
