Public Data Service
A fully functional, maintained online data service such as a knowledgebase or deposition repository provided as a live service to the community for data querying and retrieval.
Catalogue v1.2.0
All 24 non-traditional research artefact types across 5 categories. You can search, filter by category, or filter by whether active credit-capture infrastructure exists.
24 of 24 artefact types
A fully functional, maintained online data service such as a knowledgebase or deposition repository provided as a live service to the community for data querying and retrieval.
A structured, annotated biological record synthesized from literature, community knowledge, or secondary analysis, rather than direct primary experimentation by the curator.
Ensuring a dataset has comprehensive metadata, in a standard format, with supports like clear licensing to ensure it is findable, accessible, interoperable, and reusable (FAIR).
A packaged, structured dataset resulting directly from primary laboratory experimentation or other form of first hand data capture, deposited into a public archive for community access and reuse.
A formal document outlining how research data will be collected, stored, secured, and shared during and after a project.
Instructional content designed to teach specific skills, ranging from standalone slides and recordings to comprehensive e-learning modules.
A comprehensive, formalized unit of teaching that is part of a standardized academic curriculum, typically carrying formal academic credit (such as ECTS) and forming part of a wider degree programme. Contrasts with standalone training materials by requiring formal accreditation and structured assessment.
A preserved, versioned, and citable educational resource packaged with comprehensive metadata, open licensing, and a persistent identifier.
Chained together logical learning pathways of materials designed for an overall educational purpose and progression.
A scholarly output primarily authored by a student under the direct mentorship of the researcher.
User manuals, developer documentation, or interactive notebooks that explain how to deploy and use the software.
The functional source code, scripts, or algorithms developed to execute scientific analyses, actively maintained under version control.
A bundled, standardized, and easily installable collection of code, libraries, and dependencies designed to perform specific scientific functions within a broader programming ecosystem.
A preserved, versioned, and citable software release equipped with comprehensive documentation, a DOI, open licensing, and containerisation for portability.
A strategic document detailing the architecture, lifecycle, maintenance, and long-term sustainability of a software tool or service.
A live or recorded presentation showcasing the functionality, interface, and practical application of a software tool to an audience.
Formal documents guiding network efforts, outlining strategic direction, or reporting on community engagement metrics.
The captured materials resulting from organising a community event, seminar, or conference.
Accessible content designed to translate complex scientific outcomes for the general public or broad stakeholders.
Essential paperwork required for institutional and legal research operations, such as ethics approvals or financial audits.
A concise summary of research findings formatted to advise government, institutional policy, or standardisation bodies.
The comprehensive, authored document detailing a proposed research project, its methodology, and budget.
The formal, critical evaluation document of a scholarly manuscript, which is sometimes published transparently alongside the article.
The critical assessment document or panel summary provided to a funding body regarding the viability of a grant application.