Curating Conference Presentations: Building Workflows That Last

Conference proceedings have shifted dramatically over the past decade. Slides, posters, recordings, datasets and supplementary materials now form a rich digital record that demands thoughtful handling. Curating these artefacts well ensures that the effort speakers invest on stage continues to pay dividends long after the applause fades.

Researchers across Australia are increasingly aware that a presentation is rarely the final output. A talk on reef resilience delivered in Cairns might seed a collaboration with a lab in Hobart, while a workshop on bushfire modelling in Melbourne could shape policy briefs in Canberra. Treating slides and supporting data as citable, preservable outputs rather than ephemeral handouts reflects a broader cultural shift within the nation's research institutions.

The push for better data stewardship has been reinforced by local infrastructure. The Australian Research Data Commons, along with its predecessors at the Australian National Data Service, has championed the FAIR principles across the higher education sector. Universities from Perth to Brisbane now maintain data management plans that explicitly address conference outputs, and many require deposit of presentations into institutional repositories as a condition of funding compliance.

Yet the practical reality remains uneven. A researcher might prepare a polished dataset for a symposium at the University of Sydney, only to lose track of it once the event ends. Emails disappear, hard drives fail, and collaborative platforms change their terms. Establishing a repeatable workflow before the conference begins is the most reliable defence against this entropy.

Mapping the Lifecycle of Conference Materials

Every curation effort starts with a clear inventory. Before travelling to a venue, the presenter should catalogue what will be produced: the slide deck itself, any datasets referenced, code notebooks, video recordings, posters, photographs, and supplementary readings. A simple spreadsheet listing each item, its format, size and intended audience creates a baseline that survives the rush of the event itself.

Pre-conference planning also involves deciding what should be shared openly and what must remain restricted. In Australia, ethics committees routinely require that participant information from qualitative studies be anonymised before deposit. Cultural sensitivity considerations apply to research involving First Nations communities, where the CARE principles complement FAIR by asserting collective benefit and authority over data.

Preparing Before You Travel

A structured pre-conference routine reduces stress and prevents lost materials. Useful steps include:

• Exporting slides to PDF/A in addition to the original format
• Saving a copy of the dataset to an encrypted external drive
• Photographing posters at high resolution after printing
• Recording a backup audio track during the presentation
• Noting citation details for any third-party images used
• Scheduling a triage appointment within four weeks of return

During the conference, real-time capture is essential. Recording audio with a separate device, photographing posters, and saving slides to a cloud service the moment the session ends protects against accidental loss. Many Australian institutions now subscribe to university-wide licences for tools like Echo360 or Panopto, which integrate directly with learning management systems and simplify later deposit.

The post-event phase is where most workflows falter. The excitement of networking and travel dissipates, and the raw materials sit in a folder labelled "conference stuff". Assigning a deadline, ideally within four weeks of returning home, to triage and finalise each item keeps the momentum alive.

Metadata Standards and Documentation Practices

Metadata is the connective tissue that makes a conference presentation discoverable decades from now. Dublin Core remains a workhorse for simple catalogue records, while DataCite supports the creation of DOIs for citable datasets. Australian repositories frequently layer local schemas on top of these international standards, reflecting disciplinary conventions unique to fields like marine science or astronomy.

Documentation should extend beyond bibliographic fields. A readme file placed alongside the dataset explains column headings, units of measurement, and the relationship between files. For a presentation on Murray-Darling Basin water quality, the readme would clarify sampling dates, laboratory methods and the coordinate system used. Future users, including the original speaker, will thank the past self who recorded these details.

Versioning deserves explicit attention. Slides evolve rapidly in the final days before a conference, and minor edits are easy to lose. Saving each iteration with a date stamp or using a version control system like Git even for binary files helps reconstruct the journey. Some Australian research groups adopt naming conventions that include the conference acronym, date and version number, creating a self-documenting trail.

For complex multimedia outputs, structural metadata becomes crucial. A recorded keynote needs a transcript, a list of timestamps for key arguments, and a description of any embedded media. Without these layers, a video file becomes an opaque blob that search engines cannot index and human reviewers cannot navigate efficiently.

Storage, Backup and Repository Selection

Choosing where to deposit conference materials involves balancing visibility, control and longevity. Institutional repositories, such as those maintained by the University of Melbourne or the University of Queensland, offer familiarity and alignment with local data management policies. Subject repositories like Zenodo or Dryad provide broader exposure and built-in DOI minting. The right choice depends on the nature of the materials and the community that should find them.

A reliable storage strategy follows the 3-2-1 rule: three copies, on two different media, with one offsite. In the Australian context, this often means keeping a working copy on a university-managed drive, a second on an external hard drive stored in a different location, and a third in a cloud service with servers outside the country. Cloud providers with Australian data centres, such as those offering Sydney or Melbourne regions, address concerns about data sovereignty while providing geographic redundancy.

Backup routines need to be tested, not just assumed. A quarterly check that confirms files can be restored from the offsite location prevents nasty surprises. Several Australian research offices have introduced "data health check" weeks where staff verify the integrity of recent deposits, catching corruption or misfiling before it spreads.

Repository Type	Strengths	Limitations	Best Suited For
Institutional repository	Aligned with local policy, supported by library staff, integrated with CRIS systems	Limited discoverability outside the institution, variable curation depth	University-affiliated outputs, internal reporting
Subject repository (e.g. Zenodo, Dryad)	Broad exposure, built-in DOI minting, community curation	Less institutional control, metadata may not match local schema	Cross-institutional collaborations, open science outputs
National infrastructure (e.g. ANDS, ARDC-affiliated services)	Compliance with national standards, long-term funding assurance	Narrower thematic scope, sometimes restricted to funded projects	Large-scale funded research, government partnerships
Personal or project website	Full control, rapid updates	No preservation guarantee, dependent on individual maintenance	Interim sharing, informal dissemination

Selecting among these options is rarely an either-or decision. A dataset might live in a subject repository for citation purposes while a descriptive record points back to an institutional collection. Layered approaches reflect the reality that conference outputs serve multiple audiences with different needs.

Sharing, Licensing and Reuse Considerations

Licensing decisions made on the day of deposit shape the future reach of the work. Creative Commons Attribution licences have become the de facto standard across Australian academia, allowing reuse with credit while preserving authorial recognition. More restrictive options like CC BY-NC-ND serve cases where commercial sensitivity or publisher embargoes apply, though they can limit downstream synthesis.

A practical guide to reuse outlines how depositors can anticipate common questions from future users. Clear licence statements reduce the volume of permission requests and foster a culture of respectful reuse. For datasets, machine-readable licences embedded in the metadata enable automated compliance checking by aggregators.

Sensitive data requires additional safeguards. Health research, Indigenous data and location information about endangered species all carry obligations under Australian law and ethical guidelines. De-identification, aggregation, and controlled access mechanisms provide workable alternatives to outright restriction, balancing openness with responsibility.

Speakers should also consider the social context of sharing. A dataset collected through community partnership in regional Western Australia might be best deposited alongside contextual narratives that honour the contributions of participants. This relational approach, increasingly emphasised by Indigenous data sovereignty advocates, treats data as a living exchange rather than a one-way transfer.

Post-Event Preservation and Long-Term Access

Preservation extends beyond the moment of deposit. File formats migrate, software becomes obsolete, and the institutions that host repositories can change. The international preservation community recommends formats like PDF/A for documents, CSV for tabular data, and TIFF for images, all chosen for their longevity and platform independence. Avoiding proprietary formats where possible shields the work from format rot.

Persistent identifiers anchor the record across these changes. A DOI minted at the time of deposit ensures that links remain valid even if the underlying URL shifts. Australian researchers can obtain DOIs through institutional agreements with DataCite, often at no cost, and the resulting citation counts feed directly into the new Engagement and Impact assessment.

Sustainability planning is the final, often overlooked, component. Who will maintain the metadata? What happens if the lead investigator retires? Embedding curation responsibilities within a team, documenting handover procedures, and aligning with institutional commitments all contribute to resilience. Many Australian universities now require that data management plans name a steward separate from the principal investigator, distributing risk and ensuring continuity.

Habits That Extend the Life of Your Record

Long-term access depends on choices made early and reinforced through practice. Consider adopting the following:

• Store master files in preservation-grade formats such as PDF/A, CSV or TIFF
• Assign a DOI at the time of deposit rather than waiting for demand
• Document software dependencies, including version numbers and licences
• Review metadata annually to catch broken links or superseded identifiers
• Negotiate handover arrangements with a colleague before sabbaticals or retirement
• Align retention periods with the expectations of major Australian funders

The journey from a live presentation in Adelaide to a citable, preserved record available globally requires intention, infrastructure and iterative refinement. Researchers who invest the effort discover that their work reaches wider audiences and attracts new collaborators. For those beginning to formalise their approach, workflow design resources offer templates and case studies that illustrate how curation translates into measurable research impact.