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

/models/<model>/entities/<entity>/attributes/<attr>/mappings: Unimplemented features #130

Open
joeflack4 opened this issue Nov 30, 2021 · 0 comments
Assignees
Labels

Comments

@joeflack4
Copy link
Collaborator

joeflack4 commented Nov 30, 2021

Description

Not all of the SSSOM-spec fields are being used. Even for the ones that are being used, only some of them are actually producing values.

Fields currently showing in response

  • subject_match_field
  • subject_label
  • object_match_field
  • mapping_provider *
  • predicate_id
  • object_id
  • object_label
  • creator_id *
  • license *

Fields currently rendering data in response

  • subject_match_field
  • subject_label
  • object_match_field
  • mapping_provider *

* These are showing at the top level of the response, not under mappings. IMO, this is probably not a problem as long as we only do this when it is calculated that all items in the mappings response have the same exact value. Otherwise, we should render under mappings, and it might just be better/easier to always do that anyway.


All SSSOM fields

  • subject_id
  • subject_label **
  • subject_category
  • predicate_id *
  • predicate_label
  • predicate_modifier
  • object_id *
  • object_label *
  • object_category
  • match_type
  • author_id
  • author_label
  • reviewer_id
  • reviewer_label
  • creator_id *
  • creator_label
  • license *
  • subject_source
  • subject_source_version
  • object_source
  • object_source_version
  • mapping_provider **
  • mapping_cardinality
  • mapping_tool
  • mapping_tool_version
  • mapping_date
  • confidence
  • subject_match_field **
  • object_match_field **
  • match_string
  • subject_preprocessing
  • object_preprocessing
  • match_term_type
  • semantic_similarity_score
  • semantic_similarity_measure
  • see_also
  • other
  • comment

* These are currently used in the terminology service, but not fully implemented.
** These are currently used in the terminology service, and fully implemented.

@joeflack4 joeflack4 self-assigned this Nov 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant