PurificationDB: database of purification conditions for proteins
Bibliographic record
Abstract
The isolation of proteins of interest from cell lysates is an integral step to study protein structure and function. Liquid chromatography is a technique commonly used for protein purification, where the separation is performed by exploiting the differences in physical and chemical characteristics of proteins. The complex nature of proteins requires researchers to carefully choose buffers that maintain stability and activity of the protein while also allowing for appropriate interaction with chromatography columns. To choose the proper buffer, biochemists often search for reports of successful purification in the literature; however, they often encounter roadblocks such as lack of accessibility to journals, non-exhaustive specification of components and unfamiliar naming conventions. To overcome such issues, we present PurificationDB (https://purificationdatabase.herokuapp.com/), an open-access and user-friendly knowledge base that contains 4732 curated and standardized entries of protein purification conditions. Buffer specifications were derived from the literature using named-entity recognition techniques developed using common nomenclature provided by protein biochemists. PurificationDB also incorporates information associated with well-known protein databases: Protein Data Bank and UniProt. PurificationDB facilitates easy access to data on protein purification techniques and contributes to the growing effort of creating open resources that organize experimental conditions and data for improved access and analysis. Database URL https://purificationdatabase.herokuapp.com/.
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.003 | 0.011 |
| Meta-epidemiology (narrow) | 0.005 | 0.002 |
| Meta-epidemiology (broad) | 0.005 | 0.002 |
| Bibliometrics | 0.009 | 0.013 |
| Science and technology studies | 0.002 | 0.001 |
| Scholarly communication | 0.006 | 0.006 |
| Open science | 0.007 | 0.004 |
| Research integrity | 0.004 | 0.003 |
| Insufficient payload (model declined to judge) | 0.046 | 0.100 |
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".