FileMaker → wiki import contract

1. Delivery package

Each delivery is one directory:

mpg-import-v0.2/
├── classification.csv
├── images.csv
├── manifest.csv
└── images/
    └── <relative paths named by images.csv FilePath>

manifest.csv is for transfer verification, not wiki ingestion. It contains FilePath,Bytes,SHA256 for every delivered image.

The pilot directory is named mpg-import-v0.2-pilot. It also includes report.json, report.md, selection.json and provenance.json for review and verification; only the classification and image CSVs are importer inputs.

The image directory contains the canonical images selected for this delivery. Site graphics, thumbnail copies and obsolete size variants are excluded. The pilot contains four published images; it is not the full image migration.

2. CSV rules

• UTF-8 without a BOM; comma-separated; RFC 4180 quoting and doubled embedded double quotes; one header row using the exact names below.
• Record IDs and numbering-system values are strings. Do not coerce Hodges or phylogenetic numbers to floating point or remove meaningful zero padding.
• Empty/unknown values are empty strings. Never emit the text NULL, null, N/A, or a FileMaker ? error marker.
• Boolean fields use 1 and 0. BinomialChange uses Yes and No because that is what the current wiki template tests.
• A full delivery is an idempotent upsert snapshot. An absent row does not mean delete. Deletes require a future explicit action file.
• The adapter must emit the same bytes for the same source state. Validation failure stops packaging and produces a rejection report; it never silently drops a bad row.

3. classification.csv

One row per FileMaker MPG New_Taxa record that belongs in the wiki taxonomy. The file deliberately flattens the fields that currently feed both Cargo Classification and the species-content portion of the entity page. Bryan called this the “Classification table” delivery; it is an importer shape, not a claim that every column lives in Cargo Classification.

Source field names may change in FileMaker; the delivered column names and meanings above remain stable. Prince Street handles source-field mapping changes.

Rich text

Notes, TaxonomicNotes, Distribution, Description, Genitalia, and each ReferenceList entry are deterministically sanitized at the adapter boundary, then delivered as wikitext-safe text that can be placed in a template parameter unchanged. The source allowlist is:

• elements: a, b, strong, i, em, br, p, ul, ol, li;
• attributes: href and title on a only;
• URL schemes: https, http, and mailto.

Before allowlist validation, the adapter performs three narrow deterministic normalizations: remove target attributes, unwrap font and span elements while preserving their contents, and substitute ♂ / ♀ with ♂ / ♀. Scripts, styles, event handlers, images, iframes, and every other unknown element or attribute are rejected. Plain FileMaker paragraph breaks become <br>. There is no LLM cleanup step.

MediaWiki does not render <a> in wikitext, so the delivered text contains no <a> elements (version 0.1 delivered them, and they displayed literally on the page). Instead:

• Each link is a wikitext external link, [url text]. Formatting inside the link text is kept, and a ] in the link text is written ]. A link with empty text shows its URL. A link with an empty href keeps only its text.
• In URLs, space, ", <, >, [, ], {, } and | are percent-encoded, and & is written & (MediaWiki decodes it). A relative href resolves against the legacy site, https://mothphotographersgroup.msstate.edu/; almost all of them point at its Books pages. A title attribute is dropped.
• Plain-text sequences that wikitext would read as markup become character references that render identically: | as |, the first character of [[, ]], {{, }} and of an apostrophe run, and the first of three tildes.
• A link nested inside a link is a source defect and rejects.

The remaining elements (b, strong, i, em, br, p, ul, ol, li) are in MediaWiki's HTML whitelist and are delivered as tags. The validator rejects any delivered value that is not unchanged by both sanitizing and the wikitext step, so a raw <a> or an unescaped | cannot reach the importer.

4. images.csv

One row per canonical image to upload or backfill. FilePath points into the delivery's images/ directory. The extra columns beyond Bryan's list are fields already required by the live Image Upload template; Prince Street supplies them so the delivery can populate visible, usable pages in one pass.

The adapter assembles image rows from the relevant FileMaker/image sources rather than assuming MPG Images to Add is a complete store of record. Known sources include MPG Images to Add, MPG Genitalia, MPG Larvae, the legacy webdb image-bearing tables, and the archive paths they reference.

5. Validation and acceptance

Before a package can be delivered:

1. CSVs parse under the declared UTF-8/RFC 4180 rules and have exactly one header row with no duplicate columns.
2. classification.ID values are unique; every non-empty Parent and SynonymOf ID exists in the same delivery.
3. The parent graph has one root, no cycles, and no orphaned rows. A source row with no resolvable parent is rejected and reported; the adapter never invents or substitutes a parent.
4. Every image has an existing file whose byte count and SHA-256 match manifest.csv; image basenames are unique after MediaWiki normalization.
5. Every image has at least one numbering-system join that resolves to a classification row; conflicting Hodges/P-number joins are rejected.
6. Enums, booleans, coordinates, years, rich text, and the ;;; reference delimiter conform to this contract.
7. The report includes source/output row counts, warnings, rejected rows, and duplicate/orphan counts. A non-zero rejection count blocks the delivery.

The first acceptance run is a small, representative pilot: one higher taxon, one ordinary species, one synonym, one P-number revision, one primary collection image, one live image, one larva, one genitalia image, and one record containing rich text and multiple references. After the pilot imports idempotently twice, run the full snapshot and reconcile counts.