MétaCan
Menu
Back to cohort
Record W2752188587 · doi:10.1007/s10502-017-9280-5

Using the cloud for records storage: issues of trust

2017· article· en· W2752188587 on OpenAlexfundno aff
Julie McLeod, Brianna Gormly

Bibliographic record

VenueArchives and Museum Informatics · 2017
Typearticle
Languageen
FieldComputer Science
TopicCloud Data Security Solutions
Canadian institutionsnot available
FundersSocial Sciences and Humanities Research Council of Canada
KeywordsCloud computingContext (archaeology)Cloud storageSustainabilityBusinessService (business)Process (computing)Internet privacyPublic relationsKnowledge managementComputer scienceMarketingPolitical scienceGeography

Abstract

fetched live from OpenAlex

Organisations cannot avoid working in the cloud and therefore records are being stored in the cloud either by design or by default. This raises important issues of trust in using third-party cloud service providers for storing records and digital archival collections. What factors contribute to trust in the decision-making process? What are the implications that archives and records (ARM) professionals need to understand and assess? This article discusses findings from an international research project that explored issues of trust in the context of the economics of cloud storage services. The most significant issues of trust to emerge were trust in the sustainability and continued economic viability of cloud storage services. Whilst anticipated costs savings (software, hardware, human) was the most frequently cited reason for adopting a cloud storage service, the research revealed that very few organisations or ARM professionals had actually estimated the costs, suggesting decision-making processes are inadequate. A basis for trust in cloud storage solutions might be found in the enhancement of checklists and other guidance documents for ARM professionals to address economic considerations.

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.052
metaresearch head score (Gemma)0.176
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Other · Consensus signal: none
Teacher disagreement score0.052
Threshold uncertainty score0.276

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0520.176
Meta-epidemiology (narrow)0.0000.001
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0020.003
Science and technology studies0.0130.017
Scholarly communication0.0250.024
Open science0.0020.010
Research integrity0.0040.007
Insufficient payload (model declined to judge)0.0070.002

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.051
GPT teacher head0.318
Teacher spread0.267 · 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.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreOther

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

Citations15
Published2017
Admission routes1
Has abstractyes

Explore more

Same venueArchives and Museum InformaticsSame topicCloud Data Security SolutionsFrench-language works237,207