DMPRoadmap/roadmap: DCC/UC3 collaboration for a data management planning tool · GitHub

Repository navigation

Name		Name	Last commit message	Last commit date
.github		.github
app		app
bin		bin
config		config
db		db
doc		doc
lib		lib
log		log
public		public
spec		spec
.annotaterb.yml		.annotaterb.yml
.browserslistrc		.browserslistrc
.editorconfig		.editorconfig
.env.mysql2		.env.mysql2
.env.postgresql		.env.postgresql
.eslintrc.json		.eslintrc.json
.gitignore		.gitignore
.node-version		.node-version
.rubocop.yml		.rubocop.yml
.ruby-version		.ruby-version
CHANGELOG.md		CHANGELOG.md
CODE_OF_CONDUCT.md		CODE_OF_CONDUCT.md
Dangerfile		Dangerfile
Gemfile		Gemfile
Gemfile.lock		Gemfile.lock
LICENSE.md		LICENSE.md
Procfile		Procfile
Procfile.dev		Procfile.dev
README.md		README.md
Rakefile		Rakefile
babel.config.js		babel.config.js
config.ru		config.ru
package.json		package.json
postcss.config.js		postcss.config.js
yarn.lock		yarn.lock

Repository files navigation

DMP Roadmap

DMP Roadmap is a Data Management Planning tool. Management and development of DMP Roadmap is jointly provided by the Digital Curation Centre (DCC), http://www.dcc.ac.uk/, and the University of California Curation Center (UC3), http://www.cdlib.org/services/uc3/.

The tool has four main functions:

To help create and maintain different versions of Data Management Plans;
To provide useful guidance on data management issues and how to meet research funders' requirements;
To export attractive and useful plans in a variety of formats;
To allow collaborative work when creating Data Management Plans.

Click here for the latest releases.

Installation

See the Installation Guide on the Wiki.

Troubleshooting

See the Troubleshooting Guide on the Wiki.

Support

Issues should be reported here on Github Issues Please be advised though that we can only provide limited support for your local installations. Any security patches and bugfixes will be applied to the most recent version, and we will endeavour to support migrations to the current release.

Contributing

If you would like to contribute to the project. Please follow these steps to submit a contribution:

Comment on the Github issue (or create one if one does not exist) and let us know that you're working on it.
Fork the project (if you have not already) or rebase your fork so that it is up to date with the current repository's 'development' branch
Create a new branch in your fork. This will ensure that you are able to work at your own pace and continue to pull in any updates made to this project.
Make your changes in the new branch
When you have finished your work, make sure that your version of the 'development' branch is still up to date with this project. Then merge your new branch into your 'development' branch.
Then create a new Pull Request (PR) from your branch to this project's 'development' branch in GitHub
The project team will then review your PR and communicate with you to convey any additional changes that would ensure that your work adheres to our guidelines.