Behind the scenes of the IASSIST 2017 program committee

The IASSIST 2017 archive preserves the program for “Data in the Middle: The Common Language of Research,” held at the University of Kansas in Lawrence from 23 to 26 May 2017. Its schedule records plenaries, contributed presentations and practical information about check-in, transport and local recommendations. Together, these materials show a conference designed to connect researchers working with very different kinds of data.

The program committee supplied the editorial structure behind that schedule. Its task extended beyond accepting papers: it determined which subjects belonged together, balanced specialist sessions with broad-interest events and made thousands of individual contributions legible within four days. The archive does not contain private committee minutes, so some decisions must be inferred from the published program rather than presented as documented facts.

That distinction is important. The public schedule reveals the committee’s results—thematic groupings, speaker choices, recurring questions and the rhythm of each day—but not every discussion that produced them. It nevertheless provides a clear view of the judgment, negotiation and coordination required to turn a large collection of proposals into a coherent meeting.

The subject had particular resonance in Australia. Researchers in Sydney, Melbourne, Canberra, Brisbane, Adelaide and Perth were already working across statistical science, machine learning, agriculture, health and food systems. For them, the event offered both intellectual value and a demanding exercise in international collaboration across time zones.

What the archived program can reveal

A conference program is an editorial argument. Its opening plenaries establish priorities, its sessions demonstrate which questions attracted attention, and its thematic clusters show how organisers understand the field. At IASSIST 2017, the prominence of big data, deep learning, digital agriculture and global food security created a frame in which technical methods could be connected to substantive research problems.

The committee also had to consider the event as a whole rather than as a collection of excellent but disconnected talks. A schedule could feature strong individual presentations while still failing to provide the “common language” promised by the conference title. The archived groupings suggest an effort to create conversation across disciplines while retaining enough methodological depth for specialists.

Turning proposals into a coherent program

Abstract review for an interdisciplinary meeting begins with a difficult balancing act. Selection criteria must reward rigorous work, originality and relevance without favouring only established names or heavily used methods. Reviewers also need to consider whether proposed talks can sit within a session of comparable scope and whether enough complementary papers exist to sustain a discussion.

Once accepted, contributions require further shaping. Closely related papers might be combined, while others needed introductory framing or a clearly stated connection to the conference theme. The visible choices point to several editorial priorities:

• Each session had a recognisable research problem.
• Technical depth was balanced with broader implications.
• Presentations represented varied methods and application areas.
• International perspectives strengthened the discussion.
• Schedule changes were limited wherever possible.

These priorities reflect the practical work of program chairs, reviewers and session chairs. They also demonstrate why programme planning is more than clerical. A coherent meeting depends on relationships among papers as much as on the quality of each paper in isolation.

Plenary sessions as anchors for the meeting

Plenary speakers give a conference its intellectual centre. They can establish shared concepts before parallel tracks divide the audience, connect statistical practice to emerging technologies and introduce questions that specialists can carry into their sessions. The plenary information preserved by IASSIST 2017 therefore reveals how the committee framed the meeting’s central concerns.

The programme’s combination of big data and deep learning placed computational methods within a wider research conversation. Digital agriculture and global food security then showed how those methods affect decisions about production, environmental conditions, supply chains and policy. The emphasis was not simply on technical capability, but on what responsible use of data demands from researchers.

A plenary also serves a scheduling purpose. Its placement near the beginning or end of a day can bring dispersed audiences back together and reset attention before the next group of sessions. In this way, the committee’s plenary choices helped turn separate presentations into a sequence with a continuing argument.

Where disciplinary boundaries were tested

The most productive sessions in the archived programme appear to connect fields that do not normally share vocabulary. Statistical researchers may discuss uncertainty and sampling, computer scientists may focus on model architecture and computing resources, while agricultural scientists consider sensor placement and production conditions. The programme committee had to make those conversations intelligible without erasing their differences.

Several cross-disciplinary connections are visible in the subject matter:

• Big data brought scale, reproducibility and governance into sharper focus.
• Deep learning prompted discussion of interpretability and appropriate evaluation.
• Digital agriculture linked remote sensing with farm-level decisions.
• Global food security connected data quality to policy and distribution.
• Shared language enabled specialists to examine common methodological problems.

Digital agriculture offered a particularly clear example. A prediction model is not merely a software product; it must account for soils, weather, crop varieties, labour, markets and the consequences of error. Likewise, food-security analysis depends on data that may be incomplete, delayed or collected under difficult conditions. The committee’s thematic structure made those practical constraints part of the technical discussion.

Scheduling and the attendee experience

The conference schedule was also a physical operation. Sessions required rooms of suitable capacity, presenters needed arrival and departure times that could be communicated, and organisers had to limit clashes between talks likely to attract the same audience. Parallel tracks create choices for attendees, but too many conflicts can fragment the meeting.

Committee members therefore worked with logistical information alongside the academic programme. The archived guidance on check-in, transportation and local recommendations reflects a broader concern for participant experience. A visitor unfamiliar with Lawrence should be able to move between registration, lecture rooms, breaks and nearby services without wasting research time on basic navigation.

Printed schedules, posted changes, session chairs and attentive room management all served as interfaces between editorial decisions and the actual event. Technical problems were inevitable when speakers, equipment and timetables met, but the programme’s order gave organisers a contingency plan. Its apparent simplicity depended on substantial advance coordination.

The Australian relevance of a Kansas meeting

Australian participants faced a sharp time difference. During the conference, Sydney and Melbourne were 15 hours ahead of Lawrence, while Perth was 13 hours ahead. This meant an early Australian morning event could fall late at night on the conference schedule. Most journeys from Australia also required a connection through a major American gateway before reaching the relatively small regional airport serving the Lawrence area.

The research themes closely matched concerns across the Australian market. Universities, CSIRO, agricultural suppliers, banks, supermarkets and public agencies were increasingly using large datasets and machine-learning systems. Woolworths and Coles, for instance, operated supply chains shaped by forecasting, inventory analysis and consumer data. Australian farmers faced the need to interpret sensing, climate and market information across grain, livestock, cotton and horticultural regions, often while managing drought risk.

Returning travellers also needed to consider Australian biosecurity rules. Australian Border Force assesses goods under the Biosecurity Act 2015, and food, seeds, plant material, soil, animal products and agricultural samples may require declaration, permits or inspection. Purchases from a Kansas farmers’ market or commercial samples carried for research should therefore be checked before departure rather than treated as ordinary souvenirs.

These realities did not diminish the value of the meeting. They showed why international collaboration requires more than shared technical interests. Researchers must accommodate different working hours, funding systems, data environments, institutional practices and regulatory expectations. The committee’s ability to create common ground in Lawrence offered a useful model for Australian organisers facing the same task across even greater distances.

The lasting value of careful program design

The work of a programme committee is most visible when it disappears into a successful event. Attendees remember an engaging talk, a useful question or a conversation that continued beyond its assigned session. They may never see the abstract assessments, session negotiations or schedule adjustments that allowed those experiences to occur.

The IASSIST 2017 archive preserves the outcome of that hidden work. Its programme documents a deliberate attempt to place rigorous statistical practice in conversation with emerging computational methods and urgent global challenges. It also records an understanding that strong scholarship becomes more influential when audiences can recognise the problems beneath its different methods.

That is the committee’s most durable contribution. By organising around shared questions rather than isolated specialties, it made “Data in the Middle” a working principle: a place where researchers could exchange the language needed to understand data, evidence and decisions together.