Skip to content

Fix SSSOM structural mapping column names for sssom-py compatibility#144

Open
justaddcoffee wants to merge 1 commit intomainfrom
fix/sssom-empty-fallback
Open

Fix SSSOM structural mapping column names for sssom-py compatibility#144
justaddcoffee wants to merge 1 commit intomainfrom
fix/sssom-empty-fallback

Conversation

@justaddcoffee
Copy link
Copy Markdown
Collaborator

Summary

  • Renamed subject_typed4d_subject_range and object_typerocrate_value_type in the structural mapping generator and regenerated the TSV
  • Added a fallback in SSSOMIntegration when sssom-py returns 0 rows after silent drops

Context

subject_type and object_type are reserved SSSOM columns expecting EntityTypeEnum values (owl class, rdf property, etc.). The structural mapping was using these columns to store LinkML range names and Python types instead, which caused sssom-py to silently reject all 149 rows. This resulted in the test_load_structural_mapping CI failure.

The column data is preserved under non-reserved names. No mapping content was changed.

Test plan

  • sssom-py parses all 149 rows from the regenerated TSV
  • All 36 SSSOM tests pass
  • test_load_structural_mapping passes with sssom-py installed

🤖 Generated with Claude Code

Rename subject_type → d4d_subject_range and object_type →
rocrate_value_type to avoid colliding with reserved SSSOM columns
that expect EntityTypeEnum values. Add fallback in SSSOMIntegration
when sssom-py silently drops rows.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant