Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add many examples to schema and update some descriptions #394

Merged
merged 2 commits into from
Nov 5, 2024

Conversation

matentzn
Copy link
Collaborator

@matentzn matentzn commented Nov 2, 2024

See #392

this PR adds examples to most slots related to mappings, and updates some descriptions.

  • docs/ have been added/updated if necessary
  • make test has been run locally
  • tests have been added/updated (if applicable)
  • CHANGELOG.md has been updated.

If you are proposing a change to the SSSOM metadata model, you must

  • provide a full, working and valid example in examples/
  • provide a link to the related GitHub issue in the see_also field of the linkml model
  • provide a link to a valid example in the see_also field of the linkml model
  • run SSSOM-Py test suite against the updated model

[Add a description, mentioning at least relevant #ISSUE and how it was addressed. A bulleted list of all changes performed by the PR is is helpful.]

@matentzn matentzn requested a review from cthoyt November 2, 2024 21:59
mapping_provider:
description: URL pointing to the source that provided the mapping, for example
an ontology that already contains the mappings, or a database from which it was derived.
range: uri
instantiates: sssom:Propagatable
annotations:
propagated: true
examples:
- value: https://www.ohdsi.org/
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the description needs to be updated here. These URIs don't actually point to resources, so what are you supposed to do with this? This is more of a comment string since I'm not sure there's a good way to actually capture this information unless it's supposed to point to a metadata file or the source data itself

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mapping_cardinality:
description: A string indicating whether this mapping is from a 1:1 (the subject_id
maps to a single object_id), 1:n (the subject maps to more than one object_id),
n:1, 1:0, 0:1 or n:n group. Note that this is a convenience field that should be derivable
from the mapping set.
range: mapping_cardinality_enum
examples:
- value: "1:1"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you make this exhaustive?

and more specifically, give examples of one-to-one and one-to-many mappings, with an explanation of why they have these qualities

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The enum definition is exhaustive; the examples are just cherry-picked. You can see all the enums and what they mean on the enum page (which is linked from the slot/field/column page).

Copy link
Member

@cthoyt cthoyt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Useful updates, thanks

@matentzn matentzn merged commit fcdad7a into master Nov 5, 2024
3 checks passed
@matentzn matentzn deleted the schema-examples branch November 5, 2024 10:28
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.

4 participants