https://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362009-06-12T19:25:02ZEcoinformatics RedmineKepler - Bug #4151: exported RIO and ROML doc run-pairs have same KeplerLSIDhttps://projects.ecoinformatics.org/ecoinfo/issues/4151?journal_id=140712009-06-12T19:25:02Zben leinfelderleinfelder@nceas.ucsb.edu
<ul></ul><p>now generating a new LSID when the reportInstance is assembled from provenance data</p> Kepler - Bug #4151: exported RIO and ROML doc run-pairs have same KeplerLSIDhttps://projects.ecoinformatics.org/ecoinfo/issues/4151?journal_id=140722009-06-15T22:00:30ZDerik Barseghianbarseghian@nceas.ucsb.edu
<ul></ul><p>In the case where I don't do anything with reporting, I get ROML.xml and ROML.N.xml files. The files are identical and have the same LSID. Is this supposed to happen?</p> Kepler - Bug #4151: exported RIO and ROML doc run-pairs have same KeplerLSIDhttps://projects.ecoinformatics.org/ecoinfo/issues/4151?journal_id=140732009-06-18T15:58:47Zben leinfelderleinfelder@nceas.ucsb.edu
<ul></ul><p>for the time being, both ROMLs will be included.</p> Kepler - Bug #4151: exported RIO and ROML doc run-pairs have same KeplerLSIDhttps://projects.ecoinformatics.org/ecoinfo/issues/4151?journal_id=140742009-06-18T18:23:03ZDerik Barseghianbarseghian@nceas.ucsb.edu
<ul></ul><p>This breaks the ability to export more than one run, since each run will have a ROML.xml, and an error about duplicate entries pops up from KARBuilder. It sounds like SANParks usecase doesn't need more than one run exported, so delaying the fix is ok, but shouldn't we just retarget the bug instead of closing it? Retargeting to 2.0.</p> Kepler - Bug #4151: exported RIO and ROML doc run-pairs have same KeplerLSIDhttps://projects.ecoinformatics.org/ecoinfo/issues/4151?journal_id=140752009-06-18T18:50:17Zben leinfelderleinfelder@nceas.ucsb.edu
<ul></ul><p>i thought we made it so that if they had the same LSID and the same name, we'd only include the last one that was added as a KAR Entry. did that change somewhere along the line in the last week or two?</p> Kepler - Bug #4151: exported RIO and ROML doc run-pairs have same KeplerLSIDhttps://projects.ecoinformatics.org/ecoinfo/issues/4151?journal_id=140762009-06-18T18:57:06ZDerik Barseghianbarseghian@nceas.ucsb.edu
<ul></ul><p>I thought that too; not aware of any changes to that code. <br />I think this problem only occurs when you're trying to export runs that use different workflows, multiple runs of the same workflow export into a kar fine.</p> Kepler - Bug #4151: exported RIO and ROML doc run-pairs have same KeplerLSIDhttps://projects.ecoinformatics.org/ecoinfo/issues/4151?journal_id=140772009-06-18T23:58:44Zben leinfelderleinfelder@nceas.ucsb.edu
<ul></ul><p>Okay - that makes more sense: same kar entry name (ROML.xml) but different LSIDs<br />That'll definitely need to be addressed...</p> Kepler - Bug #4151: exported RIO and ROML doc run-pairs have same KeplerLSIDhttps://projects.ecoinformatics.org/ecoinfo/issues/4151?journal_id=140782009-06-19T00:11:34Zben leinfelderleinfelder@nceas.ucsb.edu
<ul></ul><p>I've prepended the workflow name to the ROML.xml entry that is generated.<br />While it's non-unique, perhaps it's the first step?<br />Can you try it out, Derik?</p> Kepler - Bug #4151: exported RIO and ROML doc run-pairs have same KeplerLSIDhttps://projects.ecoinformatics.org/ecoinfo/issues/4151?journal_id=140792009-06-24T18:45:05Zben leinfelderleinfelder@nceas.ucsb.edu
<ul></ul><p>reading the history - i believe we can close this bug (again)</p> Kepler - Bug #4151: exported RIO and ROML doc run-pairs have same KeplerLSIDhttps://projects.ecoinformatics.org/ecoinfo/issues/4151?journal_id=140802013-03-27T21:25:50ZRedmine Admin
<ul></ul><p>Original Bugzilla ID was 4151</p>