Difference between revisions of "Reports Store Gateway scenarios for VME"
(→Scenarios) |
(→Question for Aureliano) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 41: | Line 41: | ||
**{Vme7-2011, ''Profile2009'', SpecificMeasure2011} | **{Vme7-2011, ''Profile2009'', SpecificMeasure2011} | ||
| − | + | ===FAQ=== | |
The above scenario shows objects in ''italics''. These objects are already part in past VMEs. Are the italic objects also editable when shown as being part of a VME? And do they need to be shown in iMarine reports as an immutable object? | The above scenario shows objects in ''italics''. These objects are already part in past VMEs. Are the italic objects also editable when shown as being part of a VME? And do they need to be shown in iMarine reports as an immutable object? | ||
| + | |||
| + | According to UML each set of fields is associated to a Year value, hence the last VME report (for each object) is built with the most recent values available for each fields. | ||
| + | |||
| + | *In case of a new report creation (new year value): a field can be edited based on previous content but the modification does not affect the old content and are stored as new content with a different year value | ||
| + | * In case of editing an existing report (editor selected one year among those available): the edited content overwrite the existing one for that year. If that specific content was not existing for that year (but retrieved from a previous year) then there are two options: | ||
| + | 1)the updated content is overwriting for all years | ||
| + | 2)the content goes as a new record for that particular year | ||
| + | |||
| + | probably option 2 is more correct, implying that if an editor wants to modify a content for all reports need to update the "root" one. | ||
Latest revision as of 18:24, 9 November 2013
Introduction
This page describes the foreseen data entry scenarios for the iMarine Reports for the VME-DB project. This scenario will use the Reports-store-gateway
Data structure
One iMarine VME Report manipulates these objects:
- Vme
- SpecificMeasure
- Profile
Then there 4 RefReports:
- GeneralMeasure
- InformationSource
- FisheryAreasHistory
- VmesHistory
Scenarios
Data entry actions are Create, Read, Update and Delete, so 4 in total.
The input dataset consists of these objects (a dash means has):
- Vme1
- Vme2 - Profile2012
- Vme3 - SpecificMeasure2012
- Vme4 - Profile2012 - SpecificMeasure2012
- Vme5 - Profile2011 - SpecificMeasure2009
- Vme6 - Profile2009 - SpecificMeasure2011
- Vme7 - Profile2008 - Profile2009 - SpecificMeasure2010 - SpecificMeasure2011
This means in RSG terms that:
- Vme1 has 1 Report (Vme with a year still to choose)
- Vme2 has 1 Report
- Vme3 has 1 Report
- Vme4 has 1 Report {Vme4-2012, Profile2012, SpecificMeasure2012}
- Vme5 has 2 Reports ({Vme5-2009, SpecificMeasure2009}, {Vme5-2011, Profile2011, SpecificMeasure2009})
- Vme6 has 2 Reports ({Vme6 -2009, Profile2009 }, {Vme6-2011, Profile2009 , SpecificMeasure2011 })
- Vme7 has 4 Reports
- {Vme7-2008, Profile2008}
- {Vme7-2009, Profile2009}
- {Vme7-2010, Profile2009, SpecificMeasure2010}
- {Vme7-2011, Profile2009, SpecificMeasure2011}
FAQ
The above scenario shows objects in italics. These objects are already part in past VMEs. Are the italic objects also editable when shown as being part of a VME? And do they need to be shown in iMarine reports as an immutable object?
According to UML each set of fields is associated to a Year value, hence the last VME report (for each object) is built with the most recent values available for each fields.
- In case of a new report creation (new year value): a field can be edited based on previous content but the modification does not affect the old content and are stored as new content with a different year value
- In case of editing an existing report (editor selected one year among those available): the edited content overwrite the existing one for that year. If that specific content was not existing for that year (but retrieved from a previous year) then there are two options:
1)the updated content is overwriting for all years 2)the content goes as a new record for that particular year
probably option 2 is more correct, implying that if an editor wants to modify a content for all reports need to update the "root" one.
Resources
- See also Reports-store-gateway
