We’re deploying another batch of bug fixes this Wednesday, 8 June 2016 at 4:00pm PST. The release will involve a mini maintenance window to update the database—30 min max downtime, 4:00–4:30pm PST. Most of the bugs involve patching security vulnerabilities and database clean-up so they won’t be apparent to users. We did fix one issue that prevented work from being saved when users clicked to other parts of a plan without first selecting “Save Response” or “Save and Next” for the final question in a given DMP.
Over the coming weeks we’ll be focusing our efforts on the Roadmap project. Stay tuned for another progress report following our exchange visit to Glasgow/Edinburgh next week to commence co-development with our DCC partners!
We just announced a maintenance window for Wednesday, 4 May 2016, 3:00–4:00pm (PST). We’ll be updating some support scripts related to last month’s migration to AWS that help ensure the stability of the system. Following the maintenance, these bug fixes will also be in place:
- We fixed an issue that prevented admins from uploading files for institutional logos.
- We created a static FAQ page on GitHub to replace the unreliable askbot service.
- We added a date field to the API call to get a list of users. This call enables admins to track new users over time.
- We updated links on the Help pages and other outdated info throughout the platform (e.g., we have a new CDL Director: Günter Waibel!).
We’ll continue on a 2-week release cycle until all of the bugs are wiped out. You can follow our progress in the GitHub issue tracker and keep a lookout for updates. We also invite direct bug reporting and enhancement requests via GitHub issues.
First things first, we want to inform you about upcoming maintenance. The DMPTool will be unavailable on Wednesday Feb 3, 2016 5:00 – 6:00pm (PDT) while we migrate the database to AWS. The application will also be moving to the cloud so you can expect another maintenance message in the near future. We apologize for the inconvenience.
In other news, we’re excited to share the following roadmap for future development. Thanks to all of your suggestions about how to improve the DMPTool, we’ve identified and prioritized some feature enhancements to meet evolving data management planning needs:
- API work for integration projects with other data management systems, to extract guidance and customizations, and to generate additional user statistics
- Formatting tools for template creation and customization views
- Search function for lists of templates, customizations, and partner institutions
- Function for customizing auto-generated email messages (e.g., when a user submits a plan for review)
Migrations and bug fixes are already underway. We’ll provide a timeframe for the roadmap in the coming months as we clear the backlog and move on to enhancements. You can also track our progress and help shape future plans by submitting feedback through our GitHub Issue Tracker.
The DMPTool will be unavailable for a short period on Thursday April 25 starting at 3pm PT (6pm ET) while we conduct some maintenance activities. This outage should only last 10 minutes. We apologize for the inconvenience.
The DMPTool will be unavailable for a short period on Tuesday April 23 starting at 4pm PT (7pm ET) while we conduct some maintenance activities. This outage should only last 10 minutes. We apologize for the inconvenience.
The maintenance to the DMPTool has been extended until 5:00pm PST (2013-01-13 01:00 UTC). We apologize for the inconvenience.
Due to system maintenance, the DMPTool will be unavailable for periods on Saturday January 12 2013 and Sunday January 13 2013.
- Saturday January 12 2013, 10:00am to 2:00pm PST (18:00 to 22:00 UTC)
- Sunday January 13, 2013, 1:00pm to 4:00pm PST (21:00 to 23:59 UTC)
During this time, the website will be unavailable and access to data management plans will be blocked.
This maintenance window is necessary to upgrade core infrastructure in the California Digital Library’s production data center. It is possible that service to the DMPTool will be restored before the scheduled end of the outage, but this cannot be guaranteed.
Please contact us at firstname.lastname@example.org with any questions or concerns. We apologize for the inconvenience.