aceModerate evidence
Published recordLaborProblem Space
More
Artificial intelligence (AI) adoption and Chinese art teachers' career exploration behavior: The roles of job substitution risks, job insecurity, and organizational AI readiness
- Truvace record
- TRV-2026-2463raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Survey
- Sources
- 1 sourcePeer-reviewed
- sha256
- 929d4364640f…check it
The increasing use of artificial intelligence (AI) in art education raises questions about teachers' professional security and career development. Drawing primarily on Conservation of Resources (COR) theory and, in a complementary manner, on Career Construction Theory (CCT), this cross-sectional study examined associations among AI adoption, perceived job substitution risk, job insecurity, career exploration behavior, and organizational AI readiness. Survey data from 381 Chinese art teachers were analyzed using…
The problem
In a survey of 381 Chinese art teachers, heavier AI use was associated with greater perceived risk of being replaced (B = .40) and greater job insecurity (B = .37).
What this doesn’t fix
The cross-sectional, self-reported design cannot establish causal order, and reverse causality is possible. Recruitment through social contacts may have favored technologically engaged teachers, and exploration motives were not measured.
Sources
1 on file- PLOS Onedoi:10.1371/journal.pone.0362478
Cite this record
v1Truvace Impact Record TRV-2026-2463, v1: “Artificial intelligence (AI) adoption and Chinese art teachers' career exploration behavior: The roles of job substitution risks, job insecurity, and organizational AI readiness.” Truvace, 2026-11-11. /record/TRV-2026-2463 (accessed on the day you copy it). sha256 929d4364640f99e2…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2463 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.