Practitioners

Import a register from a spreadsheet

Upload a CSV or XLSX register, map its columns, and import every row as a typed value.

How-to video coming soon

For: Practitioners
You need: The register as a CSV or XLSX file: one sheet, one row per system, with a header row.
Result: One entry per row, each value typed, and an import receipt.

Steps

On Import a register, drop the CSV or XLSX file, or choose From a GitHub repository to read it from a repository already connected on Files.
Under Map the columns, check where each column goes. Columns set to not mapped are ignored, and each field takes one column. Where a column could mean two things, such as Status, choose.
Read Fields your file does not supply on Import a register. Each is written as not supplied at import, with the date checked.
Choose the import button on Import a register; it names the row count, for example Import 6 rows. An import is written whole or not at all.
Read the Import receipt: what was written, what could not be read, and the first finding of each kind.

The file is not kept. Its hash is kept, and the receipt shows it.
Every imported value is written as typed, with the note “as declared in” the file. A gate state from a file is text, not a gate record: no approver or evidence comes from a file.
In a later import, each changed row becomes a new version with a reason, and a row that matches its entry adds nothing. Nothing is overwritten.
A file that is not CSV or XLSX is refused, and nothing is read or kept. A file over the size limit shown on the import page, or not saved as UTF-8, is read once you split it or save it again.

These open the prototype, on fictional institutions. People are shown as roles.