MétaCan
Menu
Back to cohort
Record W6949213105 · doi:10.5281/zenodo.13242503

Alliance Software Management Plan (SMP) Template

2024· article· en· W6949213105 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueZenodo (CERN European Organization for Nuclear Research) · 2024
Typearticle
Languageen
FieldArts and Humanities
TopicLibraries and Information Services
Canadian institutionsToronto Dementia Research Alliance
Fundersnot available
KeywordsPlan (archaeology)SoftwareSoftware project managementAllianceSoftware developmentSoftware peer reviewSoftware as a serviceSoftware review

Abstract

fetched live from OpenAlex

Software has become an essential part of modern research and is increasingly recognized as an important output of research. Despite years of wide adoption of Data Management Plans (DMPs) to ensure good data management practices are followed, in Canada there were currently no clear guidelines that instruct various stakeholders how to plan for a piece of software to be properly developed, maintained, shared, and reused. To address this gap, the Alliance launched the Alliance Software Management Plan (SMP) Template. A Software Management Plan (SMP) details how a software project is developed, maintained, and curated, ensuring long-term accessibility and usability. The SMP can help funders to encourage, support and promote software recognition and good practices (e.g., FAIR4RS), facilitate culture change and, support communities, ensuring consistent adherence to certain software management standards and policies. It can also support and upskill researchers to develop higher-quality software, which will likely be an important part of a researcher’s portfolio in the future.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScience and technology studies, Scholarly communication, Insufficient payload (model declined to judge)
Consensus categoriesInsufficient payload (model declined to judge)
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Other · Consensus signal: none
Teacher disagreement score0.838
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0020.000
Scholarly communication0.0040.001
Open science0.0010.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0760.027

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.055
GPT teacher head0.223
Teacher spread0.168 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it