Contesimal: Import Content - Custom Data Import

Description

The Custom Data Import option enables Contesimal to ingest non-standard or customer-specific data sources (for example, JSON or XML exports, CSV files) and convert them into structured, searchable, AI-ready content in your Content Library.

Because custom data varies by system and schema, this import is assisted by the Contesimal team - you provide the source files (and context), and we help map, validate, and plug the data into the platform correctly.

• Supported inputs (typical): JSON, XML, CSV (other structured formats may be possible on request).
• How it works: You contact us → we review your sample files → confirm mapping/requirements → import and validate → you verify results in the library.
  • Point of contact: Please reach out to Contesimal Support at TBD

Step-by-Step: 

The step-by-step instructions, screen descriptions, and UI details in this section are examples only. They are intended to help you understand how the feature works and how to complete the flow. Screens, labels, and layout may change in future product updates.

A. Prepare your files

• Export your dataset to JSON/XML/CSV.
• If the dataset is large, split it into logical chunks (by date, category, or record count).
• Ensure there’s no sensitive data you’re not authorized to upload.

B. Prepare import context (recommended)

Include a short note with:

• What the data represents (e.g., “knowledge base articles”, “product catalog”, “tickets”)
• Desired output in Contesimal (one record = one article? grouped by parent object?)
• Key fields you want preserved (title, body/content, author, date, tags, source URL, IDs)

C: Contact Contesimal to initiate the import

Send a message to the point of contact with:

• Sample file(s) (or a small extract if the real dataset is large)
• Any schema documentation (if available)
• Your expected outcome (how you want content organized/searchable)

D: Mapping + validation (with Contesimal)

We will:

• Confirm supported structure and required fields
• Define how records map into Contesimal documents/articles
• Flag any issues (missing fields, inconsistent structure, encoding problems)

E: Import execution

Once mapping is approved, we will run the import and confirm:

• Number of records imported
• Any skipped/invalid records
• Where the content appears in the Content Library

F: Verify in Content Library

You verify:

• Records are present and searchable
• Fields are correctly mapped (title/body/metadata)
• Content formatting is acceptable (paragraphs, lists, special characters)

Troubleshooting Guide

A. Custom import option isn’t available / no way to upload JSON/XML yourself

• Issue: You can’t find a self-serve upload flow for JSON/XML/CSV in the UI.
• Fix: Custom imports are assisted. Contact support (or your CSM) and provide sample files + desired mapping.

B: File type not supported

• Issue: You provided a format other than JSON/XML/CSV (or a JSON/XML/CSV variant that can’t be parsed).
• Fix:
• Export as standard JSON/CSV or well-formed XML.
• If your system exports NDJSON/JSONL or a compressed archive, mention it - Contesimal can advise the best export format.

C: Import fails due to schema mismatch or inconsistent structure

• Issue: Some records don’t follow the same shape (missing fields, different nesting), causing mapping or parsing failures.
• Fix:
  • Provide 2–3 representative samples (good + problematic).
  • Normalize the export (consistent keys/types) or split into separate files by record type.

D: Missing required content fields (e.g., no body text)

• Issue: Records import but produce empty/low-value articles (no usable text content).
• Fix:
  • Confirm which field contains the primary text (e.g., content, description, bodyHtml).
  • Provide mapping guidance (“use body as content; use title as title; use tags[] as tags”).

E: Special characters look broken (encoding issues)

• Issue: Quotes, accents, or symbols display incorrectly after import.
• Fix:
  • Ensure the file is saved as UTF-8.
  • Avoid mixed encodings; re-export if needed and re-import.

F: Import completes but content is hard to search or poorly segmented

• Issue: Records are combined incorrectly or split in an unexpected way.
• Fix:
  • Clarify the desired rule: one object = one article vs. grouping by a parent entity.
  • Provide a sample of how you want a single record to look in Contesimal (title, body, metadata).

G: Import is taking longer than expected

• Issue: Large datasets require more time for mapping, ingestion, and validation.
• Fix:
  • Start with a small pilot file to validate mapping first.
  • Import in batches (by date/category) to reduce turnaround time and simplify verification.