Publishes the accepted abstracts as a searchable, branded collection — the online abstract book that is never out of date, with optional delegate Q&A.
What it is
A designed public page listing exactly the abstracts whose acceptance has been communicated — never a staged decision the submitter has not seen. Each entry carries its authors, its sections, optional keywords and disclosures, and a stable display number. Where an abstract became a scheduled talk, a poster or an on-demand paper, its entry links to that destination, and the destination links back.
Presentation is template-driven: your organization keeps a library of viewer templates, an event publishes one instance from a template with per-event overrides, and templates can also be scoped to a single event. The same template machinery drives all three viewers.
What it changes
The abstract book stops being a frozen PDF. A late withdrawal disappears from the published collection the moment it is withdrawn, and the delegate searching on a phone gets the same answer as the committee's own records.
The online abstract book
Publish every communicated acceptance, searchable and filterable by track and type, numbered for citation.
The members-only collection
Keep access at attendees-only — the default — so the collection is a benefit of registration.
Ask the author
Switch on Q&A and delegates put questions to authors from the app; authors answer from their phone or the portal.
What you can do
- Build viewer templates in the organization library — branding, layout, header and footer — and publish one per event with overrides.
- Scope a template to one event, and promote it to the organization library when it earns reuse.
- Show or hide keywords, disclosures and individual abstract sections across the whole collection.
- Open and close the collection on its own window, independent of the call and of the event dates.
- Let delegates bookmark abstracts, and follow the entry through to the session, poster or paper it became.
- Switch on ask-the-author Q&A, with answers from the portal or the app and a moderation-by-author model.
Settings
| Setting | What it controls | Default |
|---|---|---|
| Viewer access | Public to anyone with the link, or restricted to signed-in event attendees. | Attendees only |
| Viewer open / close | When the collection is up. Blank at both ends means whenever the instance is live. | Always open |
| Show keywords | Keywords on entries and in search. | On |
| Show disclosures | Author disclosure statements on the detail page. | Off |
| Highlight presenting author | Marks the presenting author in the author list. | On |
| Hidden sections | Abstract sections excluded from the published entries — a hide-list over the call's own section structure. | None hidden |
| Search / filter by track / filter by type | The three discovery controls on the collection page, individually. | All on |
| Attendee Q&A | Delegates may ask authors questions from the app. | Off |
The Abstract Viewer defaults to attendees only; the Poster and Paper Viewers default to public. That is deliberate — abstracts are the collection most often kept as a registration benefit — but if you expect uniformity, set all three explicitly.
Call for Abstracts — the viewer publishes its output and cannot be enabled without it. A published instance must also be set live; a template alone shows nothing.
Only communicated acceptances ever appear — there is no way to publish a staged decision, by design. Rejected and pending abstracts are invisible to the point of returning not-found. Q&A follows the one-thread-per-work rule: an abstract that became a poster sends questions to the poster's thread instead of carrying its own.