MétaCan
Menu
Back to cohort
Record W2470289662 · doi:10.7717/peerj-cs.86

Software citation principles

2016· article· en· W2470289662 on OpenAlexfundno aff
Arfon M. Smith, Daniel S. Katz, Kyle E. Niemeyer

Bibliographic record

VenuePeerJ Computer Science · 2016
Typearticle
Languageen
FieldDecision Sciences
TopicScientific Computing and Data Management
Canadian institutionsnot available
FundersScience and Technology Facilities CouncilEngineering and Physical Sciences Research CouncilUniversity of California, Los AngelesUniversity of California, Santa BarbaraUniversity of Illinois at Urbana-ChampaignNational Institute of Standards and TechnologyNational Institutes of HealthUniversity of ManchesterUniversity of St AndrewsLouisiana State UniversityInstitute for Quantitative Social Science, Harvard UniversityCity University of New YorkOregon State UniversityCardiff Metropolitan UniversityJohns Hopkins UniversityNational Science FoundationTRIUMFUniversity of California, DavisGraduate CenterHarvard UniversityCERNSmithsonian Institution
KeywordsCitationAcknowledgementComputer scienceSoftwareSoftware peer reviewSet (abstract data type)Working groupWork (physics)Data scienceKnowledge managementSoftware developmentSoftware engineeringWorld Wide WebSoftware constructionEngineering

Abstract

fetched live from OpenAlex

Software is a critical part of modern research and yet there is little support across the scholarly ecosystem for its acknowledgement and citation. Inspired by the activities of the FORCE11 working group focused on data citation, this document summarizes the recommendations of the FORCE11 Software Citation Working Group and its activities between June 2015 and April 2016. Based on a review of existing community practices, the goal of the working group was to produce a consolidated set of citation principles that may encourage broad adoption of a consistent policy for software citation across disciplines and venues. Our work is presented here as a set of software citation principles, a discussion of the motivations for developing the principles, reviews of existing community practice, and a discussion of the requirements these principles would place upon different stakeholders. Working examples and possible technical solutions for how these principles can be implemented will be discussed in a separate paper.

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.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.092
metaresearch head score (Gemma)0.213
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch, Scholarly communication
Consensus categoriesnone
DomainCandidate signal: Reporting · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.978
Threshold uncertainty score0.485

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0920.213
Meta-epidemiology (narrow)0.0020.002
Meta-epidemiology (broad)0.0030.004
Bibliometrics0.0170.014
Science and technology studies0.0140.033
Scholarly communication0.0220.027
Open science0.0070.015
Research integrity0.0150.015
Insufficient payload (model declined to judge)0.0100.011

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.201
GPT teacher head0.379
Teacher spread0.177 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

Study designTheoretical or conceptual
DomainReporting
GenreMethods

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations269
Published2016
Admission routes1
Has abstractyes

Explore more

Same venuePeerJ Computer ScienceSame topicScientific Computing and Data ManagementFrench-language works237,207