NSF and NIH Update for the DMPTool

Based on their responses to the Office of Science and Technology Policy (OSTP) memo, there are no immediate changes for data management and sharing plans from the National Science Foundation (NSF) or National Institutes of Health (NIH–a division of the Department of Health & Human Services), at this time. See the previous Blog post for more information on the OSTP memos.

The DMP templates for all NSF divisions/directorates and the NIH in the DMPTool are still current.

NSF Public Access Plan: http://www.nsf.gov/pubs/2015/nsf15052/nsf15052.pdf
NIH Public Access Plan: http://grants.nih.gov/grants/NIH-Public-Access-Plan.pdf

In their access plan, the NSF has clarified a few requirements. These clarifications have been added to the NSF Generic template in the DMPTool in the Instructions and Guidance section for those specific requirements (questions).

The public access plan for NIH emphasizes its current policies for data sharing and on data management plans. It then spells out “further steps under consideration”. According to the public access plan (dated February 2015):

This document describes NIH’s plans to build upon and enhance its long standing efforts to increase access to scholarly publications and digital data resulting from NIH-funded research.

The DMPTool team will keep you informed as these steps are finalized.

Public Access for Federally Funded Research

On February 22, 2013, the White House’s Office of Science and Technology Policy (OSTP) issued an executive directive that requires the results of taxpayer-funded research – both articles and data – be made freely available to the general public.

The DMPTool team has been closely monitoring the responses by federal agencies, but we could use your help (see the links below under “How you Can Help”).

Forty-three agencies were directed to come up with plans for increasing access to the results of federally funded research (see the OSTP memo links at the bottom of this blog). Since July 2014, twelve of these agencies (and their sub-agencies) have released their plans. The DMPTool team has been actively reviewing newly released funding agency announcements and plans specifically for how Data Management Plans are to be implemented. Once identified, the new plans, if the plans are different form what is already in the DMPTool, will be added to the DMPTool.

With the help of Librarians from across the country, other information from the various plans’ guidelines is being collected and consolidated (not just for data, but for published outputs as well). Columbia University and the University of Oregon are keeping up with the announcements via their Library websites:

SPARC and ARL are also trying to keep researchers and institutions informed:

How You Can Help?

Note: Memos from the Office of Science and Technology Policy (OSTP) on Public Access

We are Hiring a DMPTool Manager!

Do you love all things data management as much as we do? Then join our team! We are hiring a person to help manage the DMPTool, including development prioritization, promotion, outreach, and education. The position is funded for two years with the potential for an extension pending funding and budgets. You would be based in the amazing city of Oakland CA, home of the California Digital Library. Read more at jobs.ucop.edu or download the PDF description: Data Management Product Manager (4116).

Job Duties

Product Management (30%): Ensure the DMPTool remains a viable and relevant application. Update funder requirements, maintain the integrity of publicly available DMPs, contact partner institutions to report issues, and review DMPTool guidance and content for currency. Evaluates and presents new technologies and industry trends. Recommends those that are applicable to current products or services and the organization’s long-range, strategic plans. Identifies, organizes, and participates in technical discussions with key advisory groups and other customers/clients. Identifies additional opportunities for value added product/service delivery based on customer/client interaction and feedback.

Marketing and Ourtreach (20%): Develop and implement strategies for promoting the DMPTool. Create marketing materials, update website content, contacting institutions, and present at workshops and/or conferences. Develops and participates in marketing and professional outreach activities and informational campaigns to raise awareness of product or service including communicating developments and updates to the community via social media. This includes maintaining the DMPTool blog, Twitter and Facebook accounts, GitHub Issues, and listservs.

Project Management (30%): Develops project plans including goals, deliverables, resources, budget and timelines for enhancements of the DMPTool. Acting as product/service liaison across the organization, external agencies and customers to ensure effective production, delivery and operation of the DMPTool.

Strategic Planning (10%): Assist in strategic planning, prioritizing and guiding future development of the DMPTool. Pursue outside collaborations and funding opportunities for future DMPTool development including developing an engaged community of DMPTool users (researchers) and software developers to contribute to the codebase. Foster and engage open source community for future maintenance and enhancement.

Reporting (10%): Provides periodic content progress reports outlining key activities and progress toward achieving overall goals. Develops and reports on metrics/key performance indicators and provides corresponding analysis.

To apply, visit jobs.ucop.edu (Requisition No. 20140735)

From Flickr by Brenda Gottsabend

From Flickr by Brenda Gottsabend

Got an idea for DMPTool? Share it!

There’s always room for improvement, and that’s certainly the case with the DMPTool. Do you have a suggestion on how to make it better? Or did you discover a bug while customizing the tool for your campus? We want to hear from you! Submit your suggestions for enhancements or bugs you’ve found using our GitHub Issue Tracker.

Got ideas? We're listening! From artofhearing.com

Got ideas? We’re listening! From artofhearing.com

 

US Dept of Energy data management requirements now supported in DMPTool

On July 31, 2014 the US Department of Energy’s Office of Science issued new requirements for the management of digital research data.  Those requirements are now available in the DMPTool.  All proposals for research funding submitted to the Office of Science will be required to include a Data Management Plan that describes whether and how the digital research data generated in the course of the proposed research  will be shared and preserved.

The new requirements were formulated in response to a February 2013 Office of Science and Technology Policy directive requiring all Federal agencies over $100 million in R&D expenditures ensuring that recipients of research grant sand contract develop Data Management Plans as part of their research proposals.

The new requirements will appear in funding solicitations and invitations issued by the Office of Science beginning October 1, 2014.  A statement of the new requirements, including guidance on development of a Data Management Plan, can be found on the Office of Science website at http://science.energy.gov/funding-opportunities/digital-data-management/.

We need API use cases!

The Egyptian god Apis, a bull deity who served as an intermediary between humans and God. From Flickr by Jan.

We need your help! We are beginning work on developing the DMPTool API (application programming interface) and need use cases. If you aren’t familiar with APIs (, I’ve attached a few slides to help explain the concept. But basically, it’s how you can get information INTO or OUT OF the DMPTool. Readwrite.com has a great description:
In the simplest terms, APIs are sets of requirements that govern how one application can talk to another. APIs aren’t at all new; whenever you use a desktop or laptop, APIs are what make it possible to move information between programs—for instance, by cutting and pasting a snippet of a LibreOffice document into an Excel spreadsheet. System-level APIs makes it possible for applications like LibreOffice to run on top of an OS like Windows in the first place.
So what information do you want from the DMPTool? Or what do you want it to provide to other applications? You can comment on this post, email us, or add your suggestion directly to the GitHub issue tracker with the “API use cases” tag.

Examples:

  • You want the number of people who have completed plans for each of the different funders at your institution.
  • You want to download all of the templates that admins at your institution have created.
  • You want the DMPTool to directly deposit a copy of a plan into your institutional repository.
  • ???

Misc Stats for DMPTool2

It’s been nearly a month since we released DMPTool2, and by all accounts the new version of the application is a success. We have a few bugs to work out but generally the response to the tool has been positive. If you have feature requests or bugs to report, please visit our GitHub Issues page. Below are a few usage statistics for the tool that Perry Willett pulled together:

Number of plans & users for last 12 months

Untitled-1

Cummulative plans & users since Oct 2011

Untitled-2

Want to make some graphs of your own? Here are the data.

Contributing organizations

There are now 117 participating institutions that have either configured their campus single-signon or customized the DMPTool for their users. There are participating organizations in 41 states and the District of Columbia; California leads all states with 20 participating organizations. A map of all participating organizations is available here.