Difference between revisions of "Plan overall GPF activities"
From Geoscience Paper of the Future
(→Commitment) |
(Deleted PropertyValue: SubTask = Plan_publication_of_special_issue) |
||
| (34 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[Category:Task]] | [[Category:Task]] | ||
| − | == Overall | + | == Geoscience Paper of the Future: Overall Goals == |
The overall goal is to demonstrate how papers will be published in the future, going beyond a PDF format and including software, datasets, and workflow all published in open and accessible ways that make the paper transparent, reproducible, and machine indexable. We refer to such a paper as a "geoscience paper of the future” (GPF), and part of this activity will be to define what that means. | The overall goal is to demonstrate how papers will be published in the future, going beyond a PDF format and including software, datasets, and workflow all published in open and accessible ways that make the paper transparent, reproducible, and machine indexable. We refer to such a paper as a "geoscience paper of the future” (GPF), and part of this activity will be to define what that means. | ||
Creating a GPF will include tasks such as data publication and citation, software publication and citation, describing software, using metadata standards, and capturing workflows and provenance. GeoSoft instructors will prepare participants through best practices in these topics, and be accessible to help as needed. No programming or computer science background is needed to participate. | Creating a GPF will include tasks such as data publication and citation, software publication and citation, describing software, using metadata standards, and capturing workflows and provenance. GeoSoft instructors will prepare participants through best practices in these topics, and be accessible to help as needed. No programming or computer science background is needed to participate. | ||
| − | == | + | == Outcomes == |
| + | |||
| + | Each participant will generate a GPF about their own research. | ||
| + | |||
| + | A Special Issue of a geosciences journal (TBD) that will include all GPFs from this activity. Special Issue editors could be among the participants. Participant papers will be submitted to this Special Issue. | ||
| − | + | A separate paper co-authored by all participants will discuss challenging issues, best practices, and benefits synthesized by the group during this activity. | |
== Commitment == | == Commitment == | ||
| − | A 2 day face-to-face meeting (Feb-March) followed by biweekly calls (March-May). Most of the work will be planned at the face-to-face meeting, with about 2 hours of work per week after that. | + | A 2 day face-to-face meeting (Feb-March) followed by biweekly calls (March-May). Most of the work will be planned at the face-to-face meeting, with about 2 hours of work per week after that. |
| − | == | + | == Phased Plan == |
| − | + | The major effort for this activity will occur from January to June 2015. | |
| − | + | <ol style="list-style-type:lower-roman"> | |
| − | + | <li> '''Jan-Feb: Defining Scope'''. Anyone interested would write a short proposal specifying the target science paper that will be turned into a GPF. The paper could be: a) a paper they have already published; b) a paper they have not yet published; c) a paper from a colleague that they find useful; d) a seminar paper in their field that people would appreciate seeing published in this way. Proposals can be submitted by individuals or by small teams (up to 4 people if that makes the work more manageable). The proposals will be peer reviewed by the group in an open discussion phase, with the goal of ensuring that the scope of each proposal is feasible. | |
| − | + | <li> '''Feb-March: Face-to-Face Kickoff Meeting'''. Discussions to elaborate the goals as well as training will take place during a 2-3 day face-to-face kickoff meeting (expenses covered by the GeoSoft project). At that meeting, GeoSoft researchers will walk through the specific tasks to be covered and recommend best practices. | |
| − | + | <li> '''March-May: Biweekly Goals and Reports'''. Participants will be given a specific task every two weeks. Each participant will keep an up-to-date electronic document (eg, web site, wiki, google doc) with a detailed report of the work done, which will form the basis for their GPF. A mailing list will be set up to address any questions or issues that may come up. The group will hold a telecon at the end of each 2-week period to share their results and to synthesize what worked, what did not work, and lessons learned. | |
| − | + | <li> '''June: Paper Preparation and Review''': Participants will finalize writing their papers and will review each other’s papers. | |
| − | + | </ol> | |
| − | + | '''A detailed timeline is available [[Plan_overall_timeline | here]].''' | |
| − | + | == Possible Additional Outcomes == | |
| − | + | Possible additional outcomes to consider include: | |
* Awards to papers that best demonstrated some recognized quality of a GPF? | * Awards to papers that best demonstrated some recognized quality of a GPF? | ||
| − | * A session with presentations of these papers will be held at the EarthCube All Hands meeting in | + | * A session with presentations of these papers will be held at the EarthCube All Hands meeting in May 27-28, 2015? |
| − | * A session at AGU? | + | * A session at AGU/GSA 2015? |
| − | * The starting of a new GPF repository (within the journal? EarthCube?) | + | * The starting of a new GPF repository (within the journal? in EarthCube?) |
* Increase recognition for investments in software (eg by measuring software downloads or citations of these papers)? | * Increase recognition for investments in software (eg by measuring software downloads or citations of these papers)? | ||
* Ideas and visibility for follow-on EarthCube proposals? | * Ideas and visibility for follow-on EarthCube proposals? | ||
* A Phase V on reproducibility: ask others to run the software, perhaps try it with their own data? Engage people that could use these papers in a classroom setting? | * A Phase V on reproducibility: ask others to run the software, perhaps try it with their own data? Engage people that could use these papers in a classroom setting? | ||
| + | == Participants == | ||
| + | Participants will be selected members of the GeoSoft Early Career Advisory Committee who want to learn and demonstrate in practice how to write a GPF. | ||
| + | |||
| + | '''A list of participants is available [[Participant_sign-up | here]].''' | ||
<!-- Add any wiki Text above this Line --> | <!-- Add any wiki Text above this Line --> | ||
<!-- Do NOT Edit below this Line --> | <!-- Do NOT Edit below this Line --> | ||
{{#set: | {{#set: | ||
| − | |||
Expertise=Open_science| | Expertise=Open_science| | ||
Expertise=Reproducibility| | Expertise=Reproducibility| | ||
| Line 55: | Line 62: | ||
Expertise=Data_publication| | Expertise=Data_publication| | ||
Expertise=Software_publication| | Expertise=Software_publication| | ||
| + | Expertise=Code_repositories| | ||
Owner=Yolanda_Gil| | Owner=Yolanda_Gil| | ||
StartDate=2014-11-15| | StartDate=2014-11-15| | ||
| − | TargetDate=2015- | + | SubTask=Participant_sign-up| |
| + | SubTask=Hold_regular_telecons| | ||
| + | SubTask=Plan_face-to-face_kickoff_meeting| | ||
| + | SubTask=Plan_overall_timeline| | ||
| + | SubTask=Discuss_what_we_will_consider_a_GPF| | ||
| + | SubTask=Document_GPF_activities| | ||
| + | TargetDate=2015-07-31| | ||
Type=Medium}} | Type=Medium}} | ||
Latest revision as of 17:08, 15 April 2015
Contents
Geoscience Paper of the Future: Overall Goals
The overall goal is to demonstrate how papers will be published in the future, going beyond a PDF format and including software, datasets, and workflow all published in open and accessible ways that make the paper transparent, reproducible, and machine indexable. We refer to such a paper as a "geoscience paper of the future” (GPF), and part of this activity will be to define what that means.
Creating a GPF will include tasks such as data publication and citation, software publication and citation, describing software, using metadata standards, and capturing workflows and provenance. GeoSoft instructors will prepare participants through best practices in these topics, and be accessible to help as needed. No programming or computer science background is needed to participate.
Outcomes
Each participant will generate a GPF about their own research.
A Special Issue of a geosciences journal (TBD) that will include all GPFs from this activity. Special Issue editors could be among the participants. Participant papers will be submitted to this Special Issue.
A separate paper co-authored by all participants will discuss challenging issues, best practices, and benefits synthesized by the group during this activity.
Commitment
A 2 day face-to-face meeting (Feb-March) followed by biweekly calls (March-May). Most of the work will be planned at the face-to-face meeting, with about 2 hours of work per week after that.
Phased Plan
The major effort for this activity will occur from January to June 2015.
- Jan-Feb: Defining Scope. Anyone interested would write a short proposal specifying the target science paper that will be turned into a GPF. The paper could be: a) a paper they have already published; b) a paper they have not yet published; c) a paper from a colleague that they find useful; d) a seminar paper in their field that people would appreciate seeing published in this way. Proposals can be submitted by individuals or by small teams (up to 4 people if that makes the work more manageable). The proposals will be peer reviewed by the group in an open discussion phase, with the goal of ensuring that the scope of each proposal is feasible.
- Feb-March: Face-to-Face Kickoff Meeting. Discussions to elaborate the goals as well as training will take place during a 2-3 day face-to-face kickoff meeting (expenses covered by the GeoSoft project). At that meeting, GeoSoft researchers will walk through the specific tasks to be covered and recommend best practices.
- March-May: Biweekly Goals and Reports. Participants will be given a specific task every two weeks. Each participant will keep an up-to-date electronic document (eg, web site, wiki, google doc) with a detailed report of the work done, which will form the basis for their GPF. A mailing list will be set up to address any questions or issues that may come up. The group will hold a telecon at the end of each 2-week period to share their results and to synthesize what worked, what did not work, and lessons learned.
- June: Paper Preparation and Review: Participants will finalize writing their papers and will review each other’s papers.
A detailed timeline is available here.
Possible Additional Outcomes
Possible additional outcomes to consider include:
- Awards to papers that best demonstrated some recognized quality of a GPF?
- A session with presentations of these papers will be held at the EarthCube All Hands meeting in May 27-28, 2015?
- A session at AGU/GSA 2015?
- The starting of a new GPF repository (within the journal? in EarthCube?)
- Increase recognition for investments in software (eg by measuring software downloads or citations of these papers)?
- Ideas and visibility for follow-on EarthCube proposals?
- A Phase V on reproducibility: ask others to run the software, perhaps try it with their own data? Engage people that could use these papers in a classroom setting?
Participants
Participants will be selected members of the GeoSoft Early Career Advisory Committee who want to learn and demonstrate in practice how to write a GPF.
A list of participants is available here.
