ReportLog
Documentation menu

Logbooks

Building the questionnaire people file reports to, launching it, and what may change afterwards.

A logbook is a questionnaire whose answers are sealed. Every report filed to it is permanent, chained to the one before it in the same logbook, and checkable by anybody. A site with no open logbook accepts no reports at all.

Logbooks are managed under Logbooks and lists › Logbooks, by administrators and the owner.

Making one#

Make a logbook from nothing, from one of the starting points the software ships, or from a logbook file downloaded from another site. Whichever you choose, it arrives as a draft, which you can change freely and nobody can file to.

It asks for two things:

The starting points that ship:

Logbooks:

Lists:

A description is optional and stays editable after launch, as does the title.

Questions#

Add questions one at a time. Each has a kind (short text, a choice, a date, a location on a map, a file, and others), a label, optional help, and three settings:

Each question is its own card. One card asks one question, and nothing moves on by itself.

Three things people get wrong:

Whether reporters are asked for an email address#

This is decided by the questions, not by a switch:

On a form of choices only, Ask for an email address anyway turns the address back on, for when you still want to be able to reach reporters.

Publishing as a condition of filing#

By default reporters are asked whether their report may be published, and a report whose reporter says no, or does not answer, is never published.

Publishing is a condition of filing turns the question into a statement: the last card tells reporters that filing here means the report may be published, once a moderator approves it. It is meant for a logbook that exists to be public and asks for nothing personal. Each report records which of the two it was filed under, so the switch can change after launch without touching reports already filed.

Launching: the one-way door#

Before you launch, read the form through as a reporter would. A draft cannot be filed to, and a report filed to a launched logbook can never be deleted: a test report stays in its chain for good. The safest place to practise is a test site. Download the logbook as a file, upload it there, launch it and file as often as you like.

Launching cannot be undone. It opens the logbook to reporters, offers it on the front page, and fixes its questions. Afterwards a logbook may:

Nothing else. No removing a question, no reordering, no changing a kind or a code, no changing a condition, and no making an optional question required. Options without codes cannot be reworded either. The database itself refuses these changes, not just the website.

Why it is this strict. Every report seals the version of the questions its reporter was actually asked. If a launched form could change, one logbook would hold reports that cannot be read against one definition. Adding an optional question is safe only because a question nobody answered leaves no trace in a report at all.

A launched logbook can never be deleted. A draft can.

Opening, closing and pausing#

To stop reports on the whole site at once, see Doors and intake.

Without the site password#

While the site has a password, each launched logbook says who can file to it without knowing it:

SettingWho can file
NobodyOnly people who know the site password
Anybody who has its addressAnybody with the address of its form. Nothing else opens to them.
Anybody, and the password page offers itAs above, and the password page also offers this logbook as a way in

It opens the form and nothing else: the board, the other logbooks and the rest of the site stay behind the password.

Logbook files and chain files#

Front page buttons#

Every open logbook appears on the front page as a button wearing its own title. Under Logbooks and lists › Front page, administrators reorder the buttons, relabel them or hide them. The first button is drawn in the accent colour. See Front page, wording and look.

See this page's source