What a Conference Owes
A conference of three hundred people costs its attendees, collectively, a large sum in fees, travel and days away. What typically survives it is a page on a domain awaiting a renewal notice. For an additional workplace-management comparison, see this reference .
That disproportion is the largest inefficiency in this subject, and closing it is cheap. For broader independent context, see ISSN International Centre .
Reviewed August 9, 2026.
The six obligations
One. Publish the programme and abstracts under a permanent identity. The association's domain, not the edition's. The permanent body usually exists and is usually not used.
Two. Give the record one canonical address. Twenty-three URLs for one page is a citation problem as much as a technical one — a record with many addresses has none.
Three. Deposit once, somewhere with a mandate. The host institution's repository, a subject repository, the association's own store. One deposit, one afternoon.
Four. Collect slides as files rather than links, and publish them as a set.
Five. Assign or enable identifiers where the field expects them, or say plainly that none are assigned so nobody assumes otherwise.
Six. Hand over the credentials and a written note of where everything is. The knowledge disperses faster than the files, and the next edition's team cannot maintain what it cannot find.
Why none of it is standard
The organising team is temporary. A per-edition team disbands, and nobody's role includes what happens in year three.
Preservation has no deadline. Everything else about a conference has a hard date; the archive can always be done next month.
It benefits people who did not pay. Future readers are not in the room and did not fund anything.
And the absence is invisible. Nobody complains about a record that does not exist, because they cannot find it to complain about.
What it costs
An afternoon, once per edition, for all six.
Against an event that consumed thousands of hours and a large collective sum, and whose entire durable output currently depends on somebody remembering to pay for a domain.
The ratio is the argument. There is no version of this where the afternoon is not worth spending.
Who should own it
The association, not the edition. A permanent body can hold a policy; a rotating host cannot.
And it should be a condition of hosting. An association that says "the programme and abstracts are deposited with us within thirty days" has solved the problem permanently, for every future edition, in one sentence of a hosting agreement.
What attendees can ask for
Because the pressure has to come from somewhere.
Ask where the proceedings will live, before submitting.
Ask whether slides will be published and where.
Ask for your own recording, which the organiser usually has and rarely offers.
And say it in the feedback form. Organisers read those, "the record vanished" is not a complaint they receive, and one sentence per attendee is what changes a default.
The short version
- Six obligations: a permanent identity, one canonical address, one deposit somewhere with a mandate, slides as files, identifiers or a clear statement of their absence, and a handover note
- None is standard because the team is temporary, preservation has no deadline, it benefits non-payers, and the absence is invisible
- All six cost an afternoon per edition, against an event consuming thousands of hours and a large collective sum
- The association should own it, and a hosting condition solves it permanently in one sentence
- Attendees can ask where proceedings will live, whether slides will be published, and for their own recording
- Say it in the feedback form — "the record vanished" is a complaint organisers never receive