<?xml version="1.0"?>
<rss version="2.0">
   <channel>
      <title>Credit Everybody! Credit Early! Credit Everything! by Suzy S</title>
      <link>https://padlet.com/suzystyles/credit_eee</link>
      <description>BLIP Lab&#39;s approach to acknowledging inputs using a credits table</description>
      <language>en-us</language>
      <pubDate>2022-09-19 00:18:21 UTC</pubDate>
      <lastBuildDate>2026-01-20 09:54:17 UTC</lastBuildDate>
      <webMaster>hello@padlet.com</webMaster>
      <image>
         <url>https://padlet.net/icons/png/1f527.png</url>
      </image>
      <item>
         <title></title>
         <author>suzystyles</author>
         <link>https://padlet.com/suzystyles/credit_eee/wish/2302007180</link>
         <description><![CDATA[<div>In the example shown here, we can see many team members have contributed to multiple categories.<br><br>An additional advantage of the table is that some contributions can be designated as authorship-contributions (here, marked in blue), and meaning that the authorship list is directly linked to individual contributions in&nbsp; a transparent manner.<br><br>Example from: Styles, Suzy J; binte Amran, Shaza; Ang, Xin Wen; Mohd Salleh, Nur Sakinah; Woon, Fei Ting; Yogarrajah, Eshwaaree C, 2021, "SESAME Topic Prompts", <a href="https://doi.org/10.21979/N9/07GFI2">https://doi.org/10.21979/N9/07GFI2</a>, DR-NTU (Data), V1</div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/905682315/ae0274640c9cc8b838ebd2d86c2475b9/image.png" />
         <pubDate>2022-09-19 00:21:42 UTC</pubDate>
         <guid>https://padlet.com/suzystyles/credit_eee/wish/2302007180</guid>
      </item>
      <item>
         <title>BLIP Lab&#39;s team science</title>
         <author>suzystyles</author>
         <link>https://padlet.com/suzystyles/credit_eee/wish/2302028410</link>
         <description><![CDATA[<div>With the support of a <strong>Science of Learning Grant</strong> from Singapore's National Research Foundation, BLIP Lab's team grew rapidly from 2017-2018, with team members with specialist skills working on different branches of the research design and implementation. Large-group collaborations were crucial for our iterative design process.&nbsp;</div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/905682315/541e242b04f8d705034c118cab1ad861/image.png" />
         <pubDate>2022-09-19 00:37:02 UTC</pubDate>
         <guid>https://padlet.com/suzystyles/credit_eee/wish/2302028410</guid>
      </item>
      <item>
         <title>Keeping track of contributions in research</title>
         <author>suzystyles</author>
         <link>https://padlet.com/suzystyles/credit_eee/wish/2302030581</link>
         <description><![CDATA[<div>In team-based science, individuals bring different skills and experiences to the research process, and their contributions to <strong>research outputs</strong> can be varied.&nbsp;<br><br>Tracking the contributions of different team members is important for transparency in the scientific record, and for supporting the career development of team members at all levels.&nbsp;<br><br>This is particularly important for junior team members, whose labor might not qualify for authorship, but whose labor contributed to the research output.&nbsp;</div>]]></description>
         <enclosure url="" />
         <pubDate>2022-09-19 00:38:51 UTC</pubDate>
         <guid>https://padlet.com/suzystyles/credit_eee/wish/2302030581</guid>
      </item>
      <item>
         <title>BLIP Lab&#39;s iterative design process</title>
         <author>suzystyles</author>
         <link>https://padlet.com/suzystyles/credit_eee/wish/2302043766</link>
         <description><![CDATA[<div>To carry out our research on the emergence of multilingualism in Singapore's youngest children, our research design process involves several stages of consultation with our multilingual team members, followed by community consultation, and revision. <br><br>You can find out more about the approach in this video:<br><a href="https://youtu.be/omEIxf5Ebx8">&nbsp;https://youtu.be/omEIxf5Ebx8&nbsp;</a></div>]]></description>
         <enclosure url="https://youtu.be/omEIxf5Ebx8" />
         <pubDate>2022-09-19 00:49:16 UTC</pubDate>
         <guid>https://padlet.com/suzystyles/credit_eee/wish/2302043766</guid>
      </item>
      <item>
         <title>Credit Everybody</title>
         <author>suzystyles</author>
         <link>https://padlet.com/suzystyles/credit_eee/wish/2302057020</link>
         <description><![CDATA[<div>Given the wide range of inputs, and the long timescale for some research deliverables, BLIP Lab's approach is to document all contributions (however small), to ensure that nobody's labour is forgotten.</div><div><br></div><ul><li>Contributions by full-time lab members are documented by their line manager, and checked by at least one other senior team member, and the team member themself.</li></ul><div><br></div><ul><li>Contributions by student lab-members are documented by supervising faculty, or senior lab members leading undergraduate research teams.</li></ul><div><br></div><ul><li>Community consultants are asked by their lab-contact if they would like to be acknowledged by name, or thanked anonymously. This is an important check, as some of our community consultants are only willing to consult confidentially.</li></ul><div><br></div><ul><li>The PI has final signoff on contributions.</li></ul>]]></description>
         <enclosure url="" />
         <pubDate>2022-09-19 01:01:07 UTC</pubDate>
         <guid>https://padlet.com/suzystyles/credit_eee/wish/2302057020</guid>
      </item>
      <item>
         <title>Option 1: Credits list</title>
         <author>suzystyles</author>
         <link>https://padlet.com/suzystyles/credit_eee/wish/2302061882</link>
         <description><![CDATA[<div>One approach to documenting contributions is a credits list, with each <strong>specific role </strong>identified on a separate row, followed by a list of contributors.&nbsp;<br><br>This strategy is similar to the credits listings for artistic productions like films, stage plays, or art shows.</div>]]></description>
         <enclosure url="" />
         <pubDate>2022-09-19 01:05:02 UTC</pubDate>
         <guid>https://padlet.com/suzystyles/credit_eee/wish/2302061882</guid>
      </item>
      <item>
         <title></title>
         <author>suzystyles</author>
         <link>https://padlet.com/suzystyles/credit_eee/wish/2302063427</link>
         <description><![CDATA[<div>In the example above, you can see that many of the names are repeated multiple times in different roles, making the format somewhat inefficient.<br><br>Example from: Styles, Suzy J, 2021, "Talk Together - A four week programme of tips to enhance parent-child interactions", <a href="https://doi.org/10.21979/N9/W1D24L">https://doi.org/10.21979/N9/W1D24L</a>, DR-NTU (Data), V1&nbsp;</div>]]></description>
         <enclosure url="https://padlet-uploads.storage.googleapis.com/905682315/dab1ebf4f0d30dcab566c08e512d5c28/image.png" />
         <pubDate>2022-09-19 01:06:19 UTC</pubDate>
         <guid>https://padlet.com/suzystyles/credit_eee/wish/2302063427</guid>
      </item>
      <item>
         <title>Option 2: Credits Table</title>
         <author>suzystyles</author>
         <link>https://padlet.com/suzystyles/credit_eee/wish/2302081706</link>
         <description><![CDATA[<div>Since roles and contributors can overlap in a complex production, arranging the items in a table can be an efficient way to visualize and understand different individual contributions.<br><br>A table can be built up gradually over time, as new tasks emerge (additional columns), and new team members join (additional rows). A simple dot or letter can be used to mark out which categories an individual has contributed to.<br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2022-09-19 01:19:09 UTC</pubDate>
         <guid>https://padlet.com/suzystyles/credit_eee/wish/2302081706</guid>
      </item>
      <item>
         <title>Credit Early</title>
         <author>suzystyles</author>
         <link>https://padlet.com/suzystyles/credit_eee/wish/2302099679</link>
         <description><![CDATA[<div>In some fields of research it is common to curate author/contributor lists only at the very end of a project, when the final journal articles are written. In some cases, this means that team members who created tools or protocols at the start of the research process are no longer members of the team. In some authorship frameworks, people who did not contribute to the journal article itself are not considered authors of the journal article. This means some contributors are left out. <br><br>As junior researchers have more precarious employment, this can create a <em>structural bias against junior researchers</em> whose contributions may have been critical during the development of the project, but whose labour is subsequently forgotten.<br><br>Documenting credits from the very beginning of a project creates a more transparent record that is not limited by the constraints of which contributions are authorship-worthy for a journal article.</div>]]></description>
         <enclosure url="" />
         <pubDate>2022-09-19 01:31:27 UTC</pubDate>
         <guid>https://padlet.com/suzystyles/credit_eee/wish/2302099679</guid>
      </item>
      <item>
         <title></title>
         <author>suzystyles</author>
         <link>https://padlet.com/suzystyles/credit_eee/wish/2302105588</link>
         <description><![CDATA[<div><strong>Hint.</strong> Be kind to your future-self. By documenting early, you won't have to struggle to remember who did what on different stages of a research project! </div>]]></description>
         <enclosure url="" />
         <pubDate>2022-09-19 01:36:16 UTC</pubDate>
         <guid>https://padlet.com/suzystyles/credit_eee/wish/2302105588</guid>
      </item>
      <item>
         <title></title>
         <author>suzystyles</author>
         <link>https://padlet.com/suzystyles/credit_eee/wish/2302107773</link>
         <description><![CDATA[<div><strong>Hint.</strong> Documenting everybody gives you a great chance to let your junior lab members know that you value their work. Your juniors can also see how they could work towards greater recognition on the project. This provides transparent pathways to authorship.</div>]]></description>
         <enclosure url="" />
         <pubDate>2022-09-19 01:38:05 UTC</pubDate>
         <guid>https://padlet.com/suzystyles/credit_eee/wish/2302107773</guid>
      </item>
      <item>
         <title></title>
         <author>suzystyles</author>
         <link>https://padlet.com/suzystyles/credit_eee/wish/2302111201</link>
         <description><![CDATA[<div><strong>Hint. </strong>You don't have to wait for journal articles to get your documentation -- and your credits -- in shape. You can archive research tools, translations, protocols, processing pipelines and code. All of these elements are research outputs that will be useful for your future journal articles, as you can link them straight in when it is time.</div>]]></description>
         <enclosure url="" />
         <pubDate>2022-09-19 01:40:53 UTC</pubDate>
         <guid>https://padlet.com/suzystyles/credit_eee/wish/2302111201</guid>
      </item>
      <item>
         <title>Credit Everything!</title>
         <author>suzystyles</author>
         <link>https://padlet.com/suzystyles/credit_eee/wish/2302126152</link>
         <description><![CDATA[<div>Different projects require different kinds of contributions. Although there are several models available for what is authorship-worthy in a journal article, you can use a flexible approach to crediting within your own team.&nbsp;<br><br></div><ul><li>In some elements of our research on multilingualism, working in multiple languages is an important part of our research design, and translation can sometimes result in wholesale redesign across multiple languages. In other contexts we create a source text in English, and translate into other languages without substantial adaptation. In the first context, <strong><em>authorship</em></strong> is appropriate, while in the second <strong><em>credit</em></strong> is appropriate, but additional contributions would be required to qualify for authorship.&nbsp;</li></ul><div><br>You can take a flexible approach to crediting what is important for different projects. Even small contributions can be credited, and you can create your own credit categories.</div>]]></description>
         <enclosure url="" />
         <pubDate>2022-09-19 01:50:51 UTC</pubDate>
         <guid>https://padlet.com/suzystyles/credit_eee/wish/2302126152</guid>
      </item>
      <item>
         <title>How does this approach differ from others?</title>
         <author>suzystyles</author>
         <link>https://padlet.com/suzystyles/credit_eee/wish/2302135295</link>
         <description><![CDATA[<div>This approach is grounded in the same logic as traditional&nbsp;models of authorship + acknowledgement, with the reminder to <strong>credit everybody</strong>, <strong>credit early</strong>, and <strong>credit everything</strong>, and provides the flexible <strong>credits table</strong> as a model for how to achieve this.<br><br>• The <strong>credits table</strong> is maximally flexible, and can be adapted to suit different research projects, teams and deliverables.<br><br>• My marking out which contributions (which columns) are <strong>authorship-worthy</strong>, authorship decisions are transparent, and team members have a clear understanding of pathways to authorship.<br><br>This approach is consistent with the key principles of the <a href="https://credit.niso.org/">Contributor Roles Taxonomy (CRediT)</a>, but has the flexibility for individual teams and projects to specify their own categories for credits across a wider range of outputs.&nbsp;</div>]]></description>
         <enclosure url="" />
         <pubDate>2022-09-19 01:58:28 UTC</pubDate>
         <guid>https://padlet.com/suzystyles/credit_eee/wish/2302135295</guid>
      </item>
      <item>
         <title>How to credit everybody, early for everything</title>
         <author>suzystyles</author>
         <link>https://padlet.com/suzystyles/credit_eee/wish/2302155868</link>
         <description><![CDATA[<div>Below are two options we have used in the BLIP Lab, a Credits List, and a Credits Table. Having tried both methods, we now prefer the Credit's Table for its efficiency and transparency. </div>]]></description>
         <enclosure url="" />
         <pubDate>2022-09-19 02:14:03 UTC</pubDate>
         <guid>https://padlet.com/suzystyles/credit_eee/wish/2302155868</guid>
      </item>
      <item>
         <title></title>
         <author>suzystyles</author>
         <link>https://padlet.com/suzystyles/credit_eee/wish/2302159232</link>
         <description><![CDATA[<div>Iterative design takes time, and team membership can change between project inception and journal article writeup. Transparency in acknowledging contributions to research is achievable if you credit everybody, credit early, and credit everything.</div>]]></description>
         <enclosure url="" />
         <pubDate>2022-09-19 02:16:27 UTC</pubDate>
         <guid>https://padlet.com/suzystyles/credit_eee/wish/2302159232</guid>
      </item>
      <item>
         <title></title>
         <author>suzystyles</author>
         <link>https://padlet.com/suzystyles/credit_eee/wish/2302166042</link>
         <description><![CDATA[<div>We have found the credits table to be easier to use, and more transparent than a credits list or a typical acknowledgements narrative paragraph. The array of dots gives a visual overview of the project and the number of different contributions by different individuals. The marking of authorship-worthy contributions provides added transparency about which tasks resulted in authorship for a particular project deliverable.</div>]]></description>
         <enclosure url="" />
         <pubDate>2022-09-19 02:21:08 UTC</pubDate>
         <guid>https://padlet.com/suzystyles/credit_eee/wish/2302166042</guid>
      </item>
      <item>
         <title></title>
         <author>suzystyles</author>
         <link>https://padlet.com/suzystyles/credit_eee/wish/2302216301</link>
         <description><![CDATA[<div>Web Content by <a href="https://orcid.org/0000-0003-3517-9680">Suzy J Styles</a>&nbsp;<br>Sept 2022</div>]]></description>
         <enclosure url="" />
         <pubDate>2022-09-19 02:57:53 UTC</pubDate>
         <guid>https://padlet.com/suzystyles/credit_eee/wish/2302216301</guid>
      </item>
   </channel>
</rss>
