Data management plans for international research projects
A data management plan is the agreed record of how research data will be created, documented, stored, shared and preserved. For an international project, it must also explain where decisions are made, who can authorise access and how records move between organisations. Treating the plan as a living stewardship document rather than a form submitted for compliance gives collaborators a common reference when responsibilities, technologies and regulations change.
The archived IASSIST 2017 conference, held in Lawrence, Kansas, on 23–26 May under the theme “Data in the Middle: The Common Language of Research,” illustrates why shared evidence depends on usable documentation as much as on sophisticated analysis. Its programme on big data, deep learning, digital agriculture and global food security presents challenges that remain familiar to teams connecting Australian universities with overseas laboratories, field stations and community organisations.
For researchers in Australia, those challenges acquire local detail: institutional ethics requirements, Commonwealth and state privacy rules, cloud regions, regional connectivity and the practical need to work with growers, agronomists and food suppliers. A strong plan connects national obligations with partner expectations without pretending that every jurisdiction is alike. It should let a project lead in Melbourne, a field coordinator in Brisbane and a partner team in Nairobi use the same core guidance while retaining the records needed to satisfy local law and institutional policy.
Start with the outputs and decisions
Begin with a plain account of the project’s research outputs. List the datasets, code, models, images, interview transcripts, questionnaires and other records expected at each milestone, then distinguish working files from material intended for preservation. Describe how each output will be named, versioned, validated and linked to its source. This concrete inventory is more useful than a generic promise to “manage data well”, because it reveals whether the team needs large-scale computing, sensitive field records, multilingual annotation or long-term access to a specialist collection.
Set out the lifecycle in enough detail for a new team member to follow: collection, processing, analysis, quality assurance, storage, publication, retention and disposal. Name the formats, expected volumes, quality checks and the systems that will hold master and derivative copies. For a digital agriculture study, for example, the plan may need sensor time series, soil observations, model outputs and photographs from different farms, with field identifiers replaced before any wider release. State which standards or community vocabularies will be used, and record the consequences if a format or service becomes unavailable.
Agree a common core that every partner can adopt, with short annexes for jurisdiction-specific procedures. Australian institutions may require local research data management templates, while overseas collaborators may face different consent, intellectual property and retention rules. The core should cover purpose, roles, metadata, access and preservation; annexes can carry local approvals, storage arrangements and legal contacts. This structure avoids a single document becoming a stack of incompatible national instructions and preserves a clear chain of decisions across the consortium.
Assign ownership across borders
International data work fails in predictable ways when ownership, custody and decision rights are left implied. Name an accountable plan owner, data stewards at each site, technical custodians and authorised institutional signatories. Use a responsibility matrix for tasks such as de-identification, licence selection, breach response, repository deposit and withdrawal of consent. Give each role a deputy, and record service-level expectations for requests from partners who may work in different time zones.
Connect those roles to the research agreements. Data ownership, permitted reuse, attribution, publication embargoes and access to derived models should be settled before collection starts, not after a collaborator requests the final files. A data use agreement can describe these permissions separately from the technical plan, while both should reference the same dataset identifiers. For commercially sensitive information supplied by Australian farms or food businesses, the agreement should also specify whether the partner may be named, whether records can be inspected and how long access must be retained.
Map the approvals that apply to identifiable information. Depending on the participants, sector and state, obligations may involve the Australian Privacy Act 1988, Australian Privacy Principles, state health privacy legislation, human research ethics conditions or contractual confidentiality. Sensitive data should not be emailed as a convenient workaround. Use approved encrypted storage, role-based permissions and documented disclosure checks, and maintain a register of exceptions so that an access decision can be explained months later.
Compare storage and preservation approaches
Storage decisions should follow the data’s sensitivity, expected use, sharing model and preservation horizon. An Australian team may choose an institutional repository, a disciplinary archive, a controlled cloud environment or a partner-held collection; the right choice for a public biodiversity dataset is rarely the right choice for identifiable interview transcripts. Confirm service coverage in Australia, export options and the charges for retained data. Major providers offer Australian cloud regions in Sydney and Melbourne, although availability and pricing can change.
| Approach | Best suited to | Access and control | Ongoing responsibility |
|---|---|---|---|
| Institutional repository | Citable university outputs and governed preservation | Departmental permissions and support for restricted records | Maintain metadata, retention and deposit workflows |
| Disciplinary repository | Shared datasets with recognised community standards | Repository-defined access and stewardship | Keep field terms, provenance and licences current |
| Controlled cloud environment | Active collaboration, sensitive working data and computation | Configurable permissions, encryption and audit logs | Fund the service, monitor use and plan exit costs |
| Partner-held archive | Records that must remain under a collaborating institution | Partner-specific approvals and contracts | Assign a custodian and confirm transfer conditions |
Whichever option is selected, separate the working environment from the preservation record. Keep authoritative files in a managed location with multifactor authentication, backups and activity logs; deposit a documented copy in a trusted repository with a persistent identifier where appropriate. Restricted material should use defined access routes rather than an open link. Teams in Perth should not assume that every commercial cloud service or high-speed research connection will be equally available to regional partners, so transfer schedules and offline media procedures belong in the plan.
Document metadata, consent and language
Metadata makes a shared collection intelligible beyond the team that created it. A minimum record should include a persistent title, creators and contributors, affiliations, dates, methods, language, keywords, provenance, licence, funder details and related outputs. Use stable identifiers such as ORCID for people and DOIs for released datasets, and retain the data dictionary alongside the files. The archived IASSIST material on multilingual metadata challenges shows why agricultural research needs agreed field terms as well as English summaries when labels, crop names or local practices differ across sites.
Treat consent as a set of permissions rather than one undifferentiated tick. Participants may permit curation and reuse but not publication of identifiable details, or may withdraw while requiring earlier analytical uses to be acknowledged. Record the consent version linked to each participant, the intended data destinations and any restrictions on commercial or genetic applications. In Australia, this is particularly important where information concerns health, children, Indigenous communities or small business, and where the Privacy Act may not be the only applicable regime.
Apply the FAIR principles—findable, accessible, interoperable and reusable—while recognising that open access is not always appropriate. The CARE Principles for Indigenous Data Governance add a necessary emphasis on collective benefit, authority to control and responsible relationships. Operationalise both through a metadata schema, controlled terms, documented access tiers and a review of licences. Test the files, not just the catalogue entry: confirm that restricted fields are removed correctly, formats open in standard software, checksums match and the preservation package contains the context needed for a future analyst.
Build workable habits for Australian teams
A usable plan is reviewed through ordinary project work rather than assembled at the end. Australian teams can adopt the following practices before collection begins:
- Nominate a plan owner and a deputy at each partner site, then store the current document in a version-controlled repository accessible to all data stewards.
- Create file-naming, folder, versioning and data-dictionary rules before the first field upload, including a standard way to record changes and derived datasets.
- Budget for people time, storage, transcription, translation, annotation, software, documentation and repository fees rather than treating data work as an unfunded afterthought.
- Run a small pilot through consent, de-identification, transfer, analysis and deposit to expose unclear instructions while changes remain inexpensive.
During collaboration and release, the following checks keep data sharing accountable:
- Use institution-managed encrypted storage for identifiable files and approved collaboration platforms for transfer; apply multifactor authentication, least-privilege roles and access logs, then review permissions after staff or partner roles change.
- Check Australian Border Force requirements before travellers carry research instruments, specimens or encrypted devices into Australia, and obtain institutional import and export approval. Customs clearance does not replace ethics, biosecurity or data protection checks.
- Treat agreements with growers, regional processors or retailers such as Coles or Woolworths as evidence-governance exercises: confirm which fields may be used, whether names can be published and what must be deleted before a dataset or model enters a repository.
- Publish a metadata record for shareable outputs and justify every restriction; use a repository’s request or secure-environment mechanism for controlled access, and record the review date for future closure or release.
Measure the plan with simple indicators: metadata completeness, the share of eligible outputs deposited, time to answer a partner request and overdue access reviews. Revisit the document at major milestones and whenever consent, funding, infrastructure or law changes. The archived 2017 conference schedule remains a useful orientation point for shared research language, but current institutional policies, funder requirements and repository services must determine the operational details of every active research data plan.
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."