Archiving Conference Websites: The IASSIST 2017 Case

Conference websites are often treated as temporary services. They open a registration form, guide delegates through several days of sessions, and then disappear when the event closes. Yet a well-preserved site can become a valuable research object, especially when it records the people, ideas, practical arrangements and technical vocabulary of a particular professional community.

IASSIST 2017 offers a useful case study. The conference, “Data in the Middle: The Common Language of Research,” was held at the University of Kansas in Lawrence from 23 to 26 May 2017. Its archived website retains the programme, schedule, plenary information, presentations and visitor guidance, creating a durable record of conversations about research data and emerging technologies.

The site is significant because it links broad themes with the everyday mechanics of attendance. Information about check-in, transport and local recommendations sits alongside material on big data, deep learning, digital agriculture and global food security. That combination gives the archive value beyond a simple list of papers: it shows how a research community presented itself and organised participation at a particular moment.

For Australian universities, libraries and professional associations, this example illustrates why event preservation should begin before a conference opens. A stable archive needs more than a final PDF. It requires a plan for URLs, files, metadata, accessibility, copyright, privacy and the preservation of a site’s original relationships between pages.

Archival element	Value in the IASSIST 2017 record	Preservation priority
Programme and schedule	Establishes the event’s structure, timing and themes	Very high
Plenary session information	Identifies major arguments, speakers and institutional context	Very high
Presentation files	Preserves specialist knowledge that may not appear elsewhere	Very high
Practical attendee information	Records transport, check-in and the lived experience of the event	High
Local recommendations	Adds geographic and social context to the conference record	Medium
Navigation and page links	Shows how organisers framed relationships between topics	High

Why Conference Websites Deserve Long-Term Care

A conference website is an administrative tool while an event is running, but it becomes documentary evidence afterwards. It can show which questions were considered urgent, which organisations were visible, and how a field described its own priorities. The programme may reveal a transition from established methods to experimental ones, while speaker biographies can map professional networks that are difficult to reconstruct later.

The IASSIST 2017 archive is especially informative because its theme connected data practice with the idea of a common language for research. The surviving pages place data-intensive subjects in relation to one another rather than presenting them as isolated technical trends. Big data, deep learning, digital agriculture and global food security appear as parts of a wider conversation about how research data is collected, interpreted and shared.

Preservation also protects material that may not be formally published. A presentation title, abstract, workshop description or link to a dataset can provide the only surviving trace of a project in development. Researchers conducting historical reviews, bibliometric studies or institutional histories may find such details useful even when the original conference papers are unavailable.

For an Australian audience, this matters across universities, government agencies and learned societies. A symposium held in Sydney, Canberra or Perth may produce valuable web content that is quickly replaced by the next event. If the event concerns drought modelling, Indigenous data governance or public health, the archived website may later help explain how those issues were framed at a particular stage of policy and research.

What The IASSIST Archive Preserves

The archived IASSIST 2017 website retains several layers of information. The conference schedule gives a chronological structure, while plenary pages identify the central speakers and themes. Presentation material extends the record into the specialist content of the sessions, and practical pages document how visitors were expected to move through the event.

That mixture is important. A programme alone can tell us what happened, but not always how the organisers wanted people to experience it. Transport instructions, check-in details and local recommendations place the conference in Lawrence rather than in an abstract digital space. They preserve the relationship between an international professional gathering and its host city.

The archive also retains evidence of web-era conventions. Pages may have been designed for desktop browsing, with navigation that assumes a visitor will move through a sequence of linked sections. Some files may use older formats, embedded media or links to external services that no longer operate. These imperfections are part of the historical record, although they also create technical work for archivists.

An Australian institution preserving an event should capture both content and context. A page about a workshop should remain connected to its date, presenters, stream and downloadable materials. A search result or isolated PDF is less useful than a functioning collection in which a user can understand why each item belonged to the conference.

Capturing The Site Before It Disappears

Effective web archiving begins with a scope statement. Organisers should identify the main domain, subdomains, registration system, speaker pages, social media references, downloadable documents and externally hosted content. They should also record the event dates and establish which pages are official, provisional or supplied by partners.

A basic capture should include HTML pages, images, stylesheets, scripts and documents. The aim is to preserve the visible site and the resources required to interpret it. Automated crawlers can miss content hidden behind forms, calendars or JavaScript interfaces, so manual checking is needed. Archivists should browse the site as a delegate would, following menus and testing links from the home page through to session-level material.

File naming and metadata should be handled at the point of capture. Useful fields include title, creator, session, date, file format, rights statement, original URL and capture date. A checksum can help verify that a file has not changed during transfer or storage. Where an archive includes multiple versions of a programme, each version should be retained and labelled rather than silently overwritten.

The Australian local environment adds practical considerations. Universities commonly use content management systems that are upgraded on fixed procurement cycles, and older event sites can be lost during a platform migration. A conference hosted in Melbourne may depend on a temporary subdomain, while an event in Brisbane may use a separate registration vendor. Capturing those dependencies early is safer than assuming a central IT backup will preserve them.

Managing Copyright, Privacy And Access

Conference archives contain material from many rights holders. Organisers may own the website design and administrative text, but speakers often retain copyright in slides, photographs, recordings and papers. A preservation agreement should state what can be copied, displayed, migrated and made available for research. Permission for conference presentation does not automatically equal permission for indefinite online distribution.

Privacy requires similar care. Registration pages may contain names, email addresses, dietary requirements or accessibility information that should never enter a public archive. Photographs can identify delegates, and speaker biographies may contain personal contact details that were once published for immediate event use. A preservation workflow should separate public programme information from restricted administrative data.

Australian institutions must consider the Privacy Act 1988 and the Australian Privacy Principles when handling personal information. Public universities may also have records obligations under state or territory legislation, while copyright decisions may involve the Copyright Act 1968. These frameworks do not produce a single automatic answer for every archive, so responsibility should be assigned to records, library, legal and information-governance staff.

Access can be graduated. Public pages may be openly available, presentation files may carry a rights note, and sensitive material may be restricted to authenticated users or retained offline. A clear takedown process is also useful. It allows a rights holder to raise a concern without undermining the stability of the whole collection.

Making An Archive Usable For Researchers

Preservation is successful only when people can find and understand what has been kept. A search interface should index session titles, presenters, abstracts, keywords and file names where possible. Structured metadata makes it easier to identify all presentations from a stream or compare themes across years.

Accessibility is part of discoverability. Scanned programmes need optical character recognition and, ideally, a human check. PDFs should have meaningful titles, reading order and searchable text. Image-only slides may require a description of their contents. Colour contrast, keyboard navigation and alternative text help users approach the archive with different technologies and levels of access.

A durable archive should also document its own limits. If a recording is missing, an external link has failed or a presentation was withheld, that absence should be noted. A short archival statement can explain the capture date, known gaps, file migration and access restrictions. This is more trustworthy than presenting an incomplete collection as if it were whole.

Researchers often need to carry event knowledge into institutional work. Guidance on sharing conference learnings can complement the archive by helping staff turn sessions into internal briefings, reading lists or project discussions. The archive then serves both historical inquiry and practical knowledge transfer.

Learning From The Event’s Local Context

The IASSIST pages show why local information should be preserved rather than dismissed as temporary administration. Directions, check-in procedures and recommendations can reveal assumptions about transport, accommodation and the social life surrounding a conference. They also help future users understand what attendance involved for delegates arriving from other countries.

Australian event archives should capture this context carefully. A conference in Canberra might include guidance about the airport bus, parliamentary precinct access and walking distances between venues. In Sydney, instructions may need to distinguish Opal transport, light rail and ferry routes. In Melbourne, a programme may refer to the Myki system, while a Perth event could involve longer transfers between the airport, hotels and a university campus.

Local recommendations also reflect the market in which an event occurred. Cafés, bookstores and restaurants change quickly, especially in inner-city areas where rents and redevelopment reshape the streetscape. Keeping the original recommendations, with a date and an archival note, can preserve a snapshot of local life without presenting outdated information as current advice.

Everyday Australian habits can matter as well. Delegates may expect coffee before a morning session, accessible tap water, contactless payment and clear information about public transport disruptions. Conferences held during school holidays, summer heat or major sporting events can face different accommodation and travel conditions. Recording these details helps future researchers see the event as a lived gathering rather than just a set of intellectual outputs.

Building A Sustainable Preservation Workflow

The best approach treats archiving as part of event production. At the planning stage, organisers can assign a persistent domain, agree on file formats, include rights language in speaker contracts and nominate a records owner. During the event, staff can monitor links, collect final presentation files and record changes to the schedule.

After the event, a preservation copy should be created before the website is redesigned. The live site can then be reduced to a landing page that points to the archive, while the archived version retains its original structure where technically possible. Persistent identifiers, such as a DOI or a stable institutional URL, make citations more reliable.

Storage should follow the principles of redundancy, integrity checking and managed migration. At least one copy should be held separately from the production web server, with regular fixity checks and documented restoration procedures. Open or widely supported formats are preferable for long-term access, although original files should be retained when they carry evidential value.

The IASSIST 2017 record demonstrates the return on this investment. Its pages preserve a moment when research data, machine learning and global food systems were being discussed through a shared professional forum. By protecting both the scholarly content and the practical details of participation, conference archiving turns a short-lived website into a durable resource for researchers, institutions and future event organisers.