Vocabulary

LTO

Library Transaction Ontology

A FAIR-compliant metadata vocabulary (MV), the Library Transaction Ontology (LTO), is designed and developed for representing and managing library transaction data (LTD), including circulation, interlibrary loan, hold requests, and fiscal information. Our investigation revealed that despite significant focus on bibliographic and authority data, no standardized vocabulary exists for LTD, resulting in data loss, mapping errors, and interoperability challenges during system migration and integration.

academycatalogs
E31

FAIR 21/48

Version 1.0

Evaluated 26 Oct 2026

How scores work

Source & access

Homepagew3id.org DownloadCanonical file / PURL

Automated evaluation

F Findable FAIR0/12
  • Persistent identifier (F1)no PURL / w3id / DOI for the artefact0
  • Indexed in services (F4)not indexed anywhere0
  • Citable reference (F2)no reference publication listed0
A Accessible FAIR9/12
  • Homepage reachableHTTP 200+3
  • Artefact retrievable over HTTP(S) (A1)download HTTP 200+6
  • Metadata persists in a registry (A2)not in Bioregistry or OBO Foundry0
I Interoperable FAIR8/12
  • Formal machine-readable format (I1)RDF+5
  • Semantic-web IRIs (I2)RDF+3
  • References other vocabularies (I3)no imported vocabularies found0
R Reusable FAIR4/12
  • Clear license (R1.1)none found0
  • Release provenance (R1.2)1.0 (version IRI in the artefact)+4
  • Community standards (R1.3)no independent compliance report (not on the OBO Dashboard)0
Q Ontology consistency & quality0/20
  • Logical consistencynever checked by a reasoner0
  • OWL 2 DL profileprofile not checked0
  • Upper-ontology alignmentno BFO/COB/DOLCE import found0
  • Standard relations (RO)does not import the Relation Ontology0
  • ROBOT report: no errorsno ROBOT report available0
  • ROBOT report: warning densityno ROBOT report available0
  • Pitfall scan: no critical pitfallsno pitfall scan or ROBOT report yet0
M Maintenance10/16
  • Recency2026-08-24 → 2.1 months (≤ 3 months)+10
  • Release cadence (12 months)0 releases0
U Community adoption0/16
  • Documented adopting projects0 projects0
  • Reused by other ontologies00
  • Community signalmax(stars 0 → 0, citations 0 → 0)0
P Penalties (inactivity & inconsistency)0
  • Time since last activity0.2 years → 4 × max(0, 0.2 − 1)0
  • Inactive statusnot archived, legacy or inactive0
  • Consistencynot yet checked by a reasoner0

FAIR subtotal 21/48 · earned 31/100 = 31/100 → grade E

Community adoption 0

No adopting projects documented yet.

Know a project that uses LTO? Suggest it.

History & changes 1 run

History starts with the first archived run; changes appear after the next evaluation.

RunScoreFAIRVersion evaluatedTermsSnapshot
26 Oct 2026, 03:31 UTC31 E211.0—JSON

Provenance

Every fact on this page was fetched automatically. Each row shows where it came from and when. If a source fails, the last good value is kept and marked “carried forward”.

FactSourceRetrieved
Homepage link check (HTTP 200)w3id.org26 Oct 2026, 03:04 UTC
Download link check (HTTP 200)lov.linkeddata.es26 Oct 2026, 03:04 UTC
Artefact header (version IRI)lov.linkeddata.es26 Oct 2026, 03:04 UTC

Run 2026-10-26T02-37-38Z · evaluator v2.0.0 · rubric v3.4 · entry.json · run snapshot