21.10.2013 VME-DB

From D4Science Wiki
Revision as of 13:19, 22 October 2013 by Massimiliano.assante (Talk | contribs) (Notes)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Meeting 21 October 2013, 14:30 pm

Google Hangout

Present: M. Assante - CNR A. Gentile - FAO E. Van Ingen - FAO

Notes

  • A Web ServiceSelf-contained, self-describing, modular application that can be published, located, and invoked across the Web. Web services perform functions that can be anything from simple requests to complicated business processes. Once a Web service is deployed, other applications (and other Web services) can discover and invoke the deployed service. developed by FAO ( iMarineReportsWS in the following, not yet agreed though) will be in charge of interfacing the VME-DB and the iMarine Reports Web Application, in the following ReportsApp.
  • iMarineReportsWS source code will be hosted in the iMarine SVN service and should be Java6 compliant.
  • iMarineReportsWS will generate ReportModel instances (Java DTO) to be passed to the ReportsApp (that is capable of reading and display them nicely to the end users)
  • ReportsApp will send back the changes (deltas) performed by the end-users to the iMarineReportsWS. iMarineReportsWS will be in charge of reflecting the changes in the VME-DB. (deltas format still to be decided)
  • After 2 hours call conference, at the moment it is not clear how to perform the mapping between a VME-DB Report and the ReportModel (provided by iMarine in the gcube-reporting-library:
<groupId>org.gcube.portal</groupId>
<artifactId>gcube-reporting-library</artifactId>

However: a new Report Component Type is required in the ReportModel, a drop down list type allowing to select a predefined set of report components, populated by the iMarineReportsWS.

In case of VME-DB, this feature is aimed to support the "manual" association of a VME record to a sub-set of accompanying information (e.g. VME General Measure, VME History, Source of Information, etc.).

Next meeting

CNR is available to meet in Rome on Friday 25th to better understand and help the mapping between a VME-DB Report and the ReportModel. Maybe an hands-on session is required. If FAO is not available a call conference will be scheduled same day.

FAO to confirm for Friday 25th meeting.

CNR is not available to meet in Rome for the next 2 weeks, but is available for call conferences in the afternoon.