RDA-DMP movings and shakings

RDA Plenary 9

We had another productive gathering of #ActiveDMPs enthusiasts at the Research Data Alliance (RDA) plenary meeting in Barcelona (5-7 Apr). Just prior to the meeting we finished distilling all of the community’s wonderful ideas for machine-actionable DMP use cases into a white paper that’s now available in RIO Journal. Following on the priorities outlined in the white paper, the RDA Active DMPs Interest Group session focused on establishing working groups to carry things forward. There were 100+ participants packed into the session, both physically and virtually, representing a broad range of stakeholders and national contexts and many volunteered to contribute to five proposed working groups (meeting notes here):

  • DMP common standards: define a standard for expression of machine-readable and -actionable DMPs
  • Exposing DMPs: develop use cases, workflows, and guidelines to support the publication of DMPs via journals, repositories, or other routes to making them open
  • Domain/infrastructure specialization: explore disciplinary tailoring and the collection of specific information needed to support service requests and use of domain infrastructure
  • Funder liaison: engage with funders, support DMP review ideas, and develop specific use cases for their context
  • Software management plans: explore the remit of DMPs and inclusion of different output types e.g. software and workflows too

The first two groups are already busy drafting case statements. And just a note about the term “exposing” DMPs: everyone embraced using this term to describe sharing, publishing, depositing, etc. activities that result in DMPs becoming open, searchable, useful documents (also highlighted in a recent report on DMPs from the University of Michigan by Jake Carlson). If you want to get involved, you can subscribe to the RDA Active DMPs Interest Group mailing list and connect with these distributed, international efforts.

Another way to engage is by commenting on recently submitted Horizon2020 DMPs exposed on the European Commission website (unfortunately, the commenting period is closed here and here — but one remains open until 15 May).

DMPRoadmap update

Back at the DMPRoadmap ranch, we’re busy working toward our MVP (development roadmap and other documentation available on the GitHub wiki). The MVP represents the merging of our two tools with some new enhancements (e.g., internationalization) and UX contributions to improve usability (e.g., redesign of the create plan workflow) and accessibility. We’ve been working through fluctuating developer resources and will update/confirm the estimated timelines for migrating to the new system in the coming weeks; current estimates are end of May for DMPonline and end of July for DMPTool. Some excellent news is that Bhavi Vedula, a seasoned contract developer for UC3, is joining the team to facilitate the DMPTool migration and help get us to the finish line. Welcome Bhavi!

In parallel, we’re beginning to model some active DMP pilot projects to inform our work on the new system and define future enhancements. The pilots are also intertwined with the RDA working group activities, with overlapping emphases on institutional and repository use cases. We will begin implementing use cases derived from these pilots post-MVP to test the potential for making DMPs active and actionable. More details forthcoming…

Upcoming events

The next scheduled stop on our traveling roadshow for active DMPs is the RDA Plenary 10 meeting in Montreal (19–21 Sept 2017), where working groups will provide progress updates. We’re also actively coordinating between the RDA Active DMPs IG and the FORCE11 FAIR DMPs group to avoid duplication of effort. So there will likely be active/FAIR/machine-actionable DMP activities at the next FORCE11 meeting in Berlin (25–27 Oct)—stay tuned for details.

And there are plenty of other opportunities to maintain momentum, with upcoming meetings and burgeoning international efforts galore. We’d love to hear from you if you’re planning your own active DMP things and/or discover anything new so we can continue connecting all the dots. To support this effort, we registered a new Twitter handle @ActiveDMPs and encourage the use of the #ActiveDMPs hashtag.

Until next time.

Active, actionable DMPs

IDCC workshop participants

Roadmap project IDCC debriefing
We had a spectacularly productive IDCC last month thanks to everyone who participated in the various meetings and events focused on the DMPRoadmap project and machine-actionable DMPs. Thank you, thank you! Sarah has since taken the traveling road show onward to a meeting at CERN (slides) and Stephanie discussed institutional infrastructure for DMPs at a meeting of California data librarians. In the midst of travels we’ve been wrangling the mountain of inputs into a draft white paper on machine-actionable DMP use cases. For now, we offer a preview of the report and an invitation to keep the momentum going at the RDA plenary in Barcelona, which is just around the corner (5–7 April).

The white paper represents the outputs of the IDCC workshop: ”A postcard from the future: Tools and services from a perfect DMP world” (slides, etc. here). We convened 47 participants from 16 countries representing funders, educational institutions, data service providers, and the research community. There was so much interest in the topic that we added an overflow session to accommodate everyone who wanted to weigh in. We’re gratified to discover how many folks have been thinking about DMPs as much as we have, and aim to continue synthesizing your stakeholder-balanced, community-driven solutions for improving the data management enterprise.

mind map exercise

Solving DMPs with rainbow stickies

The contributions from IDCC align with previously gathered information and drive the agenda summarized here. Consensus emerged to:

  • Focus on integrating existing systems (Interoperability was top-voted topic for the workshop)
  • Integrate DMPs into active research workflows to emphasize benefits of planning to researchers, but keep in mind that funders still drive demand.
  • Consider the potential of persistent identifiers (ORCID iDs, Crossref Funder Registry, etc.)
  • Explore ways to offer tailored, discipline-specific guidance at appropriate points

Next steps…
All stakeholders expressed a need for common standards and protocols to enable information to flow between plans and systems in a standardized manner. This would support APIs to both read and write to DMPs, as well as creating a framework for the development of new use cases over time. Therefore, it is a top priority to define a minimum data model with a core set of elements for DMPs. The model should incorporate existing standards and avoid inventing something new; it could potentially be based on a template structure and/or use the DMPRoadmap themes. Additional requirements in this area include that it:

  • Must make use of existing vocabularies and ontologies whenever possible
  • Must employ common exchange protocols (e.g., json)
  • Must be open to support new data types, models, and descriptions
  • Should be available in a format that can be rendered for human use
  • Should accommodate versioning to support actively updated DMPs

At the RDA 9th Plenary meeting in Barcelona during the Active DMPs IG session (6 April, 9:30-11:00) we propose establishing a working group to develop standards for DMPs. This isn’t our particular area of expertise so once again we’re relying on all of you to help steer the DMP ship. We hope that additional working groups might spin out from the session and invite your ideas and contributions (e.g., publishing DMPs).

…and beyond
The DCC and UC3 will continue to pursue international collaborations related to DMPRoadmap through pilot projects. As part of an iterative process for developing, implementing, testing, and refining these use cases we’re beginning to model domain-specific and institutional pilot projects to determine what information can realistically move between stakeholders, systems, and research workflows. We have some existing funds to support a subset of this work and are actively seeking additional sources of funding to carry the project forward. In addition to technical solutions, these projects will expand our capacity to connect with key stakeholders, with particular emphasis on addressing the needs and practices of researchers and funders. Stay tuned for more details in the coming weeks and months.

You can also track our progress and find oodles of documentation on the DMPRoadmap GitHub wiki.

Roadmap retrospective: 2016

be kind rewind2016 in review

The past year has been a wild ride, in more ways than one… Despite our respective political climates, UC3 and DCC remain enthusiastic about our partnership and the future of DMPs. Below is a brief retrospective about where we’ve been in 2016 and a roadmap (if you will…we also wish we’d chosen a different name for our joint project) for where we’re going in 2017. Jump to the end if you just want to know how to get involved with DMP events at the International Digital Curation Conference (IDCC 2017, 20–23 Feb in Edinburgh, register here).

In 2016 we consolidated our UC3-DCC project team, our plans for the merged platform (see the roadmap to MVP), and began testing a co-development process that will provide a framework for community contributions down the line. We’re plowing through the list of features and adding documentation to the GitHub repo—all are invited to join us at IDCC 2017 for presentations and demos of our progress to date (papers, slides, etc. will all be posted after the event). For those not attending IDCC, please let us know if you have ideas, questions, anything at all to contribute ahead of the event!

DMPs sans frontières

Now we’d like to take a minute and reflect on events of the past year, particularly in the realm of open data policies, and the implications for DMPs and data management writ large. The open scholarship revolution has progressed to a point where top-level policies mandate open access to the results of government-funded research, including research data, in the US, UK, and EU, with similar principles and policies gaining momentum in Australia, Canada, South Africa, and elsewhere. DMPs are the primary vehicle for complying with these policies, and because research is a global enterprise, awareness of DMPs has spread throughout the research community. Another encouraging development is the ubiquity of the term FAIR data (Findable, Accessible, Interoperable, Reusable), which suggests that we’re all in agreement about what we’re trying to achieve.

On top of the accumulation of national data policies, 2016 ushered in a series of related developments in openness that contribute to the DMP conversation. To name a few:

  • More publishers articulated clear data policies, e.g., Springer Nature Research Data Policies apply to over 600 journals.
  • PLOS and Wiley now require an ORCID for all corresponding authors at the time of manuscript submission to promote discoverability and credit. Funders—e.g., Wellcome Trust, Swedish Research Council, and US Department of Transportation—are also getting on the ORCID bandwagon.
  • The Gates Foundation reinforced support for open access and open data by preventing funded researchers from publishing in journals that do not comply with its policy, which came into force at the beginning of 2017; this includes non-compliant high-impact journals such as Science, Nature, PNAS, and NEJM.
  • Researchers throughout the world continued to circumvent subscription access to scholarly literature by using Sci-Hub (Bohannon 2016).
  • Library consortia in Germany and Taiwan canceled (or threatened to cancel) subscriptions to Elsevier journals because of open-access related conflicts, and Peru canceled over a lack of government funding for expensive paid access (Schiermeier and Rodríguez Mega 2017).
  • Reproducibility continued to gain prominence, e.g., the US National Institutes of Health (NIH) Policy on Rigor and Reproducibility came into force for most NIH and AHRQ grant proposals received in 2016.
  • The Software Citation Principles (Smith et al. 2016) recognized software as an important product of modern research that needs to be managed alongside data and other outputs.

This flurry of open scholarship activity, both top-down and bottom-up, across all stakeholders continues to drive adoption of our services. DMPonline and the DMPTool were developed in 2011 to support open data policies in the UK and US, respectively, but today our organizations engage with users throughout the world. An upsurge in international users is evident from email addresses for new accounts and web analytics. In addition, local installations of our open source tools, as both national and institutional services, continue to multiply (see a complete list here).

Over the past year, the DMP community has validated our decision to consolidate our efforts by merging our technical platforms and coordinating outreach activities. The DMPRoadmap project feeds into a larger goal of harnessing the work of international DMP projects to benefit the entire community. We’re also engaged with some vibrant international working groups (e.g., Research Data Alliance Active DMPs, FORCE11 FAIR DMPs, Data Documentation Initiative DMP Metadata group) that have provided the opportunity to begin developing use cases for machine-actionable DMPs. So far the use cases encompass a controlled vocabulary for DMPs; integrations with other systems (e.g., Zenodo, Dataverse, Figshare, OSF, PURE, grant management systems, electronic lab notebooks); passing information to/from repositories; leveraging persistent identifiers (PIDs); and building APIs.

2017 things to come

This brings us to outlining plans for 2017 and charting a course for DMPs of the future. DCC will be running the new Roadmap code soon. And once we’ve added everything from the development roadmap, the DMPTool will announce our plans for migration. At IDCC we’ll kick off the conversation about bringing the many local installations of our tools along for the ride to actualize the vision of a core, international DMP infrastructure. A Canadian and a French team are our gracious guinea pigs for testing the draft external contributor guidelines.

IDCC DMP/BoF session

There will be plenty of opportunities to connect with us at IDCC. If you’re going to be at the main conference, we encourage you to attend our practice paper and/or join a DMP session we’ll be running in parallel with the BoFs on Wednesday afternoon, 22 Feb. The session will begin with a demo and update on DMPRoadmap; then we’ll break into two parallel tracks. One track will be for developers to learn more about recent data model changes and developer guidelines if they want to contribute to the code. The other track will be a buffet of DMP discussion groups. Given the overwhelming level of interest in the workshop (details below), one of these groups will cover machine-actionable DMPs. We’ll give a brief report on the workshop and invite others to feed into discussion. The other groups are likely to cover training/supporting DMPs, evaluation cribsheets for reviewing DMPs, or other topics per community requests. If there’s something you’d like to propose please let us know!

IDCC DMP utopia workshop

We’re also hosting a workshop on Monday, 20 Feb entitled “A postcard from the future: Tools and services from a perfect DMP world.” The focus will be on machine-actionable DMPs and how to integrate DMP tools into existing research workflows and services.

The program includes presentations, activities, and discussion to address questions such as:

  • Where and how do DMPs fit in the overall research lifecycle (i.e., beyond grant proposals)?
  • Which data could be fed automatically from other systems into DMPs (or vice versa)?
  • What information can be validated automatically?
  • Which systems/services should connect with DMP tools?
  • What are the priorities for integrations?

We’ve gathered an international cohort of diverse players in the DMP game—repository managers, data librarians, funders, researchers, developers, etc.—to continue developing machine-actionable use cases and craft a vision for a DMP utopia of the future. We apologize again that we weren’t able to accommodate everyone who wanted to participate in the workshop, but rest assured that we plan to share all of the outputs and will likely convene similar events in the future.

Keep a lookout for more detailed information about the workshop program in the coming weeks and feel free to continue providing input before, during, and afterward. This is absolutely a community-driven effort and we look forward to continuing our collaborations into the new year!

DMP themes: And then there were 14…

by Sarah Jones

We issued a call for input on the DMP themes in late September and received feedback from across the UK, Europe and the USA. Many thanks to all who responded. It’s really helped to confirm our thinking. (Note: the full list of Themes is here on GitHub)

We asked a few specific questions:

  • Whether ‘Existing Data’ should be a separate category?

This divided opinion. Some felt it should be a separate category as it comes with its own set of issues, while others commented that it’s not relevant for everybody and in some cases could be artificial to separate from the broader data description. We were persuaded by the arguments for merging because they’re consistent with the overall goals for themes (i.e., streamline guidance, avoid confusion).

  • Whether ‘Data Repository’ should be merged with ‘Preservation’?

There was a majority decision to keep these themes separate, partly as repositories are about more than just preservation, but also to ensure that repositories remain clearly visible in the guidance as this is a common topic for researchers’ questions. We also have a number of machine-actionable use cases tied to repositories so it helps to keep this category distinct.

  • Whether the various data sharing themes should be merged?

Again there was a clear consensus here that the themes should be merged. You felt itwas confusing for researchers to have too many separate options and it could make the guidance unwieldy. We now have one theme that covers how and when data will be shared, including guidance on managing any restrictions.

Other suggestions you made have caused us to merge ‘Data Security’ with ‘Storage and Backup’ and rename ‘Data Quality’ to ‘Data Collection’ so it covers broader concerns around data collection and organisation. There were a few requests to reinstate the ‘Project Description’ theme, but we felt this works better as metadata under the plan details rather than as a theme. As a final step, we significantly revised the guidance so this is more concise and directive too. Please take a look and let us know what you think!

We shared the new revised themes with the Data Documentation Initiative (DDI) working group who we’ve been having calls with about standards for DMPs, and will push them out to other discussion lists soon. We will also implement the revised themes in the Roadmap platform in the new year.

Other news

We’ve been working on lots of other topics in the meantime too. The developers have been busy migrating the database to a new schema and doing some refactoring. These changes will improve the performance of the tool so you won’t get the long page loading times we’ve sometimes struggled with, and will also support scalability as we’re getting increasing levels of use from around the globe. We’ll be giving a demonstration of the new DMPRoadmap codebase at IDCC and walking people through recent changes and new features. The demo will be part of a session in the main programme that will provide an opportunity to talk with the developers, hear more about our future plans, and share ideas from your DMP work.

We are also coordinating a workshop on machine-actionable DMPs. There’s already been a lot of interest in this so we are running a waiting list. If you want to join us, please get in touch soon and let us know why you are interested and what inputs you could bring. We are trying to get a diverse audience in the room so we understand use cases from different perspectives and countries.

Roadmap team cheers

Both of our teams will be enjoying a well-earned break over the Christmas holidays. Most of us are away from next week until 9th January so it may take us longer to respond to any queries in the coming weeks. We hope you all have a wonderful break too and enjoy the festivities. We raise a glass to you and more collaboration on DMPs in the future. Cheers!

Finding our Roadmap rhythm

Image from page 293 of "The life of the Greeks and Romans" (1875) by Guhl, Koner, and Hueffer. Retrieved from the Internet Archive https://archive.org/details/lifeofgreeksroma00guhl

Image from page 293 of “The life of the Greeks and Romans” (1875) by Guhl, Koner, and Hueffer. Retrieved from the Internet Archive https://archive.org/details/lifeofgreeksroma00guhl

In keeping with our monthly updates about the merged Roadmap platform, here’s the short and the long of what we’ve been up to lately:

Short update

Long(er) update

This month our main focus has been getting into a steady 2-week sprint groove that you can track on our GitHub Projects board. DCC/DMPonline is keen to migrate to the new codebase asap so in preparation we’re revising the database schema and optimizing the code. This clean-up work not only makes things easier for our core development team, but will facilitate community development efforts down the line. It also addresses some scalability issues that we encountered during a week of heavy use on the hosted instance of the Finnish DMPTuuli (thanks for the lessons learned, Finland!). We’ve also been evaluating dependencies and fixing all the bugs introduced by the recent Rails and Bootstrap migrations.

Once things are in good working order, DMPonline will complete their migration and we’ll shift focus to adding new features from the MVP roadmap. DMPTool won’t migrate to the new system until we’ve added everything on the list and conducted testing with our institutional partners from the steering committee. The UX team from the CDL is helping us redesign some things, with particular attention to internationalization and improving accessibility for users with disabilities.

The rest of our activities revolve around gathering requirements and refining some use cases for machine-actionable DMPs. This runs the gamut from big-picture brainstorming to targeted work on features that we’ll implement in the new platform. The first step to achieving the latter involves a collaboration with Substance.io to implement a new text editor (Substance Forms). The new editor offers increased functionality, a framework for future work on machine-actionability, and delivers a better user experience throughout the platform. In addition, we’re refining the DMPonline themes (details here)—we’re still collecting feedback and are grateful to all those who have weighed in so far. Sarah and I will consolidate community input and share the new set of themes during the first meeting of a DDI working group to create a DMP vocabulary. We plan to coordinate our work on the themes with this parallel effort—more details as things get moving on that front in Nov.

Future brainstorming events include PIDapalooza—come to Iceland and share your ideas about persistent identifiers in DMPs!—and the International Digital Curation Conference (IDCC) 2017 for which registration is now open. We’ll be presenting a Roadmap update at IDCC along with a demo of the new system. In addition, we’re hosting an interactive workshop for developers et al. to help us envision (and plan for) a perfect DMP world with tools and services that support FAIR, machine-actionable DMPs (more details forthcoming).

Two final pieces of info: 1) We’re still seeking funding to speed up progress toward building machine-actionable DMP infrastructure; we weren’t successful with our Open Science Prize application but are hoping for better news on an IMLS preliminary proposal (both available here). 2) We’re also continuing to promote greater openness with DMPs; one approach involves expanding the RIO Journal Collection of exemplary plans. Check out the latest plan from Ethan White that also lives on GitHub and send us your thoughts on DMP workflows, publishing and sharing DMPs.

A common set of themes for DMPs: Seeking input

When the Digital Curation Centre (DCC) revised DMPonline in 2013, we introduced the concept of themes to the tool. The themes represent the most common topics addressed in Data Management Plans (DMPs) and work like tags to associate questions and guidance. Questions within DMP templates can be tagged with one or more themes, and guidance can be written by theme to allow organisations to apply their advice over multiple templates at once. This means organisations don’t have to worry about monitoring changes in requirements and updating their guidelines each time a new template is released.

Backup and storage guidance with theme tag

Institutional guidance on ‘Storage and Backup,’ overlaid onto a funder template

Moving forward, we see potential for broader application of the themes. In collaboration with the DMPTool, we plan to use a refined set of themes to support our objectives around machine-actionable DMPs. The themes provide the beginnings of a common vocabulary and structure for DMPs and could help to identify sections of text to mine, e.g., to identify a repository named in a DMP and the volume of data in the pipeline.

Stephanie and I have revised the existing set of Data Management Planning themes and propose a shortened set of 17 themes. We merged several closely related themes, e.g., ‘Metadata’ and ‘Documentation.’ Now we’re keen to collect your feedback about whether the themes still cover all the required elements and if they make sense to users. The goal is to find a suitable balance between the total number of themes (for mining and for usability considerations when creating guidance) and granularity. Specific questions we have are:

  • Whether ‘Existing data’ should be a separate category? We’ve merged it with the general ‘Data description’ on the rationale that reusing data doesn’t apply in all domains.
  • Should the ‘Data repository’ theme be merged with ‘Preservation’ or is it better kept separate since repositories cover preservation and sharing?
  • Several themes address data sharing: one is generic (‘Data sharing’), one addresses the ‘Timeframe for sharing’ and one covers ‘Restricted-use data.’ Is this granularity needed or should some of these themes be merged, e.g., ‘Data sharing’ and ‘Restricted-use data.’

We’re reaching out to various groups on this: the Force 11 FAIR DMP group, the RDA Active DMPs group, CASRAI UK DMP working group, and the Data Documentation Initiative (DDI) Active DMPs working group. Naturally we’re also consulting the DMPonline and DMPTool user groups and are keen to receive feedback from any other quarters too so please pass this notice on to colleagues! Comments can be left on the blog here or emailed to the DMPONLINE-USER-GROUP.

The original and revised sets of themes are below for reference:

 

Getting our ducks in a row

From Flickr by Cliff Johnson, CC BY-SA 2.0

From Flickr by Cliff Johnson, CC BY-SA 2.0

Recent activity on the Roadmap project encompasses two major themes: 1) machine-actionable data management plans and 2) kicking off co-development of the shared codebase.

Machine-actionable DMPs

The first of these has been a hot topic of conversation among stakeholders in the data management game for some time now, although most use the phrase “machine-readable DMPs.” So what do we mean by machine-actionable DMPs? Per the Data Documentation Initiative definition, “this term refers to information that is structured in a consistent way so that machines can be programmed against the structure.” The goal of machine-actionable DMPs, then, is to better facilitate good data management and reuse practices (think FAIR: Findable, Accessible, Interoperable, Reusable) by enabling:

  • Institutions to manage their data
  • Funders to mine the DMPs they receive
  • Infrastructure providers to plan their resources
  • Researchers to discover data

This term is consistent with the Research Data Alliance Active DMPs Interest Group and the FORCE11 FAIR DMPs group mission statements, and it seems to capture what we’re all thinking: i.e., we want to move beyond static text files to create a dynamic inventory of digital research methods, protocols, environments, software, articles, data… One reason for the DMPonline-DMPTool merger is to develop a core infrastructure for implementing use cases that make this possible. We still need a human-readable document with a narrative, but underneath the DMP could have more thematic richness with value for all stakeholders.

A recent Cern/RDA workshop presented the perfect opportunity to consolidate our notes and ideas. In addition to the Roadmap project members, Daniel Mietchen (NIH) and Angus Whyte (DCC) participated in the exercise. We conducted a survey of previous work on the topic (we know we didn’t capture everything so please alert us to things we missed) and began outlining concrete use cases for machine-actionable DMPs, which we plan to develop further through community engagement over the coming months. Another crucial piece of our presentation was a call to make DMPs public, open, discoverable resources. We highlighted existing efforts to promote public DMPs (e.g., the DMPTool Public DMPs list, publishing exemplary DMPs in RIO Journal, Dataverse collections that include DMPs) but these are just a drop in the bucket compared to what we might be able to do if all DMPs were open by default.

You can review our slides here. And please send feedback—we want to know what you think!

Let the co-development begin!

Now for the second news item: our ducks are all in a row and work is underway on the shared Roadmap codebase.

We open with a wistful farewell to Marta Ribeiro, who is moving on to an exciting new gig at the Urban Big Data Centre. DCC has hired two new developers to join our ranks—Ray Carrick and Jimmy Angelakos—both from their sister team at EDINA. The finalized co-development team commenced weekly check-in calls and in the next week or two we’ll begin testing the draft co-development process by adding three features from the roadmap:

  1. Enhanced institutional branding
  2. Funder template export
  3. OAuth link an ORCID

In the meantime, Brian completed the migration to Rails 4.2 and both teams are getting our development environments in place. Our intention is to iterate on the process for a few sprints, iron out the kinks, and then use it and the roadmap as the touchstones for a monthly community developer check-in call. We hope this will provide a forum for sharing use cases and plans for future work (on all instances of the tool) in order to prioritize, coordinate, and alleviate duplication of effort.

The DCC interns have also been plugging away at their respective projects. Sam Rust just finished building some APIs for creating plans and extracting guidance, and is now starting work on the usage statistics use case. Damodar Sójka meanwhile is completing the internationalization project, drawing from work done by the Canadian DMP Assistant team. We’ll share more details about their work once we roll it all back into the main codebase.

Next month the UC Berkeley Web Services team will evaluate the current version of DMPonline to flag any accessibility issues that need to be addressed in the new system. We’ve also been consulting with Rachael Hu on UX strategy. We’re keeping track of requests for the new system and invite you to submit feedback via GitHub issues.

Stay tuned to GitHub and our blog channels for more documentation and regular progress updates.

The 20:51 sprint (Roadmap team-building: UK edition)

teamwork

This week we hosted the DMPTool team to flesh out our plans for ‘roadmap’ – the joint codebase we’re building together based on DMPonline and DMPTool. The key focus was reviewing and prioritising tasks for an initial release.  Building on discussions from the earlier US visit, we confirmed what work was to be done and agreed to begin with some well-defined, short tasks as a test of our co-development procedures. With everyone taking leave over the coming weeks, the first sprint will start in mid-July at which point we’ll begin adding documentation to the Github repository.

We also discussed communication plans. Stephanie and I will take turns to do monthly blog posts so you can stay in the loop with what’s happening, and we aim to start regular calls in a few months with others who are actively working on the code, such as the Portage group in Canada. This will allow everyone to share their plans for future enhancements and to coordinate development activities. We’re always learning about new people who have picked up on our software – the latest being a group in Germany who have extended the DMPTool code to offer a bi-lingual interface – so we want to do more to bring these efforts together. While we get our work underway, we encourage people to join the developers list as a place to start discussions and form a community of interest.

Machine-actionable DMPs was another key theme for which Daniel Mietchen joined our discussions. Stephanie has an RDA/US Data Share Fellowship to pursue work in this area and we’re planning to give talks at some upcoming events highlighting our ideas. We’ve started to refine the themes used for guidance in DMPonline. Currently, DCC defines 28 themes corresponding with UK funder questions that are often addressed in a DMP (e.g., Data format, Metadata, Ethical issues, etc.). These themes offer the perfect starting point for standardising and structuring DMPs so it’s more feasible to identify and mine relevant text. We’ll be seeking comments from our user communities and key working groups such as CASRAI, RDA and FORCE11 shortly on this. We’re also keen to capture more data in a controlled way so it can be put to better uses. One idea is to provide an actionable list of repositories to allow researchers to select where they are going to deposit research outputs, and then to use this data to push notifications out to alert repositories and/or monitor compliance. Machine-actionable DMPs have been part of the future plans of both teams for some years, and they are currently a hot topic. We’re excited that we now have the resources to develop those ideas and a system that will allow us to test them via deployment. We also want to collect additional use cases and explore integrations with other systems so please don’t hesitate to get in touch.

The eagle-eyed among you may have spotted some new faces in the team photos. The DCC has two student interns from Informatics working on DMPonline over the summer. Damodar is doing the internationalisation work that we consulted with the user group on at IDCC and Sam is busy developing an API. Both are making great progress so we’ll be looking for input from the user group again soon to try out the new features. The DMPTool team includes a new developer called Brian joining as technical lead. The visit was a great team-building opportunity for our transatlantic DMP roadmap project.

sprintIt was a jam-packed week with lots of meetings, brainstorming sessions and time working together on the code. We had new culinary experiences (deep-fried haggis balls no less!), heard some hilarious tales from the adventures of John Chodacki, and initiated the US team in the Glasgow-Edinburgh commute, including a quick dash one evening to make the 20:51 train home. Here’s the photographic proof of our first successful joint sprint. Stay tuned for what else we deliver over the coming months.

Roadmap team-building exercises: US edition

roadmap_wallLast week we hosted Marta Ribeiro, the lead developer for DMPonline, for an intense, donut-fueled planning meeting to define our co-development process and consolidate our joint roadmap. The following is a debriefing on what we accomplished and what we identified as our next steps.

The project team is established, with Brian Riley joining as the DMPTool technical lead. Marta is busy completing the migration of DMPonline to Rails 4.2 to deposit the code into our new Github repository: DMPRoadmap. There’s nothing to see just yet—we’re in the midst of populating it with documentation about our process, roadmap, issues, etc. As soon as everything is in place, we’ll send word so that anyone who’s interested can track our progress. This will also allow us to begin sussing out how to incorporate external development efforts to benefit the larger DMP community. In addition, Marta is mentoring a pair of summer interns who are undertaking the internationalization work and building APIs. Meanwhile, Brian will finish building the servers for the Roadmap development and staging environments on AWS with another new member of the UC3 team: Jim Vanderveen (DevOps/Developer). Additional core team members include Stephanie Simms and Sarah Jones as Service/Project Managers, Marisa Strong as the Technical Manager, and the CDL UX team (many thanks to our UX Design Manager, Rachael Hu, for spending so much time with us!). UC3 and DCC will also rely on their existing user groups for testing and feedback on both sides of the pond.

Other groundlaying activities include a web accessibility evaluation for DMPonline to ensure that the new system is accessible for disabled users and exploring what we (and others) mean when we talk about “machine-readable DMPs.” Stephanie just received an RDA/US Data Share Fellowship to develop use cases for making DMPs machine readable, in consultation with the Active DMPs Interest Group and the research community at large. In line with this effort, she’ll be participating in an interdisciplinary and international workshop on active DMPs next month, co-hosted by CERN and the RDA group. We’re actively seeking and summarizing thoughts on the topic so please send us your ideas!

We conclude this edition with a draft of our project roadmap (below); it lists all of the features that we’ll be adding to the DMPonline codebase before we release the new platform. Most of the features already exist in the DMPTool and were slated for future enhancements to DMPonline. Stay tuned for our next update following a UC3 exchange visit to Glasgow/Edinburgh in mid June to prioritize the roadmap and commence co-development work.

Roadmap

  • Migration to Rails v.4.2
  • Bring DMP Assistant’s internationalization upstream for multi-lingual support
  • Adding the concept of locales so specific organizations, funders, and templates can be defined and filtered out for certain users/contexts
  • Shibboleth support through eduGain
  • OAuth link for ORCID
  • APIs to create plans, extract guidance, and generate usage statistics
  • More robust institutional branding
  • A lifecycle to indicate the status of plans and allow institutional access to plans
  • Support for reviewing plans
  • Public sharing option > Public DMPs library
  • Flag test plans (to exclude them from usage stats)
  • Email notification system
  • Admin controls for assigning admin rights to others
  • Export template with guidance
  • Copy template option for creating new templates
  • Copy plan option for creating new plans
  • Toggle switch for navigating between Plan area and Admin area