Help > Artifact types
Artifact types
The archive and CCCURJ Flagship accept every type below. Each is written in LaTeX, gets an identifier and is labeled with its type.
| Type | What it contains |
|---|---|
| Research article | Original research: a question, the methods used, results and conclusions. |
| Literature review | A survey or synthesis of published work on a topic, organized to show what is known and what is open. |
| Replication study | A repeat of a published study or experiment, reporting whether and how its results hold. |
| Research note | A short report of a single result, observation, method or negative result. |
| Dataset | A data collection with a PDF data descriptor: how the data were gathered, what they contain and how to use them. |
| Software | Code, a tool or a model with a PDF software description: what it does, how to run it and how it was tested. |
| Research in progress | Work under way: the question, the planned or partial methods, and early results, shared for feedback. |
- Literature reviews: say how sources were found, and organize them by question.
- Replication studies: cite the original, note method changes, report results either way.
- Research notes: typically 2 to 6 pages. Negative results are welcome.
- Datasets and software: link the files and describe them in a short PDF. See below.
- Research in progress: post the finished work later as a new version.
Publishing work that is not a paper
A dataset you collected, code you wrote, a tool or a trained model can be published on its own, without a research paper around it. It gets a permanent identifier, a listing page, a citation and its own type label, and it can apply for peer review in CCCURJ Flagship like any article.
- Put the files in a public repository. Zenodo (free, gives a DOI and can archive a GitHub release), OSF, Dryad, or a public GitHub repository with a tagged release. CCCURJ links to the files; it does not host them. Give the files an open license in the repository: CC BY 4.0 or CC0 for data, an open-source license such as MIT for code.
- Write a short descriptor in LaTeX, usually 2 to 6 pages, from the CCCURJ template. It takes the place of the paper: it is what readers, editors and reviewers read, and it is released under CC BY 4.0 like everything on CCCURJ. Use the outline below.
- Submit it at Start a submission: choose Dataset or Software as the artifact type, paste the repository address in Data and code link (required for these types), and upload the LaTeX source and PDF of the descriptor.
- Optional: apply for peer review. Once it is announced, apply to CCCURJ Flagship. Reviewers judge whether the files are reachable, match the descriptor and are usable by someone else.
| Section | Dataset descriptor | Software description |
|---|---|---|
| Purpose | What the data are and why they were collected | The problem the software solves and who it is for |
| Methods | How, when and where they were gathered; instruments, sampling, ethics approval | How it works: approach, language, main dependencies |
| Contents | Files, variables, units, size and format | Features, inputs and outputs |
| Quality | Checks, cleaning and known gaps or errors | How it was tested, and any benchmarks |
| Use | A short example of loading and using the data | How to install and run it, with an example |
| Access | Link, version, license and how to cite the files | Link, release version, license and how to cite the code |
Something else, such as a lab protocol, a poster or a negative result? Write it up as a research note, or ask us which type fits.