Difference between revisions of "Reports Store Gateway scenarios for VME"
From D4Science Wiki
(→Scenarios) |
(→Scenarios) |
||
| Line 32: | Line 32: | ||
*Vme2 has 1 Report | *Vme2 has 1 Report | ||
*Vme3 has 1 Report | *Vme3 has 1 Report | ||
| − | *Vme4 has 1 Report | + | *Vme4 has 1 Report {Vme4-2012, Profile2012, SpecificMeasure2012} |
| − | *Vme5 has 2 Reports(Vme5-2011 | + | *Vme5 has 2 Reports ({Vme5-2009, SpecificMeasure2009}, {Vme5-2011, Profile2011, SpecificMeasure2009}) |
| − | *Vme6 has 2 Reports | + | *Vme6 has 2 Reports ({Vme6 -2009, Profile2009 }, {Vme6-2011, Profile2009 , SpecificMeasure2011 }) |
*Vme7 has 4 Reports | *Vme7 has 4 Reports | ||
<br> | <br> | ||
Revision as of 17:03, 8 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
Resources
- See also Reports-store-gateway
