Materials Cloud Archive

<!DOCTYPE html> <html lang="en" dir="ltr"> <head> <meta charset="utf-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Materials Cloud Archive</title> <link rel="shortcut icon" href="/static/favicon.ico"/> <link rel="apple-touch-icon-precomposed" sizes="144x144" href="/static/apple-touch-icon-144-precomposed.png"/> <link rel="apple-touch-icon-precomposed" sizes="114x114" href="/static/apple-touch-icon-114-precomposed.png"/> <link rel="apple-touch-icon-precomposed" sizes="72x72" href="/static/apple-touch-icon-72-precomposed.png"/> <link rel="apple-touch-icon-precomposed" sizes="57x57" href="/static/apple-touch-icon-57-precomposed.png"/> <link rel="stylesheet" href="/static/dist/css/mc-archive-theme.dd94d2b676e1c9b08b1f.css" /> </head> <body ng-csp itemscope itemtype="http://schema.org/WebPage" data-spy="scroll" data-target=".scrollspy-target">  <header>    <script type="text/javascript"> document.addEventListener("DOMContentLoaded", () => { document.getElementsByTagName("body")[0].setAttribute('style', "display : block"); }); </script>  <script type="text/javascript"> var header = document.getElementsByTagName("header")[0]; var plausible = document.createElement("script"); var domain_name = window.location.hostname; var rollup_name = "plausible-rollup.materialscloud.org"; // domain_name = "archive.materialscloud.org"; plausible.async = ""; plausible.defer = ""; plausible.dataset["domain"] = domain_name + "," + rollup_name; plausible.src = "https://plausible.io/js/plausible.js"; header.appendChild(plausible); </script> <nav class="navbar navbar-mcloud-invenio navbar-expand-md">    <div class="navbar-logo-hamburger">  <div class="navbar-toggler navbar-toggler-logo"> <a class="navbar-brand navbar-toggler collapsed" href="https://www.materialscloud.org/home"> <img class="navbar-logo" src="/static/images/mcloud-logo-98x79.png" alt="Materials Cloud Archive" /> </a> </div>  <div class="navbar-toggler navbar-toggler-hamburger"> <button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#navbar-mcloud" aria-expanded="false" aria-controls="navbar-mcloud"> <span class="icon-bar"></span> <span class="icon-bar"></span> <span class="icon-bar"></span> </button> </div> </div> <div class="visible-xs spacer"></div>    <div id="navbar-mcloud" class="collapse navbar-collapse">    <div id="nav-top" class="flex-row">  <div class="col-xs-12 col-md-10"> <a class="navbar-brand hidden-xs" href="https://www.materialscloud.org/home"> <img class="navbar-logo" src="/static/images/mcloud-logo-98x79.png" alt="Materials Cloud Archive"/> </a> <ul class="nav navbar-nav"> <li class="nav-item"><a href="https://www.materialscloud.org/learn">LEARN</a></li> <li class="nav-item"><a href="https://www.materialscloud.org/work">WORK</a></li> <li class="nav-item"><a href="https://www.materialscloud.org/discover">DISCOVER</a></li> <li class="nav-item"><a href="https://www.materialscloud.org/explore">EXPLORE</a></li> <li class="nav-item active"><a href="https://archive.materialscloud.org">ARCHIVE</a></li> </ul> </div>  <div class="col-xs-12 col-md-2"> <ul class="nav navbar-nav navbar-right"> <li class="dropdown"> <a class="dropdown-toggle" id="more" data-toggle="dropdown" href="#">More</a> <ul class="dropdown-menu"> <li><a href="https://www.materialscloud.org/policies">Policies</a></li> <li><a href="https://www.materialscloud.org/dmp">Data Management Plan</a></li> <li><a href="https://www.materialscloud.org/termssummary">Terms of Use</a></li> <li><a href="https://www.materialscloud.org/infrastructure">Infrastructure</a></li> <li><a href="https://www.materialscloud.org/team">Team & Contact</a></li> <li><a href="https://www.materialscloud.org/home#partners">Partners</a></li> <li><a href="https://www.materialscloud.org/explore/connect">Connect your REST API</a></li> </ul> </li> </ul> </div> </div>    <div id="nav-bottom" class="flex-row">   <div class="navbar-search col-xs-12 col-md-12 col-lg-12 col-xl-2"> <form class="navbar-form" action="/search" role="search"> <div class="form-group"> <div class="input-group"> <input type="hidden" class="form-control" name="q" id="q"> <input type="text" class="form-control" name="q0" id="q0" placeholder="Search"> <div class="input-group-btn"> <button type="submit" onclick="addQuotes()" class="btn btn-default"><i class="fa fa-search"></i></button> </div> </div> </div> </form> <ul class="nav navbar-nav"> </ul> </div>  <div id="nav-bottom-middle" class="navbar-search col-xs-12 col-md-12 col-lg-12 col-xl-3 d-flex align-items-center text-center"> <a href="/about">About</a> <span class="pr-2 pl-2">|</span> <a href="/deposit/information">Submission instructions</a> <span class="pr-2 pl-2">|</span> <a class="pr-10" href="/help">FAQs</a> </div>  <div class="navbar-login hidden-xs col-xs-12 col-md-12 col-lg-12 col-xl-7"> <form class="navbar-form navbar-float"> <button type="button" class="btn btn-default" data-toggle="modal" data-target="#instructionsModal"> Upload a record </button> <a data-toggle="tooltip" data-placement="bottom" title="Log in to access your records or upload a record" href="/login/?next=%2Fdeposit%2Finformation" class="btn btn-default"><i class="fa fa-sign-in"></i> Log in</a> <a href="/signup/" class="btn btn-default btn-warning"><i class="fa fa-edit"></i> Sign up</a> </form> </div> <div class="navbar-login visible-xs col-xs-12 col-md-12"> <form class="navbar-form navbar-float"> <button type="button" class="btn btn-default" data-toggle="modal" data-target="#instructionsModal"> Upload a record </button> <a data-toggle="tooltip" data-placement="bottom" title="Log in to access your records or upload a record" href="/login/?next=%2Fdeposit%2Finformation" class="btn btn-default"><i class="fa fa-sign-in"></i> Log in</a> <a href="/signup/" class="btn btn-default btn-warning"><i class="fa fa-edit"></i> Sign up</a> </form> </div> </div> </div> </nav>   <div class="modal fade" tabindex="-1" id="instructionsModal" role="dialog" aria-labelledby="instructionsModalLabel" aria-hidden="true"> <div class="modal-dialog" role="document"> <div class="modal-content"> <div class="modal-header" class="pb-0"> <h4 class="modal-title" id="instructionsModalLabel"></h4> <button type="button" class="close pt-2" data-dismiss="modal" aria-label="Close"> <span aria-hidden="true">×</span> </button> </div> <div class="modal-body fs-16 text-justify"> <p class="fs-16">Please Log in to access the upload form.</p> <p class="fs-16">Read the <a href="/deposit/information" target="_blank">Submission instructions</a> before uploading a record.</p> </div> <div class="modal-footer d-flex justify-content-center"> <div class="row w-100"> <div class="col-sm-2 hidden-xs"></div> <div class="col-xs-6 col-sm-4 text-center"> <p class="font-weight-bold">I don't have an account</p> <a href="/signup/" class="btn btn-default btn-warning"><i class="fa fa-edit"></i> Sign up</a> </div> <div class="col-xs-6 col-sm-4 text-center"> <p class="font-weight-bold">I already have an account</p> <a href="/login/?next=%2Fdeposit%2Finformation" class="btn btn-default"><i class="fa fa-sign-in"></i> Log in</a> </div> <div class="col-sm-2 hidden-xs"></div> </div> </div> </div> </div> </div>  <div id="spacer_flash"></div> <script type="text/javascript"> /* Add double quotes to input value, to solve problem of Elasticsearch query with ":" (ex: 10.24435/materialscloud:2019.0005/v1) */ var q = document.getElementById("q"); var q0 = document.getElementById("q0"); function addQuotes() { if (document.getElementById("q0").value !== undefined && document.getElementById("q0").value) { q.setAttribute('value', "\"" + document.getElementById("q0").value + "\""); // q.setAttribute('value', document.getElementById("q0").value); // alert(document.getElementById("q0").value); // alert(document.getElementById("q").value); } } // Open/Close sidenav with logos function openLogos() { var element = document.getElementById("logosSidenav"); element.classList.add("sidenav_width"); } function closeLogos() { var element = document.getElementById("logosSidenav"); element.classList.remove("sidenav_width"); } </script> </header>  <body class="hidePage"></body>  <div class="container"> <ul class="nav nav-tabs nav-fill" role="tablist"> <li id="tab-submission_instructions" class="nav-item active"> <a class="nav-link" role="tab" href="#submission_instructions" data-toggle="tab">SUBMISSION INSTRUCTIONS</a> </li> <li id="tab-moderation_policies" class="nav-item"> <a class="nav-link" role="tab" href="#moderation_policies" data-toggle="tab">MODERATION POLICIES</a> </li> <li id="tab-archive_policies" class="nav-item"> <a class="nav-link" role="tab" href="#archive_policies" data-toggle="tab">ARCHIVE POLICIES</a> </li> </ul>  <div class="tab-content">  <div role="tabpanel" class="tab-pane active" id="submission_instructions"> <div class="row"> <div class="col-xs-1"></div> <div class="col-xs-10"> <h3>Submission instructions</h3> </br> <div> <p> To submit a record to the Materials Cloud Archive: <ul> <li>Log in or Sign up to register to the Materials Cloud Archive.</li> <li>Once you are logged in click on "Upload a record" to access the upload form. Fill in the form with the research data and associated metadata that will appear in the final record. <br> The guidelines below and the <a href="/deposit/example" target="_blank">fac-simile of the upload form</a> will instruct you on how to fill in the form. </li> </ul> </p> </div>  <div class="pb-10"> <button class="button_as_link" data-toggle="collapse" data-target="#guidelines">Guidelines to fill in the upload form<i class="fa pl-2"></i></button> </br> <div id="guidelines" class="collapse"> <b>Title</b> <ul> <li>The title should have only the first letter of the first word in capital letters, not all words (except where English grammar requires it, e.g. for proper nouns). </li> </ul> <b>Description</b> <ul> <li>The description should clarify the topic and purpose of the work, and briefly explain the contents of the dataset.</li> <li>The description should be in the format of an abstract for a journal paper.</li> </ul> <b>Keywords</b> <ul> <li>Records should specify 3 or more relevant keywords, not counting those related to funding (see next).</li> <li>For research funded by MARVEL, MaX, SNSF, EPFL, Swissuniversities, MarketPlace, BIG-MAP, Intersect, ERC, NFFA, EMMC, PRACE, PASC, OpenModel, NEP, DOME 4.0, Marie Curie Fellowship, H2020, and/or Horizon Europe, the record should add these funding <button type="button" class="button_as_link modal_keywords" data-toggle="modal" data-target="#keywordsModal">keywords</button>.</li> <li>For experimental work add the keyword 'Experimental'.</li> <li>Keywords are not case-sensitive.</li> </ul> <b>Authors' affiliations</b> <ul> <li>Affiliations should include the name of the institute/faculty/department, the name of the university or research center and the location. E.g. Theory and Simulation of Materials (THEOS), École Polytechnique Fédérale de Lausanne (EPFL), CH-1015 Lausanne, Switzerland</li> </ul> <b>References</b> <ul> <li>There should be at least one reference to a journal article or preprint (even under review or in preparation).</li> <li>The citation style should be: <i>N. Surname, N. Surname, Journal VOLUME, PAGES (YEAR)</i>. [Example: <i>A. Einstein, Ann. Physik 11, 170-187 (1903)</i>]</li> <li>If a journal article or preprint is published, a DOI (in the format e.g. 10.1038/s41565-017-0035-5) and a permalink must be provided and must resolve correctly.</li> <li>If a journal article or preprint is not yet published, the citation text must end with "(accepted)", "(submitted)", "(in preparation)" or a similar note. In this case the DOI, the permalink, and the Journal's name are optional. The author should remember to update the reference when the article or preprint is published.</li> <li>MARVEL-funded research should eventually link to open-access papers or arXiv preprints (NB: this is a MARVEL policy, not an Archive policy).</li> </ul> <b>Files</b> <ul> <li>None of the files must contain the paper itself or any of its supplementary materials. Individual plots and tables are acceptable as part of a larger archive of files.</li> <li>Copyright: Authors affirm that they have the legal right to publish what they submit. In case of doubt about some files, moderators will point this out to the authors, but the responsibility remains with the authors. <ul> <li>If the file in question is already published on the arXiv, moderators may assume that it is legally allowed. </li> <li>In exceptional cases, it is possible to add a copyright notice to the file description and/or to the abstract.</li> </ul> </li> <li>Files should be open file formats where available (<a href="https://5stardata.info/en/" target="_blank">https://5stardata.info/en/</a>) and should strive to be F.A.I.R. (<a href="https://en.wikipedia.org/wiki/FAIR_data" target="_blank">https://en.wikipedia.org/wiki/FAIR_data</a>).</li> <li>All files should be accompanied by one-line descriptions of file contents.</li> <li>Large files should be compressed (e.g. .zip, .tar.gz -- avoid proprietary compression formats).</li> <li>When appropriate, detailed contents should be described in a separate file README.txt/.md/.rst placed outside the archives.</li> <li>All files names should have an extension.</li> <li>File size limits (total): 5 GB in general, 50 GB for AiiDA databases. Well motivated exceptions are possible: please write to archive@materialscloud.org.</li> </ul> </div> </div>  <div class="pb-10"> <button class="button_as_link" data-toggle="collapse" data-target="#submission">Submission and moderation of records<i class="fa pl-2"></i></button> </br> <div id="submission" class="collapse"> <p> Upon submission your record will be reviewed by the Materials Cloud moderators and you might be asked to make some changes to it. </p> <p> The DOI associated with your record will resolve after your record has been approved. The DOI is unique per record and cannot be changed. </p> <p> Please note that the moderators have the right in exceptional cases to retract your record or to reject your submission if the record is not in accordance with the Archive and Moderation policies. </p> </div> </div>  <div class="pb-10"> <button class="button_as_link" data-toggle="collapse" data-target="#update">Update of published records<i class="fa pl-2"></i></button> </br> <div id="update" class="collapse"> Once your record has been made public you can: <dl class="indent-20"> <dd class="mb-0">- change at any time keywords and references; </dd> <dd class="mb-0">- submit a new version of the record. The new version will have a DOI different from the previous version. </dd> </dl> </div> </div> </div> <div class="col-xs-1"></div> </div> <div class="row"> <div class="col-xs-1"></div> <div class="col-xs-10"> <h3>Integration with external applications</h3> </br> <div> <p> Leverage data you upload to the Materials Cloud Archive in external applications. The Archive currently provides connection with the applications <a href="https://chemiscope.org/" target="_blank">Chemiscope</a>, <a href="https://www.optimade.org/" target="_blank">OPTIMADE</a> and <a href="https://renkulab.io/" target="_blank">Renku</a>. When uploading your files to the Archive follow the instructions below for these applications to access your data. </p> </div>  <div id="submission_instructions_chemiscope" class="pb-10 fw-normal"> <button class="button_as_link" data-toggle="collapse" data-target="#chemiscope">Chemiscope<i class="fa pl-2"></i></button> </br> <div id="chemiscope" class="collapse pl-10"> <p class="pt-10"> <a href="https://chemiscope.org/" target="_blank">Chemiscope</a> is a tool for interactive exploration of databases of materials and molecules, correlating local and global structural representations with the properties of the systems. </p> <p>To visualise your data on Chemiscope, data should be uploaded to the Archive with filenames ending with 'chemiscope.json' or 'chemiscope.json.gz'. More information on how to create the Chemiscope input files is available on the <a href="https://chemiscope.org/docs/manual/input.html" target="_blank">Chemiscope documentation</a>.</p> <p>Once the Archive record is published, click on the icon <img src="/static/images/chemiscope-icon-32x32.png" width="20px"> next to the files to visualise and explore your data on Chemiscope.</p> </div> </div>  <div id="submission_instructions_optimade" class="pb-10 fw-normal"> <button class="button_as_link" data-toggle="collapse" data-target="#optimade">OPTIMADE<i class="fa pl-2"></i></button> </br> <div id="optimade" class="collapse pl-10"> <p class="pt-10"> <a href="https://optimade.org" target="_blank">OPTIMADE</a> (Open Databases Integration for Materials Design) is a consortium aiming to make materials databases interoperable by developing a specification for a common REST API (OPTIMADE API). </p> <p> An OPTIMADE API is a way to make structural data available through a standard programmatic interface. The data will be accessible via OPTIMADE clients (such as <a href="https://optimadeclient.materialscloud.io/" target="_blank">optimadeclient.materialscloud.io</a>) and will be published alongside other major OPTIMADE <a href="https://www.optimade.org/providers-dashboard/" target="_blank">data providers</a>. </p> <p> Archive contributors can easily create an OPTIMADE API for their entry by uploading a simple configuration file called 'optimade.yaml' that describes where the structure data is located within the entry. The exact details about this file, supported structural formats and examples are available at <a href="https://github.com/materialscloud-org/optimade-maker" target="_blank">github.com/materialscloud-org/optimade-maker</a>. </p> <p> Once the Archive record is published, the OPTIMADE API is automatically deployed within 24 hours. The Archive record will include the link to the OPTIMADE API, click on the icon <img src="/static/images/optimade_logo.svg" width="20px"> next to the files. </p> <p> For the full list of archive entries hosting an OPTIMADE API, see <a href="https://optimade.materialscloud.org/" target="_blank">optimade.materialscloud.org</a>. </p> </div> </div>  <div id="submission_instructions_renku" class="pb-10 fw-normal"> <button class="button_as_link" data-toggle="collapse" data-target="#renku">Renku<i class="fa pl-2"></i></button> </br> <div id="renku" class="collapse pl-10"> <p class="pt-10"> <a href="https://renkulab.io/" target="_blank">Renku</a> is a platform that bundles together various tools for reproducible and collaborative data analysis projects. It provides functionality for the creation and management of projects and datasets, and simple utilities to capture data provenance while performing analysis tasks.</br> Renku is developed as an open source project led by a dedicated team at the Swiss Data Science Center based at EPFL and ETHZ. </p> <p>If you use AiiDA, create a record on the Archive and upload the files with '.aiida' format. A project will be created on Renku using the data of your record.</p> <p>Once your Archive record has been published, you can access the corresponding Renku project by clicking on the Renku logo <img src="/static/images/renku_logo.svg" alt="Renku logo" width="20px"> located next to the record files. This will present an overview of the archive's basic statistics and open a Jupyter Notebook preloaded with the AiiDA profile and your data. This setup facilitates a detailed inspection and analysis of the records.</p> </div> </div> <p class="pt-20">For further questions, please consult the <a href="/help" target="_blank">FAQs</a> or contact us at: <a href="mailto:archive@materialscloud.org">archive@materialscloud.org</a>. </p> </div> <div class="col-xs-1"></div> </div> </div>  <div role="tabpanel" class="tab-pane fade" id="moderation_policies"> <div class="row"> <div class="col-xs-1"></div> <div class="col-xs-10"> <h3>Materials Cloud Moderation Policies</h3> <h4>v1.3, September 2020</h4> <p> <h3>Purpose of moderation</h3> </p> <p>The Materials Cloud Archive is a research data repository for the computational materials science community. With this goal in mind, submissions should be of computational materials science data, or experimental data that relates to published computational results. Submissions can also include codes, simulations tools, and AiiDA workflows related to computational materials science.</p> <p>A minimal level of moderation helps to ensure that its content is relevant to these goals. The moderation policies described below are inspired by those of the <a href="https://arxiv.org/help/moderation" target="_blank">arXiv preprint server</a>.</p> <h3>What criteria do moderators use?</h3> <p> Materials Cloud moderators will decline or suggest the removal of submissions that violate the <button class="button_as_link tab_redirect" value="archive_policies">Materials Cloud policies</button>, including:</p> <ul> <li> <b>Unsuitable content:</b> Submissions should provide data that is of value and could be used by other researchers in the field, for example data supporting a past, present or future refereed paper. Submissions that do not contain data produced by original or substantive research may be removed. The same applies to submissions that contain inflammatory or fictitious content, use mis-representative titles/abstracts/introductions, or submissions that are in need of significant review and revision. </li> <li> <b>Inappropriate form:</b> Abstract-only submissions, presentations, announcements, or advertisements may be removed. </li> <li> <b>Inappropriate topic:</b> Submissions that do not fall into the domain of computational materials science may be declined and redirected to a more appropriate repository, where applicable. <i>Experimental</i> materials science submissions can be accepted if one of the following criteria is met: <ul> <li>the work relates to published computational results, e.g. confirming or disproving them;</li> <li>one or more authors are affiliated with the <a href="https://www.materialscloud.org/home#partners" target="_blank">Materials Cloud partners</a>.</li> </ul> <li> <b>Duplicated content:</b> If a moderator notices that a new submission is really a revision of a recent submission, the moderator may request that the user consolidates the new submission into a replacement of the previous submission. This helps ensure that Materials Cloud is as useful as possible for readers, and it can often help authors to present a more unified body of research.</li> <li> <b>Excessive submission rate:</b> Data submitted to Materials Cloud must be of refereeable quality, and there is a practical limit to the rate at which appropriate, independent submissions can be produced by any one person. Moderators may request that any particular author limit his or her submission rate.</li> <li> <b>Submission of copyrighted material:</b> Submitting authors must hold copyright over the entirety of the submission when the files are uploaded to Materials Cloud. </li> </ul> <h3>Can I appeal a moderation decision?</h3> <p> If you disagree with a moderation decision, you should submit an appeal that explains your arguments clearly and succinctly. </p> <ul> <li>Send a detailed email, including all relevant information (especially submission ids, former correspondence, etc.) to <a href="mailto:archive@materialscloud.org">archive@materialscloud.org</a>.</li> <li>Moderators are not referees and do not provide detailed feedback on submissions. Administrators thus cannot provide detailed feedback regarding submissions deemed inappropriate, and will not enter into extended discussion regarding submissions.</li> <li>Please be <b>patient</b>, as moderation appeals are complex and may take some time.</li> <li>In rare cases we may require that a paper discussing the data be published in a conventional journal before an appeal is considered.</li> </ul> <p> The appeals process allows moderators additional time to reconsider a submission, but repeated appeals with no additional information cannot be considered. If you send an appeal and the moderators reach the same decision as they did initially, no further appeal should be submitted.</p> <h3>Disclaimer</h3> <p> The moderation team of the Materials Cloud Archive aims to ensure that the data deposited on the Materials Cloud Archive are accessible and reusable, but does not and cannot evaluate their correctness or suitability for any intended purpose. Therefore, the data are provided on an “as is” basis, and the Materials Cloud Archive and its team bear no liability for any consequence or eventual damages arising from the use of the data provided. </p> <p>We thus remind that it is the responsibility of end users to ensure that the data or records downloaded are suitable for an intended use. It is also the submitter's responsibility to update or correct the records deposited whenever the necessity might arise. </p> <h3>Who are the Materials Cloud Archive moderators?</h3> <p>Materials Cloud moderators are volunteer subject specialists who have been approved by the Materials Cloud consortium.</p> <p>Although the moderators may be publicly acknowledged, it is very inappropriate to contact any moderator directly regarding your submission. All communication about moderation decisions should be addressed to <a href="mailto:archive@materialscloud.org">archive@materialscloud.org</a>. Moderators will not reply to personal correspondence regarding Materials Cloud submissions.</p> <p> Current and past moderators of the Materials Cloud Archive are: <ul> <li>Patrick Mayor, EPFL (2021 - present)</li> <li>Marco Borelli, EPFL (2019 - 2022)</li> <li>Leopold Talirz, EPFL (2017 - 2020)</li> <li>Valeria Granata, EPFL (2019 - 2020)</li> <li>Jinhui Guo, EPFL (2019 - 2020)</li> <li>Giovanni Pizzi, EPFL (2017 - 2019)</li> <li>Nicola Marzari, EPFL</li> </ul> </p> </div> <div class="col-xs-1"></div> </div> </div>  <div role="tabpanel" class="tab-pane fade" id="archive_policies"> <div class="row pt-2"> <div class="col-xs-1"></div> <div class="col-xs-10"> <h3>Materials Cloud Archive Policies</h3> <h4>v1.2, February 2021</h4> <div class="pt-2"> <blockquote><q> The Materials Cloud Archive is an open-access, <button class="button_as_link tab_redirect" value="moderation_policies">moderated</button> repository for research data in computational materials science. Submissions to the Materials Cloud Archive are expected to be of interest, relevance, and value to the field. </q></blockquote> </div> <h3>Content</h3> <ul> <li><b>Suitable content:</b> Submissions should provide data that is of value and could be used by other researchers in the field, for example data supporting a past, present or future peer-reviewed paper (see the <button class="button_as_link tab_redirect" value="moderation_policies">moderation policies</button> for more details). References to preprints and/or published articles discussing the data are recommended but not required. </li> <li><b>Withdrawal:</b> If uploaded content must later be withdrawn, the reason for the withdrawal will be indicated on a tombstone page, which will henceforth be served in its place. Withdrawal is considered an exceptional action, which normally should be requested and fully justified by the original uploader. In any other circumstance reasonable attempts will be made to contact the original uploader to obtain consent. The DOI and the URL of the original object are retained.</li> <li><b>Data file formats:</b> All formats are allowed, even preservation unfriendly. Moderators may suggest alternative formats in line with the <a href="https://5stardata.info/en/" target="_blank">5-star deployment scheme to open web data</a>. </li> <li><b>Volume and size limitations:</b> 5 GB for general materials science research data, 50 GB for AiiDA databases. For larger datasets please contact us at <a href="mailto:archive@materialscloud.org">archive@materialscloud.org</a>.</li> <li><b>Metadata types and sources:</b> Metadata is partly provided by the uploader and partly generated automatically (e.g. submission date, version). Metadata is stored internally in JSON format. </li> </ul> <h3>Access and Reuse</h3> <ul> <li><b>Access to data objects:</b> Access to metadata and data files is provided over standard protocols such as HTTP and OAI-PMH.</li> <li><b>Embargos:</b> We plan to offer an embargoed access, allowing to deposit content under a user-defined embargo for up to two years.</li> <li><b>Use and re-use of data objects:</b> Use and re-use is subject to the license under which the data objects were deposited.</li> <li><b>Metadata access and reuse:</b> Metadata is licensed under <a href="https://spdx.org/licenses/CC-BY-SA-4.0.html" target="_blank">CC-BY-SA 4.0</a>, except for email addresses. Metadata is made available in machine-readable formats via HTML meta tags (<a href="https://www.dublincore.org/specifications/dublin-core/dc-html/" target="_blank">Dublin Core schema</a>), JSON-LD (<a href="http://www.schema.org" target="_blank">schema.org schema</a>), and the <a href="/oai2d?verb=ListRecords&metadataPrefix=oai_dc" target="_blank">OAI-PMH protocol</a> (<a href="http://www.openarchives.org/pmh/" target="_blank">OAI-PMH 2.0</a>, <a href="http://dublincore.org/schemas/xmls/" target="_blank">Dublin Core schema</a>). </li> <li><b>FAIR principles:</b> The Materials Cloud Archive follows the <a href="https://dx.doi.org/10.1038/sdata.2016.18" target="_blank">FAIR Guiding Principles for scientific data management and stewardship</a>. For details regarding the implementation, see the information on <a href="https://www.materialscloud.org/dmp" target="_blank">data management plans</a>. </li> </ul> <h3>Longevity</h3> <ul> <li><b>Versions:</b> Records are versioned. Data files are not versioned.</li> <li><b>Retention period:</b> Items will be retained for the lifetime of the repository, but at least for 10 years after deposition (guaranteed by <a href="https://www.cscs.ch/" target="_blank">CSCS</a>).</li> <li><b>Immutability:</b> Once published, records can no longer be modified without creating a new version. Exceptions to this rule are the "References" and "Keywords" fields, which may be updated a posteriori.</li> <li><b>Fixity and authenticity:</b> All data files are stored along with a MD5 checksum of the file content.</li> <li><b>Succession plans:</b> In case of closure of the repository, best efforts will be made to integrate all content into suitable alternative institutional and/or subject based repositories.</li> </ul> <h3>Fair Implementation Profile (FIP)</h3> <div class="row"> <div class="col-xs-12 pl-40"> The <a href="https://www.go-fair.org/" target="_blank">GO FAIR</a> community has launched the development of machine-actionable FAIR Implementation Profiles (FIP). The FIP is a collection of FAIR implementation choices made by a community of practice for each of the FAIR Principles. </div> </div> <div class="row"> <div class="col-xs-12 pl-40"> FIPs can be used as the basis to optimize the reuse of existing FAIR-enabling resources and interoperation within and between domains. </div> </div> <div class="row"> <div class="col-xs-12 pl-40 pt-10"> Download the Materials Cloud Archive FIP: </div> </div> <div class="row pt-20"> <div class="col-xs-6 col-md-3 pl-40 text-left"> <a href="https://archive.materialscloud.org/static/documents/fip/Materials Cloud V1.1.pdf" class="btn btn-primary" download> PDF format <i class="glyphicon glyphicon-download-alt"></i></a> </div> <div class="col-xs-6 col-md-3 text-left"> <a href="https://archive.materialscloud.org/static/documents/fip/Materials Cloud V1.1.trig" class="btn btn-primary" download> TRIG format <i class="glyphicon glyphicon-download-alt"></i></a> </div> <div class="col-md-6"></div> </div> <div class="noticesection pt-30"> <p> <i>Acknowledgement: This document is loosely based on the policies of the <a href="https://zenodo.org/" target="_blank">zenodo research data repository</a> and the <a href="https://arxiv.org/" target="_blank">arXiv preprint server</a>.</i> </p> </div> </div> <div class="col-xs-1"></div> </div> </div> </div> </div>  <div class="container">  <div class="modal fade" tabindex="-1" id="keywordsModal" role="dialog" aria-labelledby="keywordsModalLabel" aria-hidden="true"> <div class="modal-dialog mw-100 w-75" role="document"> <div class="modal-content"> <div class="modal-header"> <h2 class="modal-title" id="keywordsModalLabel">Keywords for research funded by Materials Cloud partners</h2> <button type="button" class="close pt-2" data-dismiss="modal" aria-label="Close"> <span aria-hidden="true">×</span> </button> </div> <div class="modal-body fs-16 text-justify"> <h4>Last updated 2023-07-27.</h4> <p>For research funded by MaX, SNSF, EPFL, Swissuniversities, MarketPlace, BIG-MAP, Intersect, ERC, NFFA, EMMC, PRACE, PASC, OpenModel, NEP, DOME 4.0, Marie Curie Fellowship, H2020, and/or Horizon Europe add these as keywords; for research funded by MARVEL, add the keyword(s) MARVEL/XXX (XXX can be DD1, DD2, DD3, DD4, DD5, DD6, Inc1, Inc2, OSP, HPC, P1, P2, P3, P4, ASM, QS), or just MARVEL if not associated to one of the above projects. Keywords are NoT cAsE-sEnSiTiVe.</p> </div> </div> </div> </div> </div> <footer class="footer"> <div class="menu-wrapper"> <div class="container pt-50"> </div> </div> </footer> <script src="/static/dist/js/manifest.542f5ef81bf10bf1ea20.js"></script> <script src="/static/dist/js/1.06385fc1e953c0551c8c.js"></script> <script src="/static/dist/js/3.f7488407095c285dd870.js"></script> <script src="/static/dist/js/4.60556ac1230f88568980.js"></script> <script type="text/javascript"> jQuery(document).ready(function($){ let url = location.href.replace(/\/$/, ""); // add hashtag to url $('a[data-toggle="tab"]').on("click", function() { let newUrl; const hash = $(this).attr("href"); newUrl = url.split("#")[0] + hash; history.replaceState(null, null, newUrl); }); // activate the correct tag if url has hashtag function activate_tab() { // check if hash contains name of application (chemiscope, optimade, renku, ...) var hash = location.hash; apps = ["#submission_instructions_chemiscope", "#submission_instructions_optimade", "#submission_instructions_renku"]; if (apps.includes(hash)) { location.hash = "submission_instructions"; } else { hash = null; } if (location.hash) { items = $('div').find('.tab-pane'); // deactivate all tabs for (i=0; i<items.length; i++) { var id = $(items[i]).attr('id') $(items[i]).removeClass('active'); $(items[i]).addClass('fade'); $('#tab-' + id).removeClass('active'); } // id of destination tab id = location.hash.replace('#','') // scroll top of destination tab $('#tab-' + id).scrollTop(); // activate destination tab $(location.hash).addClass('active'); $(location.hash).removeClass('fade'); $('#tab-' + id).addClass('active'); } scroll_to_application(hash); } // activate the correct tag if url has changed $(window).on('hashchange', function(e){ activate_tab(); }); // redirect to the correct tab $('.tab_redirect').click(function() { tab = $(this).val(); let newUrl; newUrl = location.href.split("#"); newUrl = newUrl[0] + '#' + tab; location.href = newUrl; }); // activate tab on page load activate_tab(); $('.modal_keywords').click(function() { $('body.hidePage').addClass('pr-0'); }); $('body').css("overflow-y", "scroll"); // add class collapsed on page load to correctly toggle arrows up/down $('[data-toggle="collapse"]').addClass('collapsed'); // scroll to the application hash (chemiscope, optimade, renku, ...) and open the div function scroll_to_application(hash){ if (hash) { if ($(hash).length) { $('html, body').animate({ scrollTop: $(hash).offset().top }, 850); hash = hash.replace("submission_instructions_", ""); $(hash).removeClass(['collapse', 'in']).addClass('collapse in'); $(hash).height('auto'); } } }; }); </script> </body> </html>

CINXE.COM

Materials Cloud Archive