Verification
After running Meta, use the verification script to check that all identifiers were processed correctly and have associated data in the triplestore.
Running verification
Section titled “Running verification”uv run python -m oc_meta.run.meta.check_results <CONFIG_PATH> <OUTPUT_FILE>Example:
uv run python -m oc_meta.run.meta.check_results meta_config.yaml report.txtWhat it checks
Section titled “What it checks”1. Identifier analysis
Section titled “1. Identifier analysis”The script parses all identifiers from input CSV files, including:
idcolumn (DOIs, PMIDs, etc.)authorcolumn (ORCID identifiers)editorcolumn (ORCID identifiers)publishercolumn (Crossref identifiers)venuecolumn (ISSNs, ISBNs)
2. OMID verification
Section titled “2. OMID verification”For each identifier, the script queries the triplestore to check:
- Does the identifier have an associated OMID?
- Does any identifier have multiple OMIDs? (indicates disambiguation issues)
3. Data graph verification
Section titled “3. Data graph verification”If generate_rdf_files: true in your config:
- Verifies that RDF files exist for each entity
- Reports missing data graphs
4. Provenance verification
Section titled “4. Provenance verification”For each OMID found:
- Queries the provenance triplestore
- Verifies provenance graphs exist
- Reports OMIDs missing provenance data
Output format
Section titled “Output format”The script reports issues grouped by category:
=== Verification Report ===
Identifiers without OMID: doi:10.1234/missing-entity-1 doi:10.1234/missing-entity-2
Identifiers with multiple OMIDs: doi:10.1234/duplicate-entity -> omid:br/060/1, omid:br/060/2
OMIDs without provenance: omid:br/060/12345
Summary: Total identifiers: 50000 Identifiers with OMID: 49998 Identifiers without OMID: 2 OMIDs with provenance: 49995 OMIDs without provenance: 3