Closed mmisw closed 8 years ago
From ber...@gmail.com on December 14, 2009 11:25:24
Summary for interface: Simple Web interface for opening and editing issues Summaries of open issues Associate issues with working groups Unique URI for every issue Summary of issues with all comments and status
From caru...@gmail.com on December 22, 2009 00:06:43
priority critical per OOI semantic prototype requirement.
Owner: carueda
Labels: -Type-Defect Type-Enhancement ooici Usability
From caru...@gmail.com on December 22, 2009 00:07:08
Labels: -Priority-Medium Priority-Critical
From caru...@gmail.com on January 05, 2010 12:53:37
Issues to be resolved for Beta 1 release
Labels: Milestone-Beta1
From jgrayb...@ucsd.edu on April 05, 2010 16:53:47
Not for Beta1, we'll have to look at this after Beta1 release.
Labels: -Milestone-Beta1
From jgrayb...@ucsd.edu on April 05, 2010 16:54:19
Labels: -Priority-Critical Priority-High
From jgrayb...@ucsd.edu on April 05, 2010 17:22:21
I concur, this is a really important improvement/feature. But it is not absolutely required for Beta1 release.
I think it is among the top five to address after the Beta1 critical issues are fixed.
Do we really want this? I agree it would be a nice-to-have, but I think users would be better off with some of the many issue tracker options out there to support the development/improvement of artifacts like ontology files. Perhaps just include some (optional) metadata property to capture where the associated issue tracker is located?
I agree, it is nice to have but not essential, and it would be hard to implement well in a short period of time. And BioPortal hasn't had good uptake on their similar feature, so it isn't automatically of great value.
Pointing to a separate project issue list would be a very nice feature instead.
Ideally someday we could get the number of open issues for a given ontology project, and display it in ORR. But not today.
Changed priorities accordingly.
Do we need to create a new issue or can we continue tracking here?
Huh, never meant to close in the first place. So, reopened.
Let's close this (as it was very specific about a proper issue tracker in the ORR system), and open a new one about just capturing a pointer to an associated issue tracker.
OK, created #382 and am closing this.
From ber...@gmail.com on December 11, 2009 09:08:14
Allow an ontology to have an issue list Ontology can have one..many issues Issue has status Issue has one to many comments
Original issue: http://code.google.com/p/mmisw/issues/detail?id=230