Difference between revisions of "AppliFish2"
From D4Science Wiki
(Created page with "; Product : Like AppliFish, AppliFishs will be an iMarine Species App for Android / iPhone devices. The application differs from AppliFish in that it has update and feed-back fea...") |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
; Product | ; Product | ||
| − | : Like AppliFish, | + | : Like AppliFish, AppliFish2 will be an iMarine Species App for Android / iPhone devices. The application differs from AppliFish in that it has update and feed-back features, integration with more gCube services, and access to an SDMX registry. |
| − | The app is a mash-up of FAO - Fishbase - OBIS - WoRMS data, and will depend on a VRE for database preparation, and reads from an iMarine geoserver to read AquaMaps. | + | The app is a mash-up of FAO - Fishbase - OBIS - WoRMS - IUCN data, and will depend on a VRE for database preparation, and reads from an iMarine geoserver to read AquaMaps. |
| − | The expected VRE will be used to 1. Manage the database behind AppliFish, including the extraction, harmonization, denormalization and transformation of source data, 2. Manage the synchronization with the individual application instances, and 3. collect feed-back from | + | The expected VRE will be used to 1. [https://issue.imarine.research-infrastructures.eu/ticket/1627 Manage] the database content behind AppliFish, including the extraction, harmonization, denormalization and transformation of source data, 2. [https://issue.imarine.research-infrastructures.eu/ticket/1636 Manage] the synchronization with the individual application instances, and 3. [https://issue.imarine.research-infrastructures.eu/ticket/1637 collect] feed-back from AppliFish instances, and 4. prepare [https://issue.imarine.research-infrastructures.eu/ticket/1638 reports] on app-use in the e-infrastructure. |
| + | Such an Application, combined with a large infrastructure, can be a very attractive proposistion for EA-CoP user that define and design spatial management plans, and require field-surveys to validate e.g. statistical data or geospatial information. An example from the forestry domain that takes this inclusive approach is offered by [http://silviaterra.com/#timber-scout SilviaTerra]. | ||
| − | == | + | == AppliFish2 proposal== |
| − | The fact sheets | + | The fact sheets fields nearly identical to AppliFish. |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
The expected changes are: | The expected changes are: | ||
# The inclusion of a [[AppliFish2 feed-back page]]; | # The inclusion of a [[AppliFish2 feed-back page]]; | ||
| − | |||
# The inclusion of a targeted Search, provided by NKUA, on e-infrastructure and selected OAI repositories; | # The inclusion of a targeted Search, provided by NKUA, on e-infrastructure and selected OAI repositories; | ||
| − | |||
# [[AppliFish2 Synchronization]] features; | # [[AppliFish2 Synchronization]] features; | ||
| − | |||
# [[Country statistics reading from the iMarine SDMX registry]]; | # [[Country statistics reading from the iMarine SDMX registry]]; | ||
| + | # Additional species. | ||
| − | + | In order to efficiently cater for the above needs, a specialized VRE to manage and serve the data behind the App is forseen. | |
; Priority to CoP | ; Priority to CoP | ||
| Line 72: | Line 45: | ||
; Presentation | ; Presentation | ||
: The App component will be similar to AppliFish. | : The App component will be similar to AppliFish. | ||
| − | : The UI Design of the VRE will be similar to ICIS. this will have to be enriched with features for reading from a WS into a temporary database table, a PgAdmin or similar tool to manage the database, a facility to export to a graph or | + | : The UI Design of the VRE will be similar to ICIS. this will have to be enriched with features for reading from a WS into a temporary database table, a PgAdmin or similar tool to manage the database, a facility to export to a graph or other visualization, a reporting tool for analysis, etc. |
| − | : There will be only a few | + | : There will be only a few datamanagers, who do not need specific context related on-line help, or training material. |
: No support is needed for VRE users, while some support may be required for AppliFish2 users in the field. | : No support is needed for VRE users, while some support may be required for AppliFish2 users in the field. | ||
Latest revision as of 09:38, 1 July 2013
- Product
- Like AppliFish, AppliFish2 will be an iMarine Species App for Android / iPhone devices. The application differs from AppliFish in that it has update and feed-back features, integration with more gCube services, and access to an SDMX registry.
The app is a mash-up of FAO - Fishbase - OBIS - WoRMS - IUCN data, and will depend on a VREVirtual Research Environment. for database preparation, and reads from an iMarine geoserver to read AquaMaps.
The expected VREVirtual Research Environment. will be used to 1. Manage the database content behind AppliFish, including the extraction, harmonization, denormalization and transformation of source data, 2. Manage the synchronization with the individual application instances, and 3. collect feed-back from AppliFish instances, and 4. prepare reports on app-use in the e-infrastructure.
Such an Application, combined with a large infrastructure, can be a very attractive proposistion for EA-CoPCommunity of Practice. user that define and design spatial management plans, and require field-surveys to validate e.g. statistical data or geospatial information. An example from the forestry domain that takes this inclusive approach is offered by SilviaTerra.
AppliFish2 proposal
The fact sheets fields nearly identical to AppliFish.
The expected changes are:
- The inclusion of a AppliFish2 feed-back page;
- The inclusion of a targeted Search, provided by NKUA, on e-infrastructure and selected OAI repositories;
- AppliFish2 Synchronization features;
- Country statistics reading from the iMarine SDMX registry;
- Additional species.
In order to efficiently cater for the above needs, a specialized VREVirtual Research Environment. to manage and serve the data behind the App is forseen.
- Priority to CoPCommunity of Practice.
- List priorities following the iMarine Board priority setting criteria:
- While AppliFish was intended as a demonstration of iMarine data and potential, AppliFish2 will add communication tools
- The expected users are contacts of iMarine partners that have shown interest to contribute to the project in general, and marine species information in particular;
- AppliFish1 was entirely funded through the project, but was quick to draw attention. AppliFish2 may be considered as an option to attract co-funding, e.g. through FAO Species Groups;
- There will NOT not been a Structural allocation of resources;
- The app is not referred in DoW;
- AppliFish2 is conceived more to serve the biodiversity community, but as communication tool also fits with BC1;
- The action attracts attention and increases visibility of the project. It thus indirectly supports sustainability aspects;
- AppliFish was a test-bed for mobile app development. AppliFish2 will have to be validated against the data providers data policies;
- AppliFish2 will re-use AppliFish base design, and can probably re-use ICIS resources for data management in a VREVirtual Research Environment.. The development path of AppliFish2, aiming at both Android and iOS users will widen the user base;
- Parentage
- The app data are loaded with CoPCommunity of Practice. Software; using FAO web-services, WoRMS web services, Fishbase database extractions;
- The ICIS VREVirtual Research Environment. is used to prepare data to load, and a D4S geoserver is used to store the maps.
- Productivity
- Basing AppliFish2 on a VREVirtual Research Environment. is new, and the effectiveness can not be measured against another approach.
- The application is a test bed for data collection, and thus does not reduce a known workload
- Presentation
- The App component will be similar to AppliFish.
- The UI Design of the VREVirtual Research Environment. will be similar to ICIS. this will have to be enriched with features for reading from a WS into a temporary database table, a PgAdmin or similar tool to manage the database, a facility to export to a graph or other visualization, a reporting tool for analysis, etc.
- There will be only a few datamanagers, who do not need specific context related on-line help, or training material.
- No support is needed for VREVirtual Research Environment. users, while some support may be required for AppliFish2 users in the field.
- Policy
- Are there any policies available that describe data access and sharing?
- Have the Copyright / attribution / metadata / legal aspects been addressed from a user and technology perspective?
