MétaCan
Menu
Back to cohort
Record W2172234609 · doi:10.1287/orsc.1040.0113

Should I Keep a Secret? The Effects of Trade Secret Protection Procedures on Employees' Obligations to Protect Trade Secrets

2005· article· en· W2172234609 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

VenueOrganization Science · 2005
Typearticle
Languageen
FieldHealth Professions
TopicTrade Secret Protection Methods
Canadian institutionsSimon Fraser University
FundersUniversity of Texas at Austin
KeywordsTrade secretBusinessEnforcementPerceptionMarketingIntellectual propertyPsychologyLawPolitical science

Abstract

fetched live from OpenAlex

Organizations' trade secrets (which can be chemical formulae, recipes, customer files, machinery designs, or many other types of information) are often valuable, enduring sources of competitive advantage. In this study, the influence of organizations' formal efforts to protect trade secrets on employees' beliefs about their obligations to protect those secrets was investigated. Quantitative and qualitative data were gathered by means of survey interviews with 111 employees of two high-tech organizations. Employees' obligations were influenced by their levels of familiarity with, and their perceptions of the enforcement of, two types of trade secret protection procedures (TSPPs): trade secret access restriction procedures (ARs) and trade secret handling procedures (HPs). Employees' levels of familiarity with ARs were negatively related to their felt obligations to protect trade secrets, but the opposite was true for HPs: Employees' levels of familiarity with HPs were positively related to the obligations they felt to protect trade secrets. For both types of TSPPs, the relationship between familiarity and felt obligations was moderated by employees' perceptions of the degree to which the TSPPs were enforced.

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.013
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch, Meta-epidemiology (narrow), Science and technology studies
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.235
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.013
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.008
Science and technology studies0.0030.000
Scholarly communication0.0000.001
Open science0.0010.000
Research integrity0.0000.001
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.059
GPT teacher head0.405
Teacher spread0.345 · 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