MétaCan
Menu
Back to cohort
Record W2964692446 · doi:10.1080/0907676x.2019.1645189

Tenacious technophobes or nascent technophiles? A survey of the technological practices and needs of literary translators

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

VenuePerspectives · 2019
Typearticle
Languageen
FieldArts and Humanities
TopicTranslation Studies and Practices
Canadian institutionsUniversity of Ottawa
Fundersnot available
KeywordsSociology

Abstract

fetched live from OpenAlex

In a context of increasing investigation of technology use by translators of pragmatic texts, there appears to be an assumption that literary translation is a unique practice and that digital tools designed to improve the productivity of non-literary translators have few applications in the literary domain. The present study seeks to challenge that assumption and find out what tools and resources literary translators actually employ in practice; how they interact with source and target texts, manage terminology, and conduct linguistic research; and what their needs may be for training in this area. Members of the Literary Translators’ Association of Canada were invited to complete an anonymous self-administered online questionnaire on their use of technology and digital resources. Results indicate that literary translators make extensive use of standard tools and electronic resources but little use of more specialized technology. However, it was also found that some respondents make ‘creative’ use of specialized technology and that literary translators have a broad range of needs, particularly for linguistic and cultural research, leading to a recommendation that future investigation in this area focus on the improvement of digital tools and resources to support literary translators in meeting their ad hoc needs.

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 categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Qualitative · Consensus signal: Qualitative
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.354
Threshold uncertainty score0.366

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.0000.001
Scholarly communication0.0000.000
Open science0.0000.000
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.048
GPT teacher head0.280
Teacher spread0.232 · 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