Difference between revisions of "Plan overall timeline"
From Geoscience Paper of the Future
(→Tasks and Timeline) |
|||
| Line 5: | Line 5: | ||
{| class="wikitable" style="color:navy; background-color:#ffffcc;" cellpadding="10" | {| class="wikitable" style="color:navy; background-color:#ffffcc;" cellpadding="10" | ||
| − | |''' | + | | style="width: 15%;"| '''TARGET DATE''' |
| − | |''' | + | | style="width: 20%;"| '''GOAL''' |
| − | |''' | + | | style="width: 65%;"| '''TASKS''' |
|- | |- | ||
|2/20 | |2/20 | ||
| Line 18: | Line 18: | ||
|- | |- | ||
|3/11-3/13 | |3/11-3/13 | ||
| − | |'''F2F Meeting''' | + | |'''Attend F2F Meeting training''' |
|Training and detailed planning | |Training and detailed planning | ||
|- | |- | ||
| Line 42: | Line 42: | ||
|- | |- | ||
|5/29 | |5/29 | ||
| − | |''' | + | |'''Prepare the article for publication''' |
| − | | | + | |Document the methods section, the figures, and the references. Submit the article to the journal. |
|} | |} | ||
Revision as of 05:30, 6 February 2015
Tasks and Timeline
| TARGET DATE | GOAL | TASKS |
| 2/20 | Make data accessible | Publish input, intermediate, and final data in a public shared repository (e.g., FigShare), and cite it in the article. |
| 3/6 | Ensure software is usable | Gather all the software used in the article, including data preparation codes, pre-processing software, visualization software, and any scripts used. Check that all software runs with input data and generates the results as expected. |
| 3/11-3/13 | Attend F2F Meeting training | Training and detailed planning |
| 3/20 | Sketch the overall workflow | Describe the data flow across software components. Define clearly for each piece of software used in the article what are the inputs and outputs and their data types. |
| 4/3 | Make software executable | Ensure that software can be run by others. |
| 4/17 | Software attribution | Document creators, authors, contributors of the software. Cite the software as appropriate in the paper. |
| 5/1 | Make software accessible | Publish software in a public repository (e.g., GitHub), use a license, and cite it in the article. Make it easy to track updates and new versions of the software. |
| 5/15 | Document domain characteristics | Describe domain data and constraints that help others understand the software. |
| 5/29 | Prepare the article for publication | Document the methods section, the figures, and the references. Submit the article to the journal. |
