<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Courier;
panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:260575558;
mso-list-template-ids:-797441152;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:752092451;
mso-list-template-ids:1698828206;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Just the narrowing down part is what I had in mind.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Sarah Ramdeen <sarah.ramdeen@gmail.com> <br>
<b>Sent:</b> Wednesday, February 16, 2022 10:30 AM<br>
<b>To:</b> Hampapuram Ramapriyan <hampapuram.ramapriya@ssaihq.com><br>
<b>Cc:</b> Lesley Wyborn <lesley.wyborn@anu.edu.au>; Mark Parsons <parsonsm.work@icloud.com>; Daniel S. Katz <dskatz@illinois.edu>; Esip-citationguidelines <esip-citationguidelines@lists.esipfed.org><br>
<b>Subject:</b> Re: [Esip-citationguidelines] [EXTERNAL] EOS article for discussion tomorrow<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Rama - a mixture of a flowchart and some images? Do you mean for the entire project or just the narrowing of the original objects from 24 possible to 9 clusters, to 5/6 object types, to the current focus on data?<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Brief timeline from reviewing the meeting notes (which might help scope what should be included). As I was not part of this group from the beginning, I may be oversimplifying or missing some aspects, so grain of salt.... <o:p></o:p></p>
<div>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
ESIP created <a href="https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fdoi.org%2f10.6084%2fm9.figshare.8441816.v1&c=E,1,u9ag-BK7CKLTKdd6HQIsVeC5XwM7eT9P1L7wdp3C3PZjyYuO4vEYhiHYgeYTdLbg9iGHD44nhgnnqXWvfpZZhz36zN7GNogXXFC2AEfKw0ri9bc,&typo=1">
data citation guidelines</a><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
In 2018 this group "recognized a need to update citation guidelines wrt to PIDs and Enabling FAIR project.. CODATA says: Citation = reference for credit and access. BUT, it’s also used for all kinds of other things (impact, provenance, evaluation etc) and is
citation the way to do that?" (<a href="https://docs.google.com/document/d/18ooEixbchKp-qgAG7qtnebKrWDYsutt4d2eX3HsaWls/edit?usp=sharing">meeting notes</a>, page 39)<o:p></o:p></li></ul>
<ul type="disc">
<ul type="circle">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1">
"Central question(s): Can we define general guidelines for citation of all research objects? Do we need to separate credit and access? "<o:p></o:p></li></ul>
</ul>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Did some preliminary work with <a href="https://docs.google.com/document/d/1Rh-M4WV9kqcxGWuYYC6R39cBaKxwoW9F3KS7y_sZpNw/edit?usp=sharing">
scenarios</a> and <a href="https://docs.google.com/spreadsheets/d/1XCo1eVxyLarCjQsn2bkHvNd9zDFC3RLj-6zAZ1Fu6Jg/edit?usp=sharing">
mapping metadata</a> standards (for machines)<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<b>Group really kicked off in 2019 - with plans to develop use case and object matrix (Credit/Different object types)</b><o:p></o:p></li></ul>
<ul type="disc">
<ul type="circle">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1">
<b>Created a matrix with research objects and the roles needed for reproducibility (with at least 24 different objections/concepts)</b><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1">
<b>This was narrowed to 9 clusters of object types</b><o:p></o:p></li></ul>
</ul>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Mark presented a <a href="https://docs.google.com/viewer?url=https://agu.confex.com/agu/fm19/mediafile/Handout/Paper612014/AGU%2520-%2520iPosterSessions.com.pdf">
poster on the topic at AGU</a><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
In 2020, began considerations on CRediT (<a href="https://docs.google.com/document/d/18ooEixbchKp-qgAG7qtnebKrWDYsutt4d2eX3HsaWls/edit?usp=sharing">meeting notes</a>, page 26)<o:p></o:p></li></ul>
<ul type="disc">
<ul type="circle">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1">
"Begin to work through the credit use case — how do the CRedIT, ISO and other attribution descriptions apply to the different research artifacts?"<o:p></o:p></li></ul>
</ul>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
<b>Work begins to narrow to 5/6 object types</b> (Data, Software, Physical Artifacts/Samples, Semantics, and Instruments [instruments sometimes switched with Education Objects])<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Activities/evidence begins to indicate CRediT doesn't work<o:p></o:p></li></ul>
<ul type="disc">
<ul type="circle">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1">
Identifying activities from object types for each CRediT role<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1">
Determining where the role would be cited (citations, acknowledgements, other documentation/metadata)<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level2 lfo1">
Ranking each role as important or not to this community<o:p></o:p></li></ul>
</ul>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Given the amount of work needed, <b>decide to focus on one object type</b> - Data<o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo1">
Inspiration for paper - based on the growing support for CRediT and its lack of fit for our world, what is the next step, where do we want to go next?<o:p></o:p></li></ul>
<div>
<p class="MsoNormal">Thanks!<br>
Sarah<o:p></o:p></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Wed, Feb 16, 2022 at 8:08 AM Hampapuram Ramapriyan via Esip-citationguidelines <<a href="mailto:esip-citationguidelines@lists.esipfed.org" target="_blank">esip-citationguidelines@lists.esipfed.org</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Yes – I would like it to be a flow diagram that shows the process we used to narrow down our considerations to data as the research artifact and authorship as the focus. I can’t
claim artistic proficiency though.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Rama.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b>From:</b> Lesley Wyborn <<a href="mailto:lesley.wyborn@anu.edu.au" target="_blank">lesley.wyborn@anu.edu.au</a>>
<br>
<b>Sent:</b> Tuesday, February 15, 2022 2:50 PM<br>
<b>To:</b> Mark Parsons <<a href="mailto:parsonsm.work@icloud.com" target="_blank">parsonsm.work@icloud.com</a>>; Hampapuram Ramapriyan <<a href="mailto:hampapuram.ramapriya@ssaihq.com" target="_blank">hampapuram.ramapriya@ssaihq.com</a>><br>
<b>Cc:</b> Daniel S. Katz <<a href="mailto:dskatz@illinois.edu" target="_blank">dskatz@illinois.edu</a>>; Esip-citationguidelines <<a href="mailto:esip-citationguidelines@lists.esipfed.org" target="_blank">esip-citationguidelines@lists.esipfed.org</a>><br>
<b>Subject:</b> Re: [Esip-citationguidelines] [EXTERNAL] EOS article for discussion tomorrow<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p style="margin:0in"><span lang="EN-GB">Is this diagram in addition to the “</span><span lang="EN-AU" style="font-family:"Arial",sans-serif;color:black">Provide an eye-catching, landscape-oriented photograph to lead the story.”</span><o:p></o:p></p>
<p style="margin:0in"><span lang="EN-AU" style="font-family:"Arial",sans-serif;color:black"> </span><o:p></o:p></p>
<p style="margin:0in"><span lang="EN-AU" style="font-family:"Arial",sans-serif;color:black">If so, for the eye catching photograph could someone do a mock up that looks like movie credits, e.g.,
</span><o:p></o:p></p>
<p style="margin:0in"><span lang="EN-AU" style="font-family:"Arial",sans-serif;color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU" style="font-family:"Arial",sans-serif;color:black"><<<Image deleted>></span><o:p></o:p></p>
<p style="margin:0in"><span lang="EN-AU"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB">We could replace the image with an image that is used to advertise some database/dataset</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB">BTW – in searching for this image, I found this reference:
<a href="https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fwww.evercast.us%2fblog%2ffilm-credits&c=E,1,qJ_VmEHS-1FHu92X_klR1vL2Ihxe1n3KqDKAKQdfSa5Yrow3fqqeD1chgdBC8YxyzWXPqsu7rvQk_v_8KGWy4ySrQumGsEXelV88m7foH6f4TEV6jvzXuMPF&typo=1" target="_blank">
https://www.evercast.us/blog/film-credits</a> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB">Take care</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB">Lesley</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-GB"> </span><o:p></o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span lang="EN-AU" style="font-size:12.0pt;color:black">From:
</span></b><span lang="EN-AU" style="font-size:12.0pt;color:black">Esip-citationguidelines <<a href="mailto:esip-citationguidelines-bounces@lists.esipfed.org" target="_blank">esip-citationguidelines-bounces@lists.esipfed.org</a>> on behalf of Mark Parsons via
Esip-citationguidelines <<a href="mailto:esip-citationguidelines@lists.esipfed.org" target="_blank">esip-citationguidelines@lists.esipfed.org</a>><br>
<b>Reply to: </b>Mark Parsons <<a href="mailto:parsonsm.work@icloud.com" target="_blank">parsonsm.work@icloud.com</a>><br>
<b>Date: </b>Wednesday, 16 February 2022 at 5:37 am<br>
<b>To: </b>Hampapuram Ramapriyan <<a href="mailto:hampapuram.ramapriya@ssaihq.com" target="_blank">hampapuram.ramapriya@ssaihq.com</a>><br>
<b>Cc: </b>"Daniel S. Katz" <<a href="mailto:dskatz@illinois.edu" target="_blank">dskatz@illinois.edu</a>>, Esip-citationguidelines <<a href="mailto:esip-citationguidelines@lists.esipfed.org" target="_blank">esip-citationguidelines@lists.esipfed.org</a>><br>
<b>Subject: </b>Re: [Esip-citationguidelines] [EXTERNAL] EOS article for discussion tomorrow</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">I’m having a hard time picturing such a diagram, but if someone wants to take a shot….</span><o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">cheers,</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">-m. </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><span lang="EN-AU"> </span><o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">On Feb 15, 2022, at 11:23 AM, Hampapuram Ramapriyan <<a href="mailto:hampapuram.ramapriya@ssaihq.com" target="_blank">hampapuram.ramapriya@ssaihq.com</a>> wrote:</span><o:p></o:p></p>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">I think the paper is looking good as well. I made only a couple of comments. A “big” acknowledgement section seems appropriate.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">One question is whether we should have diagram that shows the culling down process we went through. Reading through the paragraphs makes it sound complicated
and generally gives a negative impression – as if we were almost giving up hope with the problem being too difficult to handle.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">Rama.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span lang="EN-AU">From:</span></b><span lang="EN-AU"> Esip-citationguidelines <<a href="mailto:esip-citationguidelines-bounces@lists.esipfed.org" target="_blank">esip-citationguidelines-bounces@lists.esipfed.org</a>> <b>On
Behalf Of </b>Daniel S. Katz via Esip-citationguidelines<br>
<b>Sent:</b> Tuesday, February 15, 2022 5:48 AM<br>
<b>To:</b> Mark Parsons <<a href="mailto:parsonsm.work@icloud.com" target="_blank">parsonsm.work@icloud.com</a>><br>
<b>Cc:</b> Esip-citationguidelines <<a href="mailto:esip-citationguidelines@lists.esipfed.org" target="_blank">esip-citationguidelines@lists.esipfed.org</a>><br>
<b>Subject:</b> [EXTERNAL] Re: [Esip-citationguidelines] EOS article for discussion tomorrow</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">Hi Mark,</span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">This looks pretty good to me. I've suggested a few edits, and made a few comments.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">Dan</span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><o:p> </o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">On Feb 14, 2022, at 5:18 PM, Mark Parsons via Esip-citationguidelines <<a href="mailto:esip-citationguidelines@lists.esipfed.org" target="_blank">esip-citationguidelines@lists.esipfed.org</a>>
wrote:</span><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">Friends,</span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">The document is in good shape. <a href="https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1qsPuPkc4Hockej1wy9LrlzHfg0p42MwOURdTMVDWZ_c%2Fedit%3Fusp%3Dsharing&data=04%7C01%7Clesley.wyborn%40anu.edu.au%7C10983512aba04512398608d9f0b234f6%7Ce37d725cab5c46249ae5f0533e486437%7C0%7C0%7C637805470474183335%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=%2B9XKZYgQ0B6NnfcHc75QNB3e1gO0NspzZe%2BtzxqoNvQ%3D&reserved=0" target="_blank">https://docs.google.com/document/d/1qsPuPkc4Hockej1wy9LrlzHfg0p42MwOURdTMVDWZ_c/edit?usp=sharing</a></span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">Here’s the latest.</span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<ul type="disc">
<li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo2">
<span lang="EN-AU">Thank you to Dan and Sarah for offering alternative first paragraphs. A couple people liked Sarah’s paragraph so a lightly edited version of that is what is in place now. Others are still welcome to offer an alternative.</span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo2">
<span lang="EN-AU">I cleaned up the discussion of the work we did and tried to introduce it more clearly.</span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo2">
<span lang="EN-AU">I accepted/rejected all the various minor edits. Thanks all.</span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo2">
<span lang="EN-AU">I considered adding something about how the paper is the work of dozens and how this is ironically belied by the five author limit, but we are hitting the word limit, and I couldn’t figure out a way to do it elegantly. (The EOS editors would
probably kill it anyway).</span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo2">
<span lang="EN-AU">Instead I think we need an extensive acknowledgements section. I started to list people involved in all the CRediT roles. Please review. (I hope acknowledgements are not part of the word limit)</span><o:p></o:p></li><li class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l1 level1 lfo2">
<span lang="EN-AU">I asked AGU about including authors who need agency review and we can still do that.</span><o:p></o:p></li></ul>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">cheers,</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">-m. </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">On Feb 10, 2022, at 5:48 PM, Mark Parsons <<a href="mailto:parsonsm.work@icloud.com" target="_blank">parsonsm.work@icloud.com</a>> wrote:</span><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">Hi all,</span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">Thanks for the lively discussion today. Notes at </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"><a href="https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F18ooEixbchKp-qgAG7qtnebKrWDYsutt4d2eX3HsaWls%2Fedit%3Fusp%3Dsharing&data=04%7C01%7Clesley.wyborn%40anu.edu.au%7C10983512aba04512398608d9f0b234f6%7Ce37d725cab5c46249ae5f0533e486437%7C0%7C0%7C637805470474183335%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=ZpmVSahoaXUDUzMdR4jWkvMCG38Ym9bqYfVcQY5pxok%3D&reserved=0" target="_blank">https://docs.google.com/document/d/18ooEixbchKp-qgAG7qtnebKrWDYsutt4d2eX3HsaWls/edit?usp=sharing</a> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">I have cleaned up the current version of the manuscript based on our discussion and my review of some of the smaller editorial changes.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"><a href="https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1qsPuPkc4Hockej1wy9LrlzHfg0p42MwOURdTMVDWZ_c%2Fedit%3Fusp%3Dsharing&data=04%7C01%7Clesley.wyborn%40anu.edu.au%7C10983512aba04512398608d9f0b234f6%7Ce37d725cab5c46249ae5f0533e486437%7C0%7C0%7C637805470474183335%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=%2B9XKZYgQ0B6NnfcHc75QNB3e1gO0NspzZe%2BtzxqoNvQ%3D&reserved=0" target="_blank">https://docs.google.com/document/d/1qsPuPkc4Hockej1wy9LrlzHfg0p42MwOURdTMVDWZ_c/edit?usp=sharing</a></span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">We will meet again next Thursday, 17 Feb. at 14:30 Mountain time to finalize things on our regular Zoom channel. I’ll send an invite</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">Meanwhile, <b>everyone</b> should consider writing a new first paragraph and teaser. Do like Dan did and just insert an alternative paragraph. Don’t edit the
current version.</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">I will also try and introduce and tighten up the paragraphs describing the work we did over the several meetings. I will also add something about the full authorship
and the great irony that we are limited to five. </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">Next meeting we should:</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">1. Finalize the manuscript</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">2. Agree on a title (probably not film credits)</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">3. Finalize authorship — note AGU guidance states: “Authors listed in the byline must be those who <i>actually write</i> the manuscript.” (Their emphasis)</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">cheers,</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">-m. </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><o:p> </o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">On Feb 9, 2022, at 11:14 AM, Mark Parsons <<a href="mailto:parsonsm.work@icloud.com" target="_blank">parsonsm.work@icloud.com</a>> wrote:</span><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">I’m sending this again. It seems we have two mailing lists</span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">cheers,</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">-m. </span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><o:p> </o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">Begin forwarded message:</span><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span lang="EN-AU" style="font-family:"Helvetica",sans-serif">From: </span></b><span lang="EN-AU" style="font-family:"Helvetica",sans-serif">Mark Parsons <<a href="mailto:parsonsm.work@icloud.com" target="_blank">parsonsm.work@icloud.com</a>></span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span lang="EN-AU" style="font-family:"Helvetica",sans-serif">Subject: EOS article for discussion tomorrow</span></b><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span lang="EN-AU" style="font-family:"Helvetica",sans-serif">Date: </span></b><span lang="EN-AU" style="font-family:"Helvetica",sans-serif">February 9, 2022 at 9:31:08 AM MST</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span lang="EN-AU" style="font-family:"Helvetica",sans-serif">To: </span></b><span lang="EN-AU" style="font-family:"Helvetica",sans-serif">ESIP Research Object Citation Cluster
<<a href="mailto:esip-citations@lists.esipfed.org" target="_blank">esip-citations@lists.esipfed.org</a>></span><o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU">Hi all,<br>
<br>
Coming in at the 11th hour, here is a first draft of the EOS article for discussion at our Cluster call tomorrow. Edit at will.<br>
<a href="https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fdocument%2Fd%2F1qsPuPkc4Hockej1wy9LrlzHfg0p42MwOURdTMVDWZ_c%2Fedit%3Fusp%3Dsharing&data=04%7C01%7Clesley.wyborn%40anu.edu.au%7C10983512aba04512398608d9f0b234f6%7Ce37d725cab5c46249ae5f0533e486437%7C0%7C0%7C637805470474183335%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=%2B9XKZYgQ0B6NnfcHc75QNB3e1gO0NspzZe%2BtzxqoNvQ%3D&reserved=0" target="_blank">https://docs.google.com/document/d/1qsPuPkc4Hockej1wy9LrlzHfg0p42MwOURdTMVDWZ_c/edit?usp=sharing</a><br>
<br>
As a reminder I include our original proposal, the reviewer comments, and our response below.<br>
<br>
You may also want to review the EOS article guidelines: <br>
<a href="https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinkprotect.cudasvc.com%2Furl%3Fa%3Dhttps%253a%252f%252feos.org%252fwp-content%252fuploads%252f2021%252f03%252fEos_Author_Guidelines_Nov2020.pdf%26c%3DE%2C1%2C-1pr5k5Ar0-i0gl-bapBFMiXVsBQufIB4z2apmX-CmJh_OzW0-1Cn_N6j-4MLbaEPbSPJ7ciRM8TxvWNdsy86Jm40d9qAiCmYVDE4I80SBq_HiHjCFJsu4s%2C%26typo%3D1&data=04%7C01%7Clesley.wyborn%40anu.edu.au%7C10983512aba04512398608d9f0b234f6%7Ce37d725cab5c46249ae5f0533e486437%7C0%7C0%7C637805470474183335%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=q9%2BvBM1WcJZo0hV54uGtrUemHUHjaKIN5zsx%2Bfh1tg4%3D&reserved=0" target="_blank">https://eos.org/wp-content/uploads/2021/03/Eos_Author_Guidelines_Nov2020.pdf</a><br>
<br>
I look forward to the discussion tomorrow<br>
<br>
cheers,<br>
<br>
-m. <br>
<br>
<br>
<br>
<br>
From: <a href="mailto:eos@agu.org" target="_blank">eos@agu.org</a><br>
To: Web Production<br>
Date: July 15, 2021 at 6:48am<br>
Eos Proposal Review - Mark Parsons<br>
<br>
Dear Dr. Parsons,<br>
We are pleased to accept your proposal for an Eos article on “Film credits for science.”<br>
<br>
Please read the following instructions to ensure your article is produced in an easy and timely manner.<br>
We look forward to working together and publishing your work.<br>
—Eos<br>
<br>
_______________________________<br>
What happens next?<br>
<br>
* Within the next business day, you’ll receive an invitation to Basecamp, our editorial platform.<br>
* Within the next 3 business days, Eos science editor Tim Oleson will contact you through Basecamp with our author guide and specific advice as you begin writing your manuscript.<br>
* Once you submit a completed first draft, your article will enter our editing queue and an editor will return a first round of feedback as soon as possible.<br>
* The editorial staff will work with you until your article is finalized and passed on to the production staff to publish.<br>
* You’ll receive an automated email as soon as your article is published on <a href="https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinkprotect.cudasvc.com%2Furl%3Fa%3Dhttp%253a%252f%252fEos.org%26c%3DE%2C1%2CABNNe0jTcQlCY8nUsKuAxPeydwDGgmAnkYCsdaspcKbgazHI8L6lPkheydQi-0SPldZSHQcqFVz38gUzasH8zkKqKY2Gq2v8rw6F5wWdAU7V28g%2C%26typo%3D1&data=04%7C01%7Clesley.wyborn%40anu.edu.au%7C10983512aba04512398608d9f0b234f6%7Ce37d725cab5c46249ae5f0533e486437%7C0%7C0%7C637805470474183335%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=uX%2BWGycGvz9oyPeSjsxm5Tey38CcNN8POL%2ByRdE3nNQ%3D&reserved=0" target="_blank">Eos.org</a>.<br>
* Your article may be considered for the print version of Eos anytime in the next six months. If it is selected, you’ll be notified at the beginning of the issue production process.<br>
<br>
What should I know before I begin writing my manuscript?<br>
<br>
* Do not begin writing until<br>
* Tim Oleson contacts you on Basecamp and you read his guidance as well as the Author Guide he’ll send you.<br>
* You read the comments below from the Science Adviser, who may have instructions for you.<br>
* You have reviewed articles of the same type on <a href="https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinkprotect.cudasvc.com%2Furl%3Fa%3Dhttp%253a%252f%252fEos.org%26c%3DE%2C1%2C6sUw0EEe9D8KUEMOiDzeakaPPYe1b59lf_w3KcUoBSVDCeEvOwnpjx3JrG0-QqAdriL38QGJ4rHV7HtZUm9V-IFzKj_Kt1Vm0-poKyZDHfCZirZxTYyFLg%2C%2C%26typo%3D1&data=04%7C01%7Clesley.wyborn%40anu.edu.au%7C10983512aba04512398608d9f0b234f6%7Ce37d725cab5c46249ae5f0533e486437%7C0%7C0%7C637805470474183335%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=eIf8TV5Z3Suedcz%2BH4VzPjKBR6WCT6a%2FevBfNHWvzx4%3D&reserved=0" target="_blank">Eos.org</a> and
understand the basic format of these articles.<br>
* Your manuscript, in part or whole, should not have been published previously in print or online, or submitted elsewhere for publication.<br>
* Your editor may request draft revisions and may perform substantive editing.<br>
* Your input on the title will be considered, but the final decision is the responsibility of Eos. This also applies if your article is selected for the print edition of Eos; the editors may adapt the title and teaser for that medium.<br>
* You will get to approve the final version of the article before publication; however, irreconcilable disagreements between the author and Eos editors or Science Advisers can result in non-publication.<br>
* This process ensures that the published article is written appropriately for Eos’s broad audience. We want our audience to engage with and learn from your article, and we want you to enjoy this process with us. Please ask questions at any time!<br>
<br>
How do I use Basecamp?<br>
<br>
* Basecamp is an easy-to-use project management platform. You will have access to a folder created for your article.<br>
* Your Basecamp invitation will come with brief instructions on how to use it.<br>
* Please use Basecamp for all communication going forward.<br>
* Only corresponding authors will be invited to Basecamp.<br>
* If you’re having trouble with Basecamp, please contact our production team at <a href="mailto:eos@agu.org" target="_blank">eos@agu.org</a><<a href="mailto:eos@agu.org" target="_blank">mailto:eos@agu.org</a>>.<br>
<br>
What about coauthors (if applicable)?<br>
<br>
* You, the corresponding author, are the liaison between Eos and your coauthors.<br>
* You are responsible for notifying them of this acceptance and that only you will work in Basecamp.<br>
* You are responsible for making sure all authors listed on the manuscript have agreed to publication of its final accepted form.<br>
* You may add or swap authors after this acceptance, but the total number of authors is limited to 5. No exceptions.<br>
<br>
_______________________________<br>
Reviewer #1 Comments:<br>
The authors propose a brief description about a new initiative to increase the visibility and impact of Earth science data sets and data products. This has been a big issue over the years in seismology and many people do feel that their data products (e.g.,
a catalog of earthquake locations and sizes) are undervalued in the research community. The assignment of doi's to data centers and data sets has alleviated this a little, however at the end of the day the onus falls on journal editors to enforce citation
to relevant data products. I think the battle is being won, but it is progressing very slowly. Anyway, I would be interested in reading a short update on this issue as proposed by the authors. The good news is it would apply to all sections with AGU; the bad
news is that will mainly be interesting to practicing scientists and won't have as big an impact on the broader Eos readership of the Earth science interested public.<br>
<br>
Reviewer #2 Comments:<br>
The idea of implementing alternative structures or means to offer credit and recognize contributions in science is intriguing and, other than one or two articles making a case for improved citation of data sets that we’ve featured, isn’t something we’ve covered
in depth recently. So I generally like this proposal despite, as Keith points out, that it may be of limited interest to non-scientists.<br>
However, I’d suggest going back to the authors to ask for some elaboration on what they are proposing as far as workable alternatives to current approaches for designating authorship, credit, etc., or at least as first steps to begin coming up with alternatives.
(If they’re just pointing out a problem without offering any potential solutions, I don’t think Eos is the right venue.) They say that the “ESIP Citation Cluster advocates a new way to think about the roles and credit for all the people involved in producing
useful scientific artifacts,” but it’s not clear what this new way entails—other than perhaps that it uses the film credit analogy as a starting point. Can they give more information so we know more about what their article would look like?<br>
If they do have alternative approaches or ideas to offer, I also think it’ll be important in a potential article to acknowledge if there are possible drawbacks. For instance, much as film credits can drag on for many minutes (and surely must take a lot of time
and effort to compile in their own right), I can imagine such credit listings (e.g., for a published article) could become quite lengthy and involve significant time to assemble depending on how widely credit is extended.<br>
<br>
Reviewer #2’s Comments on Proposer’s Response to Query<br>
I see now that they're not necessarily advocating specific or one-size-fits-all solutions, but they do plan to summarize the "state of the art for several artifact types" and "discuss roles that should be considered, principles for how they should be evaluated,
and suggestions for what constitutes “authorship” in a data citation," which is the sort of value add in this discussion I was looking for and asking about. Their reply ticks the box for me.<br>
<br>
_______________________________<br>
Production Notes<br>
<br>
Project Name: OP Parsons FilmCredits<br>
Topic: n/a<br>
Index: 1900<br>
_______________________________<br>
<br>
Parsons Mark<br>
Affiliation:<br>
University of Alabama in Huntsville<br>
<br>
email:<br>
<a href="mailto:map0046@uah.edu" target="_blank">map0046@uah.edu</a><<a href="mailto:map0046@uah.edu" target="_blank">mailto:map0046@uah.edu</a>><br>
<br>
Coauthors:<br>
Madison Langseth, USGS<br>
<br>
Content type:<br>
Opinion<br>
<br>
Proposed title:<br>
Film credits for science<br>
<br>
Topic(s):<br>
Informatics, scholarly communication and credit<br>
<br>
Reviewer preference<br>
Kirk Martinez<br>
<br>
Key points:<br>
Credit is the currency of science. This has traditionally been primarily done through citation but also through awards and various other means informal and informal, including the names of geo features, instruments, methods, etc. There is increasing recognition
that roles need to be more-clearly specified (e.g. the Contributor Roles Taxonomy--CRediT) and that research artifacts other than articles also deserve credit (data, code, methods...). It is important to credit people for all kinds of work and products in
science, but that’s difficult. Citation is only one mechanism because there are different roles which need to be credited differently for different artifacts. It can actually get quite complex. The analogy of film credits is often used: Key roles listed at
the beginning of the movie and numerous supporting roles listed at the end. What may not be evident is that the order, prominence, and categories of these roles come from a highly negotiated, complex process involving agents, unions, contracts, etc. Can we
do something similar for science but simpler? The ESIP Citation Cluster advocates a new way to think about the roles and credit for all the people involved in producing useful scientific artifacts. We need a fuller and more formal method for recognizing appropriate
roles in the production of all first-class research objects.<br>
<br>
Article's importance to Eos readers<br>
In the era of open science, people deserve to be credited for all their intellectual contributions. AGU has begun to recognize this with the use of CRediT for journal articles and the growing requirement for data and software citation, but the issue is even
more complex.<br>
<br>
Broader impacts:<br>
Open science requires greater recognition for all contributions not just papers.<br>
<br>
Employer review required?<br>
No<br>
<br>
Proposer’s Response to Query<br>
<br>
Thank you for your feedback.<br>
<br>
In response to the comments from Reviewer 2: Our key finding is that there are multiple roles that need to be credited and they differ by research artifact. Therefore the “opinion” of the piece is that these roles need to be identified and credited. Current
mechanisms do not fully allow this and not all creditable roles are deserving of “authorship” and citation but should still be captured somewhere.<br>
<br>
We have found that different approaches are necessary for different types of research artifacts. For example, we reviewed how CRediT roles might apply to data, software, semantic artifacts, physical samples, and complex learning objects. We found that CReidT
didn’t really work for any of the artifacts, but it didn’t work in different ways. Moreover, different communities are taking different approaches and some are more mature than others. We will summarize what we see as the current state of the art for several
artifact types and discuss data in more detail.<br>
<br>
We don’t have a fully prescribed solution because credit is very contextual thing, but we will discuss roles that should be considered, principles for how they should be evaluated, and suggestions for what constitutes “authorship” in a data citation.<br>
<br>
We will acknowledge that this can add complexity (a potential drawback) but we think it is appropriate because it also aids openness and accountability.<br>
<br>
Our goal is not to promote a particular credit methodology or taxonomy at this point but rather to make a call for reconsidering how we provide credit in science along with some guidelines on how to do so.<br>
<br>
All this in 1500 words :-)<br>
<br>
I hope that clarifies.<br>
<br>
cheers,<br>
<br>
-m.</span><o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"><br>
_______________________________________________<br>
Esip-citationguidelines mailing list<br>
To start a new topic: <a href="mailto:Esip-citationguidelines@lists.esipfed.org" target="_blank">Esip-citationguidelines@lists.esipfed.org</a><br>
To unsubscribe and manage prefs: <a href="https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinkprotect.cudasvc.com%2Furl%3Fa%3Dhttps%253a%252f%252flists.esipfed.org%252fmailman%252flistinfo%252fesip-citationguidelines%26c%3DE%2C1%2C_xs0TfaawllDC640N4U-4phvy2vDOU6_ndO1TnfQTtjaGcz0ct0HmT8LVwOo-7CjHZodHRVHkZ2nJRJm-USZi95yi5e0tpUM29N54f0xbJI20jtnDHs%2C%26typo%3D1&data=04%7C01%7Clesley.wyborn%40anu.edu.au%7C10983512aba04512398608d9f0b234f6%7Ce37d725cab5c46249ae5f0533e486437%7C0%7C0%7C637805470474183335%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=C9VSvyp49dIhduqZjWCQBtObJc4WASmgDd358z7ASwY%3D&reserved=0" target="_blank">https://lists.esipfed.org/mailman/listinfo/esip-citationguidelines</a></span><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU" style="font-family:Courier">-- <br>
Daniel S. Katz<br>
Chief Scientist, NCSA<br>
Research Associate Professor, CS<br>
Research Associate Professor, ECE<br>
Research Associate Professor, iSchool<br>
University of Illinois<br>
(217) 244-8000<br>
<a href="mailto:d.katz@ieee.org" target="_blank">d.katz@ieee.org</a> or <a href="mailto:dskatz@illinois.edu" target="_blank">dskatz@illinois.edu</a><br>
<a href="https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinkprotect.cudasvc.com%2Furl%3Fa%3Dhttps%253a%252f%252fdanielskatz.org%26c%3DE%2C1%2Cr25y4sol_HL_tVrNG1deiwypUeqXue7zsb3qXLCLs2cwtRNRNMU14BEGsJcPIAykj17j2o0sQOP2hLx_8df6ANz5PZVvP6nZsX9xfVUBZMjv6ywIiBR8%26typo%3D1&data=04%7C01%7Clesley.wyborn%40anu.edu.au%7C10983512aba04512398608d9f0b234f6%7Ce37d725cab5c46249ae5f0533e486437%7C0%7C0%7C637805470474183335%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=DafqpOblcnzLqOhm7rM%2BtL95hGQFAM6bTy%2F4twDexME%3D&reserved=0" target="_blank">https://danielskatz.org</a></span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span lang="EN-AU"> </span><o:p></o:p></p>
</div>
</div>
</div>
<p class="MsoNormal"><br>
_______________________________________________<br>
Esip-citationguidelines mailing list<br>
To start a new topic: <a href="mailto:Esip-citationguidelines@lists.esipfed.org" target="_blank">
Esip-citationguidelines@lists.esipfed.org</a><br>
To unsubscribe and manage prefs: <a href="https://linkprotect.cudasvc.com/url?a=https%3a%2f%2flists.esipfed.org%2fmailman%2flistinfo%2fesip-citationguidelines&c=E,1,Uqu0GMU27xK9SRkGMiQ4ZOwpHTRWV7OM625udd1peW1Zr8ufAJiRUW_xNfioGLivngrkVHwq9UXiFHM3kjGauI6BHnsz7SZRZJHfdEzCen9R1xWv1FHNZQfcV2I0&typo=1" target="_blank">
https://lists.esipfed.org/mailman/listinfo/esip-citationguidelines</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Sarah Ramdeen, PhD<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>