Vocabulary/data drift for OpenContext material URIs used in facets (missing labels downstream)

[rdhyee]

Context

Downstream facet UIs use vocab_labels.parquet (built in isamplesorg.github.io) to render friendly labels for material URIs. Two OpenContext material URIs appear in facet data but do not resolve to labels:

• https://w3id.org/isample/opencontext/material/0.1/organicanimalproduct (count 261)
• https://w3id.org/isample/opencontext/material/0.1/plantmaterial (count 1)

These URIs are present in facet_summaries but absent from vocab_labels because they appear not to be in the current OpenContext material extension TTL used for label generation (which has organicanimalmaterial and organicplantmaterial).

Why filing in metadata

This seems like a metadata/vocabulary governance question: are these legacy/invalid terms, aliases, or missing concepts that should be represented explicitly?

Repro SQL

SELECT facet_value, count
FROM read_parquet('https://data.isamples.org/isamples_202601_facet_summaries.parquet')
WHERE facet_type='material'
  AND (facet_value ILIKE '%organicanimalproduct%'
       OR facet_value ILIKE '%plantmaterial%');

WITH facet AS (
  SELECT DISTINCT facet_value AS uri
  FROM read_parquet('https://data.isamples.org/isamples_202601_facet_summaries.parquet')
  WHERE facet_type='material'
), labels AS (
  SELECT DISTINCT uri
  FROM read_parquet('https://data.isamples.org/vocab_labels.parquet')
  WHERE lang='en'
)
SELECT f.uri
FROM facet f
LEFT JOIN labels l USING (uri)
WHERE l.uri IS NULL
ORDER BY f.uri;

Requested decision

Please define canonical handling for these two URIs:

1. Add/restore terms (or deprecated aliases) in the appropriate vocabulary repo/profile, OR
2. Declare them legacy/invalid and provide canonical replacements + mapping guidance for exporters.

Cross-repo linkage

Related integration issue (consumer/build side):

• Material facet label gaps: OpenContext URIs in facet_summaries missing from vocab_labels isamplesorg.github.io#161

[rdhyee]

Pinpoint after checking source vocab and downstream facet files:\n\n1) The two URIs in facet data are:\n- (261)\n- (1)\n\n2) The OpenContext material extension TTL currently defines:\n- \n- \n\nand does not define or .\n\n3) in isamplesorg.github.io is behaving as designed: it only emits labels for concepts present in the TTLs (plus versioned aliases with same slug), so those two facet URIs cannot get labels unless they exist as concepts/aliases in source vocab or are normalized upstream.\n\nConcrete gap: vocabulary/data-term drift between OpenContext terms in exported facet values and terms declared in OpenContext material vocabulary.\n\nSuggested resolution path:\n- either add deprecated/alias SKOS concepts for those two URIs in the OpenContext extension vocab, or\n- canonicalize those values in export so facet URIs use / .

[rdhyee]

Correcting/clarifying with exact identifiers (previous comment was shell-mangled):

Pinpoint after checking source vocab and downstream facet files:

1. The two URIs in facet data are:

• https://w3id.org/isample/opencontext/material/0.1/organicanimalproduct (261)
• https://w3id.org/isample/opencontext/material/0.1/plantmaterial (1)

2. The OpenContext material extension TTL currently defines:

• ocmat:organicanimalmaterial
• ocmat:organicplantmaterial

and does NOT define organicanimalproduct or plantmaterial.

3. build_vocab_labels.py in isamplesorg.github.io is behaving as designed: it only emits labels for concepts present in the TTLs (plus versioned aliases with same slug), so those two facet URIs cannot get labels unless they exist as concepts/aliases in source vocab or are normalized upstream.

Concrete gap: vocabulary/data-term drift between OpenContext terms in exported facet values and terms declared in metadata_profile_archaeology OpenContext material vocabulary.

Suggested resolution path:

• either add deprecated/alias SKOS concepts for those two URIs in the OpenContext extension vocab, or
• canonicalize those values in export so facet URIs use organicanimalmaterial / organicplantmaterial.