https://github.com/access-nri/intake-esmvalcore

Skeleton/Proof of Concept of integrating intake-esm into ESMValCore

https://github.com/access-nri/intake-esmvalcore

Science Score: 13.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
  • DOI references
  • Academic publication links
  • Academic email domains
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (11.1%) to scientific vocabulary
Last synced: 9 months ago · JSON representation

Repository

Skeleton/Proof of Concept of integrating intake-esm into ESMValCore

Basic Info
  • Host: GitHub
  • Owner: ACCESS-NRI
  • License: apache-2.0
  • Language: Jupyter Notebook
  • Default Branch: main
  • Size: 0 Bytes
Statistics
  • Stars: 0
  • Watchers: 1
  • Forks: 0
  • Open Issues: 0
  • Releases: 0
Created over 1 year ago · Last pushed over 1 year ago
Metadata Files
Readme License

README.md

General Repository Template

A general template repository for default settings when creating new repositories.

This repository uses the Apache-2.0 license. COPYRIGHT.txt contains a current copyright statement which should be included at the top of all files.

When creating a new repository you can use this repository as a template, to automate the creation of the correct license and COPYRIGHT statement.

COPYRIGHT Header

Best practice suggests adding a copyright statement at the top of every source code file, or text file where it is possible to add a copyright statement without interfering with the purpose of the file. The reasoning is if a file is separated from the repository in which it resides then it may not be possible to ascertain it's licensing, which may hamper re-use.

Making this as short and concise as possible reduces the overhead in including such a copyright statement. To that end using SPDX identifiers is simple, efficient, portable and machine-readable.

Examples

An example, short, copyright statement is reproduced below, as it might appear in different coding languages. Copy and add to files as appropriate:

plaintext

It is common to include copyright statements at the bottom of a text document or website page text © 2022 ACCESS-NRI and contributors. See the top-level COPYRIGHT file for details. SPDX-License-Identifier: Apache-2.0

python

For code it is more common to include the copyright in a comment at the top ```python

Copyright 2022 ACCESS-NRI and contributors. See the top-level COPYRIGHT file for details.

SPDX-License-Identifier: Apache-2.0

```

shell

```bash

Copyright 2022 ACCESS-NRI and contributors. See the top-level COPYRIGHT file for details.

SPDX-License-Identifier: Apache-2.0

```

FORTRAN

fortran ! Copyright 2022 ACCESS-NRI and contributors. See the top-level COPYRIGHT file for details. ! SPDX-License-Identifier: Apache-2.0

C/C++

c // Copyright 2022 ACCESS-NRI and contributors. See the top-level COPYRIGHT file for details. // SPDX-License-Identifier: Apache-2.0

Notes

Note that the date is the first time the project is created.

The date signifies the year from which the copyright notice applies. NEVER replace with a later year, only ever add later years or a year range.

It is not necessary to include subsequent years in the copyright statement at all unless updates have been made at a later time, and even then it is largely discretionary: they are not necessary as copyright is contingent on the lifespan of copyright holder +50 years as per the Berne Convention.

Owner

  • Name: ACCESS-NRI
  • Login: ACCESS-NRI
  • Kind: organization
  • Email: access.nri@anu.edu.au

Australian Earth System Simulator - National Research Infrastructure

GitHub Events

Total
  • Member event: 2
  • Push event: 2
  • Create event: 2
Last Year
  • Member event: 2
  • Push event: 2
  • Create event: 2