Skip to content

Pathway: Semantic engineer#313

Draft
joeflack4 wants to merge 1 commit intomasterfrom
semantic-engineer
Draft

Pathway: Semantic engineer#313
joeflack4 wants to merge 1 commit intomasterfrom
semantic-engineer

Conversation

@joeflack4
Copy link
Contributor

@joeflack4 joeflack4 commented Nov 29, 2022

Updates

- Add: Pathway: Semantic Engineer
- Update: Pathway: Ontology Engineer
- Update: .gitignore: Added .idea/ for JetBrains IDEs

@joeflack4 joeflack4 marked this pull request as draft November 29, 2022 16:57
- Ontology Curator GO-style: pathways/ontology-curator-go-style.md
- Ontology Curator OBI-style: pathways/ontology-curator-obi-style.md
- Ontology Engineer/Developer: pathways/ontology-engineer.md
- Semantic Engineer: pathways/semantic-engineer.md
Copy link
Contributor Author

@joeflack4 joeflack4 Nov 29, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think there is a lot of overlap between "semantic engineer" and "ontology engineer". I used that one as a template instead of the "ontology curator: go" page. There's only one section in that page that isn't in "ontology engineer", and it is the "mindset" section.

I removed some items from these lists if it's something I haven't done/used before, but I wouldn't be surprised if that changes!

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could we merge ontology engineer with semantic engineer then?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PS I didn't over think this pathway (was focusing on curator one) so happy for it to be fully revamped as semnatic engineer and taken over as so :)

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There will always be a lot of overlap, but for me, the ontology engineer is focused on design patterns, modelling, logic, while the Semantic Software Engineer is focused on using ontologies in Software and Data pipelines.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ontology Engineer sounds like Ontology/Semantic Architect! (I actually don't like to use 'architect' usually; sounds very Java)


## Getting Set-up

1. Download and install [GitHub Desktop](https://desktop.github.com/)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't use GitHub Desktop, but it's not bad. I have seen data managers and similar roles use it more often.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For a lot of these as well, I feel like if you have the title engineer or developer, a lot of this stuff will be mastered already, such as GitHub, or CLI. But for a junior engineer just starting out, or someone looking to become an engineer, I suppose it is indeed good to have some of these things in the list.

1. [Cloning a Repo](../howto/clone-mondo-repo.md)
1. [Creating pull requests](../howto/github-create-pull-request.md)

### Learning ontology engineering
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For this section, I kept everything from Ontology engineer except for these:

1. [Setting up a ODK repository](../tutorial/setting-up-project-odk.md)
1. [Developing an obo ontology](../lesson/developing-an-obo-ontology.md)
1. [Understanding product variants](../explanation/owl-format-variants.md)
1. [Dealing with large ontologies](../howto/deal-with-large-ontologies.md)
1. [Setting up slims](../howto/add-new-slim.md)

@@ -0,0 +1,61 @@
# Semantic Engineer Pathway

## Getting Set-up
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For this section, I kept everything from Ontology Engineer except for this:

4. [Setting up your ID range](../howto/idrange.md)

1. [Basics of SPARQL](../tutorial/sparql.md)
1. [Setting up slims](../howto/add-new-slim.md)

## Ontology Engineer How To Collection
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For this section, I kept everything from Ontology engineer except for these:

- [Adding taxon restrictions](../howto/add-taxon-restrictions.md)
- [Cloning a repo](../howto/clone-mondo-repo.md)
- [Creating a github fork](../howto/github-create-fork.md)
- [Creating a github pull request](../howto/github-create-pull-request.md)
- [Setting up your ID range](../howto/idrange.md)
- [Setting up ELK reasoner in protege](../howto/installing-elk-in-protege.md)
- [Obsoleting terms](../howto/obsolete-term.md)
- [Merging terms](../howto/merge-terms.md)
- [Creating slims](../howto/add-new-slim.md)
- [Setting up ODK](../howto/odk-setup.md)
- [Switching ontologies](../howto/switching-ontologies.md)

1. [Setting up a ODK repository](../tutorial/setting-up-project-odk.md)
1. [Developing an obo ontology](../lesson/developing-an-obo-ontology.md)
1. [Understanding product variants](../explanation/owl-format-variants.md)
1. [Dealing with large ontologies](../howto/deal-with-large-ontologies.md)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed this from "learning..." section because it was in the "how to..." section.

- [Cloning a repo](../howto/clone-mondo-repo.md)
- [Creating new terms](../howto/create-new-term.md)
- [Daily Curator Workflow](../howto/daily-curator-workflow.md)
- [Daily Git Workflow (Curators and Engineers)](../howto/daily-curator-workflow.md)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed this because even though the page is curator focused, it is a useful workflow to know for engineers as well. Added word 'Git' because it seems focused on largely on that.


- [Adding taxon restrictions](../howto/add-taxon-restrictions.md)
- [Changing files in pull requests](../howto/change-files-pull-request.md)
- [Cloning a repo](../howto/clone-mondo-repo.md)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For the other ones I removed from the Ontology Engineer "how to" section, it's either because (a) it is very basic, e.g. cloning, and a quick google search away if really needed, or (b) it's already in another section of the same page.

- Update: .gitignore: Added .idea/ for JetBrains IDEs
- Update: Pathway: Ontology Engineer
1. [DOSDP Templates Basic Tutorial](../tutorial/dosdp-template.md)
1. [Introduction to Managing DOSDP Templates in ODK](../tutorial/dosdp-odk.md)
1. [Basics of SPARQL](../tutorial/sparql.md)
1. OAK
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@matentzn I probably got to the most important value-add right at the end, and didn't have much time to think/write about it. I added these 5 bullet points to the bottom of "learning semantic engineering", but I did not yet create pages for these.

@joeflack4 joeflack4 requested a review from matentzn November 29, 2022 17:29
@joeflack4 joeflack4 added the documentation Improvements or additions to documentation label Nov 29, 2022
@shawntanzk
Copy link
Collaborator

@joeflack4 thanks for doing this! looks awesome :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants