MétaCan
Menu
Back to cohort
Record W2051546532 · doi:10.1057/jit.2014.5

Design for Maintenance: How Kms Document Linking Decisions Affect Maintenance Effort and Use

2014· article· en· W2051546532 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

VenueJournal of Information Technology · 2014
Typearticle
Languageen
FieldComputer Science
TopicInformation Architecture and Usability
Canadian institutionsWestern University
Fundersnot available
KeywordsComputer scienceDesign for manufacturabilityInformation systemKnowledge managementEngineering

Abstract

fetched live from OpenAlex

Information system maintenance is an important aspect of information system development, especially in systems that provide dynamic content, such as Web-based systems and Knowledge Management Systems (KMS). Design for Maintenance (DFM) is an approach that argues that maintenance effort should be considered during the design of information systems in addition to the usual system design considerations. This research examines how the design of links among knowledge documents in a KMS affects both their maintenance and use. We argue that providing links among knowledge documents increases the cost of maintenance because when a document changes, the documents that link to and from that document are more likely to need changes. At the same, linking knowledge documents makes it easier to locate useful knowledge and thus increases use. We examine this tension between use and maintenance using 10 years of data from a well-established KMS. Our results indicate that as the number of links among documents increases, both maintenance effort and use for these documents increase. Our analyses suggest two DFM principles for dynamic content in practice. First, knowledge coupling (i.e., linking) to documents internal to the KMS rather than sources external to the KMS better balances maintenance effort and use. Second, designing small, knowledge cohesive documents (e.g., 250-350 words) leads to the best balance between maintenance effort and use.

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 categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.688
Threshold uncertainty score0.363

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.000
Science and technology studies0.0000.000
Scholarly communication0.0000.003
Open science0.0010.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.012
GPT teacher head0.246
Teacher spread0.234 · 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