Accessing and reusing data from IASSIST 2017 talks
IASSIST 2017 brought researchers and practitioners together at the University of Kansas in Lawrence from 23 to 26 May 2017, under the theme “Data in the Middle: The Common Language of Research.” Its archived programme preserves the structure of that event: sessions, plenaries, speakers and presentation links on big data, deep learning, digital agriculture and global food security. For researchers, this trail offers more than a record of what was discussed; it can reveal datasets, methods and relationships that remain useful years later.
Access and reuse should be treated as separate permissions. Opening a slide deck or downloading a recording lets you inspect it, but it does not automatically grant the right to republish it, train a model on it or include its figures in a commercial report. The archive is therefore best used as a discovery layer: identify the talk, follow every supporting link, inspect the stated licence, and seek permission where the evidence remains incomplete.
Researchers in Australia need an extra layer of practical context. A conference held in Kansas sits in a different time zone from Canberra, Sydney, Melbourne, Brisbane and Adelaide, while Australian privacy, Indigenous data and biosecurity rules can affect how research outputs are shared or transported. A local example may need adaptation for Australian soils, crops, institutions and markets before its findings are applied. The archived event remains global, but responsible reuse must fit the destination setting.
A dependable workflow moves from discovery to documentation, permission, verification and citation. It keeps the original talk context intact, distinguishes published artefacts from incidental references, and records any cleaning or subsetting performed later. That sequence is especially valuable when a 2017 presentation contains links to repositories that have moved, commercial services that have changed, or datasets whose access conditions have evolved.
Mapping the archive before you download
Begin with the conference programme and schedule, then open the relevant session or plenary page. Capture the talk title, presenter names, date, session theme and URL before following a presentation asset. This prevents an orphaned PDF or repository record from being mistaken for the complete research object.
| Access route | What to extract | Reuse value | Main caution |
|---|---|---|---|
| Programme and schedule | Sessions, speakers, themes and dates | Establishes the event context | Contains metadata rather than underlying data |
| Talk and session pages | Slides, abstracts, videos or transcripts | Provides direct conference materials | Some assets may be absent or incomplete |
| External paper, data and code links | DOIs, repositories, software and versions | Strongest route to provenance and reuse | Links may move or carry restrictive terms |
| Presenter and institution pages | Current publications, projects and contact details | Recovers resources missing from the archive | Ownership and identity must be verified |
| Personal research record | Citations, notes, manifests and checksums | Creates a durable audit trail | Depends on accurate manual documentation |
Use the routes as complementary evidence. A programme establishes that a talk occurred, while a slide deck can reveal methods and a repository can establish a versioned dataset. If two sources disagree, treat the later, itemised record as more authoritative for data details and the conference archive as the authority for event context. Record redirects and access dates because external services may no longer resolve the original address.
Reading the schedule and reconstructing context
The schedule is particularly helpful for talks whose slides provide little provenance. Grouping by “big data,” “deep learning,” “digital agriculture” and “global food security” shows which methods were presented together and which plenary speakers framed the wider discussion. It also helps distinguish a conference synthesis from a tested result. A claim introduced in a keynote may point to a policy direction, whereas a project presentation may name code, observations and validation work.
For each candidate talk, create a metadata record with the session, room, speaking time and named collaborators. Add a short abstract or summary, but keep it separate from your own interpretation. Check names against the programme because transliterations, reordered surnames and multiple authors can break searches in Trove, institutional repositories and the Australian Research Data Commons catalogue. Stable identifiers are more reliable than title fragments when tracing later publications.
Locating slides, recordings and supporting evidence
Presentation pages may point directly to slides, papers, posters, videos or transcripts. Save each linked item while preserving its parent page, since the latter supplies the event context needed for citation. If a file has no visible version or date, do not rename it as though it were an official release. Use a working title in your notes and label the item “conference copy” where appropriate.
Recordings can provide explanations absent from slides, but a spoken claim is not automatically peer-reviewed evidence. Listen for qualifications, sample size, geography, funding and stated limitations, then corroborate numerical or causal claims against a paper or dataset. Transcripts improve searching, yet automatic captions can alter technical terms, so retain the original media and mark any transcription errors.
When an external link fails, search by presenter, exact title, co-author and distinctive dataset name in the relevant repository or university profile. DOI records and archived citation files can recover the intended version, but they do not restore access to restricted data. Document every substitution, and do not use a later dataset with the same name until its provenance and relationship to the talk have been checked.
Following datasets, code and cross-border dependencies
Slides often name the underlying observations, software and validation strategy more clearly than a programme does. Look for repository names, file formats, geographic scope, collection dates, codebooks and statements about consent. In digital agriculture, for example, check whether the imagery concerns Kansas only or a broader region; in global food security work, verify the units and food categories before combining figures with Australian datasets.
Cross-border reuse can involve several owners: a presenter, a university, a funder, a platform and publishers of third-party images or code. The staged logic in this cross-border procedure guide offers a useful analogy for separating authority, evidence and review. Build an ownership map for each output and identify where consent, licences or institutional transfer approval are required.
For code, preserve the original release identifier, runtime dependencies and a reproducible example. For data, retain a file manifest or checksum, transformation steps and a record of excluded records. If you harmonise American measures with Australian standards, explain the conversion rather than silently changing labels. A derived dataset should have its own version and citation, linked back to the unmodified conference source.
Handling permissions, attribution and Australian requirements
Copyright, database rights, confidentiality and privacy can each limit reuse. A Creative Commons licence on one slide does not necessarily cover an embedded journal figure, map or commercial dataset, while a public presentation may contain participant information that was not suitable for open release. Check the licence for every component, and contact the relevant rights holder when the terms are unclear.
Australian teams should also assess the OAIC Australian Privacy Principles, applicable health-data requirements and community expectations around Indigenous Cultural and Intellectual Property. Personal, location or agricultural data may have low sensitivity in one jurisdiction and meaningful consequences in another. Use de-identification only where it meets the relevant standard, and consider whether findings should remain with the originating community rather than enter an open repository.
Ask presenters for the material they can lawfully share and request a specific licence, attribution statement or data-use agreement. A concise email should name the talk, link to the archived item, explain the intended Australian research or teaching use, and ask which files may be redistributed. Keep the exchange with the record. Where permission is pending, cite and describe the source but do not assume publication rights.
Accounting for travel, customs and Australian markets
Plan access across time zones. In May 2017, Lawrence was on Central Daylight Time, while Sydney, Melbourne and Canberra were on Australian Eastern Standard Time, 15 hours ahead; Adelaide was 14½ hours ahead. Australian daylight-saving dates can change that gap. For archived assets there is no live session to attend, yet these offsets matter when interpreting timestamps in recordings, logs or repository updates.
The conference’s archived travel guide provides useful baseline information for Lawrence and the University of Kansas. If reuse involves physical research materials rather than digital files, Australian Border Force handles customs matters, and soil, seed, food or biological specimens may require biosecurity checks through BICON before shipment or import. Digital datasets themselves do not pass through customs, but their governance can be affected by the movement of linked samples or equipment.
The Australian research market offers local pathways for discovery and preservation through the Australian Research Data Commons, the National Library of Australia’s Trove service, university repositories and CSIRO or departmental archives. Commercial metadata, data-management and repository services are also available, usually with contracts or licences priced in Australian dollars. These options can improve citation and access, but they should not replace the archived conference provenance or obscure third-party rights.
Recommendations for responsible reuse
A practical checklist keeps a talk-derived resource useful to collaborators, reviewers and future teams. Apply it to each output rather than assuming that one licence covers an entire talk.
- Record the talk title, speakers, session, event date, archived URL and access date in one metadata record.
- Separate slides, recordings, papers, datasets and code into distinct items, preserving their original identifiers and versions.
- Verify licences component by component and store written permission, attribution wording and contact details.
- Document extraction, cleaning, harmonisation, exclusions and environmental assumptions with scripts and file manifests.
- Publish a citation, README and limitations statement alongside any retained or derived research object.
The result is a traceable research package rather than a loose collection of downloads. It preserves what was said at IASSIST 2017, shows how the material was checked and adapted, and gives an Australian audience enough context to evaluate whether the evidence fits their own communities, landscapes, policy settings and markets.
At the Conference
What attendees experienced in Lawrence
Plenary Sessions
Keynotes from Daniel Reed on data, technology, and culture, and Jennifer Clarke on digital agriculture and the Midwest Big Data Hub.
Workshops
Full-day technical workshops on Tuesday, May 23. Morning sessions ran 9:00–12:00 and afternoon sessions 13:00–16:00. Laptops were required.
Social Events
An opening reception at The Oread, a banquet, and an optional post-conference tour of Kansas City including Crescent Moon Winery.
Venue & Accommodations
Where the conference took place
Kansas Union
University of Kansas campus, Lawrence. Main conference venue with check-in on the 4th and 5th floor lobbies.
The Oread
1200 Oread Avenue, Lawrence. Hosted the opening reception and offered a room block for attendees.
The Eldridge
701 Massachusetts Street, Lawrence. A partner hotel with a reserved room block for conference guests.
Springhill & TownePlace Suites
Marriott properties in Lawrence with room blocks reserved under the "KU IASSIST Conference" name.
Program Highlights
Sessions and activities
Getting Here
Lawrence, Kansas
Kansas Union · University of Kansas
1301 Jayhawk Blvd, Lawrence, KS 66045
Kansas City International Airport (MCI) is approximately 50 minutes by car. Lawrence Transit Routes 10 and 11 served the area ($1 exact change).
Plan Your Stay
Accommodation options that were available
The Eldridge
701 Massachusetts Street, Lawrence, KS 66044. Room block now closed.
The Oread
1200 Oread Avenue, Lawrence, KS 66044. Room block now closed.
Springhill Suites
Marriott property. Room block reserved under "KU IASSIST Conference."
TownePlace Suites
Marriott property. Room block reserved under "KU IASSIST Conference."