MétaCan
Menu
Back to cohort
Record W2972408874 · doi:10.1108/lht-03-2019-0058

Supporting successful data sharing practices in earthquake engineering

2019· article· en· W2972408874 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.

Bibliographic record

VenueLibrary Hi Tech · 2019
Typearticle
Languageen
FieldComputer Science
TopicResearch Data Management Practices
Canadian institutionsUniversity of Alberta
Fundersnot available
KeywordsData curationData sharingOriginalityKnowledge managementCurriculumQualitative propertyInformation sharingKnowledge sharingData managementComputer scienceQualitative researchBusinessData scienceWorld Wide WebPolitical scienceSociologyDatabase

Abstract

fetched live from OpenAlex

Purpose Prior studies identified a need for further comparison of data-sharing practices across different disciplines and communities. Toward addressing this need, the purpose of this paper is to examine the data-sharing practices of the earthquake engineering (EE) community, which could help inform data-sharing policies in EE and provide different stakeholders of the EE community with suggestions regarding data management and curation. Design/methodology/approach This study conducted qualitative semi-structured interviews with 16 EE researchers to gain an understanding of which data might be shared, with whom, under what conditions and why; and their perceptions of data ownership. Findings This study identified 29 data-sharing factors categorized into five groups. Requirements from funding agencies and academic genealogy were frequent impacts on EE researchers’ data-sharing practices. EE researchers were uncertain of data ownership and their perceptions varied. Originality/value Based on the findings, this study provides funding agencies, research institutions, data repositories and other stakeholders of the EE community with suggestions, such as allowing researchers to adjust the timeframe they can withhold data based on project size and the amount of experimental data generated; expanding the types and states of data required to share; defining data ownership in grant requirements; integrating data sharing and curation into curriculum; and collaborating with library and information schools for curriculum development.

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.002
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScholarly communication, Open science
Consensus categoriesScholarly communication, Open science
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.670
Threshold uncertainty score0.997

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0040.181
Open science0.0100.012
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

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.100
GPT teacher head0.368
Teacher spread0.268 · 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