Sustainable Data Management/20160722 ESIP summer mtg

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 Analysis See sustainable DM wiki http://wiki.esipfed.org/index.php/Sustainable_Data_Management/20160720_ESIP_summer_mtg

Need: 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 Technology Gaps 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

Group Data Commons Session summary: breakout promoted easier use. Need a mechanism - how can repos be coupled?

Shared: search mechanisms Tools for researchers

How do we fund people who are doing the invisible work -- right now people are funded to make bells and whistles

Future steps: 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