openrif/developers

A repository dedicated to core developer content and activities. Restricted to dev-team.

vivo-isf-dev

A repository dedicated to core developer content and activities. Restricted to the developer team.

developers's Issues

Simplify and document how to make contributions

We will establish tooling, documentation, and a process for how to contribute to the various projects. I will show in a week or two one possible tool to help with this.

using MARC relators as roles

This idea has been floating between me and Melissa and few other folks for a while. For those not familiar with MARC relators please have a look here: http://id.loc.gov/vocabulary/relators.html

Let's look at one of the examples - the MARC presenter role: http://id.loc.gov/vocabulary/relators/pre.html

and see if we can we utilize it like in the image bellow. In this scenario the Presenter replaces the Attribution from the diagram Melissa had (we need to upload that one here as well). In this scenario I believe that under violeta, which is Agent, we can use any URI, including the VIVO URI. Thoughts?

Document standards for existing content and new contributions

We need to specify minimum requirements for developing our content. For example, classes should follow a naming convention, should have a text description, properties should have a domain and range, etc.

There are few existing resources to help with this. Let's find them and discuss in this issue.

Document how to create local extensions that could later be contributed to the core ontologies

The community can benefit from some documentation and guidance for how to extend the ontologies in a way that is consistent with our modeling principles, styles, etc.

Centralized place (wiki, issues, etc.) for end users and developers

We currently have the “vivo-isf/vivo-isf” GitHub repository to serve as a central place for issues and wiki pages that are for the general community and external stakeholders (not developers, contributors, etc.). The idea was to simplify what this group of people needs to understand. For example, if a VIVO user would like to propose that the VIVO-ISF needs to add a specific term or subdomain, this user should not have to figure out which specific repository deals with this, who to contact, etc. The user can go to the central place and create the issues. Someone on the core team will pick it up from there and implement and then update the issue to point the user to a more specific place for more details.

These users also have a Google Groups mailing list.

Does this setup work? Is it needed or useful? What should we change?

I think there is some confusion regarding the current setup due to the naming problem rather than the issue numbers. I think once we have a new name for the organization, we can make it very clear by following something like this:

https://github.com/new-name/community (currently vivo-isf/vivo-isf)
https://github.com/new-name/developers (currently vivo-isf/vivo-isf-dev)

Who are our current users?

Who currently uses any of the VIVO-ISF, or VIVO content? This could be applications, data, etc.

Automate some of the documentation

This is part of the release process (a tabled discussion for now, too early) but let's capture related thoughts and resources here.

Mailing lists, wikis, etc.

We can probably reorganize some of the existing resources such as websites, mailing lists, wikis, etc. to help the community and to help us keep up future development.

I think we agreed that we will have a new Google Group mailing list for the core development team. I'll create this once we have the new name.

Any ideas for reorganizing existing sites?

Provide tools and documentation for how to reuse the ontologies

Currently it is difficult to use the VIVO-ISF ontology due to its size, lack of official downloadable release, documentation not up to date, etc. We need tools and plans for addressing this issue.

We need a stable VM for a build server, testing, etc. Who can provide one?

Can anyone provide a VM for this project? I think we need as much memory as we can get to help with OWL reasoning.

Test issue 1

Test issue 1.
Matt

Understand and address data migration issues

We need a better understanding of how our ontologies are used to avoid creating problems going forward. For example, ontology changes might have significant impact on existing data, queries, reasoning, etc.

We need a well defined process for introducing change.

New name for the organization

We need a better name for our efforts and especially for the GitHub organization and repositories. The organization name should be general enough to cover the various projects we are involved in but still specific enough to be recognizable.

Along with the organization name we need a domain name. The GitHub organization name should be short if possible to help with GitHub mentions like @vivo-isf/dev-team.