[kepler-dev] [Bug 5017] ReportLayout LSID and referral list should be maintained

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5017

Derik Barseghian <barseghian at nceas.ucsb.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |

--- Comment #6 from Derik Barseghian <barseghian at nceas.ucsb.edu> 2010-06-07 15:42:34 PDT ---
Hey Debi, while it may be ok to only increment the LSID whenever a report
layout is saved, one of the ways a report layout is saved is to provenance when
the workflow is run. So if the LSID now only increments during a save to KAR,
that won't be sufficient because of the following scenario:

1) Design a workflow and report layout
2) Execute (call this run1)
3) Change the report layout
4) Execute (call this run2)
5) Export to KAR run1
6) Export to KAR run2

run1.kar and run2.kar now contain two different report layouts, but each with
the same LSID.

Less important, but just to note: another reason I'm not a fan of this approach
is that you can design a workflow and report, save to kar, then save to another
kar, and you then have two report layouts that are essentially identical, but
simply have different LSIDs (the LSID is the only thing keeping them from being
the same).

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.