Community Ontology Repository (COR) Feature Updates

[lewismc]

Idea

The ESIP COR is a custom deployment of the MMISW ORR Software which provides a data hub for semantic technologists across ESIP.
In addition to the open issues for the ORR frontend and backend, there are a number of unlogged feature requests including reasoning, inference, development of a reporting API, etc. This project would involve heavy development of the ORR software to address the above feature requests and open issues.

Skills Needed

Scala, JavaScript, Shell

Mentors

Lewis John McGibbney, NASA JPL
Carlos Rueda, MBARI

[jaskirat1208]

I would like to contribute to it. Please guide me how to start.

[lewismc]

Hello @jaskirat1208 thank you for registering your interest. ESIP has been selected as a particpating organization so you should scope out the guidelines and timeline over at the GSoC site.
As it turns out, Student Applications open March 12, 2018 at 09:00 (PDT), however I would encourage you to begin getting involved in COR development before then.
@carueda I think this is a good time for us to begin prioritizing 'new-comer' issues to COR development... can you assist here? Thanks

[carueda]

Hi @jaskirat1208 yes, thanks for your interest. Let us know as you explore and see potential tasks and tell us perhaps about any preference in terms of backend or frontend focus, etc.

@lewismc Lewis, yes, I'll start by adding the 'good first issue' label in the ORR issue trackers and looking into using it in appropriate entries. And yes, we need to enter those unlogged feature requests.

[jaskirat1208]

@carueda @lewismc could you please give me some easy to start tasks that I can do to start with?

[vaibhavchellani]

@carueda @lewismc i would like to work on this as well . I was looking forward to developing COR and was searching for repos in the organisation to view the existing issues . if you could direct me to the correct repo it would be great .
Thanks !

[carueda]

Please see the Idea section.

[vaibhavchellani]

@carueda apologies . thank you

[carueda]

Hi @jaskirat1208 @vaibhavchellani @lewismc and everyone interested.

I was intending to provide some additional information but it has taken a bit longer than planned, sorry.

So, the parent space is https://github.com/mmisw/

The key repositories are:

https://github.com/mmisw/orr

This one is mainly to build the integrated ORR system, which involves "dockerization" of the ORR itself and use of the docker images for MongoDB and AllegroGraph. We don't currently have any specific pressing needs here.

https://github.com/mmisw/orr-ont

This is the backend service. Written in Scala it uses http://scalatra.org/ as the web toolkit.

A bit challenging depending on prior experience but certainly feasible task is mmisw/orr-ont#47, where in particular we are interested in using a much more active and mature web toolkit as well as facilitate the automatic generation of the OpenAPI specification (which we already use) for the REST API. Among the various benefits, with this in place we would also make the automatic generation of client libraries (eg., python) more reliable.

Another important issue is mmisw/orr-ont#64, about the reasoning capabilities of the SPARQL endpoint and possible use of alternative underlying triple stores, ideally open-source.

I also just marked mmisw/orr-ont#63 as a "good first issue."

https://github.com/mmisw/orr-portal

This is the frontend. Written in Javascript it uses https://angularjs.org/ as the web framework.

A common enhancement request has been about the user-friendlier display of vocabularies, for example as captured at mmisw/orr-ont#57; note, on the backend repo tracker. although it is possible that improvements here may involve both frontend and backend components.

Other related usability issues:

• better display of regular ontology mmisw/orr-portal#68
• nicer LOD-friendly display of content on ontology page mmisw/orr-portal#92

Other possible tasks?

There are other various aspects/issues that can be addressed as well depending on the applicant interests and experience, in particular regarding semantics and its proper use in the ORR. If you are interested in these or other aspects by exploring the existing entries in the trackers, do please let us know so we can coordinate.

[lewismc]

@jaskirat1208 any updates here?