Abstract low-poly geometric background in shades of pale blue and white

Data in the Middle: The common language of research

Planning A Data-Forward Summer School With IASSIST 2017

A strong summer school does more than deliver a sequence of lectures. It creates a shared working language for people who collect, manage, analyse, interpret and apply data in different settings. That principle sits at the heart of IASSIST 2017, whose theme, “Data in the Middle: The Common Language of Research,” offers a useful model for designing a contemporary programme.

For an Australian audience, the model can be adapted to local research priorities and practical conditions. A course might connect librarians with data scientists, agronomists with policy analysts, or postgraduate researchers with community organisations. The aim is a focused learning experience in which technical skills, research practice, ethics and real-world decision-making reinforce one another.

Define The Shared Data Question

The first planning task is to identify a substantial question that can hold the school together. IASSIST 2017 brought together themes such as big data, deep learning, digital agriculture and global food security. These subjects are broad, yet they become teachable when placed around a common research problem.

An Australian summer school could centre on a question such as: how can data support climate-resilient food systems? That question gives participants a reason to move between satellite imagery, farm records, weather observations, supply-chain information and social research. It also creates room to discuss who owns the data, who benefits from analysis and which communities may be overlooked.

The central question should be specific enough to guide practical work. “Using data for sustainability” is too open-ended, while “combining seasonal rainfall data with crop and market indicators to assess wheat-growing risk in regional New South Wales” gives teams a clear direction. The subject can still accommodate participants from different disciplines because each person contributes a distinct perspective.

A useful planning statement includes four elements:

  • The social or scientific problem being addressed
  • The types of evidence participants will work with
  • The decisions that analysis should inform
  • The ethical or community conditions that must shape the work

This approach prevents the programme from becoming a collection of unrelated workshops. A session on machine learning has a clear purpose when participants use it to classify crop stress, assess disaster exposure or examine patterns in food access. A data-management session becomes more meaningful when it prepares them to document, share and preserve those same datasets.

Design A Learning Journey Across Disciplines

The programme should move from shared concepts to applied practice, then to interpretation and communication. This progression reflects the way research teams operate. Participants need enough common vocabulary to collaborate before they can make useful decisions together.

Begin with a data landscape session. Introduce data types, metadata, reproducibility, data quality, privacy, licensing and responsible reuse. Avoid treating these subjects as administrative material that sits outside the “real” technical work. A poorly documented dataset can undermine an otherwise impressive model, while an apparently useful dataset may be unsuitable for a particular purpose because of consent or cultural restrictions.

The next stage can introduce analytical methods at different levels. A deep learning demonstration may be valuable, but it should sit alongside simpler approaches such as descriptive statistics, visual exploration and rule-based classification. Participants should compare methods rather than assume that the most complex model is automatically the best. Explainability, computational cost, maintenance and the availability of suitable training data all matter.

Build interdisciplinary teams early and give each participant a defined role. A librarian or research data specialist might lead documentation; a domain expert can test whether variables make sense; a statistician can challenge assumptions; and a community or policy representative can consider consequences beyond the dataset. This structure makes collaboration visible and reduces the risk that one confident technical participant dominates the project.

Plan for mixed digital confidence as well. Australian universities and research organisations often bring together people with very different experiences of coding, cloud platforms and data governance. Use short demonstrations, guided notebooks and optional extension tasks so that beginners remain engaged while experienced participants have room to advance.

Build A Practical Australian Setting

A data-forward summer school should feel connected to its location rather than transplanted from an overseas template. In Australia, the physical scale of the country affects attendance, scheduling and delivery. A participant travelling from Perth to an event in Canberra or Brisbane may spend much of a day in transit, while a regional attendee may need an additional connection or ground transfer.

Clear travel information should be part of the learning experience’s practical design. The archived IASSIST material provides a useful example of how to separate arrival guidance from academic content, including air travel information for attendees. An Australian programme should similarly explain airport transfers, public transport, accessibility, accommodation areas and the distance between the venue and evening activities.

Timing matters too. Australian institutions generally operate on a February-to-June first semester and a July-to-November second semester, with a winter break around June and July. A “summer school” held in January may be convenient for some staff but difficult for academics preparing teaching, while a December programme can compete with end-of-year closures. In practice, a January intensive may need early communication, and a July version may be more comfortable for university participants, even if the name remains summer school for international audiences.

Local customs can shape the atmosphere. Include a proper welcome and, where appropriate, an Acknowledgement of Country developed with local guidance. Provide tea, coffee and substantial morning refreshments rather than assuming a brief break will suit everyone. Australian participants often value direct discussion and informal networking, so allow time for questions, practical troubleshooting and conversation after plenary sessions.

The local market should influence examples and partnerships. A school in Adelaide could work with viticulture and water-use data; one in Brisbane might examine flood mapping and public health; a programme in Melbourne could draw on urban mobility or biomedical research; and a course in Perth could explore mining, remote sensing or biodiversity. Connections with CSIRO, the Australian Research Data Commons, state government departments, universities, agricultural cooperatives and Indigenous organisations can make the programme more credible and useful.

Make Ethics And Governance Part Of The Method

Data literacy includes understanding the conditions under which data can be collected, combined and reused. A practical school should therefore treat governance as a core method rather than a final compliance lecture. Participants can examine consent, de-identification, access controls, retention periods, licensing and the risks of linking datasets.

Australian settings require particular care around Indigenous data. The CARE Principles—Collective Benefit, Authority to Control, Responsibility and Ethics—provide a valuable complement to the FAIR Principles of findability, accessibility, interoperability and reusability. A dataset can be technically discoverable and well documented while still being inappropriate to share or interpret without community authority.

Use case studies that expose difficult choices. A project might combine health and geographic data to identify service gaps, but the same analysis could stigmatise a neighbourhood. A farm dataset may support better irrigation decisions while revealing commercially sensitive information. A public dashboard may improve transparency yet make it easier to identify vulnerable individuals or small communities.

Governance activities should be hands-on. Ask teams to create a data-use agreement, write a plain-language consent statement or develop an access decision for a sensitive dataset. Give them a fictional request from a commercial partner, government agency or journalist and ask them to assess whether the request is compatible with the project’s purpose.

A strong programme also teaches participants to recognise limits. Data is not a neutral substitute for local knowledge, lived experience or professional judgement. Models reflect the data and categories used to build them. If rural, remote, low-income or culturally diverse communities are poorly represented, a polished analysis may still produce an incomplete account of reality.

Turn The Programme Into A Reusable Research Experience

The best summer schools leave participants with more than presentation slides. They produce reusable workflows, documented datasets, prototype analyses and relationships that continue after the final session. This requires a deliberate project structure from the beginning.

Give teams a compact dataset or a carefully scoped collection of sources. Require a short project charter that defines the question, intended users, assumptions, risks and success measures. Teams can then create a data dictionary, record decisions in a shared repository and present an initial result before the final day.

Assessment should reward process as well as output. A technically impressive model with weak documentation should not receive the same recognition as a transparent, reproducible project that another team could inspect and extend. Include peer review, a short methods presentation and a plain-language briefing for a non-specialist audience.

The final event can borrow the rhythm of a conference programme: a plenary framing the issue, focused workshops, team demonstrations and a closing discussion about future research. Invite external reviewers from universities, industry, government and community organisations. Their role is to test whether the projects answer meaningful questions rather than simply celebrate technical novelty.

Plan the operational details with the same care as the curriculum. Confirm venue capacity, internet access, software requirements, catering, accessibility, recording permissions, travel support and backup activities. Australian summer weather can bring heatwaves, bushfire smoke or sudden storms, so include a communication plan and flexible arrangements for participants travelling from regional areas.

A simple framework can help organisers match ambition to resources:

Programme Model Best For Typical Format Main Strength Key Risk
Short Data Clinic Early-career researchers needing core skills Two to three days Focused and affordable Limited time for team projects
Interdisciplinary Intensive Mixed cohorts working on a shared challenge Five to seven days Strong collaboration and applied learning Requires careful facilitation
Research Partnership School Universities, agencies and community groups One to two weeks Produces richer local projects Higher coordination and governance demands
Distributed Hybrid School Participants separated by distance Online sessions with local hubs Reduces travel barriers across Australia Weaker informal networking

The delivery model should reflect the audience and the data problem. A five-day intensive may suit a cohort based near one campus, while a distributed format can include participants from Darwin, Hobart, Sydney and regional centres without requiring everyone to travel. Hybrid delivery works best when remote participants receive equivalent access to datasets, facilitators, breakout activities and social connection.

Measure Learning, Collaboration And Use

Evaluation should begin before the first session. Ask participants to rate their confidence in data management, analysis, visualisation, governance and interdisciplinary communication. Add a short practical diagnostic, such as asking them to identify risks in a sample dataset or interpret a basic chart.

During the school, facilitators can track whether teams are documenting sources, testing assumptions and sharing tasks fairly. Short daily reflections reveal where participants are confused or where the timetable needs adjustment. A technical lab may need more support than expected, while a planned lecture could be shortened because the cohort is ready for applied work.

Evaluate the final projects against clear criteria:

  • Relevance of the research question
  • Quality and suitability of the data
  • Transparency of the workflow
  • Ethical and governance awareness
  • Clarity of communication
  • Potential value for a real user or community

Follow-up is essential. At three or six months, ask whether participants have reused a method, improved a data-management practice, formed a collaboration or progressed the project. Track practical outcomes such as a deposited dataset, a policy brief, a research proposal, a community workshop or a new partnership.

The central lesson drawn from IASSIST 2017 is that data becomes more valuable when people can work across professional and disciplinary boundaries. A well-designed Australian summer school can make that principle tangible: it can connect technical expertise with local knowledge, research infrastructure with community needs, and ambitious analysis with responsible action.

At the Conference

What attendees experienced in Lawrence

p1 reed

Plenary Sessions

Keynotes from Daniel Reed on data, technology, and culture, and Jennifer Clarke on digital agriculture and the Midwest Big Data Hub.

platinum icpsr

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.

gold rockhurst

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

silver ifdo

Kansas Union

University of Kansas campus, Lawrence. Main conference venue with check-in on the 4th and 5th floor lobbies.

platinum ddi

The Oread

1200 Oread Avenue, Lawrence. Hosted the opening reception and offered a room block for attendees.

silver ciser

The Eldridge

701 Massachusetts Street, Lawrence. A partner hotel with a reserved room block for conference guests.

platinum icpsr

Springhill & TownePlace Suites

Marriott properties in Lawrence with room blocks reserved under the "KU IASSIST Conference" name.

Program Highlights

Sessions and activities

Plenary Sessions Workshops Poster Presentations Committee Meetings Opening Reception Banquet Tour Kansas City Pecha Kucha Check-In Local Favorites

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

silver ifdo

The Eldridge

701 Massachusetts Street, Lawrence, KS 66044. Room block now closed.

platinum ddi

The Oread

1200 Oread Avenue, Lawrence, KS 66044. Room block now closed.

silver ciser

Springhill Suites

Marriott property. Room block reserved under "KU IASSIST Conference."

gold rockhurst

TownePlace Suites

Marriott property. Room block reserved under "KU IASSIST Conference."