Difference between revisions of "Reports Store Gateway scenarios for VME"

From D4Science Wiki
Jump to: navigation, search
(Scenarios)
(Scenarios)
Line 25: Line 25:
 
* Profile(P)
 
* Profile(P)
  
{| width="200" border="1" cellpadding="1" cellspacing="1"
+
{| class="prettytable"
 
|-
 
|-
 
|
 
|
Line 56: Line 56:
 
|-
 
|-
 
|
 
|
#
+
 
  
 
|
 
|
Line 84: Line 84:
 
|-
 
|-
 
|
 
|
#
+
 
  
 
|
 
|
Line 112: Line 112:
 
|-
 
|-
 
|
 
|
#
+
 
  
 
|
 
|
Line 140: Line 140:
 
|-
 
|-
 
|
 
|
#
+
 
  
 
|
 
|
Line 193: Line 193:
 
|-
 
|-
 
|
 
|
#
+
 
  
 
|
 
|
Line 209: Line 209:
 
|-
 
|-
 
|
 
|
#
+
 
  
 
|
 
|
Line 225: Line 225:
 
|-
 
|-
 
|
 
|
#
+
 
  
 
|
 
|
Line 241: Line 241:
 
|-
 
|-
 
|
 
|
#
+
 
  
 
|
 
|
Line 257: Line 257:
 
|-
 
|-
 
|
 
|
#
+
 
  
 
|
 
|

Revision as of 14:45, 4 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

  • Vme (V)
  • SpecificMeasure(SM)
  • Profile(P)

Scenario

V 2010

V 2011

SM 2009

SM 2010

SM 2012

P 2010

P 2011

P 2012


*


*



*




*



*



*



*




*



*


*

*

*

*

*

*

*

*


  • GeneralMeasure (GM)
  • InformationSource (IS)
  • FisheryAreasHistory (FH)
  • VmesHistory (VH)

Scenario

GM 2009

IS 2010

FH 2011

VH 2012


*






*






*






*


*

*

*

*

Resources