owlcollab / owlcollab/owltools
Creating a change report for an ontology
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 115
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
From HDie...@lbl.gov on March 04, 2013 12:45:05
The ontology editors want customized report and summaries for ontology changes.
We need to decide whether to keep tweaking Amelia's perl code, switch to a 3rd party solution (such as James Malone's Boubakis), or different options in Jenkins.
This issue is a place holder, as this might not be implemented in owltools.
Original issue: http://code.google.com/p/owltools/issues/detail?id=56
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
Review the issue's listed alternatives: Amelia's Perl code, a third-party solution such as Boubakis, and Jenkins options. This is a placeholder and may not be implemented in OWLTools, so first establish scope and acceptance criteria; done means a decided approach for producing customized ontology change reports.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100