1. Managing Data: The Long View FORCE15 – 12 January 2015 Amy Friedlander, Ph.D.

2. Credits: Stephen Houston; Stephen Salpukas, College of William & Mary ; Jean Clottes (France); Angie Payne, University of Arkansas; Angie Payne, University of Arkansas

3. About this talk: A slightly longer view A look at the last 20 years or so Future state: Information is ubiquitous Next steps (next 6-18 months) 3

4. 4 A quick look backwards

5. Capture and analytical technologies Simulation Connectivity and communications technologies T ext/word processing/collaboration/ presentation IT, scholarly communication, and the nature of evidence 5

6. What has happened? Heterogeneous data and objects Invisible/visible – rising expectations o Storage, preservation, and access o Informal/formal communication Vocabulary and logic based on objects with properties o Identifiers o Description, including access rights and permissions o Location Software as a first class object 6

7. Question 1 7 Must managing data be collocated with storing the data? Yes. Closely coupled architectures No. Distributed architectures (cloud) Where does that leave software?

8. Question 2 Who gets access to what? And when? Public/open access policies Restrictions/permissions on access and use Standards and formats

9. Question 3 9 What (and who) can I trust? I don’t have an answer to that one. But there is a lot of research.

10. 10 Future state: Information is ubiquitous

11. Imagine... An environment in which the investigator could upload once and the information could be discovered and used by many An environment in which all publications were linked to the underlying evidence (data), analytical tools, and software If so, what would it take to get there? What can government do? What can you do?

12. A collaborative research culture Build infrastructure o Unique, persistent identifiers o Metadata and description o Repositories and storage o Platforms that enable collaboration and sharing Foster institutions that enable consensus building around standards and best practices Create rewards and incentives

13. What can government do? Articulate policy (international, national, state, agency) Develop implementations that: o Make it easy – and provide incentives -- to do the “right” thing and difficult to go wrong o Are not over-engineered or prematurely specified Encourage use of infrastructure elements adopted by the research communities

14. Some public/open access milestones Berlin Open Access Initiative (2002); Bethesda Statement on Open Access Publishing (2003); Berlin Declaration on Open Access to Scientific Knowledge (2003) NIH policy – 2008 NSF data management plan (2011); data citation (2013) RCUK (2011, 2012) OSTP memo and Open Data executive order (2013) Gates Foundation (2014) State and university policies

15. NSF’s DMP principles Defer to the communities Implicitly acknowledge a distributed environment of multiple stakeholders and resources Provide high level coherence that allow for heterogeneity in data and research communities Address evidence

16. Next steps (6-18 months )

17. NSF’s approach to public access Recognizes that science takes place in communities o Diversity of sciences with heterogeneous research results o Range of institutions, professional societies, stewardship institutions, and publishers o Multiple funding streams Builds on current practice Leverages resources across government, higher education, and the private sector

18. The NSF Plan provides a framework. Deploy in phases – “easy case” Learn from one phase to inform the next Focus on publications in the initial implementation with the expectation that the architecture will extend to other kinds of research products Integrate the internal systems within the enterprise architecture to minimize burden on investigators and program staff Work with the communities to understand needs with respect to data and data management and this is an international challenge

19. What should you expect? NSF will post the approved plan to nsf.gov. NSF will post FAQs and guidance to nsf.gov; these will evolve. Technical pilot(s) will provide opportunities for feedback. Changes to procedures will be announced with opportunities for notice/comment as required by Federal-wide policies. Waiver process for changes to the 12-month embargo NSF will retain existing requirements and practices, to the extent possible, including: o Data management plan o Allowance for publication/data costs in the budget proposals o Data citation in Biographical Sketches Look for more specific guidance at the program/division/ directorate levels.

20. What can you do? Adopt consistent practices concerning citation and deposit of data and software Recognize different kinds of contributions Data Software Ask harder questions in panel and editorial reviews Encourage your students to become conversant in data and software

21. We must, indeed, all hang together, or assuredly we shall all hang separately. Attributed to Benjamin Franklin, 1776

22. 22 Thank you! Amy Friedlander (afriedla@nsf.gov)afriedla@nsf.gov Clifford Gabriel (cjgabrie@nsf.gov)cjgabrie@nsf.gov Joanne Tornow (jtornow@nsf.gov)jtornow@nsf.gov