Review: Customizing the DMPTool

On June 18th we gave a webinar on customizing the DMPTool for your institution. While the recording and slides from that presentation can be found on the webinar series page, here’s a brief review of the major topics that were covered.

What Do We Mean by Customization?

The DMPTool comes pre-populated with funder-provided information on how to construct a data management plan. Customizing the tool gives you a chance to modify what grant writers see when using the tool. Broken up into separate sections, administrators can provide help text, suggested answers, contacts at the institution, and resource links such as best practices guides or support groups.

http://commons.wikimedia.org/wiki/File:Researchers_review_ documents.jpg

The DMPTool’s audience includes students, researchers, and grant writers. Source: wikimedia commons

Customizing the DMPTool for your users can accomplish two goals. First, by setting up authentication and linking to resources and people from your institution, it encourages confidence in users. There are a lot of resources out there, so researchers will be looking for familiar signs. Second, you can ensure that your researchers are being connected to reliable, up-to-date information.

How to Customize

There are three steps to the customization process. Step one is to set up Shibboleth Authentication. Shibboleth is an open source software package used by many universities to provide a single login for multiple services. This can be extended to work with the DMPTool, to allow researchers to use the same login as other tools at their institution. Shibboleth is not required for customization, but without it researchers have to create their own account which can be a barrier to access. More information on how to set up shibboleth with DMPTool can be found at our website.

The second step is the customization documentation itself. This is where you provide information about your institution, and specific advice for each funder. These documents can be found at the Templates for Institutional Customization page on our bitbucket wiki. The institution settings document lets you select the email address where help requests should be sent as well as resource links that are relevant for each step in the process.

fundertemplate

The 5 columns of the Funder Template, and the Information they need

We break up the other documents by funding agency to give you as much control as possible with your customization. Each document is broken up into different sections, and lets you provide resource links relevant to that question, a suggested answer, and help text.

Once these documents are filled out, you can attach them to an email and send them to uc3@ucop.edu for submission. We’ll populate the fields with the information you provide, and add your institution to the dropdown list at the DMPTool website.

For More Information…

We’ve started an Example Documentation page where institutions can share how they’ve used DMPTool customization. This is a great place to start if you want to see how others have customized the DMPTool.

For a more in-depth breakdown of how to customize the tool, as well how we’re working to provide more administrative control in future versions of the DMPTool, check out the full webinar. If you have any questions or feedback, feel free to email me at daniel.phipps@ucop.edu or uc3@ucop.edu.

DMPTool2 Project – Functional Requirements

In our last post, we mentioned that we would be talking more about the development work on the next generation of the DMPTool: the DMPTool2. We have now made available our current draft of the functional requirements. For those of you who haven’t read a functional requirements document, these are fairly detailed documents that specify the capabilities and, well, functions of a system. But this document should begin to give those of you who are interested a sense of where we’re expanding and adding functionality to the DMPTool.

Over the next few weeks, we’ll be highlighting very specific areas to talk in more detail (and in more colloquial language!) about these developments.

DMPTool2 Project – Advisory Board Meetings

The DMPTool 2 project has two advisory boards: one for researchers and one for administrative users, such as librarians, research offices, and IT professionals. The role of both is to provide feedback and guidance on the development of the DMPTool as well as our outreach and communication efforts. May was a busy month for both sets of board members, as we held two (virtual) meetings with each advisory board, with the second meetings. We thought we’d highlight here some of the things that we talked about at these informative and enlightening meetings.

For both boards, we shared examples of the functionality, roles, and wireframes that are under development for the next phase of the DMPTool. For both groups we highlighted the new functionality that will allow researchers to truly collaborate with others on the development of a DMP. For the Administrative Advisory Board, we focused in large part on the new functionality for institutions: ability to customize resource templates, such as local links and help text, requirement templates if an institution has a need to set up their own DMP requirements,  and new types of institutional roles such as editors. This was the first chance we had had to share these with people outside of the project team, and we were thrilled to hear positive response to these developments, as well as feedback and suggestions. (Also, watch this space as we’ll be highlighting a lot of this functionality over the next few weeks!)

In response to questions from the first meetings with the advisory boards, we had begun to investigate further some of the usage patterns of the tool. While we have always collected use statistics, we haven’t done much in depth exploration or segmentation of these – for example, tracking numbers of repeat users or understanding spikes in usage of the tool. Working with this data and hearing the questions from board members is helping us to better understand the types of data that would be interesting to the institutions that use the tool, but also how we begin to measure the impact of the tool. For example, is the number of repeat users within a year a strong metric of success? How many researchers apply multiple times for funding within a year? The advisory boards are helping us to think critically about these issues.

We are lucky to have such engaged advisory boards and we encourage you to share your thoughts with board members as well as with us directly!

DMPTool2 Project — June 2013 Report

Overview

DMPTool2 is currently immersed in the execution phases of the project. Each team has met significant project deadlines and milestones. Furthermore, the group is deeply engaged with each of the User Advisory Boards, implementing feedback into the project as well as engaging in constructive discussion with each board.

Technical Team

The technical team has made significant progress on development. The technical development schedule has been finalized and is currently on track. Much of the first of four planned phases is complete. Initial wireframes were presented to Administrative User and Researcher Advisory Boards at the end of May. The team is currently processing feedback from the boards to influence some remaining minor changes. As all the login functionality pieces fall into place, focus has shifted toward user interface design. Most functionality should be in place by the end of August, when efforts will transition toward the open API. In preparation, the technical team has already reached out to the Center for Open Science to discuss integrating the DMPTool2 into their Open Science Framework.

Communications/Outreach Team

The Outreach Coordinator position faced significant bureaucratic delays in May; however, with the coordinator now hired, the team is at work developing an outreach plan. Meanwhile, the team was successful in attaining targeted feedback and directing specific questions to the Advisory Boards in May. The communications team is currently coordinating responses to board inquiries and tentatively scheduling the next meeting for the beginning of September. Furthermore, while the team regularly receives collaborative agreements from Partner Institutions, we have only received 30 agreements. The outreach team is currently discussing strategies to attain the rest in a timely manner. Finally, the recently-launched webinar series has met success. The first two sessions had 150 and 80 participants, respectively.

Metrics

The outcome metrics outlined in Sloan Foundation communications are currently being used to track and evaluate project success. After defining each metric, the DMPTool team has assessed its progress toward each goal as well as a tentative due date for each. The project management team is currently discussing an objective-based strategy with the outreach team and technical team. Furthermore, we have presented initial impact metrics to Advisory Boards, the feedback from which has proved to be useful in refocusing the team’s current concentration.

Overall Project

Though it is still estimated that certain aspects may carry into early next year, the overall project is on track to end on time. In the next month, we expect to see significant strides in technical development and outreach efforts.

DMPTool’s Top 10

We have determined the top-ranked institutions that use the DMPTool based on the number of users and of plans they create (October 2011 – Present).

Top 10 Institutions by Number of Users:

The following institutions have produced the most number of users on DMPTool.

Institution # Users
University of Illinois Urbana-Champaign 161
UC San Diego 146
UCLA 141
Stanford 133
North Carolina State 121
UC Davis 114
University of Virginia 109
University of Washington 97
UC Berkeley 92
UC Irvine 80

Top 10 Institutions by Number of Plans:

The following institutions have produced the most data management plans using DMPTool.

Institution # Plans
UC San Diego 189
University of Illinois Urbana Champaign 138
University of Virginia 115
North Carolina State 105
UCLA 103
University of North Texas 97
Stanford 88
UC Berkeley 78
University of North Carolina – Chapel Hill 74
UC Davis 73

Congratulations to the eight institutions that made both lists: North Carolina State University, Stanford University, UC Berkeley, UC Davis, UCLA, UC San Diego, University of Illinois, and University of Virginia.

Data Management Resources: Libguides

What are Libguides?

While putting together our upcoming webinar on existing data management resources, one consistent source of useful information was librarian-authored research guides called libguides, hosted by various institutions. While we’ll be going into more detail in the webinar itself, I wanted to talk about what makes the libguide platform especially useful to librarians looking to make a data management guide for their patrons.

Libguides are designed to be made up of replaceable parts that are easy to share with other guides. Img source: Wikimedia Commons

Libguides are a web platform designed for librarians to create and share research guides, without having to tangle with web design tools. They can be used to answer frequently asked questions, highlight materials in the catalog, or point to useful outside resources. Organizationally, Libguides are made up of tabs and boxes. Tabs allow you to create sub-pages within the guide to keep content organized. Each page is populated with boxes that contain different kinds of content, such as lists of links, RSS feeds, or videos.

The Power of Linked Pages

Aside from allowing librarians to assemble simple page structures, breaking the site into various boxes allows users to share individual components of their guides with other librarians for use in their own guides. This means useful information can be repeated across multiple guides without reinventing the wheel. This modularity makes libguides a great tool for disseminating data management information. Not only can librarians create a guide specifically to answer questions about data issues, but relevant pages can be easily ported to subject specific guides. By properly organizing the information on your data management libguide, you can easily re-use pages specific to the sciences or humanities to their relevant topics. Later, when  you update these pages the changes will automatically be reflected across all the guides that are using it as a linked page.

When sitting down to create a data management libguide, you should design it in such a way where it can be useful to researchers who might only see a portion of it. Properly sharing individual tabs will not only capture researchers who might not have started considering the data management element of their work, but also guide traffic to the main data management site. Reaching out to the authors of frequently visited libguides can be a good way to add information that might be of value to their patrons.

For examples of data management libguides and other useful resources, check out the DMPTool Community Resources Page. If you need technical advice on how to customize your libguide, check out guidefaq.com to find answers to frequently asked questions about the libguide platform.

DMPTool2 Project – May 2013 Report

Overview

DMPTool2 is at the point of transition from formal planning activities to startup efforts toward the execution phases of the project.

Technical Team

Many of the planning and preparation goals have been accomplished and the technical team is moving forward on development. Both application developers have been hired and have commenced work as of May 1st. The functional specifications have been revised and reviewed and initial wireframes have been drafted. We are currently working through revising and making minor changes to wireframes and user stories and will present them to Researcher and Administrative User Advisory Boards for feedback on May 30th. The updated technical development schedule is nearly complete and will be shared soon.

Communications/Outreach Team

Candidate evaluation for the Sloan Outreach Coordinator position began on May 2nd, as planned, and we hope to have that position filled within the next month or so. The Researcher and Administrative User Advisory Boards have begun meeting, with initial meetings both in early May. These meetings focused on review and discussion of high-level project issues and technical specifications. The next set of meetings is scheduled for the end of May, and will focus on more targeted feedback.  With the newly implemented governance structure in place, we continue to enroll institutions as “Partners” through signed collaborative agreements. We maintain our goal to enroll all currently authenticating institutions by the end of May. Furthermore, the outreach team has successfully launched a webinar series on the DMPTool blog, already garnering significant community interest.

Metrics

There have been significant developments in project metrics. The outcome metrics outlined in Sloan Foundation communications will be used to track and evaluate project success. We are currently creating objective-based strategies for each. Longer-term impact metrics are still in development and we are still evaluating the best choices. We will seek more targeted feedback on them during the meetings at the end of May, and likely via broader community discussion opportunities.

Overall Project

Though we expect that certain project aspects may carry into early next year due to previously stated delays, we are quickly catching up to our original project plans. Now that the project is fully staffed, with a complete set of requirements, we are moving forward quickly on development.

-Andrew Sallans, University of Virginia Library, DMPTool2 Project Manager

 

Data Services Environmental Scan: First Steps

Author: Shannon Smith, U.S. Fish and Wildlife Service

Source: WikiMedia Commons

As a library, taking on an increased support role for data management is a long-term project that involves coordinating with groups institution-wide. Environmental scan interviews are a vital first step. They can help you find advocates in other departments, and find trouble on the horizon. We’ll be discussing how to perform an environmental scan in our webinar series this summer, but there are steps you can take within your library to begin the process. The first task at hand is to identify your own library’s existing services.

The library self-assessment is a critical first step to developing an environmental scan. Before speaking with the other technical or research support groups at your institution, you should have a written list of the services, initiatives, and plans that your library has undertaken.

What are you looking for?

The purpose of assembling this written list is to inform your later interviews and to help you focus on you institution’s priorities. In an ideal world, a thorough survey of library patrons and the services they need from the library would not only give you insight into how you focus your activities, but also give you ammunition when speaking to other departments about the importance of library data services. In the short term, speaking to your fellow librarians (especially reference, research, or subject specialists) about their interactions with researchers can give you a quick-and-dirty overview of where to focus your efforts. Looking at other university libguides on data services can also give you an idea of things researchers find useful.

Interviewing your Library’s Director

The other half of the internal review is the top-down approach. Taking what you’ve learned about the current state of affairs, meeting with your library director can give you broader, long term goals. Other, more detailed guides on how to conduct informative interviews exist, but broadly it’s useful to approach the interview with a pre-established set of goals for information you want to leave with, an understanding of how formal/detailed the interview will be, and a list of questions to ask. This should give you a wider-scale view of your Library’s data services work, and how it fits in with the campus’ larger scale priorities. You may also walk away with a better understanding of other groups on campus with a stake in data management for later use, as well as the internal organization of your own library.

Review, Recycle, Remix

While a self-assessment is the first step to developing an environmental scan of the whole institution, it also stands alone as a short-term thing librarians can do to start working on their own data practices. Before rushing off to coordinate with researchers, grant writing offices, or IT make sure you take the time to review the information you’re getting from your patrons, fellow librarians, and other staff. Giving yourself some weeks to digest this information will give you a better idea of what you can do in-house, what tasks require outside collaboration, and what might be out-of-scope for now.

For more on environmental scanning and other important aspects of data services at your library, keep an eye on our webinar page over the coming months.

Response to OSTP Memorandum – How the DMPTool Can Contribute

The Office of Science and Technology Memorandum of February 22, 2013, entitled “Increasing Access to the Results of Federally Funded Scientific Research” is a milestone in a path carved over at least the past decade and a half.  The DMPTool group traces this shift back to at least the late 1990s, with a minor change in the Office of Management and Budget policies, indicating a broader interest in openness and access to federally funded research.  Subsequent initiatives from the National Institutes for Health and National Science Foundation have been major steps in advancing this shift, but there is still a long way to go.

This statement is intended to offer specific points on how the DMPTool may be of service to the requirements of the memorandum.  We plan to initially distribute this statement as a post on the DMPTool blog, but will also contribute it towards the planning meetings scheduled for mid-May, organized by the National Research Council (NRC) Division on Behavioral and Social Sciences and Education DBASSE).  Likewise, we may submit it to other relevant RFI calls, such as the “Reducing Investigator’s Administrative Workload for Federally Funded Research“.   We hope our efforts will be of benefit to as many constituents as possible throughout this initiative for increased access.

Background Information

The DMPTool was officially launched in October 2011, after months of collaborative development between the California Digital Library, University of Virginia Library, University of Illinois – Urbana Champaign, University of California – Los Angeles, University of California – San Diego, UK Digital Curation Centre, DataONE, and the Smithsonian Institution.  While initially the tool focused meeting the needs of data management planning requirements from the National Science Foundation, it has since expanded to include requirements from the National Institutes of Health, the Institute for Museum and Library Services, the National Endowment for the Humanities, the National Oceanic and Atmospheric Administration, and several private funding organizations.  In 2012 and 2013, the group received funding from the Alfred P. Sloan Foundation and the Institute for Museum and Library Services, to expand functionality and support for the DMPTool into new areas and to meet new needs.  The DMPTool is presently used by over 4,500 users at over 650 institutions, and sees the greatest use from researchers applying to the NSF Biological Sciences (BIO) directorate, the National Institutes of Health, and the NSF Social, Behavioral, and Economic Sciences (SBE) directorate.  A community governance model is presently being implemented, and details can be found at  bitbucket.org/dmptool/main/wiki/Governance.

DMPTool Contributions

Based on the context outlined above, we propose the following three areas where the DMPTool may be of most service towards achieving the goals of “increasing access to the results of federally funded scientific research” and in particular the mandate to “ensure that all extramural researchers receiving Federal grants and contracts for scientific research and intramural researchers develop data management plans” (Page 5 of memorandum, item 4b):

  1. Clear communication of the data management planning requirements: The DMPTool is presently the only known location providing an aggregate view of data management requirements and policies across funding agencies.  It also tracks changing requirements and realigns the updated requirements with associated guidance. This is a significant service to researchers who seek one place for answers.   Partnership between the DMPTool and agencies would enable further growth and establishment of the DMPTool as a coordinated hub, with relatively minimal effort or cost and improved researcher compliance.
  2. Preparation of high-quality data management plans:  The success of this access initiative depends heavily on the quality of data management planning. Proper planning from the start requires having the right information at hand when making critical project decisions and plans; this will lead to better data discoverability and access.  This is challenging in research, as there are often many complex actors, including funding agencies, institutions, associations, national laboratories, repositories, and more.  The DMPTool community is well connected with many of these groups. For example, we have partnered with DataONE, ICPSR, and DataBib to connect our data management planning process with archival solutions.
  3. Harmonization of requirements across agencies and communities:  With funding from two grants to improve the DMPTool, we are expanding the tool’s functionality, with particular attention to administrative user needs. These administrators may be at the institution level (e.g., at a university grants office), or at the funder level (e.g.,National Science Foundation).  As an example, new functionality will enable the Smithsonian Institution to use the DMPTool for preparation, approval, and tracking of all data management plans, across the entire institution, for all researchers.  It will allow institutional administrators to see plans being created by their researchers, and to better anticipate the types of resources and policies that will be needed to financially support research efforts.  Through this functionality and a broad view of data management planning requirements and practices, we believe that there is an opportunity here for improvement of overall requirements and practices to a point of harmonization.

We look forward to future discussions about how the DMPTool might help achieve the goals of broader access to federally funded scientific research.