Transformation of Data Access Models In BC
Bibliographic record
Abstract
IntroductionThe current data access model in BC involves project-specific applications and data provisioning. The timeline from application to provisioning is 6-8 months. Novel initiatives including Program of Research (POR), Core Data Sets (CORE), and Data Reuse are being explored and evaluated. Objectives and ApproachWe aim to develop data provisioning models that improve efficiency and access timelines by reducing process duplication and adopting open and flexible approaches to data use while ensuring data privacy. ResultsPOR allows researchers to access broad programmatic data that fulfills data requirements for multiple thematically-linked projects. While we provision the program data, a research team data manager extracts the project-specific data from the program dataset. A pilot program with two active projects is ongoing. The timeline from application to program data provisioning was 8 months. Project data was delivered in 2-3 months. CORE is a transformative data provisioning model that allows researchers to access entire data sets that contain a group of pre-approved and non-sensitive data variables for the BC population for all available years. This decreases the possibility of variable omission which is prevalent under the existing process. Additionally, this model allows researchers the flexibility to identify their cohort using their preferred methodology. Data Reuse allows re-use of data between similar projects conducted by the same investigator. Projects were surveyed for similar objectives, investigators and data requirements. Similar projects were grouped and analyzed to evaluate pre-implementation timelines. Application to provisioning timeline for one group of six projects ranged from 7-18 months. Post-implementation timelines will be evaluated once Data Reuse is implemented. Conclusion / ImplicationsThese new initiatives have shown promising results in access efficiency and data privacy in the pilot phase. Continuous process and privacy evaluations are involved and ongoing collaborations with the data providers and researchers are required prior to full implementation.
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 imitationNot 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.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.010 | 0.035 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.000 | 0.002 |
| Bibliometrics | 0.002 | 0.004 |
| Science and technology studies | 0.002 | 0.002 |
| Scholarly communication | 0.008 | 0.006 |
| Open science | 0.003 | 0.006 |
| Research integrity | 0.001 | 0.003 |
| Insufficient payload (model declined to judge) | 0.011 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
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".