Built site for gh-pages

Author: Quarto GHA Workflow Runner

.nojekyll

@@ -1 +1 @@
-8cc07a28
+08f7a4a1

index.html

@@ -9,7 +9,7 @@
 <meta name="author" content="Julien Brun">
 <meta name="author" content="Renata Curty">
 <meta name="author" content="Greg Janée">
-<meta name="dcterms.date" content="2024-04-10">
+<meta name="dcterms.date" content="2024-04-15">
 
 <title>Good enough practices to manage your project data - Project Data Management</title>
 <style>
@@ -171,7 +171,7 @@ <h1 class="title">Project Data Management</h1>
     <div>
     <div class="quarto-title-meta-heading">Published</div>
     <div class="quarto-title-meta-contents">
-      <p class="date">April 10, 2024</p>
+      <p class="date">April 15, 2024</p>
     </div>
   </div>
 
@@ -202,13 +202,13 @@ <h1 class="title">Project Data Management</h1>
 <div id="quarto-appendix" class="default"><section class="quarto-appendix-contents" id="quarto-citation"><h2 class="anchored quarto-appendix-heading">Citation</h2><div><div class="quarto-appendix-secondary-label">BibTeX citation:</div><pre class="sourceCode code-with-copy quarto-appendix-bibtex"><code class="sourceCode bibtex">@online{brun2024,
   author = {Brun, Julien and Curty, Renata and Janée, Greg},
   title = {Project {Data} {Management}},
-  date = {2024-04-10},
+  date = {2024-04-15},
   url = {https://ucsb-library-research-data-services.github.io/project-data-management/},
   langid = {en}
 }
 </code><button title="Copy to Clipboard" class="code-copy-button"><i class="bi"></i></button></pre><div class="quarto-appendix-secondary-label">For attribution, please cite this work as:</div><div id="ref-brun2024" class="csl-entry quarto-appendix-citeas" role="listitem">
 Brun, Julien, Renata Curty, and Greg Janée. 2024. <span>“Project Data
-Management.”</span> April 10, 2024. <a href="https://ucsb-library-research-data-services.github.io/project-data-management/">https://ucsb-library-research-data-services.github.io/project-data-management/</a>.
+Management.”</span> April 15, 2024. <a href="https://ucsb-library-research-data-services.github.io/project-data-management/">https://ucsb-library-research-data-services.github.io/project-data-management/</a>.
 </div></div></section></div></main> <!-- /main -->
 <div>
   <p></p><hr><p></p>

preserve.html

@@ -189,24 +189,25 @@ <h1 class="title">Archiving and preserving your data</h1>
 
 
 <p>As you finalize your project, an important task is to archive your data in a publicly available repository (pending sensitivity and by non-disclosure agreement exceptions). There are a few important steps to ensure that your data can be reused by others and thus make your work more reproducible.</p>
+<p>Your general philosophy when preparing the preservation of your scientific products should be: <strong><em>Document what you used and preserve what you produced</em></strong></p>
+<p>See below for more information.</p>
+<hr>
 <section id="what-scientific-products-to-preserve" class="level2">
 <h2 class="anchored" data-anchor-id="what-scientific-products-to-preserve">What scientific products to preserve?</h2>
 <p>Often the first question that comes to mind when starting to preserve your work is: What should I include in my data archive? Generally speaking, you want to preserve <strong>your</strong> work. This means capturing the methodology you used, the raw data you collected, any data cleaning you did, and any data and output (figure, report, etc.) you generated. Okay… so you mean everything!? Well, yes and no. Everything that was relevant to help you to come to the findings and conclusions discussed in your project report or any other publications and deliverables. Let’s break this down!</p>
 <section id="raw-data" class="level3">
 <h3 class="anchored" data-anchor-id="raw-data">Raw data</h3>
 <p>Here are a few questions to ask yourself to determine if you should refer in your documentation to the raw data you used or also include them in your data archive.</p>
 <ol type="1">
-<li>The <strong>raw data is already publicly accessible</strong>, and the hosting solution (website, FTP server, etc.) seems well maintained (ideally providing a recommended citation)</li>
-</ol>
-<p>=&gt; Document the website or process you used to collect the data and when you accessed/downloaded the data you used. Try also to determine if a pecific version number is associated with the data you used.*</p>
-<ol start="2" type="1">
-<li>The raw data is <strong>not</strong> publicly accessible</li>
-</ol>
+<li><p>The <strong>raw data is already publicly accessible</strong>, and the hosting solution (website, FTP server, etc.) seems well maintained (ideally providing a recommended citation)</p>
+<p>=&gt; <em>Document the website or process you used to collect the data and when you accessed/downloaded the data you used. Try also to determine if a specific version number is associated with the data you used.</em></p></li>
+<li><p>The raw data is <strong>not</strong> publicly accessible</p>
 <p>Note that we are not talking about data under a non-disclosure agreement (NDA) here but more about data with an unclear reuse status or obtained by interactions with a person or an institution. For example, if the data you used were sent to you privately, then we recommend that you:</p>
 <ul>
 <li>inquire with your person of contact about the status of licensing and if they would be willing to let you share those data publicly. You might face resistance at first, so take the time to explain why you think it is valuable to your work to also share those data sets.</li>
 <li>if, in the end, it is not possible to share the data, please still describe the data in your documentation and list the contact information (person or institution) to inquire about this data set.</li>
-</ul>
+</ul></li>
+</ol>
 </section>
 <section id="intermediate-data" class="level3">
 <h3 class="anchored" data-anchor-id="intermediate-data">Intermediate data</h3>
@@ -224,6 +225,7 @@ <h3 class="anchored" data-anchor-id="code">Code</h3>
 <section id="final-products" class="level3">
 <h3 class="anchored" data-anchor-id="final-products">Final products</h3>
 <p>We recommend including any data set used to produce statistics, figures maps, and other visualizations that were used in your work, in this case, even if generated by scripts.</p>
+<hr>
 </section>
 </section>
 <section id="choosing-a-data-repository" class="level2">
@@ -263,11 +265,11 @@ <h3 class="anchored" data-anchor-id="choosing-a-license">Choosing a license</h3>
 </section>
 <section id="documenting-your-work" class="level2">
 <h2 class="anchored" data-anchor-id="documenting-your-work">Documenting your work</h2>
-<p>To make your archiving process the most efficient, it is key to document your work as you progress throughout your project. If you do so, archiving your data will consist of collecting existing information about the various parts of your project rather than developing it from scratch a few months after you have generated this specific dataset.</p>
+<p>To make your archiving process the most efficient, it is key to document your work as you progress throughout your project. If you do so, archiving your data will consist of collecting existing information about the various parts of your project rather than developing it from scratch a few months after you have generated this specific data set.</p>
 <p>Add an image about the power of README</p>
 <section id="metadata" class="level3">
 <h3 class="anchored" data-anchor-id="metadata">Metadata</h3>
-<p>Metadata aims at describing your data with enough information that should let you be able to reuse this data even if you know nothing about this specific dataset. It is sometimes defined as data about data. So what should you include? Here are some pointers:</p>
+<p>Metadata aims at describing your data with enough information that should let you be able to reuse this data even if you know nothing about this specific data set. It is sometimes defined as data about data. So what should you include? Here are some pointers:</p>
 <ul>
 <li>Describe the contents of data files. If you are using complex jargon or concepts make sure you refer to external vocabulary or clearly define these terms as used in your project</li>
 <li>Keep data entry consistent</li>