|
|
# co-editing HDO - 1st steps:
|
|
|
# co-editing HDO - 1st steps:
|
|
|
|
|
|
for getting used to co-editing, and setting up our basic hierarchies in HDO:
|
|
|
|
|
|
- claim some terms and set up an issue like [this one](https://gitlab.hzdr.de/hmc/hmc-public/hob/hdo/-/issues/7)
|
|
|
- start a merge request based on that issue like [this one](https://gitlab.hzdr.de/hmc/hmc-public/hob/hdo/-/merge_requests/2)
|
|
|
- git pull the latest version of the main branch and then checkout your branch in your local repo
|
... | ... | @@ -7,3 +9,18 @@ for getting used to co-editing, and setting up our basic hierarchies in HDO: |
|
|
- Go through your self-assigned terms and add their parent class (should be in the genus of the definition) in the SubClass Of field.
|
|
|
- If the definition is not clear or unsettled, then leave the class without a SubClass Of entry and change the has curation status field to requires discussion (in the IRI Editor, that's [http://purl.obolibrary.org/obo/IAO_0000428](https://ontobee.org/ontology/IAO?iri=http://purl.obolibrary.org/obo/IAO_0000428))
|
|
|
- Save, git add-commit-push your changes (results would look like [this](https://gitlab.hzdr.de/hmc/hmc-public/hob/hdo/-/commit/29e79535fb4326286e71b20f00bd7d401f412f85)) to your branch and then we'll merge stuff in on Tuesday.
|
|
|
|
|
|
# ID Ranges for the contributors
|
|
|
|
|
|
| assignee | range |
|
|
|
|----------|-------|
|
|
|
| initial terms | 0-100 |
|
|
|
| @p.videgain.barranco | 101-1000 |
|
|
|
| @v.hofmann | 1001-2000 |
|
|
|
| @clemster | 2001-3000 |
|
|
|
| @jan.schweikert | 3001-4000 |
|
|
|
| @markus.kubin | 4001-5000 |
|
|
|
| @pier.buttigieg | 5001-6000 |
|
|
|
| @s.fathalla | 6001-7000 |
|
|
|
| @steinm01 | 7001-8000 |
|
|
|
|