Links to Exploration step
Le document en format XML
<record><TEI><teiHeader><fileDesc><titleStmt><title xml:lang="en">Protocols.io: Virtual Communities for Protocol Development and Discussion</title>
<author><name sortKey="Teytelman, Leonid" sort="Teytelman, Leonid" uniqKey="Teytelman L" first="Leonid" last="Teytelman">Leonid Teytelman</name>
<affiliation><nlm:aff id="aff001"><addr-line>protocols.io, Berkeley, California, United States of America</addr-line>
</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Stoliartchouk, Alexei" sort="Stoliartchouk, Alexei" uniqKey="Stoliartchouk A" first="Alexei" last="Stoliartchouk">Alexei Stoliartchouk</name>
<affiliation><nlm:aff id="aff001"><addr-line>protocols.io, Berkeley, California, United States of America</addr-line>
</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Kindler, Lori" sort="Kindler, Lori" uniqKey="Kindler L" first="Lori" last="Kindler">Lori Kindler</name>
<affiliation><nlm:aff id="aff002"><addr-line>Department of Agricultural and Biosystems Engineering, University of Arizona, Tucson, Arizona, United States of America</addr-line>
</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Hurwitz, Bonnie L" sort="Hurwitz, Bonnie L" uniqKey="Hurwitz B" first="Bonnie L." last="Hurwitz">Bonnie L. Hurwitz</name>
<affiliation><nlm:aff id="aff002"><addr-line>Department of Agricultural and Biosystems Engineering, University of Arizona, Tucson, Arizona, United States of America</addr-line>
</nlm:aff>
</affiliation>
</author>
</titleStmt>
<publicationStmt><idno type="wicri:source">PMC</idno>
<idno type="pmid">27547938</idno>
<idno type="pmc">4993360</idno>
<idno type="url">http://www.ncbi.nlm.nih.gov/pmc/articles/PMC4993360</idno>
<idno type="RBID">PMC:4993360</idno>
<idno type="doi">10.1371/journal.pbio.1002538</idno>
<date when="2016">2016</date>
<idno type="wicri:Area/Pmc/Corpus">000268</idno>
</publicationStmt>
<sourceDesc><biblStruct><analytic><title xml:lang="en" level="a" type="main">Protocols.io: Virtual Communities for Protocol Development and Discussion</title>
<author><name sortKey="Teytelman, Leonid" sort="Teytelman, Leonid" uniqKey="Teytelman L" first="Leonid" last="Teytelman">Leonid Teytelman</name>
<affiliation><nlm:aff id="aff001"><addr-line>protocols.io, Berkeley, California, United States of America</addr-line>
</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Stoliartchouk, Alexei" sort="Stoliartchouk, Alexei" uniqKey="Stoliartchouk A" first="Alexei" last="Stoliartchouk">Alexei Stoliartchouk</name>
<affiliation><nlm:aff id="aff001"><addr-line>protocols.io, Berkeley, California, United States of America</addr-line>
</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Kindler, Lori" sort="Kindler, Lori" uniqKey="Kindler L" first="Lori" last="Kindler">Lori Kindler</name>
<affiliation><nlm:aff id="aff002"><addr-line>Department of Agricultural and Biosystems Engineering, University of Arizona, Tucson, Arizona, United States of America</addr-line>
</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Hurwitz, Bonnie L" sort="Hurwitz, Bonnie L" uniqKey="Hurwitz B" first="Bonnie L." last="Hurwitz">Bonnie L. Hurwitz</name>
<affiliation><nlm:aff id="aff002"><addr-line>Department of Agricultural and Biosystems Engineering, University of Arizona, Tucson, Arizona, United States of America</addr-line>
</nlm:aff>
</affiliation>
</author>
</analytic>
<series><title level="j">PLoS Biology</title>
<idno type="ISSN">1544-9173</idno>
<idno type="eISSN">1545-7885</idno>
<imprint><date when="2016">2016</date>
</imprint>
</series>
</biblStruct>
</sourceDesc>
</fileDesc>
<profileDesc><textClass></textClass>
</profileDesc>
</teiHeader>
<front><div type="abstract" xml:lang="en"><p>The detailed know-how to implement research protocols frequently remains restricted to the research group that developed the method or technology. This knowledge often exists at a level that is too detailed for inclusion in the methods section of scientific articles. Consequently, methods are not easily reproduced, leading to a loss of time and effort by other researchers. The challenge is to develop a method-centered collaborative platform to connect with fellow researchers and discover state-of-the-art knowledge. Protocols.io is an open-access platform for detailing, sharing, and discussing molecular and computational protocols that can be useful before, during, and after publication of research results.</p>
</div>
</front>
<back><div1 type="bibliography"><listBibl><biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct><analytic><author><name sortKey="Goff, Sa" uniqKey="Goff S">SA Goff</name>
</author>
<author><name sortKey="Vaughn, M" uniqKey="Vaughn M">M Vaughn</name>
</author>
<author><name sortKey="Mckay, S" uniqKey="Mckay S">S McKay</name>
</author>
<author><name sortKey="Lyons, E" uniqKey="Lyons E">E Lyons</name>
</author>
<author><name sortKey="Stapleton, Ae" uniqKey="Stapleton A">AE Stapleton</name>
</author>
<author><name sortKey="Gessler, D" uniqKey="Gessler D">D Gessler</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Giardine, B" uniqKey="Giardine B">B Giardine</name>
</author>
<author><name sortKey="Riemer, C" uniqKey="Riemer C">C Riemer</name>
</author>
<author><name sortKey="Hardison, Rc" uniqKey="Hardison R">RC Hardison</name>
</author>
<author><name sortKey="Burhans, R" uniqKey="Burhans R">R Burhans</name>
</author>
<author><name sortKey="Elnitski, L" uniqKey="Elnitski L">L Elnitski</name>
</author>
<author><name sortKey="Shah, P" uniqKey="Shah P">P Shah</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Richardson, Cd" uniqKey="Richardson C">CD Richardson</name>
</author>
<author><name sortKey="Ray, Gj" uniqKey="Ray G">GJ Ray</name>
</author>
<author><name sortKey="Dewitt, Ma" uniqKey="Dewitt M">MA DeWitt</name>
</author>
<author><name sortKey="Curie, Gl" uniqKey="Curie G">GL Curie</name>
</author>
<author><name sortKey="Corn, Je" uniqKey="Corn J">JE Corn</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Moreira, S" uniqKey="Moreira S">S Moreira</name>
</author>
<author><name sortKey="Valach, M" uniqKey="Valach M">M Valach</name>
</author>
<author><name sortKey="Aoulad Aissa, M" uniqKey="Aoulad Aissa M">M Aoulad-Aissa</name>
</author>
<author><name sortKey="Otto, C" uniqKey="Otto C">C Otto</name>
</author>
<author><name sortKey="Burger, G" uniqKey="Burger G">G Burger</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
</listBibl>
</div1>
</back>
</TEI>
<pmc article-type="other"><pmc-dir>properties open_access</pmc-dir>
<front><journal-meta><journal-id journal-id-type="nlm-ta">PLoS Biol</journal-id>
<journal-id journal-id-type="iso-abbrev">PLoS Biol</journal-id>
<journal-id journal-id-type="publisher-id">plos</journal-id>
<journal-id journal-id-type="pmc">plosbiol</journal-id>
<journal-title-group><journal-title>PLoS Biology</journal-title>
</journal-title-group>
<issn pub-type="ppub">1544-9173</issn>
<issn pub-type="epub">1545-7885</issn>
<publisher><publisher-name>Public Library of Science</publisher-name>
<publisher-loc>San Francisco, CA USA</publisher-loc>
</publisher>
</journal-meta>
<article-meta><article-id pub-id-type="pmid">27547938</article-id>
<article-id pub-id-type="pmc">4993360</article-id>
<article-id pub-id-type="doi">10.1371/journal.pbio.1002538</article-id>
<article-id pub-id-type="publisher-id">PBIOLOGY-D-16-00843</article-id>
<article-categories><subj-group subj-group-type="heading"><subject>Community Page</subject>
</subj-group>
<subj-group subj-group-type="Discipline-v3"><subject>Biology and Life Sciences</subject>
<subj-group><subject>Ecology</subject>
<subj-group><subject>Community Ecology</subject>
</subj-group>
</subj-group>
</subj-group>
<subj-group subj-group-type="Discipline-v3"><subject>Ecology and Environmental Sciences</subject>
<subj-group><subject>Ecology</subject>
<subj-group><subject>Community Ecology</subject>
</subj-group>
</subj-group>
</subj-group>
<subj-group subj-group-type="Discipline-v3"><subject>People and Places</subject>
<subj-group><subject>Population Groupings</subject>
<subj-group><subject>Professions</subject>
<subj-group><subject>Scientists</subject>
</subj-group>
</subj-group>
</subj-group>
</subj-group>
<subj-group subj-group-type="Discipline-v3"><subject>Research and Analysis Methods</subject>
<subj-group><subject>Research Assessment</subject>
<subj-group><subject>Reproducibility</subject>
</subj-group>
</subj-group>
</subj-group>
<subj-group subj-group-type="Discipline-v3"><subject>Research and Analysis Methods</subject>
<subj-group><subject>Scientific Publishing</subject>
</subj-group>
</subj-group>
<subj-group subj-group-type="Discipline-v3"><subject>Science Policy</subject>
<subj-group><subject>Open Science</subject>
</subj-group>
</subj-group>
<subj-group subj-group-type="Discipline-v3"><subject>Social Sciences</subject>
<subj-group><subject>Economics</subject>
<subj-group><subject>Commerce</subject>
<subj-group><subject>Vendors</subject>
</subj-group>
</subj-group>
</subj-group>
</subj-group>
<subj-group subj-group-type="Discipline-v3"><subject>Research and Analysis Methods</subject>
</subj-group>
<subj-group subj-group-type="Discipline-v3"><subject>Physical Sciences</subject>
<subj-group><subject>Mathematics</subject>
<subj-group><subject>Statistics (Mathematics)</subject>
<subj-group><subject>Statistical Data</subject>
</subj-group>
</subj-group>
</subj-group>
</subj-group>
</article-categories>
<title-group><article-title>Protocols.io: Virtual Communities for Protocol Development and Discussion</article-title>
</title-group>
<contrib-group><contrib contrib-type="author"><contrib-id authenticated="true" contrib-id-type="orcid">http://orcid.org/0000-0001-8573-8351</contrib-id>
<name><surname>Teytelman</surname>
<given-names>Leonid</given-names>
</name>
<xref ref-type="aff" rid="aff001"><sup>1</sup>
</xref>
<xref ref-type="corresp" rid="cor001">*</xref>
</contrib>
<contrib contrib-type="author"><name><surname>Stoliartchouk</surname>
<given-names>Alexei</given-names>
</name>
<xref ref-type="aff" rid="aff001"><sup>1</sup>
</xref>
</contrib>
<contrib contrib-type="author"><name><surname>Kindler</surname>
<given-names>Lori</given-names>
</name>
<xref ref-type="aff" rid="aff002"><sup>2</sup>
</xref>
</contrib>
<contrib contrib-type="author"><name><surname>Hurwitz</surname>
<given-names>Bonnie L.</given-names>
</name>
<xref ref-type="aff" rid="aff002"><sup>2</sup>
</xref>
<xref ref-type="corresp" rid="cor001">*</xref>
</contrib>
</contrib-group>
<aff id="aff001"><label>1</label>
<addr-line>protocols.io, Berkeley, California, United States of America</addr-line>
</aff>
<aff id="aff002"><label>2</label>
<addr-line>Department of Agricultural and Biosystems Engineering, University of Arizona, Tucson, Arizona, United States of America</addr-line>
</aff>
<author-notes><fn fn-type="COI-statement" id="coi001"><p>We have read the journal's policy and have the following conflicts: Leonid Teytelman and Alexei Stoliartchouk are employees of protocols.io and both own equity in the company.</p>
</fn>
<corresp id="cor001">* E-mail: <email>bhurwitz@email.arizona.edu</email>
(BLH); <email>lenny@protocols.io</email>
(LT)</corresp>
</author-notes>
<pub-date pub-type="epub"><day>22</day>
<month>8</month>
<year>2016</year>
</pub-date>
<pub-date pub-type="collection"><month>8</month>
<year>2016</year>
</pub-date>
<pub-date pub-type="pmc-release"><day>22</day>
<month>8</month>
<year>2016</year>
</pub-date>
<pmc-comment> PMC Release delay is 0 months and 0 days and was based on the . </pmc-comment>
<volume>14</volume>
<issue>8</issue>
<elocation-id>e1002538</elocation-id>
<permissions><copyright-statement>© 2016 Teytelman et al</copyright-statement>
<copyright-year>2016</copyright-year>
<copyright-holder>Teytelman et al</copyright-holder>
<license xlink:href="http://creativecommons.org/licenses/by/4.0/"><license-p>This is an open access article distributed under the terms of the <ext-link ext-link-type="uri" xlink:href="http://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution License</ext-link>
, which permits unrestricted use, distribution, and reproduction in any medium, provided the original author and source are credited.</license-p>
</license>
</permissions>
<self-uri content-type="pdf" xlink:href="pbio.1002538.pdf"></self-uri>
<abstract><p>The detailed know-how to implement research protocols frequently remains restricted to the research group that developed the method or technology. This knowledge often exists at a level that is too detailed for inclusion in the methods section of scientific articles. Consequently, methods are not easily reproduced, leading to a loss of time and effort by other researchers. The challenge is to develop a method-centered collaborative platform to connect with fellow researchers and discover state-of-the-art knowledge. Protocols.io is an open-access platform for detailing, sharing, and discussing molecular and computational protocols that can be useful before, during, and after publication of research results.</p>
</abstract>
<abstract abstract-type="toc"><p>This Community Page presents an open-access platform, protocols.io (<ext-link ext-link-type="uri" xlink:href="https://www.protocols.io/">https://www.protocols.io/</ext-link>
), which enables collaborative sharing and discovery of state-of-the-art research methods.</p>
</abstract>
<funding-group><funding-statement>1. Gordon Betty Moore Foundation GBMF4733 <ext-link ext-link-type="uri" xlink:href="https://www.moore.org/grant-detail?grantId=GBMF4733">https://www.moore.org/grant-detail?grantId=GBMF4733</ext-link>
2. The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript.</funding-statement>
</funding-group>
<counts><fig-count count="2"></fig-count>
<table-count count="0"></table-count>
<page-count count="6"></page-count>
</counts>
</article-meta>
</front>
<body><sec id="sec001"><title>Introduction: The Changing Landscape of Science Publishing</title>
<p>The act of publishing research serves to communicate discoveries and results. However, to truly advance knowledge and scientific understanding, scientists are expected to share material, methods, and data so that others may reproduce and build upon the published work. When publishing scientific articles, it is standard practice for authors to deposit DNA and protein sequences into public repositories such as GenBank, EMBL, or DDBJ. Over the past decade, journals have extended these open science practices to include all available associated data, statistical methods, and code. Yet, there is a growing recognition that disparate data provided by individual authors upon request—on their websites or in supplementary information files—is far less desirable than pooling resources in curated databases. Hence, many publishers now guide authors to share supplementary data files via DataDryad, figshare, or similar repositories and make software available in code repositories such as GitHub. The PLOS Data Sharing policy [<xref rid="pbio.1002538.ref001" ref-type="bibr">1</xref>
] is a good example of this paradigm shift. Yet, simply sharing data and code is not enough to allow for scientific reproducibility, resulting in a rising focus on the importance of reporting detailed methods. Journals such as <italic>Nature Protocols</italic>
[<xref rid="pbio.1002538.ref002" ref-type="bibr">2</xref>
], <italic>JOVE</italic>
[<xref rid="pbio.1002538.ref003" ref-type="bibr">3</xref>
], and <italic>MethodsX</italic>
[<xref rid="pbio.1002538.ref004" ref-type="bibr">4</xref>
] have begun to fill this void in the last decade. Moreover, attempts have been made to create central open-access communities where protocols can be crowdsourced, including BioProtocols [<xref rid="pbio.1002538.ref005" ref-type="bibr">5</xref>
], Open Wet Ware [<xref rid="pbio.1002538.ref006" ref-type="bibr">6</xref>
], and Nature Protocol Exchange.</p>
<p>In creating protocols.io, we extended the idea of an open, up-to-date protocol repository, applying lessons learned from previous efforts. Our goal was to create a platform that serves researchers’ reporting of methods, with benefits before, during, and after publication of findings, in the same way GitHub serves software developers. Here, we describe the development of the protocol.io platform as a resource for researchers to share and discover experimental and computational methods.</p>
</sec>
<sec id="sec002"><title>Integration of Protocols.io into the Research Process</title>
<p>Protocols.io can be used at any point in the research cycle, long before the results or methods are ready for public sharing. Every new protocol is private by default to the user who created it. In contrast to a PDF or paper copy, each protocol may be followed step-by-step during experimental lab work. That is, the protocols are “runnable” on the web and on the native iOS and Android apps, in a checklist manner. At run time, the user can note changes to individual steps, as performed at that moment (<xref ref-type="fig" rid="pbio.1002538.g001">Fig 1</xref>
). These features help researchers keep track of the position in the experiment and create a precise electronic record of the experimental detail and changes to the implementation of a protocol. These lab notebook–like records reduce the need for handwritten notes and can be exported in a variety of formats.</p>
<fig id="pbio.1002538.g001" orientation="portrait" position="float"><object-id pub-id-type="doi">10.1371/journal.pbio.1002538.g001</object-id>
<label>Fig 1</label>
<caption><title>Running a protocol in protocols.io using a mobile device.</title>
<p>Users can run protocols in protocols.io and annotate any departures from the existing protocol for later reference in lab notebook–like records.</p>
</caption>
<graphic xlink:href="pbio.1002538.g001"></graphic>
</fig>
<p>Personal protocols can also be shared with individuals and groups for collaborative development. Similarly to Google Docs, sharing permissions can be specified to allow editing or viewing only. Moreover, individual researchers can form groups that can be public or private, helping to organize commonly used methods and facilitate discussion among colleagues and collaborators.</p>
<p>The platform can be used privately or collaboratively during research to facilitate reproducibility by capturing methodological nuances in a given field or for a particular software suite. Specifically, users can add detailed annotations on protocols attached to specific steps, including example datasets, reagents or equipment, links to code repositories, cyberinfrastructure platforms [<xref rid="pbio.1002538.ref007" ref-type="bibr">7</xref>
,<xref rid="pbio.1002538.ref008" ref-type="bibr">8</xref>
], or virtual machines. Moreover, steps in protocols can include images and videos to better communicate the visual intricacies of experimental or computational techniques.</p>
</sec>
<sec id="sec003"><title>Use of Protocols.io during Manuscript Submission</title>
<p>In light of concerns over the reproducibility of published research, the journals <italic>Genetics</italic>
and <italic>GigaScience</italic>
have partnered with protocols.io and are encouraging authors to share detailed methods via protocols.io instead of supplementary files. A private reviewer link is available when submitting work for publication so that reviewers can access protocols associated with the paper without having to create an account on protocols.io.</p>
<p>Early adopters have also begun to include the links to protocols.io in their submissions and publications, independent of formal integration of the platform with journals. The following are examples of recently published papers that cite protocols.io, where DOIs can be reserved via CrossRef prior to formal publication for a journal-friendly citation to protocols.io from a paper’s materials and methods section [<xref rid="pbio.1002538.ref009" ref-type="bibr">9</xref>
,<xref rid="pbio.1002538.ref010" ref-type="bibr">10</xref>
].</p>
</sec>
<sec id="sec004"><title>Postpublication: Keeping the Methods Current</title>
<p>After the publication of a research paper, the underlying protocols are frequently optimized by the authors or other researchers using the methods; mistakes are discovered, steps are modified for new applications, and details are optimized to improve the protocol or to take advantage of a new kit or reagent. However, there is no central infrastructure that enables scientists to share corrections and improvements of methods that have been already published. Protocols.io was created explicitly to address this gap.</p>
<p>Once published, a protocol cannot be edited or removed, but authors can easily create new versions. This preserves the scientific record and ensures that DOI links to protocols.io from publications do not break. At the same time, a “master” version of any protocol can be maintained, and visitors who land on earlier versions can be alerted that an updated version exists [<xref rid="pbio.1002538.ref011" ref-type="bibr">11</xref>
].</p>
<p>While versioning is available strictly for the author, anyone can fork (copy) a public method, modify it, and publish their changes as a new derivative with a clear link to the original. Furthermore, step-level and protocol-level comments enable discussions. The author is automatically notified of all questions and annotations, allowing the author or other researchers to respond publicly. Thus, instead of repeatedly answering the same questions by email, scientists can make their responses public. This functionality allows for an FAQ-like enrichment of the published protocols, with hints, clarifications, and updates accumulating over time (see example [<xref rid="pbio.1002538.ref012" ref-type="bibr">12</xref>
]).</p>
</sec>
<sec id="sec005"><title>Virtual Communities</title>
<p>To enhance virtual collaboration and sharing, groups are not limited to individual labs or companies; broader virtual communities or “super-groups” can be created around a field or topic, such as the VERVE Net group for viral ecologists [<xref rid="pbio.1002538.ref013" ref-type="bibr">13</xref>
,<xref rid="pbio.1002538.ref014" ref-type="bibr">14</xref>
].</p>
<p>Virtual communities are method-centered but have a number of additional features that allow researchers to share up-to-date information, news, jobs, conferences, and events with their virtual communities. Groups can also maintain a shared literature reference library specific to their area of interest and get recommendations of newly published papers in PubMed.</p>
<p>The key mission of this group functionality is to encourage community collaboration and to make it easier for new researchers joining a given field to get help and to discover state of the art methods and key papers. Moreover, authors can highlight collections of protocols associated with a paper they recently published.</p>
</sec>
<sec id="sec006"><title>Protocols.io Is Open Access</title>
<p>Protocols.io is open access—it is both free to read and free to publish. Every protocol can be exported as PDF or json, and public APIs are available [<xref rid="pbio.1002538.ref015" ref-type="bibr">15</xref>
]. All accounts are free, there is no charge for the mobile apps, and all public protocols can be viewed without registration or sign-in.</p>
<p>As a private company in the science communication sphere, protocols.io recognizes the need to ensure digital preservation of the public protocol knowledge. In addition to the export and public APIs mentioned above, protocols.io partners with the Center for Open Science [<xref rid="pbio.1002538.ref016" ref-type="bibr">16</xref>
] to mirror all public content. Protocols.io is also developing archiving with CLOCKSS [<xref rid="pbio.1002538.ref017" ref-type="bibr">17</xref>
], as is common for established research journals.</p>
<p>Protocols.io relies on subscription revenue to its analytics dashboard, allowing vendors and publishers to study in real time the adoption and experimental use of their protocols and reagents. Private information about the users and email addresses are never shared. All data in analytics are anonymized and aggregated; modifications are never shared unless public.</p>
<p>While protocols.io partners with vendors and publishers, the core mission is to serve as a crowdsourced community resource for both academic and industry researchers. The steady growth of the methods on protocols.io is mostly driven by academic scientists around the world, with over 2,000 protocols developed since April 2014, of which 800 are public (<xref ref-type="fig" rid="pbio.1002538.g002">Fig 2</xref>
).</p>
<fig id="pbio.1002538.g002" orientation="portrait" position="float"><object-id pub-id-type="doi">10.1371/journal.pbio.1002538.g002</object-id>
<label>Fig 2</label>
<caption><title>Growth in public and private protocols in protocols.io from April 2014–2016.</title>
</caption>
<graphic xlink:href="pbio.1002538.g002"></graphic>
</fig>
</sec>
</body>
<back><ack><p>We would like to thank Anjuli Manche for feedback on the manuscript.</p>
</ack>
<glossary><title>Abbreviations</title>
<def-list><def-item><term>API</term>
<def><p>Application Program Interface</p>
</def>
</def-item>
<def-item><term>CLOCKSS</term>
<def><p>Controlled Lots of Copies Keep Stuff Safe</p>
</def>
</def-item>
<def-item><term>VERVE Net</term>
<def><p>The Viral Ecology Research and Virtual Exchange Network</p>
</def>
</def-item>
</def-list>
</glossary>
<ref-list><title>References</title>
<ref id="pbio.1002538.ref001"><label>1</label>
<mixed-citation publication-type="other">PLoS ONE. Data availability. <ext-link ext-link-type="uri" xlink:href="http://journals.plos.org/plosone/s/data-availability">http://journals.plos.org/plosone/s/data-availability</ext-link>
. Accessed 23 May 2016.</mixed-citation>
</ref>
<ref id="pbio.1002538.ref002"><label>2</label>
<mixed-citation publication-type="other">Nature Protocols. Journaol Home. <ext-link ext-link-type="uri" xlink:href="http://www.nature.com/nprot/index.html">http://www.nature.com/nprot/index.html</ext-link>
. Accessed 23 May 2016</mixed-citation>
</ref>
<ref id="pbio.1002538.ref003"><label>3</label>
<mixed-citation publication-type="other">JoVE Peer Reviewed Scientific Video Journal—Methods and Protocols. Journal Home. <ext-link ext-link-type="uri" xlink:href="http://www.jove.com">http://www.jove.com</ext-link>
. Accessed 23 May 2016.</mixed-citation>
</ref>
<ref id="pbio.1002538.ref004"><label>4</label>
<mixed-citation publication-type="other">MethodsX. Journal Home. <ext-link ext-link-type="uri" xlink:href="http://www.sciencedirect.com/science/journal/22150161">http://www.sciencedirect.com/science/journal/22150161</ext-link>
. Accessed 23 May 2016.</mixed-citation>
</ref>
<ref id="pbio.1002538.ref005"><label>5</label>
<mixed-citation publication-type="other">BioProtocol. A Web-Based Collection of Protocols, Is Launched. <ext-link ext-link-type="uri" xlink:href="http://www.bioprocessonline.com/doc/bioprotocol-a-web-based-collection-of-protoco-0001">http://www.bioprocessonline.com/doc/bioprotocol-a-web-based-collection-of-protoco-0001</ext-link>
. Accessed 23 May 2016.</mixed-citation>
</ref>
<ref id="pbio.1002538.ref006"><label>6</label>
<mixed-citation publication-type="other">OpenWetWare. Main Page. <ext-link ext-link-type="uri" xlink:href="http://openwetware.org/wiki/Main_Page">http://openwetware.org/wiki/Main_Page</ext-link>
. Accessed 23 May 2016.</mixed-citation>
</ref>
<ref id="pbio.1002538.ref007"><label>7</label>
<mixed-citation publication-type="journal"><name><surname>Goff</surname>
<given-names>SA</given-names>
</name>
, <name><surname>Vaughn</surname>
<given-names>M</given-names>
</name>
, <name><surname>McKay</surname>
<given-names>S</given-names>
</name>
, <name><surname>Lyons</surname>
<given-names>E</given-names>
</name>
, <name><surname>Stapleton</surname>
<given-names>AE</given-names>
</name>
, <name><surname>Gessler</surname>
<given-names>D</given-names>
</name>
, <etal>et al</etal>
<article-title>The iPlant Collaborative: Cyberinfrastructure for Plant Biology</article-title>
. <source>Front Plant Sci</source>
. <year>2011</year>
;<volume>2</volume>
: <fpage>34</fpage>
<comment>doi: <ext-link ext-link-type="uri" xlink:href="http://dx.doi.org/10.3389/fpls.2011.00034">10.3389/fpls.2011.00034</ext-link>
</comment>
<pub-id pub-id-type="pmid">22645531</pub-id>
</mixed-citation>
</ref>
<ref id="pbio.1002538.ref008"><label>8</label>
<mixed-citation publication-type="journal"><name><surname>Giardine</surname>
<given-names>B</given-names>
</name>
, <name><surname>Riemer</surname>
<given-names>C</given-names>
</name>
, <name><surname>Hardison</surname>
<given-names>RC</given-names>
</name>
, <name><surname>Burhans</surname>
<given-names>R</given-names>
</name>
, <name><surname>Elnitski</surname>
<given-names>L</given-names>
</name>
, <name><surname>Shah</surname>
<given-names>P</given-names>
</name>
, <etal>et al</etal>
<article-title>Galaxy: a platform for interactive large-scale genome analysis</article-title>
. <source>Genome Res</source>
. <year>2005</year>
;<volume>15</volume>
: <fpage>1451</fpage>
<pub-id pub-id-type="pmid">16169926</pub-id>
</mixed-citation>
</ref>
<ref id="pbio.1002538.ref009"><label>9</label>
<mixed-citation publication-type="journal"><name><surname>Richardson</surname>
<given-names>CD</given-names>
</name>
, <name><surname>Ray</surname>
<given-names>GJ</given-names>
</name>
, <name><surname>DeWitt</surname>
<given-names>MA</given-names>
</name>
, <name><surname>Curie</surname>
<given-names>GL</given-names>
</name>
, <name><surname>Corn</surname>
<given-names>JE</given-names>
</name>
. <article-title>Enhancing homology-directed genome editing by catalytically active and inactive CRISPR-Cas9 using asymmetric donor DNA</article-title>
. <source>Nat Biotechnol</source>
. <ext-link ext-link-type="uri" xlink:href="http://nature.com">nature.com</ext-link>
; <year>2016</year>
;<volume>34</volume>
: <fpage>339</fpage>
–<lpage>344</lpage>
. <comment>doi: <ext-link ext-link-type="uri" xlink:href="http://dx.doi.org/10.1038/nbt.3481">10.1038/nbt.3481</ext-link>
</comment>
<pub-id pub-id-type="pmid">26789497</pub-id>
</mixed-citation>
</ref>
<ref id="pbio.1002538.ref010"><label>10</label>
<mixed-citation publication-type="journal"><name><surname>Moreira</surname>
<given-names>S</given-names>
</name>
, <name><surname>Valach</surname>
<given-names>M</given-names>
</name>
, <name><surname>Aoulad-Aissa</surname>
<given-names>M</given-names>
</name>
, <name><surname>Otto</surname>
<given-names>C</given-names>
</name>
, <name><surname>Burger</surname>
<given-names>G</given-names>
</name>
. <article-title>Novel modes of RNA editing in mitochondria</article-title>
. <source>Nucleic Acids Res</source>
. Oxford Univ Press; <year>2016</year>
;<volume>44</volume>
(<issue>10</issue>
):<fpage>4907</fpage>
–<lpage>19</lpage>
. <comment>doi: <ext-link ext-link-type="uri" xlink:href="http://dx.doi.org/10.1093/nar/gkw188">10.1093/nar/gkw188</ext-link>
</comment>
<pub-id pub-id-type="pmid">27001515</pub-id>
</mixed-citation>
</ref>
<ref id="pbio.1002538.ref011"><label>11</label>
<mixed-citation publication-type="other">Schwessinger, Benjamin. High quality DNA from Fungi for long read sequencing e.g. PacBio. <ext-link ext-link-type="uri" xlink:href="https://www.protocols.io/view/High-quality-DNA-from-Fungi-for-long-read-sequenci-evube6w?comments">https://www.protocols.io/view/High-quality-DNA-from-Fungi-for-long-read-sequenci-evube6w?comments</ext-link>
. Accessed 23 May 2016.</mixed-citation>
</ref>
<ref id="pbio.1002538.ref012"><label>12</label>
<mixed-citation publication-type="other">Albert, Ardiana. Low input Library Preparation for Illumina Sequencing protocol by VERVE Team on protocols.io. <ext-link ext-link-type="uri" xlink:href="https://www.protocols.io/view/Low-input-Library-Preparation-for-Illumina-Sequenc-ddq25v?comments">https://www.protocols.io/view/Low-input-Library-Preparation-for-Illumina-Sequenc-ddq25v?comments</ext-link>
. Accessed 23 May 2016.</mixed-citation>
</ref>
<ref id="pbio.1002538.ref013"><label>13</label>
<mixed-citation publication-type="other">Kindler LJ, Stoliartchouk A, Gomez C, Thornton J, Teytelman L, Hurwitz BL. VERVENet: the viral ecology research and virtual exchange network. Preprint. PeerJ Preprints; 2016 Mar. Report No.: e1901v1. <comment>doi: <ext-link ext-link-type="uri" xlink:href="http://dx.doi.org/10.7287/peerj.preprints.1901v1">10.7287/peerj.preprints.1901v1</ext-link>
</comment>
</mixed-citation>
</ref>
<ref id="pbio.1002538.ref014"><label>14</label>
<mixed-citation publication-type="other">VERVE Net. Viral ecology research and virtual exchange group on protocols.io. <ext-link ext-link-type="uri" xlink:href="https://www.protocols.io/groups/verve-net">https://www.protocols.io/groups/verve-net</ext-link>
. Accessed 23 May 2016</mixed-citation>
</ref>
<ref id="pbio.1002538.ref015"><label>15</label>
<mixed-citation publication-type="other">Protocols.io. Protocols.io for developers. <ext-link ext-link-type="uri" xlink:href="https://www.protocols.io/developers">https://www.protocols.io/developers</ext-link>
. Accessed 14 June 2016.</mixed-citation>
</ref>
<ref id="pbio.1002538.ref016"><label>16</label>
<mixed-citation publication-type="other">Center for Open Science. Center for Open Science and Protocols.io announce collaboration. <ext-link ext-link-type="uri" xlink:href="https://cos.io/pr/2015-12-03">https://cos.io/pr/2015-12-03</ext-link>
. Accessed 14 June 2016.</mixed-citation>
</ref>
<ref id="pbio.1002538.ref017"><label>17</label>
<mixed-citation publication-type="other">CLOCKSS. Home Page. <ext-link ext-link-type="uri" xlink:href="https://www.clockss.org/clockss/Home">https://www.clockss.org/clockss/Home</ext-link>
. Accessed 14 June 2016.</mixed-citation>
</ref>
</ref-list>
</back>
</pmc>
</record>
Pour manipuler ce document sous Unix (Dilib)
EXPLOR_STEP=$WICRI_ROOT/Ticri/CIDE/explor/CyberinfraV1/Data/Pmc/Corpus
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 000268 | SxmlIndent | more
Ou
HfdSelect -h $EXPLOR_AREA/Data/Pmc/Corpus/biblio.hfd -nk 000268 | SxmlIndent | more
Pour mettre un lien sur cette page dans le réseau Wicri
{{Explor lien |wiki= Ticri/CIDE |area= CyberinfraV1 |flux= Pmc |étape= Corpus |type= RBID |clé= |texte= }}
![]() | This area was generated with Dilib version V0.6.25. | ![]() |