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.

Sign up for GitHub

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

Jump to bottom

Terminology provider - access agreed mappings - gain efficiency in data exchange #15

Open
gwemon opened this issue Jan 11, 2020 · 2 comments
Open

Terminology provider - access agreed mappings - gain efficiency in data exchange #15

gwemon opened this issue Jan 11, 2020 · 2 comments
Labels
data model alignment select appropriate data sets for use with physical computational models semantic alignment align concepts from terminologies terminology management gather/curate and maintain the individual terms within a terminology

Comments

@gwemon
Copy link
Member

gwemon commented Jan 11, 2020 •
edited
Loading

As a...

terminology provider to a large multinational data management community who standardizes their variable names using our vocabulary resources

I want to...

be able to use a common source of agreed and trusted mappings between known and well used terminologies for observable properties

So that...

we save ourselves and our customers time and effort when mapping their terms to our terms, and improve consistency, efficiency, and accuracy of the data annotation and transfer processes.

Domain(s)

Any domain would benefit but my particular area of interest is oceanography/marine sciences in general, and contaminant measurements in biota, sediment and water in particular. This user story could also focus on nitrogen variables.

Addition Information

For example, many organisations whose data is eventually submitted to SeaDataNet may have their data tagged with ICES vocabularies and codes, or CF standard names already. A common interoperability framework would allow us to take a more formal, fully or semi-automated approach to mapping our terminologies making them easier to use, more reliable, and persistent.
@gwemon gwemon changed the title Terminology provider - Desired Action - Benefit Terminology provider - access agreed rusted mappings - gain efficiency in data exchange Jan 11, 2020
@gwemon gwemon changed the title Terminology provider - access agreed rusted mappings - gain efficiency in data exchange Terminology provider - access agreed mappings - gain efficiency in data exchange Jan 11, 2020
kitchenprinzessin3880 added a commit to i-adopt/usecase_analysis that referenced this issue Feb 26, 2020
@kitchenprinzessin3880
included user stories i-adopt/users_stories#3
40dd4f7 
modified codes, domain areas and description of user stories i-adopt/users_stories#15
@mabablue mabablue added semantic alignment align concepts from terminologies terminology management gather/curate and maintain the individual terms within a terminology and removed user story labels Mar 19, 2020
@mabablue
Copy link
Member

mabablue commented Apr 1, 2020

dear Gwen please check once again whether you are happy with the assigned use cases or change them.

@gwemon gwemon added the data model alignment select appropriate data sets for use with physical computational models label Apr 19, 2020
@gwemon
Copy link
Member Author

gwemon commented Apr 19, 2020

Thanks @mabablue I have added data model alignment in addition to semantic alignment and terminology management.

@gwemon gwemon removed their assignment Apr 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
data model alignment select appropriate data sets for use with physical computational models semantic alignment align concepts from terminologies terminology management gather/curate and maintain the individual terms within a terminology
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gwemon @mabablue