Difference between revisions of "Sustainable Data Management/20160722 ESIP summer mtg"
(added formatting) |
(added sections) |
||
| Line 3: | Line 3: | ||
Next steps: | Next steps: | ||
| − | Group ROI | + | == Group ROI == |
| − | Develop framework for ROI analysis | + | === Develop framework for ROI analysis === |
: For whom (different stakeholders, and their motivations) is the ROI measured - | : For whom (different stakeholders, and their motivations) is the ROI measured - | ||
:: investors, | :: investors, | ||
| Line 28: | Line 28: | ||
| − | Group Landscape Analysis | + | == Group Landscape/Gap Analysis == |
See sustainable DM wiki http://wiki.esipfed.org/index.php/Sustainable_Data_Management/20160720_ESIP_summer_mtg | See sustainable DM wiki http://wiki.esipfed.org/index.php/Sustainable_Data_Management/20160720_ESIP_summer_mtg | ||
| − | + | === Identify needs === | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | : Understand content in re3data|copdess. | |
| + | :: Eg, confirm: re3data is canonical, copdess is view + additional info | ||
| + | :; maintenance frequency, responsible parties. | ||
| + | ::: Contact: ?Shelley Stall? | ||
| + | :: Understand activities of copdess to avoid duplication | ||
| + | ::: Schema used by COS | ||
| + | ::: Best mechanisms for conversation | ||
| − | Group | + | :Apply peer pressure to get data into the registries or update (via Shelley etc) |
| + | |||
| + | |||
| + | == Group Technical Vision == | ||
Identify both gaps and overlaps, to avoid straining an already overloaded funding system\ | Identify both gaps and overlaps, to avoid straining an already overloaded funding system\ | ||
Identify value of the small and large repositories | Identify value of the small and large repositories | ||
Identify the common things we need | Identify the common things we need | ||
| − | Group Data Commons | + | |
| + | == Breakout groups of interest this week == | ||
| + | Other breakout groups or clusters that we overlap with, and should be aware of their work | ||
| + | |||
| + | ===Group Data Commons=== | ||
| + | Session summary: http:// | ||
Session summary: breakout promoted easier use. Need a mechanism - how can repos be coupled? | Session summary: breakout promoted easier use. Need a mechanism - how can repos be coupled? | ||
| − | Shared: search mechanisms | + | The things small repos want to share are |
| − | Tools for researchers | + | : Shared: search mechanisms |
| + | : Tools for researchers | ||
| + | Note: a lot of what we do to 'sustain data' is in visible work, and most of what gets funded is the bells and whistles (eg, web apps). how do we make the invisible work more appreciated? | ||
| + | |||
| + | ===Stewardship=== | ||
| + | their focus is the preservation of data. some of that is by the repos. (remember, that for sustDM, the repos is only a POV for organizing tasks and potential collaboration, because they offer DM services. | ||
| − | |||
| − | + | ==Action items== | |
| − | + | ROI: | |
| + | needs to meet and nail down questions to ask | ||
(perhaps meet in November in Arizona again) | (perhaps meet in November in Arizona again) | ||
Revision as of 09:47, July 22, 2016
Notes 7_22 Sustainable Data Management
Next steps:
Group ROI
Develop framework for ROI analysis
- For whom (different stakeholders, and their motivations) is the ROI measured -
- investors,
- user/researcher,
- Institution,
- Purely business approach by the repository
- Considerations:
- Repository maturity
- Data set maturity (degree of integration with other data)
- Decide on approach:
- Case study,
- Provide a place within ESIP to collect user stories, count publications
- Guidelines to do an assessment but leave it to the repository
- How do we know that we succeeded when we are done with the evaluation
- Roles of small vs larger repos
- Value of small repositories -
- Parameters may differ from large repo params
- Their role may be peer-pressure (social)
- Federators (eg, dataone) params
- May be more technical
Group Landscape/Gap Analysis
See sustainable DM wiki http://wiki.esipfed.org/index.php/Sustainable_Data_Management/20160720_ESIP_summer_mtg
Identify needs
- Understand content in re3data|copdess.
- Eg, confirm: re3data is canonical, copdess is view + additional info
- maintenance frequency, responsible parties.
-
- Contact: ?Shelley Stall?
- Understand activities of copdess to avoid duplication
- Schema used by COS
- Best mechanisms for conversation
- Apply peer pressure to get data into the registries or update (via Shelley etc)
Group Technical Vision
Identify both gaps and overlaps, to avoid straining an already overloaded funding system\ Identify value of the small and large repositories Identify the common things we need
Breakout groups of interest this week
Other breakout groups or clusters that we overlap with, and should be aware of their work
Group Data Commons
Session summary: http:// Session summary: breakout promoted easier use. Need a mechanism - how can repos be coupled?
The things small repos want to share are
- Shared: search mechanisms
- Tools for researchers
Note: a lot of what we do to 'sustain data' is in visible work, and most of what gets funded is the bells and whistles (eg, web apps). how do we make the invisible work more appreciated?
Stewardship
their focus is the preservation of data. some of that is by the repos. (remember, that for sustDM, the repos is only a POV for organizing tasks and potential collaboration, because they offer DM services.
Action items
ROI: needs to meet and nail down questions to ask (perhaps meet in November in Arizona again)
Join the mailing list Attend monthly calls Meet up at RDA/International Data Week in Denver Winter ESIP
