The common language of research: IASSIST 2017 revisited
From 23 to 26 May 2017, the University of Kansas in Lawrence hosted IASSIST 2017, a meeting built around “Data in the Middle: The Common Language of Research.” Its central proposition was deceptively simple: research becomes more useful when people who create data, build analytical systems and act on findings can describe what they need in terms others can understand. The archived programme preserves that ambition as a snapshot of an emerging research conversation.
Viewed years later, the conference is valuable less as a prediction of technology than as a record of expectations. Sessions on big data, deep learning, digital agriculture and global food security now sit beside rapid changes in generative AI, data governance and open research. The archived material lets readers ask which questions were already urgent, which vocabulary remained durable and which assumptions deserve another look.
For an Australian audience, that history has particular resonance. CSIRO, the Australian Research Data Commons and institutions around Canberra, Melbourne, Adelaide and Sydney have built connected national capabilities around research data, analytics and computation. Australian research also has a strong applied orientation in agriculture, water and regional services, making the meeting’s attention to shared methods relevant to problems that cross institutional and state borders.
The archive goes beyond papers and plenaries by retaining the practical information attendees needed for check-in, transport and local recommendations. That material matters because conference design shapes exchange as much as presentation content does. Clear arrival details, useful venue information and thoughtful hospitality can turn specialised sessions into durable professional relationships.
Why the 2017 gathering endured
At its best, a conference supplies a shared vocabulary without pretending that every discipline uses words in the same way. IASSIST 2017 gathered researchers, developers and practitioners around information systems, data and society. Its value lay in making those boundaries discussable: a statistician could clarify uncertainty, a software researcher could expose an implementation constraint, and an agricultural scientist could explain why a technically elegant result might fail in a field.
The phrase “data in the middle” described more than a technical layer between systems. It pointed to relationships among people, institutions and decisions. Data passed through laboratories, farms, administrative agencies and commercial organisations before reaching a public claim or policy choice. A conference devoted to this journey could examine provenance, interpretation and use without reducing quality to one universal checklist.
That remains the strongest element of the conference legacy. Interoperability, metadata, governance and explanatory communication are durable concerns even when particular tools change. The archived presentations also show why these concerns belong together: a powerful model with weak documentation, or a well-governed dataset that lacks a meaningful application, cannot advance research on its own.
Reading the programme as a research map
The archived programme gives readers more than a sequence of talk titles. It connects plenaries with specialist sessions, shared projects and practical encounters at the University of Kansas. That structure reveals how the organisers positioned big data, deep learning and digital agriculture: as connected challenges requiring contributions from software engineering, information science, domain expertise and public policy.
The schedule is especially revealing because movement between sessions is part of the argument. A discussion of learning systems beside a presentation on agricultural data invites questions about transfer, scale and context. A plenary on research data can establish a frame that later sessions test through cases from health, agriculture, information management and software systems. The programme becomes a map of relationships rather than a collection of isolated specialisms.
Reading it retrospectively also reveals what the programme could not show. It captures confidence in data-driven innovation, yet it does not fully anticipate today’s concern with model drift, synthetic data, platform concentration or the environmental cost of computation. Its strongest cases are those that make assumptions visible. That quality offers a sound method for reassessing old claims: identify the vocabulary, trace the evidence and ask which context remains valid.
Big data, deep learning and responsible interpretation
Big data and deep learning supplied much of the conference’s technical energy. Presentations explored how large volumes of textual, numerical and observational data could support analysis that was difficult to perform manually. Neural networks, predictive models and new approaches to unstructured information encouraged participants to consider what became possible when computation, instrumentation and data storage improved together.
The AIC 2017 archive provides a useful second historical window onto the wider information landscape. Read alongside the Lawrence sessions, it helps distinguish conference-specific conclusions from ideas circulating across adjacent research communities. Both records show a period in which “scale” was often treated as a sign of insight, even though volume by itself says little about representativeness or usefulness.
Responsible interpretation has since become more demanding. Australian research teams now work within federal privacy reforms, Australia’s AI Ethics Principles and institutional rules for data access, while maintaining pressure to publish and collaborate. The common language of research must therefore include uncertainty, model monitoring, documentation of training data and meaningful human oversight. The technical questions remain, but their consequences are no longer confined to experimental teams.
Digital agriculture and global food security
Digital agriculture connected the conference’s computational themes to decisions made under field conditions. Remote sensing, soil readings, weather records and machine telemetry can help researchers compare varieties, estimate yields and identify spatial patterns. The challenge is to ensure that those signals support agronomic judgment rather than obscure it. A model trained in one location may perform poorly when soil, cultivars, pests or management practices differ.
Global food security widened the frame again. Food systems depend on production, storage, transport, prices, labour and household access, while many of the communities most affected by hunger contribute limited data to influential models. Research collaboration must address who owns the data, who benefits from the analysis and whether local knowledge is represented. Technical interoperability is therefore tied to fairness in the food and research markets.
Australian examples make these issues concrete. Grain growers across the wheat belt of New South Wales and Queensland, cotton producers in northern New South Wales, and sugar industries in Queensland face long distances, variable rainfall and tight water-allocation decisions. Farm-gate advice travels poorly if it ignores local varieties, soil management or irrigation conditions. Australian agronomy therefore offers a demanding setting for testing whether digital agriculture produces practical value at regional scale.
Practical design as part of research
The archived guidance on check-in, transportation and local recommendations shows that organisers understood participation as more than attending talks. Knowing where to register, how to reach the venue and where to meet colleagues reduces uncertainty for first-time visitors, international guests and people with accessibility needs. Those details also create informal contact points, often where collaborations begin.
The Kansas setting offered useful contrasts for Australian visitors. Lawrence supported a campus-to-downtown meeting environment, while Australian delegates commonly arrive in large cities with substantial transit systems and then travel long distances to regional institutions. Clock differences matter as well: in late May, Kansas was in late spring and Australia was moving through autumn or early winter. A roughly fourteen-to-fifteen-hour difference could shape attendance, online participation and the informal conversations that follow formal sessions.
Local language and social expectations can be just as consequential. In Australia, “arvo” means the afternoon, while “shout” can mean buying drinks for a group. Conference organisers often clarify whether food or drinks are supplied and whether guests should bring their own. Translating those details into clear guidance prevents small cultural assumptions from excluding people or making already demanding travel schedules harder.
Priorities for Australian collaborators
Australian research operates through a mixed market of competitive grants, institutional funding, state programs, CSIRO partnerships and industry co-investment. Projects that join universities with producers, technology firms or public agencies must therefore manage different timelines, evidence standards and commercial expectations. IASSIST’s collaborative ideal transfers well when it is adapted to this funding environment rather than copied without adjustment.
The practical task is to turn shared language into shared infrastructure. That means defining data and model terms across disciplines, documenting provenance, and creating governance that respects regional differences and the rights of data-providing communities. Australian teams can draw on established repositories and national research capabilities while avoiding the assumption that technical connection guarantees equitable access or lasting impact.
- Establish a shared metadata crosswalk that maps local datasets to national and domain repository standards.
- Pair every predictive model with documented provenance, transparent validation criteria and a monitoring plan for drift.
- Co-design agricultural pilots with producers, state agencies and agribusiness so benefits reach operational decisions.
- Treat interdisciplinary vocabulary as an interface, defining terms explicitly rather than assuming shared meanings.
- Preserve the conference’s practical care through clear check-in guidance, accessible digital records and carefully scheduled Australian collaboration windows.
A durable framework for future research meetings
A retrospective becomes useful when it separates durable principles from temporary technologies. The 2017 meeting correctly emphasised data as connective tissue between research and society, but its strongest examples also asked who could participate, how uncertainty travelled and whether results could travel into practice. Those questions remain relevant as the tools surrounding them have changed.
The shift can be read across several dimensions:
| Research concern | IASSIST 2017 emphasis | Australian test today |
|---|---|---|
| Shared language | Common concepts across information disciplines | Explicit agreements between universities, agencies and industry |
| Large-scale data | New analytical possibilities | Provenance, representativeness and responsible reuse |
| Deep learning | Predictive and unstructured-data opportunities | Explainability, model monitoring and human oversight |
| Digital agriculture | Technology for crop and food-system decisions | Regional fit, producer value and water sensitivity |
| Collaboration | Connections among research communities | Durable funding, interoperable infrastructure and equitable access |
| Conference design | Registration, transport and local guidance | Accessible participation across distance, time zones and language |
IASSIST 2017 therefore offers more than an archive of early discussions about artificial intelligence and data. Its enduring contribution is a disciplined view of research as a chain of relationships, in which technical systems, institutional choices and human understanding must develop together. That perspective remains well suited to Australian science and to the complex data questions of the present.
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."