Data management resources » History » Version 17
Steve Welburn, 2013-01-07 01:28 PM
| 1 | 12 | Steve Welburn | h1. Data management resources for C4DM researchers |
|---|---|---|---|
| 2 | 2 | Steve Welburn | |
| 3 | 10 | Steve Welburn | h2. Source Code Management |
| 4 | 4 | Steve Welburn | |
| 5 | 11 | Steve Welburn | "Sound Software":http://code.soundsoftware.ac.uk provides Mercurial version control and assorted project management facilities (e.g. options for issue logs, Gantt charts, wikis, downloads, documentation). These facilities are available for any researcher in the audio and music field within the UK, working with UK researchers, or working on a project of interest to UK researchers. |
| 6 | 1 | Steve Welburn | |
| 7 | 13 | Steve Welburn | Sound Software projects can be either public (visible to everyone) or private (visible to selected Sound Software users). We recommend that code will be published should be developed in a source code repository in a project which is intended to be public (although the project may be private for the initial development). Developing the code in this manner reminds you that it is not an appropriate place to put any private material (e.g. server details, passwords, local branding) and means that when it is time to formally publish the code you simply have to make the project public. Any private details (aforementioned server details etc.) can be stored in a private sub-project. The sub-project may also be appropriate for an internal wiki, minutes of project meetings etc. |
| 8 | 13 | Steve Welburn | |
| 9 | 13 | Steve Welburn | Public project: |
| 10 | 13 | Steve Welburn | * Published code repository |
| 11 | 13 | Steve Welburn | * Issue tracking |
| 12 | 13 | Steve Welburn | * Documentation |
| 13 | 13 | Steve Welburn | * Downloads |
| 14 | 13 | Steve Welburn | * News |
| 15 | 13 | Steve Welburn | |
| 16 | 13 | Steve Welburn | Private sub-project: |
| 17 | 13 | Steve Welburn | * Internal project management |
| 18 | 13 | Steve Welburn | * Local configuration (servers, passwords, branding) |
| 19 | 13 | Steve Welburn | * Internal project documentation e.g. status reports, budgets |
| 20 | 13 | Steve Welburn | |
| 21 | 10 | Steve Welburn | h2. Backing Up |
| 22 | 4 | Steve Welburn | |
| 23 | 10 | Steve Welburn | For researchers within the QMUL school of Electronic Engineering and Computer Science, details of available file servers can be found "on the intranet":https://intranet.eecs.qmul.ac.uk/services/file. Home and research group directories are backed up to tape but bulk data storage facilities are not. |
| 24 | 10 | Steve Welburn | |
| 25 | 10 | Steve Welburn | h2. Data Publication |
| 26 | 10 | Steve Welburn | |
| 27 | 17 | Steve Welburn | For C4DM researchers, data can be published through the "C4DM research data repository":http://c4dm.eecs.qmul.ac.uk/rdr/xmlui/. This is a "DSpace repository":http://www.dspace.org/ configured to allow research data to be published with basic metadata (author, preferred citation etc.). |
| 28 | 14 | Steve Welburn | |
| 29 | 14 | Steve Welburn | The C4DM RDR is backed up to tape. |