Best practices for running a data bazaar at academic events

An academic conference gathers researchers, students, software teams, public-sector partners and industry specialists in temporary, busy rooms. A data bazaar turns that mix into a structured exchange: visitors can discover datasets, test tools, compare methods and meet potential collaborators while the event is in progress. Its value comes from useful conversations and responsible access, not from the number of datasets displayed.

The archived IASSIST 2017 conference at the University of Kansas in Lawrence reflects the interdisciplinary environment such an exchange must support. Its programme covered big data, deep learning, digital agriculture and global food security, bringing together people who might not normally encounter one another. Effective bazaar practices make those connections accessible, ethical and actionable for first-time participants as well as established specialists.

Define the bazaar before choosing a format

Start with a plain description of what can happen at each stand: share a dataset, demonstrate a service, review a research method, match a problem with expertise or co-design a study. This prevents a showcase from becoming a collection of sales pitches and gives visitors a clear reason to move between spaces. The purpose also determines what must be booked, staffed and recorded.

Bazaar format	Best suited to	Main benefit	Frequent risk
Dataset showcase	Groups with publishable or documented resources	Visitors can scan many resources quickly	Displays feel promotional rather than usable
Data clinic	Organisations needing help with access, metadata or analysis	Participants leave with a concrete next step	Advice becomes vague when no technical expert is present
Matchmaking desk	Projects seeking partners, skills or independent review	Connections can lead to funded collaboration	Details are collected without consent or follow-through
Co-design market	Teams exploring a shared research question	Ideas are developed collectively	Scope expands beyond the event’s capacity

Choose one primary format and add only one secondary activity. A conference with many simultaneous tracks often benefits from short, scheduled conversations, while a smaller workshop may work better with extended clinics. Test the design with several likely attendees before publishing the programme, especially if visitors are expected to bring unfamiliar data or work under time pressure.

Publish the scope in advance. State whether raw data can be viewed, whether demonstrations are hands-on, who may attend and what happens after a meeting. Clear expectations reduce queues and make the bazaar feel like a working session rather than an exhibition. Keep the language accessible to attendees from different disciplines, including students and community delegates who may be less familiar with formal data marketplaces.

Design a clear participant journey

Map the participant journey from promotion through follow-up. Before the event, publish a short brief explaining who should attend, what to bring, how data will be protected, which sessions require booking and where remote visitors can join. This gives people time to prepare a usable sample rather than an incomplete spreadsheet and helps organisers identify specialist support in advance.

On arrival, create one visible check-in point with a short orientation and several staffed pathways. Visitors might follow a self-guided route, request a data consultation or reserve a matchmaking conversation. Display the same information on printed signs, the event app and the conference website. Do not assume that digital participation means every attendee has a company laptop, reliable mobile data or permission to photograph their badge.

Give each participant a clear next step. A dataset exhibitor might offer a ten-minute demonstration followed by a booking link for longer discussions. A visitor might leave with a shortlist of relevant contacts, a request for documentation or an agreed task for a later meeting. Capture these actions in a shared system so the bazaar produces partnerships rather than a large collection of business cards.

Set rules for data access and consent

Write data-access and consent rules before inviting participants. Distinguish between open resources that can be downloaded, restricted resources that require approval and closed resources that can only be discussed. Every exhibit should show a data dictionary, collection method, update date, known limitations and a named contact. If the material contains personal, commercially sensitive or culturally restricted information, replace it with a representative sample.

For organisations covered by the federal Privacy Act 1988, the Australian Privacy Principles govern how personal information is collected, used, stored and disclosed. Registration forms should explain the purpose of each field, who can see the information and how long it will be retained. Sensitive details should not be required merely to reserve a place. State and territory health-record laws may also apply to information held by health services, so organisers need to check the relevant rules before bringing patient or client data to the event.

Operational controls matter as much as written policies. Use password-protected transfers, multifactor authentication for administrative accounts and secure document storage. Delete temporary files after the agreed retention period, and avoid emailing raw datasets across unsecured conference networks. Sensitive material should stay on site or in an approved remote-access system. Where Indigenous data is involved, apply the relevant protocols for Indigenous data governance and involve the relevant communities in decisions about access, interpretation and reuse.

Build the venue plan around Australian realities

Australian cities require different transport and venue arrangements. Melbourne’s tram-heavy network, Sydney’s rail and bus corridors and Brisbane’s lower-density spread can affect arrival times and the distance between venues. Many public transport systems support contactless tap-on with a bank card or phone, yet visitors may still need a physical card or ticket. Publish precise travel times, walking directions and any transfer allowances, and build enough flexibility into the opening session for delayed arrivals.

Account for everyday meeting habits and practical dependencies. Coffee breaks often become the busiest networking periods, so place tables away from the main demonstration flow and schedule conversations in adjacent rooms. Provide clear signs for power outlets, Australian Type I connections, charging options and accessible toilets. Confirm whether demonstration devices will use local adapters and whether the venue can support the number of screens, speakers and video calls required.

Price services and products for an Australian audience. Use Australian dollars, follow the convention of showing GST-inclusive consumer prices and make payment methods visible before purchase. Invite local agritech firms, health technology developers, universities, libraries and open-source communities rather than relying exclusively on national brands. A balanced local presence can create follow-up opportunities after the conference and makes the bazaar relevant to the regional research economy.

Recruit a balanced and useful mix

Recruit participants based on the connections the event needs to create. Subject specialists without data skills, data professionals without domain knowledge and community organisations with practical questions can all contribute. Include postgraduate students and early-career researchers, but give them substantive roles such as facilitating a clinic or summarising discussions. Participation should provide learning or access, not simply unpaid labour.

Avoid building an exhibitor list dominated by large technology vendors. Give smaller research teams and public-interest groups comparable visibility, affordable participation options and suitable demonstration space. Review the invited mix for geographic, disciplinary and accessibility gaps. Community representatives, policymakers and industry practitioners often identify deployment questions that remain invisible inside a purely academic programme.

Ask every exhibitor to bring something usable. Suitable materials include a representative sample, a concise dataset card, a reproducible notebook, a workflow diagram, a validation checklist or a short consultation offer. Raw files should not be the only demonstration asset. Clear examples help visitors compare resources quickly, while technical staff can focus on the questions that require deeper discussion.

Run exchanges that create shared value

Staff the bazaar with people who can facilitate rather than merely supervise. Give each zone a host with authority to resolve access problems, explain boundaries and arrange specialist support. Use short rotations for demonstrations, consultations and matchmaking so participants do not spend the entire session waiting. A visible schedule should show free activities as well as those requiring bookings.

Standardise the demonstration format where possible. A five-minute pitch can state the problem, the resource, its maturity, suitable collaborators and the next available action. Longer sessions can include a sample workflow, a limitation and a question for visitors. Display one pathway for independent access and another for facilitated discussion. This keeps the pace suitable for delegates moving between parallel conference sessions.

Record follow-up only with permission. Provide a simple way for both visitors and exhibitors to exchange contact details, request access or agree on a task, with clear choices for whether their details may be shared. Some participants will prefer to discuss openly; others may need a private channel. Sending information through a conference platform that the organisation controls can make these choices easier to enforce and audit.

Measure impact and preserve the record

Evaluate the bazaar through outcomes rather than attendance alone. Useful measures include the number of qualified matches, consultations completed, access requests submitted, collaborations initiated and participant perceptions of usefulness. Gather feedback through a short survey and a few conversations with exhibitors, visitors and people who chose not to participate. Review whether certain disciplines or communities found the event welcoming, since participation figures alone may conceal barriers.

Preserve a public record of what was offered. Following the pattern of the IASSIST 2017 archive, retain the programme, session descriptions, presentation materials and approved links in a structured location. Dataset cards, consent terms, demonstration notes and short outcome summaries make the bazaar useful to people who could not attend. Apply a clear retention schedule, remove restricted contact details and document which versions were public.

Send a concise outcome report soon after the event. Include the themes discussed, agreed actions, responsible contacts and resources that remain available. A durable data bazaar becomes more than a temporary exhibition: it creates a traceable academic and industry network, demonstrates responsible data practice and gives future events a stronger foundation for participation.