owlcollab / owlcollab/owltools
Comparing with most recent release
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 115
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
From cmung...@gmail.com on December 20, 2011 14:53:04
User should optionally be able to specify a path to the most recent editors version of the ontology prior to this release.
Prior to building, Oort can compare the current editors version with the previous one and check that every ID in the previous one is accounted for in the most recent one. In OBODoc terms, every ID should still be there (either for a deprecated or non-deprecated class) OR should be present as an altId.
In future we can also allow plugging in of OWLDiff or Amelia visual ontology differencing tool (though we may want to do this outside Oort, e.g. in Jenkins)
Original issue: http://code.google.com/p/owltools/issues/detail?id=28
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating Oort's build entry point and how it represents OBODoc identifiers; no source files or tests are named in the issue. Review how a prior editor's ontology path could be supplied and how IDs or altIds are checked before building. Done means the comparison is optional and verifies that every prior ID remains present or has an altId.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100