SOURCE//PUBLIC / Companion series
Better repositories. A larger public return.
A development agenda for each source in the founding atlas. These are proposed improvements, not completed technical audits or findings of defects. Recommendations require a dated observation, a reproducible test and maintainer context before becoming an evaluated repository review.
Discoverability · Funding provenance · Version identity · Licensing clarity · Reproducibility · Preservation · Accessibility · Maintenance transparency.
Future reports will use pass, partial, fail, not tested and not applicable, with evidence for every result. No rankings or scores have been assigned at launch. Maintainers may submit corrections and responses through the existing journal submission workflow.
Publish coverage dates and machine-readable agency reporting gaps.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Reconcile legacy inventories with current agency reporting and retain redirects.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Separate software, data, APIs and funding records with explicit resource types.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Connect award identifiers to independently verified software releases.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Expose software-specific release identifiers and award-to-repository relationships.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Add persistent software output links with version and maintenance dates.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Provide typed software-output relationships and documented pagination.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Display executable access separately from downloadable source and licensing.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Connect packages to releases, support policies and award acknowledgments.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Make gateway tools discoverable with source, version and reuse metadata.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Give each tool an explicit code-availability and reproducibility statement.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Link award numbers to versioned software records and evidence of support.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Connect intramural accounts to extramural software discovery without conflating them.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Distinguish resources, code packages, services and underlying awards.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Standardize release-level citations, dependencies and maintenance status.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Expose award identifiers and reproducible installation pathways per tool.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Add structured package-level funder and award evidence where maintainers supply it.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Connect resource identities to version-specific software identifiers and funding evidence.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Keep dataset permissions distinct from software licensing and execution requirements.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Record immutable container digests, workflow versions and award provenance together.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Strengthen cross-links between awards, releases, repository moves and archived versions.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Publish coverage, update cadence and release-level provenance consistently.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Differentiate software from publications and link related outputs bidirectionally.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Make distribution conditions and source access explicit before download requests.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Keep archival releases, support windows and funding acknowledgments visible.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Describe licensing pathways without presenting every offering as open source.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Normalize software citation, installation and lifecycle metadata.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Connect each project to releases, stewardship and preservation destinations.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Preserve historical organization aliases and stable redirects when names change.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Help users compare distribution classes before choosing a catalog.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Make source availability and distribution eligibility prominent per record.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Link approved releases to development repositories and archival identifiers.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Connect software, measurement publications and reproducibility artifacts.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Add machine-readable citation, funding and lifecycle fields across repositories.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Distinguish software releases from accompanying datasets and documents.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Differentiate provisional and approved releases with persistent version evidence.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Make the authoritative release location explicit when mirrors exist.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Publish compatible component-version matrices and reproducible run examples.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Show source, executable, platform and license status as separate fields.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Provide release-level dependencies and validation examples for scientific models.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Connect funded projects, component releases and deployment requirements.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Maintain account ownership, redirects and project lifecycle metadata.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Display archival status and support commitments alongside release links.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Attach software purpose, release documentation and applicable validation limits.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Separate API data terms from client-code licenses and version guarantees.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Cross-link software with associated research and maintenance contacts.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Keep code, content and API discovery paths distinct and current.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Provide a discoverable bridge from policy guidance to released project inventories.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Expose release provenance, maintenance state and reproducible build information.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Make project-specific license and support conditions easy to compare.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Preserve funding evidence, canonical links and release citations in project metadata.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Improve portable metadata and archival links across hosted and self-hosted instances.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Distinguish concept DOIs from release DOIs and validate award references.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Connect intrinsic source identifiers to external funding and scholarly metadata.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.
Add linked award evidence without inferring funding from domain or topic.
Evaluation plan: sample representative records; document the current experience; test this proposal against the eight lenses; publish evidence and limitations. Success measure: a reader can trace funding, identify a release and understand reuse conditions with fewer unresolved steps. Status: proposed; implementation and outcomes not evaluated.