You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This has probably been raised in arms or osd already, but we need this to be dm bon-wide: a vocabulary that allows us to harmonise how we write terms (both in terms of HowWe_write-them, and in terms of what they mean) that come into the different projects. Don't actually create a vocab from scratch, but select from existing and enhance when necessary. Create a CSV (for scientists to look at) and triples. We would map each new project onto this, and also map from DwC and MiXS etc onto this, so we can also use it when exporting data to OBIS/GBIF/ENA/..
The text was updated successfully, but these errors were encountered:
this really is about making sure that our semantic-uplifting process is organized in a way that applying it to the dmbon applications becomes as easy as possible
It makes a lot of sense but is currently bit ahead of the curve
I think we first need to
organise our templates into ro-profiles
apply them to the repos that need them
have github actions pick up on their changes to do the semantic uplifting
and use that experience to further think about optimally organising the workflow to get that done
maybe by providing temoplate macro's
maybe by having reference lists of recurring patterns
...
However assembling the list of recurring things and issues is already a smart thing to do --> @kmexter -- maybe assemble these in comments to this issue
This has probably been raised in arms or osd already, but we need this to be dm bon-wide: a vocabulary that allows us to harmonise how we write terms (both in terms of HowWe_write-them, and in terms of what they mean) that come into the different projects. Don't actually create a vocab from scratch, but select from existing and enhance when necessary. Create a CSV (for scientists to look at) and triples. We would map each new project onto this, and also map from DwC and MiXS etc onto this, so we can also use it when exporting data to OBIS/GBIF/ENA/..
The text was updated successfully, but these errors were encountered: