March 19, 2021 Working paper Open Access

Richard J. Cordes; Daniel Ari Friedman

MARC21 XML Export

<?xml version='1.0' encoding='UTF-8'?>
<record xmlns="http://www.loc.gov/MARC21/slim">
  <leader>00000nam##2200000uu#4500</leader>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Remote Teams</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Collaborative Writing</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Catechisms</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">OPORDs</subfield>
  </datafield>
  <controlfield tag="005">20210601180707.0</controlfield>
  <controlfield tag="001">4633921</controlfield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">University of California, Davis, Department of Entomology</subfield>
    <subfield code="0">(orcid)0000-0001-6232-9096</subfield>
    <subfield code="a">Daniel Ari Friedman</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">152916</subfield>
    <subfield code="z">md5:8e822e88b3930303e444c352aefddbed</subfield>
    <subfield code="u">https://zenodo.org/record/4633921/files/C3PO.pdf</subfield>
  </datafield>
  <datafield tag="542" ind1=" " ind2=" ">
    <subfield code="l">open</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2021-03-19</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="p">openaire</subfield>
    <subfield code="o">oai:zenodo.org:4633921</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="u">COGSEC</subfield>
    <subfield code="0">(orcid)0000-0002-9913-7159</subfield>
    <subfield code="a">Richard J. Cordes</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Collaborative Writing for Catechism-Based Teams</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="u">https://creativecommons.org/licenses/by/4.0/legalcode</subfield>
    <subfield code="a">Creative Commons Attribution 4.0 International</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="7">
    <subfield code="a">cc-by</subfield>
    <subfield code="2">opendefinition.org</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">&lt;p&gt;Asynchronous and remote collaborative written projects (research, field guides, code, etc.) in emergent, interdisciplinary teams can be an incredibly productive and enjoyable pursuit. The convergence of diverse perspectives, personalities, and expertise in the rapid production of written deliverables can provide immense value and insight, not just to the situation, problem, or opportunity space the team was formed to address, but also to the disciplines each author brought to the table. Yet, asynchronous and remote collaborative writing can also be rather perilous. Managing deadlines, handling disputes, communicating, staying on mission, managing resources, collective editing (and over-editing), and avoiding contradiction are only some of the challenges. While the presence of a catechism-styled operations order&amp;nbsp;and the use of a team &amp;ldquo;Facilitator&amp;rdquo; can greatly improve the likelihood of success, making sure all of the authors have an alignment on protocol and etiquette while writing as a catechism-based team prevents unnecessary misunderstandings and keeps things on schedule.&lt;br&gt;
&lt;br&gt;
This &amp;quot;3-Paragraph Order&amp;quot; for Collaborative Writing, or C-3PO,&amp;nbsp;is meant to rapidly onboard authors to collaborative writing procedures and etiquette.&amp;nbsp;&lt;/p&gt;</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="n">doi</subfield>
    <subfield code="i">isVersionOf</subfield>
    <subfield code="a">10.5281/zenodo.4624298</subfield>
  </datafield>
  <datafield tag="024" ind1=" " ind2=" ">
    <subfield code="a">10.5281/zenodo.4633921</subfield>
    <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">publication</subfield>
    <subfield code="b">workingpaper</subfield>
  </datafield>
</record>