template-metadata-files
Collection of metadata files (gitignore, pyproject, editorconfig, license etc.) to be used for initializing workflow and project repositories
https://github.com/core-unit-bioinformatics/template-metadata-files
Science Score: 44.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
✓CITATION.cff file
Found CITATION.cff file -
✓codemeta.json file
Found codemeta.json file -
✓.zenodo.json file
Found .zenodo.json file -
○DOI references
-
○Academic publication links
-
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (13.0%) to scientific vocabulary
Repository
Collection of metadata files (gitignore, pyproject, editorconfig, license etc.) to be used for initializing workflow and project repositories
Basic Info
- Host: GitHub
- Owner: core-unit-bioinformatics
- License: mit
- Default Branch: main
- Size: 17.6 KB
Statistics
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
- Releases: 12
Metadata Files
README.md
Template Metadata files
This repository is a collection of metadata files that should be used to initialize new repositories if appropriate (no strong arguments speak against it).
Repository-related metadata files
LICENSE: using this file is mandatory for all CUBI repositoriesCITATION.md: using this file is mandatory for all CUBI repositories- if no other - more specific - citation information applies to a repository, a link to this CITATION file must be added at the end of the top-level repository README (same wording as at the end of this README).
.editorconfig: using this file is mandatory for all CUBI repositories.gitignore: strongly recommended, contains ignore rules for Python, R and some custom entries by default. There must be a good reason not to use (an extended version of) this file.
CUBI metdata files
By convention, and for convenience, all CUBI metadata are organized in form of a pyproject.toml file
containing a minimal amount of descriptive entries. This file must be located at the top-level of the
respective repository. The "hierarchy" in these files is as follows:
- include Python tool settings for coherent formatting of Python code
- if the repository does not contain any Python code, this may be omitted
- include the CUBI metadata information, i.e., the top-level
pyproject.tomlin this repository - include specific metadata...
- ...for a project repository
- ...for a workflow template repository
- ...for a workflow repository
As a reminder, read the development guidelines to learn about key characteristics of workflows and projects, and naming conventions:
CUBI dev process in the knowledge base
CUBI naming conventions in the knowledge base
Conda environment template
This repository contains a minimal Conda environment file despite the fact that this repo does not include any executable code. This Conda environment template file should be used as the base file for more complex environments where applicable and reasonable:
This template environment encodes a few hard requirements for CUBI code developments:
YAML
dependencies:
- Python=3.11.* # the target Python3 version
- pip=25.1.*
# For conda itself:
# most recent; whatever can be resolved.
# Oct. '23 marks the switch to the libmamba
# solver and since then, there should not be
# too much of a speed difference between
# conda and mamba
- conda>23.10.0
# All of the below:
# There are config options set for these
# tools in 'tomls/formatting/pyproject.toml'
# and, hence, changing any of the versions
# requires checking that all options/parameters
# are still supported:
- pyyaml=6.0.*
- toml=0.10.*
- semver=3.0.*
- pylint=3.3.*
- isort=6.0.*
- black=24.10.*
- ruff=0.12.*
Citation
If not indicated otherwise above, please follow these instructions to cite this repository in your own work.
Owner
- Name: core-unit-bioinformatics
- Login: core-unit-bioinformatics
- Kind: organization
- Repositories: 15
- Profile: https://github.com/core-unit-bioinformatics
Citation (CITATION.md)
# Citing this repository
If you are using the content of this repository in whole or in part for your own work,
please credit the Core Unit Bioinformatics in an appropriate form.
In general, please add this statement to the acknowledgments of your publication:
This work was supported by the Core Unit Bioinformatics
of the Medical Faculty of the Heinrich Heine University Düsseldorf.
Additionally, please follow the below instructions to obtain a citable reference
for your publication.
## Identifying the right source link
Each repository of the Core Unit Bioinformatics is assigned a persistent
identifier (PID) at some point (usually after the prototype stage). Please use
this PID to link to the repository. You always find the PID in the top-level
`pyproject.toml`. Depending on the type of repository (project, workflow, or
workflow template), the relevant PID is listed in the corresponding metadata
section:
```toml
# workflow repository
[cubi.workflow]
pid = "THE-PID"
```
```toml
# workflow template repository
[cubi.workflow.template]
pid = "THE-PID"
```
```toml
# project repository
[cubi.project]
pid = "THE-PID"
```
If a PID has not yet been assigned to the repository, please use the repository URL,
and, if time permits, contact the repository maintainer regarding assigning a PID
in the near future.
### 1. Release version
For release versions, please use the respective version string in addition to the source link,
i.e. ideally in combination with the PID, and integrate that information into your list
of references as appropriate.
Note that repositories of the type "project" may not contain a lot of code, and are thus
often not amenable to the usual "release cycle" following bug fixes, feature integrations and so on.
Hence, the "project" metadata do not contain a "version" key (as opposed to workflow and workflow
template repositories). See the next point if you encounter that situation.
### 2. Development (non-release) version
For development versions, please use the respective git commit hash in addtion to the source link,
i.e. ideally in combination with the PID, and integrate that information into your list
of references as appropriate. It is strongly recommended to only use git commits from the two
central branches `main` and `dev`.
If a "project" repository is lacking an explicit release version, please use the same strategy
to obtain a citable reference of the repository.
### 3. None of the above
Please get in touch and we'll find a solution for your case :-)
GitHub Events
Total
- Create event: 5
- Issues event: 4
- Release event: 3
- Delete event: 2
- Issue comment event: 1
- Push event: 7
Last Year
- Create event: 5
- Issues event: 4
- Release event: 3
- Delete event: 2
- Issue comment event: 1
- Push event: 7
Issues and Pull Requests
Last synced: 6 months ago
All Time
- Total issues: 3
- Total pull requests: 0
- Average time to close issues: 3 months
- Average time to close pull requests: N/A
- Total issue authors: 2
- Total pull request authors: 0
- Average comments per issue: 0.67
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 2
- Pull requests: 0
- Average time to close issues: 1 day
- Average time to close pull requests: N/A
- Issue authors: 2
- Pull request authors: 0
- Average comments per issue: 0.5
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Top Authors
Issue Authors
- ptrebert (2)
- FerallOut (1)
Pull Request Authors
- ptrebert (2)