Deliverables are the tangible knowledge products that your cluster produces: journal articles, datasets, policy briefs, tools, training materials, and other research outputs. MARLO tracks each deliverable from its initial registration in the planning phase through actual production, dissemination, and QA validation. All deliverables are subject to Open Access and FAIR compliance requirements — MARLO enforces these during data entry so issues surface before the reporting deadline, not after.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/CCAFS/MARLO/llms.txt
Use this file to discover all available pages before exploring further.
What a deliverable contains
Each deliverable record captures both planning intent and actual evidence:| Field | Description |
|---|---|
| Title | Short, descriptive name of the knowledge product |
| Type | Category of output (e.g., journal article, dataset, tool, training material) |
| Expected year | The year in which delivery is planned or occurred |
| Dissemination channel | How and where the output is shared (e.g., CGSpace, institutional repository, conference) |
| DOI | Digital Object Identifier, required for Open Access compliance |
| License | Open license assigned (e.g., CC BY 4.0) |
| Repository handle / URL | CGSpace link or external repository URL |
| FAIR indicators | Findable, Accessible, Interoperable, Reusable — each assessed separately |
| Cross-cutting markers | Gender, youth, climate change, nutrition (scored 0–2) |
| Linked outcomes | Outcome and impact pathway elements this deliverable contributes to |
Deliverable lifecycle
Deliverables move through four states across the annual cycle: Planned → In progress → Complete → QA validated- In the POWB phase you register the deliverable with a type, expected year, and description.
- During UpKeep you update progress status and any emerging dissemination details.
- In the Annual Report phase you upload the artifact, add the DOI or CGSpace link, and confirm the Open Access license.
- After submission, QA reviewers validate the metadata and compliance evidence.
MARLO’s program-wide Open Access compliance target is ≥ 95% of validated deliverables per year. This threshold is tracked in the BI dashboard and reviewed by PMU and QA teams at the close of each Annual Report phase.
FAIR compliance tracking
MARLO supports the FAIR principles as a structured compliance layer on each deliverable:- Findable — The output has a persistent identifier (DOI or handle) and is indexed in a discoverable repository.
- Accessible — The output is retrievable via an open or controlled-access protocol (e.g., CGSpace landing page).
- Interoperable — Metadata uses standard vocabularies and formats (Dublin Core, AGRIS, etc.).
- Reusable — The output has a clear open license and sufficient provenance metadata.
Register a deliverable in the planning phase
Open your cluster's deliverables section
Navigate to Projects → select your cluster → Deliverables in the left submenu. The active phase chip at the top of the page confirms you are working in the POWB phase.
Add a new deliverable
Click Add deliverable. A new expandable block appears in the deliverable list.
Fill in core metadata
Enter the title, select the deliverable type, set the expected year, and choose a dissemination channel. These fields are required to save.
Link to outcomes
In the Outcome contributions section, select the project outcome and impact pathway element that this deliverable supports. This linkage is required for completeness scoring.
Set cross-cutting markers
Score the deliverable’s relevance to gender, youth, climate change, and nutrition (0 = not targeted, 1 = significant, 2 = principal). If none apply, select Not applicable.
Update a deliverable in the reporting phase
When the Annual Report phase opens, return to the deliverable to add evidence:Open the deliverable in the AR phase
Switch the phase chip to AR [year], then open Projects → your cluster → Deliverables. Find the deliverable in the list and expand it.
Confirm or update status
Set the deliverable status to Complete if it was produced, or update it to Cancelled or Continues next phase as appropriate.
Add Open Access evidence
Enter the DOI and the CGSpace handle or URL. Select the open license (e.g., CC BY 4.0). These fields are required for Open Access compliance.
Upload supporting files (if applicable)
For outputs not yet deposited in a repository, you can attach the file directly. CGSpace deposit remains the preferred dissemination path for permanent open-access archiving.
Complete FAIR fields
Mark each FAIR dimension as compliant or note the issue. The platform calculates a per-deliverable FAIR score visible on the BI dashboard.
Open Access compliance in QA
During the QA phase, reviewers check:- That the DOI resolves and matches the title on record.
- That the license is an approved open license (CC BY 4.0 is preferred).
- That the CGSpace deposit is complete and publicly accessible.
- That FAIR metadata fields are populated correctly.