Build web-x

Build for PASTAplus/content-x@83c908a

templates/about/edi-policy.html

@@ -71,7 +71,7 @@ <h3 id="sensitive-data">Sensitive data</h3>
 <li><a href="https://opendp.org/" rel="noopener noreferrer" target="_blank">OpenDP</a> - A community effort to build trustworthy, open-source software tools for statistical analysis of sensitive private data.</li>
 </ul>
 <h3 id="offline-data">Offline data</h3>
-<p>There is an option to declare data "offline" within the distribution field of the data package metadata. Doing so eliminates the need to have data be "network" accessible to the EDI Data Repository during the data package upload process. The use of offline data is only recommended for data that are too voluminous for network or storage capacity, such as the output from numerical models. Offline data must be provided to the EDI Data Repository through alternative means (e.g., SSD drive via a common carrier) prior to uploading the data package metadata. EDI requests that an explanation of the offline status be provided in the data entity description field of the data package metadata, including the preferred method of data distribution if required to satisfy a data request. <a href="https://ediorg.github.io/data-package-best-practices/large-data-sets.html" rel="noopener noreferrer" target="_blank">See here for details</a>.</p>
+<p>There is an option to declare data "offline" within the distribution field of the data package metadata. Doing so eliminates the need to have data be "network" accessible to the EDI Data Repository during the data package upload process. The use of offline data is only recommended for data that are too voluminous for network or storage capacity, such as the output from numerical models. Offline data must be provided to the EDI Data Repository through alternative means (e.g., SSD drive via a common carrier) prior to uploading the data package metadata. EDI requests that an explanation of the offline status be provided in the data entity description field of the data package metadata, including the preferred method of data distribution if required to satisfy a data request. <a href="https://ediorg.github.io/data-package-best-practices/guide-special-cases/large-offline.html" rel="noopener noreferrer" target="_blank">See here for details</a>.</p>
 <h3 id="intellectual-rights-of-the-data-contributor">Intellectual rights of the data contributor</h3>
 <p>EDI makes every effort to ensure that all data are curated with intellectual rights defined by the data provider as found in the data package metadata. Although EDI advocates for open and unfettered access to data packages without use restrictions, we do not forbid data providers from declaring more restrictive licensing agreements for use of their data packages. Data providers should include a statement of Intellectual Rights in the metadata of their submissions. If they do not, EDI reserves the right to add a default declaration of intellectual rights to the data package metadata. The default declaration of intellectual rights used by EDI is based on the Creative Commons CC0 "No Rights Reserved" waiver. See below for the full default statement:</p>
 <p><em>This data package is released to the "public domain" under <a href="https://creativecommons.org/publicdomain/zero/1.0/" rel="noopener noreferrer" target="_blank">Creative Commons CC0 1.0</a> "No Rights Reserved". It is considered professional etiquette to provide attribution of the original work if this data package is shared in whole or by individual components. A generic citation is provided for this data package on <a href="https://portal.edirepository.org" rel="noopener noreferrer" target="_blank">the website</a> (herein "website") in the summary metadata page. Communication (and collaboration) with the creators of this data package is recommended to prevent duplicate research or publication. This data package (and its components) is made available "as is" and with no warranty of accuracy or fitness for use. The creators of this data package and the website shall not be liable for any damages resulting from misinterpretation or misuse of the data package or its components. Periodic updates of this data package may be available from the website. Thank you.</em></p>

templates/featured/featured-20200401.00.html

@@ -7,7 +7,7 @@ <h2>The Influence of Legacy Phosphorus on Lake Water Quality in the Yahara Water
 <h3>Citation</h3>
 <p>Motew, M., S. Carpenter, C. Kucharik, and E. Booth. 2020. WSC – The Influence of Legacy P on Lake Water Quality ver 1. Environmental Data Initiative. <a href="https://doi.org/10.6073/pasta/1bada17c0e32d1a0e634146bc05f75dc" rel="noopener noreferrer" target="_blank">https://doi.org/10.6073/pasta/1bada17c0e32d1a0e634146bc05f75dc</a>.</p>
 <h3>Description</h3>
-<p>This data package represents an example of published model code, including model input, output, and processing scripts. Generally, model based datasets archived in the EDI and other data repositories may include the model code itself, input data, model parameter settings, and output data. Based on our experience with this process we are currently developing best practices for publishing model software code and data. Those guidelines will be available for our community on our <a href="https://github.com/EDIorg/data-package-best-practices" rel="noopener noreferrer" target="_blank">“Data package best practices” GitHub page</a> soon.</p>
+<p>This data package represents an example of published model code, including model input, output, and processing scripts. Generally, model based datasets archived in the EDI and other data repositories may include the model code itself, input data, model parameter settings, and output data. Based on our experience with this process we are currently developing best practices for publishing model software code and data. Those guidelines will be available for our community on our <a href="https://ediorg.github.io/data-package-best-practices/" rel="noopener noreferrer" target="_blank">“Data package best practices” GitHub page</a> soon.</p>
 <p>The archived model code and output is from a suite of numerical models that was used to  investigate the influence of legacy P on water quality in the Yahara Watershed of southern Wisconsin, USA (Motew et al. 2017) as part of the NSF funded project <a href="https://wsc.limnology.wisc.edu/" rel="noopener noreferrer" target="_blank">“Water Sustainability and Climate (WSC) in the Yahara Watershed”</a>. The Yahara lakes are among the world’s most studied bodies of freshwater. Changes in climate and land use are impacting their health and could continue to do so into the future. An impact of particular concern is phosphorus pollution from agricultural and urban areas. </p>
 <div class="figure_featured" style="width: 50%;">
 <figure>

templates/featured/featured-20210901.00.html

@@ -21,7 +21,7 @@ <h3>Description</h3>
 </figure>
 </div>
 <p>Lead author of the data package, Laurel Braden Symes (Assistant Director of the <a href="https://www.birds.cornell.edu/ccb" rel="noopener noreferrer" target="_blank">K. Lisa Yang Center for Conservation Bioacoustics</a> at Cornell University) and colleagues collected more than 400 10-minute sound recordings of birds in and near Hubbard Brook Experimental Forest during their breeding season. The data set includes 130,776 vocalizations from 46 taxa over a period of two years. In addition to the recordings, the data package also includes analyses of habitat associations, phenology, and spatial patterning in vocalization activity.</p>
-<p>The design of this data package follows <a href="https://ediorg.github.io/data-package-best-practices/datapackage-design/" rel="noopener noreferrer" target="_blank">EDI’s data package best practices guidelines for special data</a>, as established by a working group of LTER information managers and members of EDI (Gries et al. 2021), among them Mary Martin, Information Manager for HBES. Instructions on how to work with audio files can be found under the <a href="https://ediorg.github.io/data-package-best-practices/datapackage-design/images-and-documents-as-data.html" rel="noopener noreferrer" target="_blank">“Images and Documents as Data”</a> section of the guidelines. Information and considerations are provided on data package structure and documentation as well as an inventory table which serves as a document catalog. Mary prepared the audio recordings for publication in the EDI data repository.</p>
+<p>The design of this data package follows <a href="https://ediorg.github.io/data-package-best-practices/guide-special-cases/preface.html" rel="noopener noreferrer" target="_blank">EDI’s data package best practices guidelines for special data</a>, as established by a working group of LTER information managers and members of EDI (Gries et al. 2021), among them Mary Martin, Information Manager for HBES. Instructions on how to work with audio files can be found under the <a href="https://ediorg.github.io/data-package-best-practices/guide-special-cases/images-and-docs.html" rel="noopener noreferrer" target="_blank">“Images and Documents as Data”</a> section of the guidelines. Information and considerations are provided on data package structure and documentation as well as an inventory table which serves as a document catalog. Mary prepared the audio recordings for publication in the EDI data repository.</p>
 <p>You can listen to an audio file from June 2018 at the Middle Hubbard Brook location on Soundcloud: <a href="https://soundcloud.com/hubbard-brook/m01rec010040/s-LA5LCAY0WoH" rel="noopener noreferrer" target="_blank">https://soundcloud.com/hubbard-brook/m01rec010040/s-LA5LCAY0WoH</a>, with vocalizations of the black-throated blue warbler, black-throated green warbler, ovenbird, red-eyed vireo, scarlet tanager and yellow-bellied sapsucker. The data collection was also featured in a story of the New Hampshire Public Radio Station (NHPR): <a href="https://www.nhpr.org/climate-change/2021-02-04/pandemic-sparks-innovation-at-n-h-s-influential-hubbard-brook-experimental-forest" rel="noopener noreferrer" target="_blank">https://www.nhpr.org/climate-change/2021-02-04/pandemic-sparks-innovation-at-n-h-s-influential-hubbard-brook-experimental-forest</a>.</p>
 <div class="figure_featured" style="width: 40%;">
 <figure>

templates/resources/designing-a-data-package.html

@@ -25,7 +25,7 @@ <h3 id="reproducible-science">Reproducible science</h3>
 <p>If publishing data in support of a manuscript, then include the data and processing scripts required to reproduce the results.</p>
 <p><img src="/static/images/reproducible-research.png" width="15%"/> </p>
 <h3 id="duplicated-data">Duplicated data</h3>
-<p>Have these exact data been published elsewhere? If so, then don't republish unless <a href="https://ediorg.github.io/data-package-best-practices/datapackage-design/data-in-other-repositories.html" rel="noopener noreferrer" target="_blank">the duplication is warranted</a>. Duplicates create maintenance issues for data managers and confusion for users. If data published elsewhere is used to create a derived dataset, reference these data via <a href="/resources/provenance-metadata">provenance metadata</a>. Derived data are not exact copies and can be archived. Mutable data licensed under the public domain can be archived. When in doubt, consult the data authors before republishing.</p>
+<p>Have these exact data been published elsewhere? If so, then don't republish unless <a href="https://ediorg.github.io/data-package-best-practices/guide-special-cases/other-repositories.html" rel="noopener noreferrer" target="_blank">the duplication is warranted</a>. Duplicates create maintenance issues for data managers and confusion for users. If data published elsewhere is used to create a derived dataset, reference these data via <a href="/resources/provenance-metadata">provenance metadata</a>. Derived data are not exact copies and can be archived. Mutable data licensed under the public domain can be archived. When in doubt, consult the data authors before republishing.</p>
 <p><img src="/static/images/organize-duplication.png" width="25%"/> </p>
 <h3 id="theme-of-the-data">Theme of the data</h3>
 <p>Data packages may include the full set of data for one study, or each type of measurement (e.g. biological, chemical, physical) may comprise its own data package. The decision depends on the research question from the study, and whether all data are needed to interpret them or if they may be used out of context from each other.</p>

templates/resources/types-of-contributions.html

@@ -40,7 +40,7 @@ <h2 id="accepted-data-types-and-file-formats">Accepted data types and file forma
 <h2 id="open-access-vs-embargoed">Open access vs. embargoed</h2>
 <p>All published data are immediately made open access, and only under specific circumstances may data be published in an embargoed form. For more information on embargoes see the <a href="/about/edi-policy#data-package-accessibility">EDI Data Policy</a>. Please <a href="/support/contact-us">contact us</a> if you have a use case for which an embargo should be considered.</p>
 <h2 id="upload-size-limit">Upload size limit</h2>
-<p>There is a soft limit of 500 MB and hard limit of 100 GB per data package. The 500 MB limit can be relaxed by contacting the EDI Data Curation Team and avoided entirely by information managers with an EDI account and <a href="https://docs.google.com/document/d/1DC403Wd6PfssjPXl-ToRNlC97xcr6kVoTWoFE4R2_bk/edit#heading=h.3yagd380wsrl" rel="noopener noreferrer" target="_blank">uploading with static data links</a>. For data packages exceeding 100 GB please see the recommendations for <a href="https://ediorg.github.io/data-package-best-practices/large-data-sets.html" rel="noopener noreferrer" target="_blank">publishing large datasets</a> or <a href="/support/contact-us">contact us</a> to find a solution.</p>
+<p>There is a soft limit of 500 MB and hard limit of 100 GB per data package. The 500 MB limit can be relaxed by contacting the EDI Data Curation Team and avoided entirely by information managers with an EDI account and <a href="https://docs.google.com/document/d/1DC403Wd6PfssjPXl-ToRNlC97xcr6kVoTWoFE4R2_bk/edit#heading=h.3yagd380wsrl" rel="noopener noreferrer" target="_blank">uploading with static data links</a>. For data packages exceeding 100 GB please see the recommendations for <a href="https://ediorg.github.io/data-package-best-practices/guide-special-cases/large-offline.html" rel="noopener noreferrer" target="_blank">publishing large datasets</a> or <a href="/support/contact-us">contact us</a> to find a solution.</p>
 <h2 id="fees">Fees</h2>
 <p>Publication to the EDI Data Repository is currently free of cost for most use cases. If expecting to publish large volumes of data please <a href="/support/contact-us">contact us</a> to negotiate cost sharing.</p>
 </main>

templates/resources/updating-a-data-package.html

@@ -25,7 +25,7 @@ <h1 id="updating-a-data-package">Updating a Data Package</h1>
 </blockquote>
 
 <h2 id="metadata-to-include">Metadata to include</h2>
-<p>It is important to communicate changes and significance in the metadata of an updated data package so users can understand what has changed and why. This information is included in the <a href="https://ediorg.github.io/data-package-best-practices/maintenance.html" rel="noopener noreferrer" target="_blank">maintenance</a> section of EML metadata. Guidance on adding this information is provided below.</p>
+<p>It is important to communicate changes and significance in the metadata of an updated data package so users can understand what has changed and why. This information is included in the <a href="https://ediorg.github.io/data-package-best-practices/guide-eml-bp/content-recommendations.html#maintenance" rel="noopener noreferrer" target="_blank">maintenance</a> section of EML metadata. Guidance on adding this information is provided below.</p>
 <h2 id="editing-data-and-metadata">Editing data and metadata</h2>
 <h3 id="ezeml">ezEML</h3>
 <p>Edit data and metadata using <a href="https://ezeml.edirepository.org/eml/" rel="noopener noreferrer" target="_blank">ezEML</a>:</p>

templates/support/frequently-asked-questions.html

@@ -29,7 +29,7 @@ <h2 id="what-services-does-edi-offer">What services does EDI offer?</h2>
 <h2 id="how-much-do-edi-services-cost">How much do EDI services cost?</h2>
 <p>Both the EDI Data Repository and our data curation services are currently free of cost for the submission of datasets. Caveats are large data volumes and extensive curatorial support. If you anticipate the need to archive large volumes of data, then we may have to negotiate some cost sharing agreement or if you would like to take advantage of skilled data management support for your project, please contact us for more information.</p>
 <h2 id="is-there-a-limit-to-the-amount-of-data-i-may-archive">Is there a limit to the amount of data I may archive?</h2>
-<p>No. However, large data volumes will require planning and may require some cost sharing between your project and EDI. For more on publishing large data see <a href="https://ediorg.github.io/data-package-best-practices/large-data-sets.html" rel="noopener noreferrer" target="_blank">the data package best practices for large datasets</a>.</p>
+<p>No. However, large data volumes will require planning and may require some cost sharing between your project and EDI. For more on publishing large data see <a href="https://ediorg.github.io/data-package-best-practices/guide-special-cases/large-offline.html" rel="noopener noreferrer" target="_blank">the data package best practices for large datasets</a>.</p>
 <h2 id="how-do-i-obtain-an-edi-user-account">How do I obtain an EDI user account?</h2>
 <p>EDI user accounts are for data managers providing curation services to a research group and uploading directly to the EDI Data Repository. Please contact us if you feel you are such a data manager. </p>
 <p>An EDI user account is not required to submit data to the EDI Data Repository. Google, ORCID, and GitHub account credentials provide access to our online metadata editor <a href="https://ezeml.edirepository.org/eml/" rel="noopener noreferrer" target="_blank">ezEML</a>, which may be used to submit data to EDI. If you do not have any of these accounts then please contact us for guidance on how to proceed data submission.</p>