Data in Jeopardy
Bibliographic record
Abstract
During the last 30 years, there has been a serious neglect of the information base stored within our data holdings. In the 1800's data was stored in media such as books, which had encapsulated indexes, meta information, versioning and data. The media, paper, was stable and could be opened up a hundred years later and the information could still be retrieved. Due in large part to rapid technology shifts and the lack of appropriate international standards, this is no longer the case. For the past 30 years, technology shifts have created serious problems in large data repositories. The constant change of storage media from punched cards, to paper tape to 800 BPI magnetic tapes, to cartridges, to magnetic disks, to optical media etc. has resulted in major problems for very large data archives. The hardware and software required to read the old media may not be available in a hundred years, leaving the entire information base in a crisis state. The technology providers also constantly change application software to store and read data. These changes are sometimes implemented within the space of six months, such as in GIS and Wordprocessing software applications. The software is not always backward compatible due to the encapsulation of proprietary file architectures, algorithms and smart compression. These file architectures, algorithms, compression or otherwise, may not be available if the company should ever go out of business or radically change the application domain. There is an urgent need to stabilize the storage data structures to some open international standard for long term archival. If not, the large data holdings will be in jeopardy - not in a hundred years but in less then ten years. A generic storage mechanism, SDS (Self Defining Structure), has been proposed to the ISOTC211 WG1 under the guidance of the Image and Gridded Data Working Group. This paper addresses problems encountered in the state of the data sets used for Canada's Law of the Sea project and possible solutions using SDS (Self Defining Structures) and distributed archives.
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.008 | 0.046 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.005 | 0.006 |
| Science and technology studies | 0.007 | 0.007 |
| Scholarly communication | 0.018 | 0.021 |
| Open science | 0.004 | 0.014 |
| Research integrity | 0.004 | 0.010 |
| Insufficient payload (model declined to judge) | 0.167 | 0.081 |
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".