Eve library

World Anvil import — field coverage (P16.7)

Guide

Revision 1

On this page

The import is best-effort by declaration: the table below (mirrored at runtime from WORLD_ANVIL_FIELD_MAP in src/lib/world-anvil-import.ts, which the Interop panel renders) is the entire mapping contract. Any field on an imported article that is not listed here is returned in unmappedFields, shown in the preview before import, and stored on the captured idea's payload.worldAnvil.unmappedFields — never silently dropped.

World Anvil field Maps to Notes
title idea.title Truncated to 300 chars with a warning; missing titles import as "Untitled World Anvil article" with a warning.
content_parsed idea.body Preferred over content when both exist (already rendered HTML). Stripped to text; original HTML kept in payload.worldAnvil.contentHtml.
content idea.body Used when content_parsed is absent. Same strip-and-keep treatment.
excerpt idea.body Fallback when no content field exists.
template idea.tags Becomes a wa:<template> tag (e.g. wa:location).
templateType idea.tags Same as template; whichever is present.
tags idea.tags Accepts an array or a comma-separated string; total tag list capped at 20 with a warning.
id payload.worldAnvil.id Provenance only.
url payload.worldAnvil.url Provenance only.
slug payload.worldAnvil.slug Provenance only.
world payload.worldAnvil.world The World Anvil world reference is recorded but not auto-bound to a hathor world — binding canon is a deliberate act, not an import side-effect.

Everything else (cssClasses, fullRender, isDraft, section containers, relation maps, secrets, subscriber groups, …) is unmapped and listed. Lossy steps warn: title/body truncation and tag capping each produce a warning in the preview.

Every import lands through the standard capture route, so content safety screening (P10.1) applies to imported articles exactly as it does to typed captures, and every imported idea carries the world-anvil-import tag.