https://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362010-05-14T23:56:05ZEcoinformatics RedmineKepler - Bug #4988: Instantiating a wf as a composite that has a tag doesn't work as expectedhttps://projects.ecoinformatics.org/ecoinfo/issues/4988?journal_id=172452010-05-14T23:56:05ZDerik Barseghianbarseghian@nceas.ucsb.edu
<ul></ul><p>pushing to wrp-modules-2.X.Y as discussed in last call</p> Kepler - Bug #4988: Instantiating a wf as a composite that has a tag doesn't work as expectedhttps://projects.ecoinformatics.org/ecoinfo/issues/4988?journal_id=172462011-01-14T22:47:44ZSean Riddleswriddle@gmail.com
<ul></ul><p>(In reply to comment #0)</p>
<blockquote>
<p>However if I tag a workflow, Save Archive it into my local repo workflows<br />folder, then find and expand this KAR in the component library gui and drag the<br />workflow out to canvas, the parent does not get the tag. If I open the<br />composite, it's not in there either.</p>
</blockquote>
<p>This is expected behavior. The tag bar displays all tags on the top-level workflow. The tag is displayed in the original workflow, when it is on the top-level. When that workflow is instantiated into another as a composite, the tag is now on the composite, not on the top-level workflow, so it is not displayed in the tag bar. The tag's presence on the composite can be confirmed by selecting the Semantic Annotation Pane from the context menu of the composite.</p> Kepler - Bug #4988: Instantiating a wf as a composite that has a tag doesn't work as expectedhttps://projects.ecoinformatics.org/ecoinfo/issues/4988?journal_id=172472013-03-27T21:28:48ZRedmine Admin
<ul></ul><p>Original Bugzilla ID was 4988</p>