Kepler

now generating a new LSID when the reportInstance is assembled from provenance data

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?

for the time being, both ROMLs will be included.

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.

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?

I thought that too; not aware of any changes to that code.
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.

Okay - that makes more sense: same kar entry name (ROML.xml) but different LSIDs
That'll definitely need to be addressed...

I've prepended the workflow name to the ROML.xml entry that is generated.
While it's non-unique, perhaps it's the first step?
Can you try it out, Derik?

reading the history - i believe we can close this bug (again)

Original Bugzilla ID was 4151