Bulk import

Bulk import is how you get a lot of data in at once — people, events, or a whole week’s schedule from another system. The wizards are built to let you change your mind: nothing is written until the final step.

There are two. The ordinary one takes flat CSV files. The other reads weekly schedules exported from Theatron.

Import needs a full screen

The wizards are not available on mobile. Column matching and per-row review need room, so sit down at a desktop before you start.

The six steps

The CSV importer runs through Upload, Column matcher, FK matcher, Validate & preview, Conflict resolution and Commit & progress.

First you upload the file. Then you connect the columns in your CSV to runorder’s own fields — the wizard suggests the ones it recognises. The third step matches the values in your file against things that already exist here: productions, rooms, event types. If a value has no match, you can create it from there.

The fourth step is a dry run. You get row counts and per-row errors without anything being saved. This is where you find out the date format was wrong, rather than afterwards.

When rows collide with data you already have

A conflict is a row that matches something that already exists. Conflicts are evaluated on the server when you commit, and you choose in advance how they should be handled:

• Decide per row — each conflict is reviewed individually, while rows without conflicts commit normally.
• Skip conflicts — the conflicting rows are skipped and everything else commits. Nothing existing changes.
• Discard the whole import — nothing commits. Use this when a conflict means the source data is wrong.

The final step queues the job and shows its progress as it runs. Large imports run in the background, so you can follow along without holding the page open.

Weekly schedules from Theatron

Import schedule accepts the weekly plan as Theatron exports it — a grid with rooms as columns and days as rows, in RTF.

The steps follow the same shape, but the mapping is different: you confirm which year the plan covers, match each production title to a production here (or fold one-offs into a single one), attach each Theatron column to a room, and each parenthetical to an event type. The preview shows counts, date warnings and a sample of the events before you commit.

Templates

Templates holds example files with the right column headers and sample rows. Start there if you are building the file yourself — it is faster than guessing at column names and having them rejected at step two.

The wizards are in English

The import surfaces are not translated yet. The buttons and step names appear in English whatever language you otherwise use runorder in.