Structuring data deposit packages

Well-organised data packages make it easier for users to understand the relationships between files and reduce the effort required during repository deposit and curation.

Before finalising folder structures and file organisation, data producers should consult the submission requirements of the repository or archive they plan to use. Repositories often specify preferred formats, folder structures, documentation standards and metadata fields. Aligning data packages with these requirements early helps avoid rework and deposit delays.

Principles of clean folder organisation

In practice, good data package organisation usually involves:

• Grouping related files into clear, logical folder structures.
• Using concise, consistent and meaningful file naming conventions.
• Separating data, documentation and code into distinct folders.
• Organising files in a way that reflects how the data are intended to be used.

Simple and transparent structures are generally more effective than deeply nested or complex folder systems.

Running a final technical review

Before preparing data for deposit, a final technical review should be carried out.

This typically involves:

• Opening files in standard software to confirm accessibility.
• Checking that documentation matches the data content.
• Verifying that links between data, code and metadata are correct.
• Ensuring that anonymised or access-controlled versions are clearly labelled.

Completing these checks before deposit helps streamline repository review processes and improves the overall quality and usability of shared data.