Difference between revisions of "Earth Science Data Analytics/2016 Plan"

From Earth Science Information Partners (ESIP)
 
(2 intermediate revisions by the same user not shown)
Line 38: Line 38:
  
 
===Things we may do to fulfill our objectives:===
 
===Things we may do to fulfill our objectives:===
 +
 +
* Continue to provide an 'academic' atmosphere for ESIP members to learn about ESDA, in particular, at ESIP meeting cluster sessions
 +
 +
* Continue to engage guest speakers with expertise that can provide the ESIP community with a better understanding of: Data/information analytics needs, ESDA methodologies currently being utilized, and careers in data analytics
 +
 +
* Collaborate with, or otherwise be cognizant of, other information science activities and organizations, addressing the same issues as we are regarding the understanding and development of ESDA
 +
 +
* Brainstorm other activities that can more effectively trigger the development and usability of ESDA tools and techniques
 +
 +
* Collaborate with ESDA educators in supporting the development of curriculums that teach data analytics pertaining to Earth science
  
  
Line 44: Line 54:
 
''(e.g. Partnerships, in-kind support, staff support)''
 
''(e.g. Partnerships, in-kind support, staff support)''
  
 +
* Data and Information users who can describe how they use large heterogeneous data in their research, applications, etc.
  
  
 
===How will we know we are on the right track?===
 
===How will we know we are on the right track?===
  
 +
* If we can determine and document a gap analysis (described above), we are on the right track
 +
 +
* If we can articulate requirements for tools/techniques, that currently do not exist, and that satisfy a group of users, then we are really on the right track  (First time, any decent number of users would be good)
 +
 +
* If ESIP partners, singly or in collaboration, can implement and deploy tools that satisfy user requirements, then we have reached nirvana
  
  
 
===How will others know what we are doing in & out of ESIP?===
 
===How will others know what we are doing in & out of ESIP?===
  
 +
* ESIP Federation could publicly endorse the work
 +
 +
* Publish
  
  
 
==== Cross-collaboration area connections ====  
 
==== Cross-collaboration area connections ====  
 
(Identify other areas that you consider cross collaboration. Are there things that you need us to provide in support the cross collaboration?)
 
(Identify other areas that you consider cross collaboration. Are there things that you need us to provide in support the cross collaboration?)
 +
 +
*  MatchTool, Interoperability and Technology, maybe Discovery
  
 
[[category:2016Plan]]</nowiki>
 
[[category:2016Plan]]</nowiki>

Latest revision as of 16:23, March 18, 2016

ESIP ESDA Collaboration Area Strategic Plan 2016

ESIP Vision

To be a leader in promoting the development, implementation, and deployment of Earth science data analytics tools/techniques that facilitate gleaning knowledge from Earth science data and information.

2015-2020 Strategic Plan Goals

  • Educate ESIP members on the significance and future development growth of Data Analytics
  • Compile and categorize existing ESDA tools/techniques according to ESDA defined types and goals
  • Provide a comprehensive gap analysis between ESDA needs and available tools/techniques
  • Create a path for Information technologists to develop needed, but unavailable, ESDA tools/techniques that increase the use and value of Earth science data and information
  • Seek graduate data analytics/ Data Science student internship opportunities

Resources: 2015-2020 Strategic Plan Executive Summary
Strategic Plan Roadmap

Collaboration Area Plan

Collaboration Area Objective:

  • Provide a forum for ‘Academic’ discussions that allow ESIP members to be better educated and on the same page in understanding the various aspects of Data Analytics
  • Bring in guest speakers to describe overviews of external efforts and further teach us about the broader use of Data Analytics.
  • Perform activities that:

-- Compile use cases generated from specific community needs to cross analyze heterogeneous data (could be ESIP members or external)

-- Compile experience sources on the use of analytics tools, in particular, to satisfy the needs of the above data users (also, could be ESIP members or external)

-- Examine gaps between needs and expertise

-- Document the specific data analytics expertise needed in above collaborations

  • Seek graduate data analytics/ Data Science student internship opportunities


Things we may do to fulfill our objectives:

  • Continue to provide an 'academic' atmosphere for ESIP members to learn about ESDA, in particular, at ESIP meeting cluster sessions
  • Continue to engage guest speakers with expertise that can provide the ESIP community with a better understanding of: Data/information analytics needs, ESDA methodologies currently being utilized, and careers in data analytics
  • Collaborate with, or otherwise be cognizant of, other information science activities and organizations, addressing the same issues as we are regarding the understanding and development of ESDA
  • Brainstorm other activities that can more effectively trigger the development and usability of ESDA tools and techniques
  • Collaborate with ESDA educators in supporting the development of curriculums that teach data analytics pertaining to Earth science


Things our collaboration area needs to deliver our objectives?

(e.g. Partnerships, in-kind support, staff support)

  • Data and Information users who can describe how they use large heterogeneous data in their research, applications, etc.


How will we know we are on the right track?

  • If we can determine and document a gap analysis (described above), we are on the right track
  • If we can articulate requirements for tools/techniques, that currently do not exist, and that satisfy a group of users, then we are really on the right track (First time, any decent number of users would be good)
  • If ESIP partners, singly or in collaboration, can implement and deploy tools that satisfy user requirements, then we have reached nirvana


How will others know what we are doing in & out of ESIP?

  • ESIP Federation could publicly endorse the work
  • Publish


Cross-collaboration area connections

(Identify other areas that you consider cross collaboration. Are there things that you need us to provide in support the cross collaboration?)

  • MatchTool, Interoperability and Technology, maybe Discovery</nowiki>