Difference between revisions of "Ecosystem Approach Community of Practice: SPREAD"
(→Product) |
(→Product) |
||
| Line 17: | Line 17: | ||
With SPREAD capture time-series can be | With SPREAD capture time-series can be | ||
| − | + | ==== Priority to CoP ==== | |
''List proposed solution priority following the iMarine Board priority setting criteria: '' | ''List proposed solution priority following the iMarine Board priority setting criteria: '' | ||
| Line 29: | Line 29: | ||
* ''Re-usability – benefits – compatibility'' | * ''Re-usability – benefits – compatibility'' | ||
| − | + | ==== Parentage ==== | |
''Relation to CoP Software'' | ''Relation to CoP Software'' | ||
''Relation to D4S technologies'' | ''Relation to D4S technologies'' | ||
| Line 37: | Line 37: | ||
''If the proposed solution can be used in another SW scenario (not users!) please describe.'' | ''If the proposed solution can be used in another SW scenario (not users!) please describe.'' | ||
| − | + | ==== Public ==== | |
''How big is the expected user community after delivery?'' | ''How big is the expected user community after delivery?'' | ||
| − | + | ==== Productivity ==== | |
''Are the proposed measures effective?'' | ''Are the proposed measures effective?'' | ||
''Does it reduce a known workload?'' | ''Does it reduce a known workload?'' | ||
| − | + | ==== Price ==== | |
''Is the proposed solution cheap?'' | ''Is the proposed solution cheap?'' | ||
''Expected effort in PM:'' | ''Expected effort in PM:'' | ||
| − | + | ==== Presentation ==== | |
''How is the component delivered to users? (Design / on-line help / training material / support).'' | ''How is the component delivered to users? (Design / on-line help / training material / support).'' | ||
| − | + | ==== Privacy ==== | |
''Are they safe?'' | ''Are they safe?'' | ||
''Need the proposed solution to manage confidential info at data / dataset / organizational level?'' | ''Need the proposed solution to manage confidential info at data / dataset / organizational level?'' | ||
''Describe security and privacy issues:'' | ''Describe security and privacy issues:'' | ||
| − | + | ==== Policy ==== | |
''Are there any policies available that describe data access and sharing?'' | ''Are there any policies available that describe data access and sharing?'' | ||
''Are these really needed?'' | ''Are these really needed?'' | ||
''Copyright / attribution / metadata / legal'' | ''Copyright / attribution / metadata / legal'' | ||
| − | + | ==== Perils ==== | |
''Do they introduce moral hazard? (A hazard here is the risk that users will behave more recklessly if they are insulated from the effects of the software, or if they do noit understand what it produces, where data come from, what they represent etc. .)'' | ''Do they introduce moral hazard? (A hazard here is the risk that users will behave more recklessly if they are insulated from the effects of the software, or if they do noit understand what it produces, where data come from, what they represent etc. .)'' | ||
Revision as of 12:07, 9 February 2012
SPREAD Profile
The SPatial REallocation of Aquatic Data (SPREAD) aims to provide the conversion of geospatial explicit data from one resolution to another.
The Use Cases were already descibed in D4ScienceAn e-Infrastructure operated by the D4Science.org initiative.-II, and can be found under the Advanced Curation Use Case.
It was included under ICIS Advanced Curation because in the context of D4ScienceAn e-Infrastructure operated by the D4Science.org initiative.-II, the starting point for a re-allocation is a TS-Object, and the re-allocation was perceived as a precision of geospatial location of a reported capture without much reasoning or change of the reported values.
A progress report on SPREAD accomplishments and opportunities can be found on BSCW (SPREAD120207.docx).
Problem
Describe the CoPCommunity of Practice. issue to be addressed by the Componenent (VREVirtual Research Environment. / service / resource / etc)
Product
Describe the proposed solution in maximum 3 sentences:
With SPREAD capture time-series can be
Priority to CoPCommunity of Practice.
List proposed solution priority following the iMarine Board priority setting criteria:
- Identified community: Users now:
- Potential for co-funding:
- Structural allocation of resources:
- Referred in DoW:
- Business Cases:
- How does the proposed action generally support sustainability aspects
- How consistent it is with EC regulations/strategies (eg INSPIRE, ... ):
- Re-usability – benefits – compatibility
Parentage
Relation to CoPCommunity of Practice. Software Relation to D4S technologies
Does the proposed solution solve other problems associated with EA-CoPCommunity of Practice. Business Cases?
If the proposed solution can be used in another SW scenario (not users!) please describe.
Public
How big is the expected user community after delivery?
Productivity
Are the proposed measures effective?
Does it reduce a known workload?
Price
Is the proposed solution cheap?
Expected effort in PM:
Presentation
How is the component delivered to users? (Design / on-line help / training material / support).
Privacy
Are they safe? Need the proposed solution to manage confidential info at data / dataset / organizational level? Describe security and privacy issues:
Policy
Are there any policies available that describe data access and sharing? Are these really needed? Copyright / attribution / metadata / legal
Perils
Do they introduce moral hazard? (A hazard here is the risk that users will behave more recklessly if they are insulated from the effects of the software, or if they do noit understand what it produces, where data come from, what they represent etc. .)
