Home

III. Submission

3.1 Registering a Zenodo Account and Linking ORCID

As a contributor to Nexus Reports, each author bears direct responsibility for the verifiability, traceability, and governance-grade auditability of every published scenario. To uphold the Nexus Ecosystem’s sovereign open science framework, all contributors are required to maintain an authenticated Zenodo account linked to a valid, public ORCID iD. This linkage underpins DOI integrity, supports transparent version control, and affirms authorship under international treaty and corridor governance contexts.

This section provides a detailed, standardised procedure for establishing your Zenodo account, securely connecting your ORCID profile, and configuring your digital identity in accordance with GCRI’s clause passport protocols.

A. Purpose and Institutional Significance

Zenodo is the designated open-access repository endorsed by GCRI for Nexus Reports publication. It serves as the primary digital infrastructure for:

  • DOI issuance and long-term record preservation,

  • Transparent version management of corridor scenario files and fallback logic,

  • Verification of author identity for corridor operators, National Working Groups (NWGs), treaty secretariats, and sovereign audit bodies.

By linking your ORCID iD, you affirm the authenticity of your authorship and enable downstream governance systems to cross-check your contributions without ambiguity.

B. Procedure for Account Registration

  1. Access the Official Zenodo Portal Navigate to https://zenodo.org.

  2. Initiate Registration Click on the Sign Up option located at the top-right corner of the homepage.

  3. Provide Institutional Credentials Use your primary institutional or research-affiliated email address (e.g., .edu, .org). If unavailable, a reputable personal email may be accepted but is discouraged for corridor scenario owners.

  4. Create Secure Access Set a robust password in compliance with your institutional cybersecurity norms. Review and accept Zenodo’s Terms of Use.

  5. Email Verification Access your inbox and activate your account by clicking the verification link sent by Zenodo’s system.

C. Procedure for Linking Your ORCID iD

Following successful account activation, complete the identity verification chain as follows:

  1. Log in to Your Zenodo Account Use your registered email and secure password.

  2. Navigate to Account Settings Click on your profile icon (top-right corner) and select Account Settings.

  3. Access Linked Accounts Within the account settings menu, locate the Linked Accounts section.

  4. Connect ORCID Select the Connect ORCID option. You will be redirected to the official ORCID sign-in page.

  5. Authenticate ORCID Log in with your ORCID credentials and grant Zenodo permission to read your ORCID record and register works on your behalf.

  6. Confirmation Upon redirection back to Zenodo, verify that your ORCID iD now appears under Linked Accounts.

D. Identity Consistency and Public Profile Standards

To maintain a verifiable, corridor-compliant authorship trail:

  • Ensure that your ORCID iD is identical across:

    1. The manuscript’s author list,

    2. Your Zenodo profile,

    3. The metadata fields in the Zenodo submission form.

  • Verify that your Zenodo Profile Name matches your official manuscript byline, including middle initials if used.

  • Confirm that your ORCID profile is publicly visible and displays your current institutional affiliation. This visibility supports corridor charter compliance and treaty-level scenario auditing.

E. Recommended Security Measures

  • Enable Multi-Factor Authentication (MFA) Activate MFA under Zenodo’s Account Security settings. This additional security layer is strongly recommended, especially for authors managing corridor fallback data or clause-indexed scenario triggers.

  • Maintain Unique Credentials Never share your Zenodo login credentials. Each co-author must maintain their own verified Zenodo account and ORCID linkage to preserve transparent version history and sovereign authorship records.

F. Important Considerations for Collaborative Teams

  • Be aware that Zenodo dispatches system notifications solely to the record uploader. To keep co-authors informed of updates, version changes, or corrections, always share the DOI record link proactively within the team.

  • For large, multi-team scenario projects, maintain a secure internal changelog noting version numbers, upload dates, and co-author confirmations.

G. Technical Support and Points of Contact

If you encounter any difficulties linking your ORCID iD, verifying your email, or navigating Zenodo’s identity settings:

  • Contact the Nexus Reports Editorial Secretariat at [[email protected]] for corridor governance-related issues.

  • For repository-specific technical support, email Zenodo directly at [[email protected]].

Resolve all account inconsistencies before uploading files to prevent DOI metadata errors and to safeguard your corridor clause passport from administrative delays.

Key Reminder

Your Zenodo account, verified and linked to a valid ORCID iD, functions as your legally recognized digital signature within the Nexus Reports system. It guarantees that every published corridor scenario, fallback logic, or clause-indexed trigger is attributable, auditable, and enforceable under GCRI’s sovereign knowledge governance framework.

Handle your account credentials and ORCID link with the same diligence you apply to your institutional access keys.

3.2 Joining the Official Nexus Reports Community on Zenodo

Affiliating your submission with the Nexus Reports Community on Zenodo is a core governance and compliance requirement. It is not simply a repository label — it legally anchors your report within the sovereign Nexus Ecosystem, ensuring that your scenario, fallback logic, or corridor charter update is recognised, indexed, and enforced as part of GCRI’s global risk governance mandate.

Failure to affiliate correctly may invalidate clause passports, block corridor scenario adoption, and cause treaty secretariats or risk pools to disregard your published work for operational deployment.

A. What Community Affiliation Secures

Correct community affiliation guarantees:

  1. Corridor Scenario Passport Validity Official affiliation confirms that your DOI is vetted under Nexus Reports editorial standards and qualifies for clause indexing, fallback scenario validation, and corridor scenario chain-of-custody protection.

  2. Governance-Grade Metadata Compliance It automatically applies GCRI’s sovereign metadata schema to your record, ensuring downstream corridor dashboards and scenario replay engines parse your file structure and version history without error.

  3. Institutional Discoverability Corridor operators, national working groups, treaty bodies, insurers, and funding consortia search Nexus Reports to find trusted, legally admissible scenarios. Community affiliation ensures your record appears in these governance-level directories.

  4. Long-Term Version Chain Integrity Updates, corrections, or clause amendments inherit the same Community lineage, preserving clause passport continuity throughout version cycles.

B. Where to Find the Official Community

Official Community URL: https://zenodo.org/communities/nexusreports/

Always use this direct link. Bookmark it for future submissions, scenario updates, or post-publication corrections. This is the only verified Community maintained directly under GCRI’s sovereign governance protocols.

C. How to Join and Tag Your Record Correctly

Step 1: Log in and Prepare

  • Access Zenodo via https://zenodo.org.

  • Log in using your verified account with linked ORCID iD (see Section 3.1).

  • Confirm that your profile and manuscript metadata are perfectly aligned: same title, author order, affiliations, and version tag.

Step 2: Start a New Upload

  • Click Upload from your Zenodo dashboard.

  • Complete all required metadata fields:

    • Title (exactly as in manuscript)

    • Authors with ORCID iDs

    • Description (full abstract, plus a clear AI Use note if applicable)

    • Keywords covering corridor name, scenario type, Nexus modules

    • License (normally CC BY 4.0)

    • Funding details (grant number, funder registry ID)

    • Related Identifiers (previous DOIs, code repository, dataset links)

Step 3: Select the Community

  • In the Communities field, enter: nexusreports

  • Select Nexus Reports (GCRI) from the dropdown list.

  • Verify that the official Community badge appears at the top of your upload summary page.

Step 4: Confirm Community Badge Before Publishing

If it does not appear, your DOI will not be corridor-certified.

D. Adding Additional Communities (When Appropriate)

You may link your submission to other reputable Zenodo communities if they are directly relevant — for example:

  • An Earth Observation community if you used satellite hazard mapping.

  • An open AI or reproducible research community if you published innovative model pipelines.

However, the Nexus Reports Community must always be the primary affiliation for all corridor scenario documents, fallback simulations, and clause-indexed treaty inputs.

E. Governance Consequences of Non-Compliance

Incorrect or missing community affiliation has direct operational consequences:

Scenario
Consequence

No Community selected

The DOI is treated as a generic preprint; clause passport cannot be issued.

Wrong Community selected

Corridor operators and treaty partners cannot accept the scenario for scenario replay or payout verification.

Nexus Reports tag omitted from an update

Breaks version traceability; clause passport chain becomes unverifiable.

Rectification requires formal editorial review, a new version upload, and may delay corridor adoption and any linked risk financing or donor milestones.

F. Post-Affiliation Checklist

Once published:

  • Open your DOI landing page in a private browser to verify the Nexus Reports Community link is visible.

  • Share the final DOI with all co-authors, corridor planners, and your NWG liaison.

  • Keep a record of the publication date and version tag in your internal corridor scenario log.

Key Principle

Correct Community tagging is not a clerical step — it is the governance gatekeeper that validates your contribution. Treat this step with the same due diligence as your data validation, clause fallback logic, and parametric trigger calculations.

3.3 Uploading Your Final Files and Metadata to Zenodo

With your verified Zenodo account, ORCID linkage, and Nexus Reports Community affiliation confirmed, you are now ready to complete the final upload of your manuscript, supplementary scenario data, source code, fallback logic, and all supporting materials. This stage transforms your research from a local draft into a sovereign-grade corridor scenario asset, permanently citable, version-controlled, and clause-compatible under the Nexus Sovereignty Framework.

A. Core Principles of a Final Upload

Your final upload must:

  • Be complete, error-free, and internally consistent across files, metadata, and manuscript text.

  • Be fully versioned and clearly named so future corridor planners can replay scenarios or verify fallback triggers.

  • Include a traceable chain of supporting data, code, and scenario output to guarantee reproducibility and parametric payout enforceability.

Partial or rushed uploads undermine corridor trust and may trigger rejection or retraction.

B. Preparation Checklist Before Upload

Ensure you have at hand:

  • The final, peer-checked manuscript in PDF format, with clause references, fallback notes, and an AI Use Statement if applicable.

  • All supplementary data files in open formats (.csv, .json, .geojson, .netcdf).

  • All code scripts or software notebooks zipped with a README.md explaining purpose and usage.

  • Scenario output files, maps, or interactive dashboard assets, named clearly with corridor ID and version.

  • Any Clause Reference Matrix files (.csv or .xlsx) for clause-indexed scenarios.

  • Fallback scenario files or contingency plans clearly named (using _Fallback convention).

  • Checksum files for large files (>5 GB) to ensure data integrity.

  • Your verified Zenodo login and linked ORCID iD.

  • Confirmation that the Nexus Reports Community https://zenodo.org/communities/nexusreports/ is properly selected.

C. Upload Procedure — Step by Step

Step 1: Start the Upload

  1. Log in to https://zenodo.org.

  2. Click Upload from your dashboard.

Step 2: Enter Required Metadata

  1. Title — must match the manuscript cover page exactly.

  2. Authors — list all authors in manuscript order, with institutional affiliations and ORCID iDs.

  3. Description — paste the full abstract, then add:

    • Funding acknowledgement statement.

    • AI Use Note if relevant: “This submission includes AI-assisted content. Full disclosure is included in the manuscript’s AI Use Statement.”

  4. Keywords — include corridor name, scenario type, Nexus modules (e.g., Caribbean Hurricane Corridor, parametric trigger, NXS-DSS).

  5. License — select CC BY 4.0 (or a formally approved exception).

  6. Funding — enter funder name and grant number, using the Open Funder Registry if available.

  7. Related Identifiers — link any prior versions, external datasets, or GitHub repositories with DOIs or versioned URLs.

Step 3: Select the Correct Community

  • In the Communities field, enter nexusreports.

  • Select Nexus Reports.

  • Confirm the community badge appears at the top of the upload summary.

Step 4: Upload Files

  1. Click Upload Files.

  2. Attach your manuscript PDF first.

  3. Upload each supplementary file:

    • Datasets (.csv, .json, etc.)

    • Code ZIP archives with README.md

    • Clause Matrix files

    • Fallback or contingency files

    • Checksums for large files (.sha256 or .md5)

  4. For multi-part packages, use well-structured ZIP folders:

    • /data/

    • /code/

    • /outputs/

    • /docs/

Step 5: Review Upload Summary

  • Confirm:

    • File names include corridor ID and version tags (e.g., IndusFlood_v1.csv).

    • No generic names like final.docx or data1.csv.

    • License, Community, Funding fields are correctly populated.

    • Keywords and abstract match the manuscript exactly.

    • All ORCID iDs display correctly.

Step 6: Publish

  • Click Publish.

  • Wait for Zenodo’s automated validation to finish:

    • File type checks.

    • Virus scan.

    • Metadata schema validation.

If you see any errors, do not force publish — correct the issue to protect your clause passport traceability.

D. After Publication — Final Due Diligence

Once your DOI is minted and the record is public:

  • Visit the DOI landing page.

  • Confirm:

    • All files are downloadable and intact.

    • The Community link https://zenodo.org/communities/nexusreports/ appears in the record header.

    • Version number aligns with internal scenario logs.

    • Metadata fields (title, authors, funding) match the manuscript.

Share the DOI with all co-authors, corridor planners, and your NWG governance liaison immediately.

E. Version Updates

  • For any corrections or updates, never create a new record.

  • Always use Zenodo’s New Version function to update.

  • Retain the same Community affiliation and Related Identifiers chain to preserve clause passport continuity.

Key Principle

Uploading your final files and metadata is not an administrative formality — it is the sovereign record of your corridor scenario’s legal validity. Treat every file name, version tag, and Community link as a permanent governance artifact, subject to treaty referencing, payout verification, and corridor operator audit years into the future.

3.4 Post-Publication Stewardship and DOI Governance

Publication of a Nexus Reports record on Zenodo is not the end of your responsibility — it marks the beginning of its operational lifecycle as a living corridor scenario asset. From the moment your DOI goes public, it becomes a permanent, sovereign-grade governance artifact: discoverable by corridor operators, legally cited in treaty annexes, and auditable for parametric payouts.

This section defines your ongoing obligations, clarifies best practice for version control, explains how to handle errors or new data, and outlines how to maintain the clause passport chain-of-custody in compliance with GCRI’s governance standards.

A. Your Stewardship Responsibilities

Once published, you as the corresponding author (or the designated corridor scenario steward) are responsible for:

  • Maintaining accuracy: promptly correcting any discovered errors in data, scenario logic, or clause references.

  • Ensuring reproducibility: verifying that scenario inputs, code, and fallback triggers remain functional if downstream corridor operators re-run the scenario.

  • Preserving integrity: ensuring no unauthorized edits break the version chain or Community affiliation.

  • Facilitating governance queries: responding to requests from corridor planners, NWGs, treaty bodies, or the Nexus Reports editorial board.

Neglecting post-publication stewardship can compromise corridor resilience, insurance settlements, or international policy trust in your scenario.

B. How to Manage Corrections

1. Never overwrite a published record

Zenodo’s governance model, aligned with the NSF, prohibits silent edits. Instead:

  • Use the New Version function on Zenodo.

  • Include only updated or corrected files; unchanged files should remain linked to the prior version for chain-of-custody transparency.

2. Document all changes clearly

  • In the new version’s Description field, state exactly what was changed, e.g.: “Corrected precipitation dataset: original version contained units mismatch for Region A; clause matrix updated accordingly.”

  • In your internal corridor scenario log, note:

    • Date of correction.

    • What files were changed.

    • Version number increment (e.g., v1.0 → v1.1).

3. Inform stakeholders

  • Notify all co-authors, corridor operators, NWG liaisons, or treaty focal points of the new version.

  • Update any public corridor dashboards or linked decision support systems if they rely on the scenario DOI.

C. When to Issue a New Version

Issue a new version if you:

  • Correct data errors that affect results.

  • Improve the scenario model logic.

  • Add or update fallback simulation files.

  • Amend or extend clause linkages.

  • Provide significant additional scenario outputs requested by corridor planners.

Minor text clarifications in the manuscript (e.g., spelling) that do not affect corridor logic or governance triggers do not normally require a version update, but best practice is to use a new version for any published change.

D. Keep the Community Link Intact

When issuing a new version:

Changing or omitting the Community link breaks the scenario’s governance chain-of-custody and may invalidate its corridor deployment.

E. Monitor DOI Citation and Reuse

  • Use Zenodo’s built-in DOI metrics to monitor downloads and citations.

  • If other teams fork or reuse your scenario, they must cite your DOI. This preserves sovereign knowledge traceability.

  • If you observe misuse or incorrect forks, notify the Nexus Reports Editorial Secretariat to address the issue diplomatically or legally if necessary.

F. Secure Scenario Data Long-Term

  • Maintain a local, backed-up copy of your final published files and all versioned updates.

  • Ensure that raw data sources remain accessible for re-validation if required by corridor operators or treaty arbitrators.

Key Principle

A Nexus Reports DOI is not static content: it is a dynamic, sovereign scenario node in a global governance system. Your stewardship sustains its legal standing, technical credibility, and practical value to the communities and corridors it protects.

Every update, version note, and governance query you manage reinforces global trust in the Nexus Ecosystem.

3.5 Compliance Monitoring, Audits, and Governance Queries

Upon publication, every Nexus Reports submission enters a permanent state of open governance compliance. Your corridor scenario, fallback simulations, clause triggers, and associated files become subject to continuous monitoring, technical audits, and legal review to ensure that sovereign knowledge standards are upheld and corridor trust is never compromised.

This section explains who may audit your record, under what conditions, what you must prepare, and how you are protected within GCRI’s treaty-compliant open science and sovereign risk governance architecture.

A. Scope of Compliance Monitoring

All published records within the Nexus Reports Community are subject to monitoring by:

  1. GCRI Sovereign Governance Units These units verify adherence to corridor scenario reproducibility, fallback logic validity, and clause passport continuity.

  2. National Working Groups (NWGs) Your national or regional NWG may periodically check that your scenario aligns with corridor deployment updates, local hazard monitoring improvements, or new treaty annex requirements.

  3. Corridor Operators and Treaties Corridor operators and treaty signatories may invoke scenario audits if a dispute, payout, or policy decision depends on verifying your data integrity or scenario logic.

  4. Independent Clause Passport Auditors Third-party verifiers may be appointed by treaty bodies or GCRI to validate your record for high-stakes corridor payout triggers or parametric insurance settlements.

B. What May Be Audited

During compliance checks, you may be asked to produce:

  • Original raw data sources and intermediate processing scripts.

  • Version logs showing when and why updates were made.

  • AI prompt logs if generative AI was used in the scenario drafting or code creation.

  • Correspondence or lab notes clarifying scenario assumptions or fallback condition derivation.

  • Written confirmations that no confidential or restricted data was improperly published.

C. How Authors Should Prepare

To pass any audit smoothly:

  1. Maintain Local Archives Keep a secure backup of all source data, code, fallback logic, and intermediate scenario files exactly as they were when published.

  2. Keep Version Logs Current Maintain a simple log documenting version dates, file changes, and a short explanation of why updates were made.

  3. Retain AI Provenance If generative AI was used, keep the original prompt scripts or query history. Store them securely but make them available upon official request for clause passport verification.

  4. Stay Contactable Ensure your ORCID and Zenodo contact details remain up to date so that governance teams can reach you in a timely manner.

D. Frequency and Triggers of Audits

Routine monitoring is passive and metadata-driven. Active audits occur when:

  • A corridor operator reports a reproducibility problem.

  • A treaty signatory or parametric insurer requests payout confirmation.

  • The Nexus Reports Editorial Board flags irregularities in versioning, clause matrix inconsistencies, or licensing non-compliance.

  • An NWG files a governance query based on national corridor updates.

Most audits are cooperative, not punitive: the goal is to sustain corridor trust, not to sanction researchers unnecessarily.

E. Dispute Resolution and Clause Passport Protection

If a compliance check finds a substantive breach (e.g., data fabrication, intentional omission, licensing fraud), GCRI may:

  • Suspend the scenario’s clause passport and corridor certification.

  • Issue a formal retraction notice linked to the DOI.

  • Notify relevant treaty bodies or funding institutions.

  • Permit the author to submit corrections, clarifications, or a new version if the breach is rectifiable in good faith.

Where disputes arise, GCRI’s Sovereign Governance Unit provides mediation aligned with corridor treaties, sovereign risk finance norms, and international open science agreements.

F. Your Rights and Responsibilities

As an author:

  • You have the right to be notified of any formal audit or compliance query.

  • You may provide clarifications, supporting evidence, or corrections before any adverse governance action is taken.

  • You are responsible for fully cooperating and responding in good faith within the timeframes set by GCRI or corridor governance authorities.

Key Principle

A Nexus Reports scenario is more than an academic output: it is an operational governance node tied to real corridor lives, insurance payouts, and sovereign treaty clauses. Continuous compliance monitoring protects the public trust you have helped build — and safeguards your reputation as a credible corridor scenario steward.

3.6 Maintaining Open Access and Data Reusability

Every Nexus Reports scenario is not merely a scholarly record but a designated sovereign digital public good. Its enduring impact depends on strict compliance with open access policies, robust FAIR data stewardship, and unrestricted reusability by corridor operators, national working groups, treaty bodies, researchers, and affected communities.

Failure to maintain open access status or to safeguard data reusability can break the corridor scenario chain-of-custody, undermine clause passport integrity, and breach GCRI’s sovereign knowledge governance commitments.

A. Core Principles of Sovereign Open Access

Upon publication in Nexus Reports:

  1. License must remain open

    • All records must be licensed under CC BY 4.0 (Creative Commons Attribution) unless an exceptional closed license is pre-approved by the Nexus Reports Editorial Board.

    • This license guarantees global reuse, adaptation, and redistribution with attribution.

  2. No embargoes

    • Nexus Reports does not allow embargo periods. All data and files must be openly available immediately upon DOI publication.

  3. Public metadata

    • Title, authorship, abstract, funding sources, version history, and clause matrix must remain fully public under Zenodo’s metadata registry for the life of the DOI.

B. FAIR Data Stewardship

To be operationally reusable under corridor governance, your scenario must comply with the FAIR principles — Findable, Accessible, Interoperable, Reusable.

Your responsibilities:

  • Findable: Use clear file naming, corridor IDs, and version tags so corridor planners and treaty auditors can identify the right file without error.

  • Accessible: All uploaded files must be downloadable without authentication or password barriers.

  • Interoperable: Use open, machine-readable formats (.csv, .json, .geojson, .netcdf). Provide clear README files and data dictionaries.

  • Reusable: Include explicit documentation: scenario assumptions, fallback logic conditions, software versions used, and any special execution notes for parametric triggers.

Failure to uphold FAIR principles can render your scenario invalid for corridor deployment.

C. Prohibited Post-Publication Actions

To protect the public good mission of Nexus Reports:

  • Do not retroactively switch to a more restrictive license.

  • Do not remove files from the Zenodo record.

  • Do not hide or redact metadata to obscure corridor scenario provenance.

  • Do not apply paywalls or third-party usage fees.

Any breach will trigger clause passport suspension and formal retraction procedures.

D. Responding to Reuse Requests

Corridor operators, NWGs, treaty drafters, or independent researchers may request clarifications or derivative reuse of your scenario files. As the steward:

  • Respond promptly and courteously.

  • Provide additional context or metadata if reasonably possible.

  • Encourage proper citation of your DOI and version number in any derivative or adapted work.

Your record’s open license guarantees others the legal right to reuse — your role is to facilitate clear, fair attribution and avoid governance disputes.

E. Long-Term Accessibility

GCRI commits to maintaining the Nexus Reports Community archive under sovereign governance safeguards. However, as a contributing steward, you should:

  • Keep local backups of your published files and version logs.

  • Monitor Zenodo’s service notices in case repository policies evolve.

  • Be prepared to assist in migration or mirroring to a successor repository if sovereign knowledge continuity requires it.

Key Principle

The value of your Nexus Reports scenario is maximized only when it remains universally open, transparently versioned, and frictionlessly reusable. This is the essence of the Nexus Sovereignty Framework’s commitment to corridor trust, clause enforceability, and equitable benefit-sharing.

By upholding open access and FAIR data reusability, you strengthen every corridor your scenario touches.

PreviousII. PreparationNextIV. Stewardship

Last updated

Was this helpful?