Difference between revisions of "23.07.2012 WP3 Progress"

From D4Science Wiki
Jump to: navigation, search
(Created page with "== WP3 Progress and Planning (Summary of several Skype Meetings) == === Participants === * FAO: A. Ellenbroek, Y.Laurent * CNR: P.Pagano, GP.Coro, L.Lelli * Trust-IT: N.Fergu...")
 
(Notes)
Line 11: Line 11:
  
 
# WP4 materials  
 
# WP4 materials  
## FAO and CNR to use the same demo format; a screencast; description  of format; intro – action – summary; in total 2-3 mins
+
## Demonstration screencasts (P.pagano, A.Ellenbroek)
## Ecological Niche modeling example. CNR already presented examples at TCOM. Plans to produce 4 portlets with different screencasts.  
+
### FAO and CNR to use the same demo format; a screencast; description  of format; intro – action – summary; in total 2-3 mins
 +
### Ecological Niche modeling example. CNR already presented examples at TCOM. Plans to produce 4 portlets with different screencasts.  
 
### CNR: department can provides a style; Lino to share example with Anton.  
 
### CNR: department can provides a style; Lino to share example with Anton.  
## Demo titles for Anton; “Upload a ts Cl and batch replace”, “Filter & send to R”
+
### Demo titles for Anton; “Upload a ts Cl and batch replace”, “Filter & send to R”. Aims at 31 July.
## CNR: will demo the new biodiversity functionality.  The planning is to have 2-3 screencasts per VRE
+
### CNR: will demo the new biodiversity functionality.  The planning is to have 2-3 screencasts per VRE
## iMarine App; Community info, e.g. only a species search input box, plus a few info sheets. Anton will try to discuss with Nicolas (no reply until 23-07)
+
## iMarine App; (H.Hanahoe, S.Garavelli, A.Ellenbroek, L.Pagano)
 +
### Anton distributed a high level use-case, to be reviewed by Trust-IT. An android app would contain species fact sheets, combining multiple community information. It would have a species name search input, plus a few info sheets; FAO-Facts, AM-Distro, FAO-Stats, FAO-SpeciesMap, OBIS-Names.  
 +
### Trust-IT to discuss with their developers, and will reply.
 +
### Anton will try to discuss with N.Bailly on more community requirements (no reply until 23-07), and on species fact sheet info.
 +
## Training material (Yann Laurent, N.Fergusson, A.Ellenbroek)
 +
### The focus for now is to develop a training material development plan. Most VRE's are still being extended, and the training material has to aim at better identified communities. The FAO case to use ICIS for the Tuna Atlas, and FCPPS for the VME-DB reporting are advanced, and development of the training material can start, after the community has been consulted.
 +
### Feed-back from the communities indicate that the UI has to be made 'simpler', i.e. align closer to their specific use-case, and be less generic. Another suggestion is to have better identified steps in the VRE, to give users a clear idea where they are, and what they are expected to do, and ease the identification of training and assistance materials. E.g. in ICIS there could be steps 1. Input, 2. Curation, 3. Analysis, 4. Sharing and Publication.
 +
### Trust-IT will send a list of question to FAO on the expected VRE's, who they will serve, and what is expected in terms of training courses and materials.
  
 
# ICIS  
 
# ICIS  
Line 22: Line 30:
 
### Support for Work-flow,  
 
### Support for Work-flow,  
 
### Structure support (DSD, ‘template’);  
 
### Structure support (DSD, ‘template’);  
### September CNR will deliver ‘ Read SDMX’. With DSD. The dependency on curation to control the validity remains.  
+
### September CNR will deliver ‘ Read SDMX’. With DSD. The dependency on manual curation to control the validity remains.  
### September Removal of duplicates.  
+
### CNR: September Removal of duplicates.  
### However, the requirements are huge, and FAO expects this will continue until project end. Adaptive management support will always be required, just like for all comparable information systems.   
+
### Yann welcomed progress, and reported that CNR has the correct priorities.
### At a later stage, the production of SDMX will start. There is however no registry integrated yet.
+
### Anton noted that the requirements are huge, and FAO expects ICIS development to continue until project end. Adaptive management support will always be required, just like for all comparable information systems.   
 +
### CNR reported that production of SDMX will start after September. There is no registry integrated yet.
 
### CNR has dedicated Lucio and Federico to ICIS until December.   
 
### CNR has dedicated Lucio and Federico to ICIS until December.   
### CNR seeks the involvement of NKUA for maps visualization
+
### CNR seeks the involvement of NKUA for maps visualization, where NKUA has specialized expertise.
## ICIS Review document. Anton suggests to discuss mainly Discuss annex 4, then more detail. Yann’s main issues are lack of flexibility in the curation phase for aggregating, lack of structure support (DSD), and lack of work-flows (with update policies)
+
### Yann identified prioties for TA use case exploiting ICIS:
### Yann identified next steps:
+
#### Duplicated columns. Lino: could be available mid-October
### a
+
#### 5x5 square definition replaced by a unique ID
### another
+
#### Persistence of indicator definition
## SPREAD; FAo asked about the CNR support to the scenario. (Read from FAO, import / export JSON, an algoritm, WPS, Vizualization)
+
 
 +
## SPREAD; FAO asked about the CNR support to the scenario. (Read from FAO, import / export JSON, an algoritm, WPS, Vizualization)
 
### FAO can postpone reading geospatial data from FAO.  
 
### FAO can postpone reading geospatial data from FAO.  
### JSON; Lino re-allocation can be done using JSON. Propose export import JSON. Will verify with Federico. Data access and storage as TimeSeries in the e-infrastructure, and also the WPS for re-allocation algorithm is part of the e-infrastructure.  
+
### JSON; P.Pagano: technically ICIS can read / write JSON representations of TS. However, CNR has a more advanced approach. GP Coro will explain.  
## FAO will have to elaboarte on the requirements for vizualization.  
+
### Data access and storage of re-allocated data will be as TimeSeries in the e-infrastructure, and also the WPS for re-allocation algorithm is part of the e-infrastructure.
# Plans for reporting features based on FCPPS;
+
### GP Coro explained the status of the technology work. The interface to the TS environment is nearly ready, and Emmanuel can implement that to gain access to TS object. He is passed references to db objects, to the WPS, and the Postgis database. This should be enough to perform the reallocation, and pass the result back to the TS environment. When Lucio is ready, he can assist Emmanuel in the implementation.
## off-line tool for FishFinder, and  
+
### For displaying TS and re-allocated TS on maps, FAO will have to elaborate on the requirements for vizualization.  
## geo features for VME DB
+
 
## off-line tool for FishFinder,  
+
# Plans for reporting features based on FCPPS; Anton reported at the TCom that there are the following desiderata:
## Lino : Can offer a distro for a laptop. Part for authors to write, import / export from a file, not from workspace. JAVA desktop application.  
+
## off-line tool for FishFinder, and   
## Anton Suggests server 2 go or similar, only need to interact with MyDocuments folder, some folder organization suggestions
+
### Lino : CNR can offer a FCPPS distro for a laptop. Part for authors to write, import / export from a file, not from workspace. JAVA desktop application.  
## PP: Will discuss features in CNR
+
### Anton Suggests server-2-go or similar, which can be distributed on a flash drive, to avoid any installation issues. The only need is then to interact with MyDocuments folder, if the storage on the flash drive is not sufficient.
## Anton The new VMEDB may require geo features  
+
### PP: Will discuss features in CNR
## PP: Asks for requirements. Activity to start in 2013
+
## VME-DB; the requirements have been collected. FAO is demoing this week the opportunity of FCPPS in Mauritius.
# COTRIX; on an rdf store, add versioning and codelist mapping.
+
### Anton The new VMEDB may require interactive geo features; 2 persons drawing together a confidential map. 
## AE: Align with FAO initiatives in software, e.g. data.fao.org and VocBench, all seemingly moving to OWLIM 5.  
+
### PP: Asks for requirements. But any activity can not start before 2013
## Anton: trying to recruit a developer in Bangkok to add versioning and time dimension to VoCBench. Also allows to generate private codelists from published ones.  
+
 
 +
# COTRIX; Code list management using an rdf store. FAO plans to add versioning, time awareness and code list mapping to the existing VocBench project.  
 +
## Anton: We aim to collaborate with several FAO initiatives in software, e.g. data.fao.org, phenix workstation, and VocBench, all seemingly moving to OWLIM 5.  
 +
## Anton: FAO is trying to recruit a developer in Bangkok to add versioning and time dimension to VoCBench. Also allows to generate private codelists from published ones.  
 +
 
 
# VRMF:  
 
# VRMF:  
## Anton suggest that Federico and Fabio Simeoni discuss with F.Fiorellato on mutual benefits.  
+
## Anton suggest that Federico and Fabio Simeoni discuss with F.Fiorellato on mutual benefits and sharing services.
 
## Lino notes that CNR has participated in a similar project. A real opportunity for collaboration because the need also exists elsewhere:  
 
## Lino notes that CNR has participated in a similar project. A real opportunity for collaboration because the need also exists elsewhere:  
## Also needed in the Biodiversity area for reconciliation.  
+
## Entity distance calculation are also needed in the Biodiversity area for reconciliation.  
## Also the gazetteer, mentioned by DGMARE. Beginning October.
+
## VRMF can already offer the use of a gazetteer, mentioned by DGMARE.  
 +
## By the beginning October a draft plan can be ready to present to the next Board Meeting.

Revision as of 14:47, 26 July 2012

WP3 Progress and Planning (Summary of several Skype Meetings)

Participants

  • FAO: A. Ellenbroek, Y.Laurent
  • CNR: P.Pagano, GP.Coro, L.Lelli
  • Trust-IT: N.Fergusson

Notes

  1. WP4 materials
    1. Demonstration screencasts (P.pagano, A.Ellenbroek)
      1. FAO and CNR to use the same demo format; a screencast; description of format; intro – action – summary; in total 2-3 mins
      2. Ecological Niche modeling example. CNR already presented examples at TCOM. Plans to produce 4 portlets with different screencasts.
      3. CNR: department can provides a style; Lino to share example with Anton.
      4. Demo titles for Anton; “Upload a ts Cl and batch replace”, “Filter & send to R”. Aims at 31 July.
      5. CNR: will demo the new biodiversity functionality. The planning is to have 2-3 screencasts per VREVirtual Research Environment.
    2. iMarine App; (H.Hanahoe, S.Garavelli, A.Ellenbroek, L.Pagano)
      1. Anton distributed a high level use-case, to be reviewed by Trust-IT. An android app would contain species fact sheets, combining multiple community information. It would have a species name search input, plus a few info sheets; FAO-Facts, AM-Distro, FAO-Stats, FAO-SpeciesMap, OBIS-Names.
      2. Trust-IT to discuss with their developers, and will reply.
      3. Anton will try to discuss with N.Bailly on more community requirements (no reply until 23-07), and on species fact sheet info.
    3. Training material (Yann Laurent, N.Fergusson, A.Ellenbroek)
      1. The focus for now is to develop a training material development plan. Most VREVirtual Research Environment.'s are still being extended, and the training material has to aim at better identified communities. The FAO case to use ICIS for the Tuna Atlas, and FCPPS for the VME-DB reporting are advanced, and development of the training material can start, after the community has been consulted.
      2. Feed-back from the communities indicate that the UI has to be made 'simpler', i.e. align closer to their specific use-case, and be less generic. Another suggestion is to have better identified steps in the VREVirtual Research Environment., to give users a clear idea where they are, and what they are expected to do, and ease the identification of training and assistance materials. E.g. in ICIS there could be steps 1. Input, 2. Curation, 3. Analysis, 4. Sharing and Publication.
      3. Trust-IT will send a list of question to FAO on the expected VREVirtual Research Environment.'s, who they will serve, and what is expected in terms of training courses and materials.
  1. ICIS
    1. Plans for ICIS; also in a meeting with Yann. Lino Explains what is in the scaffolds:
      1. Support for Work-flow,
      2. Structure support (DSD, ‘template’);
      3. September CNR will deliver ‘ Read SDMX’. With DSD. The dependency on manual curation to control the validity remains.
      4. CNR: September Removal of duplicates.
      5. Yann welcomed progress, and reported that CNR has the correct priorities.
      6. Anton noted that the requirements are huge, and FAO expects ICIS development to continue until project end. Adaptive management support will always be required, just like for all comparable information systems.
      7. CNR reported that production of SDMX will start after September. There is no registry integrated yet.
      8. CNR has dedicated Lucio and Federico to ICIS until December.
      9. CNR seeks the involvement of NKUA for maps visualization, where NKUA has specialized expertise.
      10. Yann identified prioties for TA use case exploiting ICIS:
        1. Duplicated columns. Lino: could be available mid-October
        2. 5x5 square definition replaced by a unique ID
        3. Persistence of indicator definition
    1. SPREAD; FAO asked about the CNR support to the scenario. (Read from FAO, import / export JSON, an algoritm, WPS, Vizualization)
      1. FAO can postpone reading geospatial data from FAO.
      2. JSON; P.Pagano: technically ICIS can read / write JSON representations of TS. However, CNR has a more advanced approach. GP Coro will explain.
      3. Data access and storage of re-allocated data will be as TimeSeries in the e-infrastructure, and also the WPS for re-allocation algorithm is part of the e-infrastructure.
      4. GP Coro explained the status of the technology work. The interface to the TS environment is nearly ready, and Emmanuel can implement that to gain access to TS object. He is passed references to db objects, to the WPS, and the Postgis database. This should be enough to perform the reallocation, and pass the result back to the TS environment. When Lucio is ready, he can assist Emmanuel in the implementation.
      5. For displaying TS and re-allocated TS on maps, FAO will have to elaborate on the requirements for vizualization.
  1. Plans for reporting features based on FCPPS; Anton reported at the TCom that there are the following desiderata:
    1. off-line tool for FishFinder, and
      1. Lino : CNR can offer a FCPPS distro for a laptop. Part for authors to write, import / export from a file, not from workspace. JAVA desktop application.
      2. Anton Suggests server-2-go or similar, which can be distributed on a flash drive, to avoid any installation issues. The only need is then to interact with MyDocuments folder, if the storage on the flash drive is not sufficient.
      3. PP: Will discuss features in CNR
    2. VME-DB; the requirements have been collected. FAO is demoing this week the opportunity of FCPPS in Mauritius.
      1. Anton The new VMEDB may require interactive geo features; 2 persons drawing together a confidential map.
      2. PP: Asks for requirements. But any activity can not start before 2013
  1. COTRIX; Code list management using an rdf store. FAO plans to add versioning, time awareness and code list mapping to the existing VocBench project.
    1. Anton: We aim to collaborate with several FAO initiatives in software, e.g. data.fao.org, phenix workstation, and VocBench, all seemingly moving to OWLIM 5.
    2. Anton: FAO is trying to recruit a developer in Bangkok to add versioning and time dimension to VoCBench. Also allows to generate private codelists from published ones.
  1. VRMF:
    1. Anton suggest that Federico and Fabio Simeoni discuss with F.Fiorellato on mutual benefits and sharing services.
    2. Lino notes that CNR has participated in a similar project. A real opportunity for collaboration because the need also exists elsewhere:
    3. Entity distance calculation are also needed in the Biodiversity area for reconciliation.
    4. VRMF can already offer the use of a gazetteer, mentioned by DGMARE.
    5. By the beginning October a draft plan can be ready to present to the next Board Meeting.