Difference between revisions of "Sustainable Data Management/20200214 telcon notes"

From Earth Science Information Partners (ESIP)
 
(17 intermediate revisions by the same user not shown)
Line 12: Line 12:
 
===Background===
 
===Background===
 
====Our original raison d'etre====
 
====Our original raison d'etre====
This group formed in late 2015 to investigate pathways for sustainable, increased collaboration and coordination among repositories engaged in environmental data management that will benefit both research networks and individual investigators.  The group has three major activities: Developing a framework for describing Return on Investment (ROI) in data repositories; describing the landscape of data services offered by repositories, to identify gaps; and defining a Common Technical Vision to sustain data, rather than the repositories themselves.
+
This group formed in late 2015 to investigate pathways for sustainable, increased collaboration and coordination among repositories engaged in environmental data management that would benefit both research networks and individual investigators.  Although the participants are all associated with repositories, the goal is sustainability of the data holdings, not necessarily the repository. The group has three major activities:  
 +
* Develop a framework for describing Return on Investment (ROI) in data repositories;  
 +
* Describe the landscape of data services offered by repositories, to identify gaps; and  
 +
* Define a Common Technical Vision which best sustains data.
  
 
Link to notes from the Tempe meeting:
 
Link to notes from the Tempe meeting:
 
http://wiki.esipfed.org/index.php/Notes_from_Collaborative_Strategies_for_Sustained_Environmental_Data_Management_workshop_(Tempe,_AZ_Nov_2015)
 
http://wiki.esipfed.org/index.php/Notes_from_Collaborative_Strategies_for_Sustained_Environmental_Data_Management_workshop_(Tempe,_AZ_Nov_2015)
 
  
 
====Accomplishments====
 
====Accomplishments====
Line 29: Line 31:
  
  
=====Define a Common Technical Vision to sustain data, rather than the repositories themselves.=====
+
=====Define a Common Technical Vision to sustain data.=====
 
** Held a followup workshop in Santa Barbara: Developing a Common Technical Vision for Repository Interoperability  
 
** Held a followup workshop in Santa Barbara: Developing a Common Technical Vision for Repository Interoperability  
 
*** Notes:  
 
*** Notes:  
Line 47: Line 49:
 
From Megan:  
 
From Megan:  
  
Data stewardship cluster might want to work in the repository-landscape area. they think of themsleves as an umbrella for a lot of other clusters.
+
Data stewardship cluster might want to work in the repository-landscape area. they think of themselves as an umbrella for a lot of other clusters.
 
they spin off other clusters (info quality cluster, ____. they all report back to data stewardship.  
 
they spin off other clusters (info quality cluster, ____. they all report back to data stewardship.  
 
* Denise Hills
 
* Denise Hills
 
* Mark Parsons
 
* Mark Parsons
 
Amber Budden is the new chair of data stewardship
 
Amber Budden is the new chair of data stewardship
 +
Action item: drop into their next call (Amber is also in our cluster, or was)
  
 
Copdess - not currently an active esip cluster. related
 
Copdess - not currently an active esip cluster. related
  
 
From Megan:  
 
From Megan:  
cluster lifecycle-
+
* cluster lifecycle-
* there is a stage where clusters spin down. So that is a possible next option for this group if you want it.
+
:* there is a stage where a cluster spins down or goes into hiatus. So that is a possible next option for this group if you want it.
* Megan has a process for this if we need it, a one-pager.
+
:* Megan has a process for this if we need it, a one-pager required from us.
 +
 
 +
* other ideas for when we don't know what we are doing:
 +
:* bring in speakers - eg, maybe even new members
 +
:* think up what you want to do at the next ESIP meeting. then plan your telecon activities to plan for that
 +
::* e.g., unveiling what you already did, more exploration.  
 +
::* 4 calls before ESIP summer mtg (march, april, may, june)
 +
 
 +
Philip and Bob
 +
* we could follow up on metrics:
 +
:* look at how to collect those metrics
 +
:* what does that metric really mean. go down to the next level of detail
 +
:* Check back on our metrics paper, there were some refs that had that kind of detail
 +
*It's important that there is enough interest to get critical mass
 +
 
 +
 
 +
* Other facets of data repository sustainability
 +
:* we went down the metrics path as a way to justify what we do. Could look at other aspects
 +
::* governance
 +
::* skills and training 
 +
 
 +
* the data itself -
 +
:* data rescue
 +
 
 +
* Our name: it's sustainable DM -- meaning that the important part is the sustainability of the data itself, not necessarily the repository holding it.
 +
 
 +
Per Megan:
 +
* Nancy H and Karl B: proposed a new cluster: Research data management
 +
*
  
 
==Action items==
 
==Action items==
 
Margaret
 
Margaret
write a few sentences for Megan about the ROI paper.
+
write a few sentences for Megan about the ROI paper for the Monday update. BY FEB 24
 +
 
 
* groups that participated
 
* groups that participated
 
* output of the sustainable DM cluster
 
* output of the sustainable DM cluster

Latest revision as of 12:09, April 9, 2020

To connect

  • Dial in using your phone: :United States: +1 (571) 317-3122
    • Access Code: 618-011-013

Agenda

  1. Where do we go next?


Background

Our original raison d'etre

This group formed in late 2015 to investigate pathways for sustainable, increased collaboration and coordination among repositories engaged in environmental data management that would benefit both research networks and individual investigators. Although the participants are all associated with repositories, the goal is sustainability of the data holdings, not necessarily the repository. The group has three major activities:

  • Develop a framework for describing Return on Investment (ROI) in data repositories;
  • Describe the landscape of data services offered by repositories, to identify gaps; and
  • Define a Common Technical Vision which best sustains data.

Link to notes from the Tempe meeting: http://wiki.esipfed.org/index.php/Notes_from_Collaborative_Strategies_for_Sustained_Environmental_Data_Management_workshop_(Tempe,_AZ_Nov_2015)

Accomplishments

In the major areas above:

Framework for describing Return on Investment (ROI) in data repositories;
Describing the landscape of data services offered by repositories, to identify gaps;

This topic is being covered by RE3data (https://www.re3data.org/). Our involvement with them has been intended to further this objective


Define a Common Technical Vision to sustain data.
    • Held a followup workshop in Santa Barbara: Developing a Common Technical Vision for Repository Interoperability
      • Notes:
    • Paper: Gries C, A. Budden, C. Laney, M. O'Brien, M. Servilla, W. Sheldon, K. Vanderbilt, D. Vieglas. 2018. Facilitating and Improving Environmental Research Data Repository Interoperability. Data Science Journal. https://doi.org/10.5334/dsj-2018-022

Attending

  • Philip Tarrant
  • John Porter
  • Bob Downs
  • Margaret O'Brien
  • Megan Carter

Regrets

Corinna

Notes

From Megan:

Data stewardship cluster might want to work in the repository-landscape area. they think of themselves as an umbrella for a lot of other clusters. they spin off other clusters (info quality cluster, ____. they all report back to data stewardship.

  • Denise Hills
  • Mark Parsons

Amber Budden is the new chair of data stewardship Action item: drop into their next call (Amber is also in our cluster, or was)

Copdess - not currently an active esip cluster. related

From Megan:

  • cluster lifecycle-
  • there is a stage where a cluster spins down or goes into hiatus. So that is a possible next option for this group if you want it.
  • Megan has a process for this if we need it, a one-pager required from us.
  • other ideas for when we don't know what we are doing:
  • bring in speakers - eg, maybe even new members
  • think up what you want to do at the next ESIP meeting. then plan your telecon activities to plan for that
  • e.g., unveiling what you already did, more exploration.
  • 4 calls before ESIP summer mtg (march, april, may, june)

Philip and Bob

  • we could follow up on metrics:
  • look at how to collect those metrics
  • what does that metric really mean. go down to the next level of detail
  • Check back on our metrics paper, there were some refs that had that kind of detail
  • It's important that there is enough interest to get critical mass


  • Other facets of data repository sustainability
  • we went down the metrics path as a way to justify what we do. Could look at other aspects
  • governance
  • skills and training
  • the data itself -
  • data rescue
  • Our name: it's sustainable DM -- meaning that the important part is the sustainability of the data itself, not necessarily the repository holding it.

Per Megan:

  • Nancy H and Karl B: proposed a new cluster: Research data management

Action items

Margaret write a few sentences for Megan about the ROI paper for the Monday update. BY FEB 24

  • groups that participated
  • output of the sustainable DM cluster
  • convening aspect of ESIP, why appropriate that ESIP hosts this stuff
  • add invitation to next meeting, we will talk about what we want to take on next

TBD: Maybe a blog post later