Deploying to gh-pages from @ b86dc40 🚀

7-data-management.html

@@ -571,6 +571,10 @@ <h3><span class="header-section-number">7.1.1</span> Expectations by project pha
 <li>Check that data storage locations and methods are well described and linked </li>
 <li>Check that necessary stakeholders are identified </li>
 <li>Check that appropriate privacy and security measures are working as expected </li>
+<li>Add any publications or research outputs are to DMP outputs
+<ul>
+<li>DOI’s can be assigned to code, datasets, and published articles</li>
+</ul></li>
 <li>Check that your data products and code meet the needs of your proposed long term storage solution</li>
 <li><a href="https://calendar.google.com/calendar/appointments/schedules/AcZssZ3GOwk4nzuezs8t_Ua1IxLW8aXHhyo4_tv1-mIv9nmT4rDkEaQuV7HbwqXervbMiX1ijDN65UZ-">Schedule a meeting</a> with the <a href="https://www.ecohealthalliance.org/personnel/collin-schwantes">Data Librarian</a></li>
 </ul>

8-airtable.html

@@ -487,8 +487,8 @@ <h2><span class="header-section-number">8.3</span> When should I use Airtable?<a
 Airtable shines when you have multiple data entities that are linked via common data elements. For example, if you are sampling bats then conducting antibody screening, running multiplex PCR, and keeping physical samples of blood and urine from those bats, you have multiple data entities (bats, antibody test results, PCR test results, and physical samples) that are all linked via common data elements like site and collector.
 What is more, the test results depend on the physical samples and the physical samples depend on the bats. Those common data elements only need to be entered into a single entity (or table) then shared across the other entities in your base using linked elements. Once you have linked elements you no longer have to worry about updating the same piece of information in multiple locations and you can quickly navigate between entities and understand hierarchical relationships.</p>
 <div class="figure"><span style="display:block;" id="fig:bat-data"></span>
-<div id="htmlwidget-e1726c6e37719214bd24" style="width:672px;height:200px;" class="grViz html-widget "></div>
-<script type="application/json" data-for="htmlwidget-e1726c6e37719214bd24">{"x":{"diagram":"\ndigraph bat_sampling {\n\n  # a \"graph\" statement\n  graph [overlap = true, nodesep = .5, ranksep = .25, compound = true, color = MediumAquamarine, fontsize = 10, rankdir = LR]\n\n  # \"node\" styling\n  node [shape = circle,\n        fixedsize = true,\n        width = 1,\n        fontname = Helvetica,\n        style = filled,\n        fillcolor = MediumAquamarine]\n        \n  a [label = \"Collector\"]\n  b [label = \"Site\"]\n  c [label = \"Bat\"]\n  d [label = \"Antibody\ntest result\"]\n  e [label = \"PCR\ntest result\"]\n  f [label = \"Physical\nsample\"]\n  \n  edge [color = grey, \n        arrowhead = none,\n        arrowtail = none,\n        penwidth = 3]\n \n a -> c [label = \"Collected by\"]\n b -> c [label = \"Collected at\"]\n c -> f [label = \"Collected from\"]\n f -> d [label = \"Derived from\"]\n f -> e [label = \"Derived from\"]\n \n}\n  \n","config":{"engine":"dot","options":null}},"evals":[],"jsHooks":[]}</script>
+<div id="htmlwidget-c58e3ea7194d08a6f6d0" style="width:672px;height:200px;" class="grViz html-widget "></div>
+<script type="application/json" data-for="htmlwidget-c58e3ea7194d08a6f6d0">{"x":{"diagram":"\ndigraph bat_sampling {\n\n  # a \"graph\" statement\n  graph [overlap = true, nodesep = .5, ranksep = .25, compound = true, color = MediumAquamarine, fontsize = 10, rankdir = LR]\n\n  # \"node\" styling\n  node [shape = circle,\n        fixedsize = true,\n        width = 1,\n        fontname = Helvetica,\n        style = filled,\n        fillcolor = MediumAquamarine]\n        \n  a [label = \"Collector\"]\n  b [label = \"Site\"]\n  c [label = \"Bat\"]\n  d [label = \"Antibody\ntest result\"]\n  e [label = \"PCR\ntest result\"]\n  f [label = \"Physical\nsample\"]\n  \n  edge [color = grey, \n        arrowhead = none,\n        arrowtail = none,\n        penwidth = 3]\n \n a -> c [label = \"Collected by\"]\n b -> c [label = \"Collected at\"]\n c -> f [label = \"Collected from\"]\n f -> d [label = \"Derived from\"]\n f -> e [label = \"Derived from\"]\n \n}\n  \n","config":{"engine":"dot","options":null}},"evals":[],"jsHooks":[]}</script>
 <p class="caption">
 Figure 8.1: Data model for bat sampling example.
 </p>
@@ -530,8 +530,8 @@ <h3><span class="header-section-number">8.5.1</span> Workspaces, Bases, Tables,
 <p>Bases are equivalent to databases. They consist of a set of tables that can be linked and allow you to perform some task (e.g. IRB tracking, capturing research data, etc.). Bases can be duplicated and shared across your workspaces and you can share bases with other users.</p>
 <p>Tables are where most of the action happens. Data is entered in tables, tables can be transformed via views into calendars, dashboards, or galleries, and tables can be manipulated via the API. They describe a data entity and are composed of fields. In the bat sampling example, each circle would be a table in the bat sampling base.</p>
 <div class="figure"><span style="display:block;" id="fig:unnamed-chunk-1"></span>
-<div id="htmlwidget-1c97733dc78ec01cc87f" style="width:672px;height:200px;" class="grViz html-widget "></div>
-<script type="application/json" data-for="htmlwidget-1c97733dc78ec01cc87f">{"x":{"diagram":"\ndigraph bat_sampling {\n\n  # a \"graph\" statement\n  graph [overlap = true, nodesep = .5, ranksep = .25, compound = true, color = MediumAquamarine, fontsize = 10, rankdir = LR]\n\n  # \"node\" styling\n  node [shape = circle,\n        fixedsize = true,\n        width = 1,\n        fontname = Helvetica,\n        style = filled,\n        fillcolor = MediumAquamarine]\n        \n  a [label = \"Collector\"]\n  b [label = \"Site\"]\n  c [label = \"Bat\"]\n  d [label = \"Antibody\ntest result\"]\n  e [label = \"PCR\ntest result\"]\n  f [label = \"Physical\nsample\"]\n  \n  edge [color = grey, \n        arrowhead = none,\n        arrowtail = none,\n        penwidth = 3]\n \n a -> c [label = \"Collected by\"]\n b -> c [label = \"Collected at\"]\n c -> f [label = \"Collected from\"]\n f -> d [label = \"Derived from\"]\n f -> e [label = \"Derived from\"]\n \n}\n  \n","config":{"engine":"dot","options":null}},"evals":[],"jsHooks":[]}</script>
+<div id="htmlwidget-91d1e9b8cd093cbf8f81" style="width:672px;height:200px;" class="grViz html-widget "></div>
+<script type="application/json" data-for="htmlwidget-91d1e9b8cd093cbf8f81">{"x":{"diagram":"\ndigraph bat_sampling {\n\n  # a \"graph\" statement\n  graph [overlap = true, nodesep = .5, ranksep = .25, compound = true, color = MediumAquamarine, fontsize = 10, rankdir = LR]\n\n  # \"node\" styling\n  node [shape = circle,\n        fixedsize = true,\n        width = 1,\n        fontname = Helvetica,\n        style = filled,\n        fillcolor = MediumAquamarine]\n        \n  a [label = \"Collector\"]\n  b [label = \"Site\"]\n  c [label = \"Bat\"]\n  d [label = \"Antibody\ntest result\"]\n  e [label = \"PCR\ntest result\"]\n  f [label = \"Physical\nsample\"]\n  \n  edge [color = grey, \n        arrowhead = none,\n        arrowtail = none,\n        penwidth = 3]\n \n a -> c [label = \"Collected by\"]\n b -> c [label = \"Collected at\"]\n c -> f [label = \"Collected from\"]\n f -> d [label = \"Derived from\"]\n f -> e [label = \"Derived from\"]\n \n}\n  \n","config":{"engine":"dot","options":null}},"evals":[],"jsHooks":[]}</script>
 <p class="caption">
 Figure 8.2: Data model for bat sampling example.
 </p>

index.html

@@ -452,7 +452,7 @@ <h1>
 <div id="header">
 <h1 class="title">EHA Modeling &amp; Analytics Handbook</h1>
 <h2 class="subtitle"><em><p>“These aren’t rules, just some things that we figured out.” – <a href="https://www.youtube.com/watch?v=66VtriAxcyw">Michael Reno Harrel</a><br />
-Last edit 2023-08-24 by Collin Schwantes</p></em></h2>
+Last edit 2023-09-12 by Collin Schwantes</p></em></h2>
 </div>
 <div id="introduction" class="section level1 unnumbered hasAnchor">
 <h1>Introduction<a href="index.html#introduction" class="anchor-section" aria-label="Anchor link to header"></a></h1>