Implementation of FAIR Principles for Ontologies in the Disaster Domain: A Systematic Literature Review
Bibliographic record
Abstract
The success of disaster management efforts demands meaningful integration of data that is geographically dispersed and owned by stakeholders in various sectors. However, the difficulty in finding, accessing and reusing interoperable vocabularies to organise disaster management data creates a challenge for collaboration among stakeholders in the disaster management cycle on data integration tasks. Thus the need to implement FAIR principles that describe the desired features ontologies should possess to maximize sharing and reuse by humans and machines. In this review, we explore the extent to which sharing and reuse of disaster management knowledge in the domain is inline with FAIR recommendations. We achieve this through a systematic search and review of publications in the disaster management domain based on a predefined inclusion and exclusion criteria. We then extract social-technical features in selected studies and evaluate retrieved ontologies against the FAIR maturity model for semantic artefacts. Results reveal that low numbers of ontologies representing disaster management knowledge are resolvable via URIs. Moreover, 90.9% of URIs to the downloadable disaster management ontology artefacts do not conform to the principle of uniqueness and persistence. Also, only 1.4% of all retrieved ontologies are published in semantic repositories and 84.1% are not published at all because there are no repositories dedicated to archiving disaster domain knowledge. Therefore, there exists a very low level of Findability (1.8%) or Accessibility (5.8%), while Interoperability and Reusability are moderate (49.1% and 30.2 % respectively). The low adherence of disaster vocabularies to FAIR Principles poses a challenge to disaster data integration tasks because of the limited ability to reuse previous knowledge during disaster management phases. By using FAIR indicators to evaluate the maturity in sharing, discovery and integration of disaster management ontologies, we reveal potential research opportunities for managing reusable and evolving knowledge in the disaster community.
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.034 | 0.118 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.004 | 0.005 |
| Bibliometrics | 0.026 | 0.021 |
| Science and technology studies | 0.002 | 0.003 |
| Scholarly communication | 0.006 | 0.008 |
| Open science | 0.003 | 0.004 |
| Research integrity | 0.002 | 0.002 |
| Insufficient payload (model declined to judge) | 0.003 | 0.000 |
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".