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

Soil Data manager - Normalize data - Achievement of a standard #3

Open
lbtgnn68 opened this issue Nov 14, 2019 · 4 comments
Open

Soil Data manager - Normalize data - Achievement of a standard #3

lbtgnn68 opened this issue Nov 14, 2019 · 4 comments
Assignees
Labels
data model alignment select appropriate data sets for use with physical computational models semantic alignment align concepts from terminologies semantic modelling develop formal terminologies to represent concepts and their relationships

Comments

@lbtgnn68
Copy link

lbtgnn68 commented Nov 14, 2019

As a

Soil data manager

I want to

normalize (both) the collected (and collectable) soil information in agreement with the INSPIRE directive (https://inspire.ec.europa.eu/id/document/tg/so; https://inspire.ec.europa.eu/data-model/approved/r4618-ir/html/ - Themes>Annex III>SO) ) according to the Observation and Measurement Standard (https://www.opengeospatial.org/standards/om),

so that

observableProperties (together with UnitsOfMeasure, and Processes) would result in unambiguous descriptions.

Domain(s)

Soil; Geographic information; Biology; Biochemistry; Microbiology; Chemistry; Mineralogy; Pedology; Physics; Hydrology; Micromorphology

Addition Information

Usually, relational databases store data according to a physical implementation into tables, records, and columns where tables partly identify natural entities, columns identify properties (parameters) and records the recorded data (semantic representation). Unnormalized structures are unfortunately characterized by different notations of the same parameter, or feature-of-interest, related to different natural entities. Searching for all properties related to nitrogen in an unnormalized database means checking manually all coding for every column and table (hundreds of fields). No query automatically implements such a simple search. Normalizing the database would allow for a simple query to enable such a search.
The achievement of a standard goes through the normalizing step.

kitchenprinzessin3880 added a commit to i-adopt/usecase_analysis that referenced this issue Feb 26, 2020
modified codes, domain areas and description of user stories i-adopt/users_stories#15
@mabablue mabablue added semantic alignment align concepts from terminologies semantic modelling develop formal terminologies to represent concepts and their relationships data model alignment select appropriate data sets for use with physical computational models and removed example user story user story labels Mar 17, 2020
@mabablue
Copy link
Member

mabablue commented Apr 2, 2020

Dear @lbtgnn68 could you please check whether the assigned labels fit as use cases for your user story? Please check this table to find a better or additional use case which matches better your user story.

@lbtgnn68
Copy link
Author

Hi @mabablue, I would add data annotation & metadata annotation. Thanks!

@lbtgnn68
Copy link
Author

Could you do it for me?

@mabablue
Copy link
Member

yes I could do, but we decided to have only 3 labels for each user story. So either we decide to delete one of the other labels or we don't add annotation. Please reconsider your proposal. Thanks

@SirkoS SirkoS mentioned this issue Jul 11, 2020
27 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data model alignment select appropriate data sets for use with physical computational models semantic alignment align concepts from terminologies semantic modelling develop formal terminologies to represent concepts and their relationships
Projects
None yet
Development

No branches or pull requests

3 participants