MétaCan
Menu
Back to cohort
Record W2059445051 · doi:10.1021/ci200253g

Integrated Project Views: Decision Support Platform for Drug Discovery Project Teams

2012· article· en· W2059445051 on OpenAlexaff
Eric J. Baede, Ernest den Bekker, Jan‐Willem Boiten, Deborah Cronin, Rob van Gammeren, Jacob de Vlieg

Bibliographic record

VenueJournal of Chemical Information and Modeling · 2012
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicBig Data and Business Intelligence
Canadian institutionsDiscovery Centre
Fundersnot available
KeywordsComputer scienceConsistency (knowledge bases)Project teamProcess (computing)Data scienceProcess managementKnowledge managementEngineeringArtificial intelligence

Abstract

fetched live from OpenAlex

Drug discovery teams continuously have to decide which compounds to progress and which experiments to perform next, but the data required to make informed decisions is often scattered, inaccessible, or inconsistent. In particular, data tend to be stored and represented in a compound-centric or assay-centric manner rather than project-centric as often needed for effective use in drug discovery teams. The Integrated Project Views (IPV) system has been created to fill this gap; it integrates and consolidates data from various sources in a project-oriented manner. Its automatic gathering and updating of project data not only ensures that the information is comprehensive and available on a timely basis, but also improves the data consistency. Due to the lack of suitable off-the-shelf solutions, we were prompted to develop custom functionality and algorithms geared specifically to our drug discovery decision making process. In 10 years of usage, the resulting IPV application has become very well-accepted and appreciated, which is perhaps best evidenced by the observation that standalone Excel spreadsheets are largely eliminated from project team meetings.

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 imitation

Not 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.

metaresearch head score (Codex)0.013
metaresearch head score (Gemma)0.029
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.025
Threshold uncertainty score0.084

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0130.029
Meta-epidemiology (narrow)0.0020.002
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0050.004
Science and technology studies0.0010.001
Scholarly communication0.0080.008
Open science0.0040.008
Research integrity0.0020.003
Insufficient payload (model declined to judge)0.0250.015

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.105
GPT teacher head0.335
Teacher spread0.230 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designSimulation or modeling
Domainnot available
GenreMethods

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".

Quick stats

Citations5
Published2012
Admission routes1
Has abstractyes

Explore more

Same venueJournal of Chemical Information and ModelingSame topicBig Data and Business IntelligenceFrench-language works237,207