feature to create ontology and use created ontology to replace existing version

[mmisw]

_From steph_wa...@consolidated.net on November 09, 2009 14:51:48_

What capability do you want added or improved? Shouldn't we add some capability to avoid the issue that we had with CF-- where we had an XML file of a vocabulary (not yet an ontology) and we needed, within the portal, to: a) develop a new ontology, and b) upload that new ontology to replace an existing ontology. In other words, we were trying to create ontology and then replace one with this new version. If I'm not mistaken, portal users can only create an ontology and then register it as a new ontology (not as an updated version) in the portal. Where do you want this capability to be accessible? from the voc2rdf component What sort of input/command mechanism do you want? button for registering as an updated version What is the desired output (content, format, location)? Other details of your desired capability? What version of the product are you using? Please provide any additional information below (particular ontology/ies, text contents of vocabulary (voc2rdf), operating system, browser/version (Firefox, Safari, Chrome, IE, etc.), screenshot, etc.)

Original issue: http://code.google.com/p/mmisw/issues/detail?id=217

[mmisw]

From caru...@gmail.com on November 09, 2009 16:28:18

I think issue #203 (already implemented) addresses the feature described here. In fact, I used the new feature to be able to register the new version of the CF vocab. Can you review and confirm? If so, then this issue can be marked as duplicate with reference to issue #203 (so it gets merged into it). Thanks.

[mmisw]

_From steph_wa...@consolidated.net on November 10, 2009 08:29:06_

I don't think 203 is quite the same thing. Your new feature allows for in-place editing or an upload of an ontology (not a simple vocabulary) file. For vocabularies that are not yet ontologies (like CF started out),where there are significant changes to a vocabulary (too cumbersome to do with in-place editing), the portal should allow for a) creating a new ontology file from the updated/significantly changed vocabulary, and b) registering this file as an update to an existing ontology file in the ORR.

[mmisw]

From caru...@gmail.com on November 10, 2009 12:27:46

Hi Stephanie,

So it seems this issue is basically about your point a) that is, facilitating the conversion from something not-already-in-ontology-format to an ontology format. (Your point b) is what issue #203 is about.)

I'm CC-ing Luis here as he has the tool to do the conversion in the CF case. We would like the conversion to be fully automated, even including the registration step, but I doubt we can have all of that in the near future. Comments/suggestions welcome.

Cc: bermud

[mmisw]

From caru...@gmail.com on November 25, 2009 09:29:35

Just setting ownership to Luis. Luis: please comment/update at your convenience.

Owner: bermud
Cc: -bermud

[mmisw]

From caru...@gmail.com on August 05, 2010 12:35:35

I'm updating this entry according to recent re-prioritization of tasks as well as developments in the watchdog module: https://code.google.com/p/mmisw/source/browse/trunk/org.mmisw.watchdog/README.txt

Status: Started
Owner: carueda
Cc: jgrayb...@ucsd.edu
Labels: -Priority-Medium Priority-High watchdog Milestone-Beta1

[mmisw]

From caru...@gmail.com on August 05, 2010 17:32:33

Upon re-reading the original request and the other comments in this entry, I'm closing it because:

• there are mechanisms to create ontologies and registering them within the ORR itself, in concrete: "tabular" vocabularies (using the "voc2rdf" interface), and mappings (using the "vine" interface). This is possible for both creation and submission of new versions.
• there is the mechanism to upload existing ontologies.
• the mechanism to upload an external ontology and replace the corresponding existing version has also been in place. So the statement, "portal users can only create an ontology and then register it as a new ontology (not as an updated version) in the portal" is incorrect.

(Regarding the associated metadata, it's worth clarifying that in the process of registering a new version from the file being uploaded, the user has the ability to give preference to either the file being uploaded or the ontology already registered to pre-fill the metadata sections. But all of this can be further edited if necessary before the final registration of the new version.)

• creation/registration of ontologies from files that are not in a recognized format (see issue #271 ) is a functionality being addressed by the "watchdog" module, see: https://code.google.com/p/mmisw/issues/list?can=2&q=label%3Awatchdog

Status: Fixed
Cc: -jgrayb...@ucsd.edu