stadt-geschichte-basel.github.io

Documentation of the work of the team for research data management and digital education of Stadt.Geschichte.Basel.

https://github.com/stadt-geschichte-basel/stadt-geschichte-basel.github.io

Science Score: 36.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
    Found .zenodo.json file
  • DOI references
  • Academic publication links
    Links to: zenodo.org
  • Academic email domains
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (15.0%) to scientific vocabulary

Keywords

documentation public-history research-data-management
Last synced: 6 months ago · JSON representation

Repository

Documentation of the work of the team for research data management and digital education of Stadt.Geschichte.Basel.

Basic Info
Statistics
  • Stars: 0
  • Watchers: 1
  • Forks: 2
  • Open Issues: 9
  • Releases: 0
Topics
documentation public-history research-data-management
Created about 1 year ago · Last pushed 6 months ago
Metadata Files
Readme Changelog Contributing License Code of conduct Citation Security

README.md

stadt-geschichte-basel.github.io

This repository contains the documentation of the work of the team for research data management and digital education of Stadt.Geschichte.Basel.

GitHub issues GitHub forks GitHub stars Code license Data license DOI

Repository Structure

The structure of this repository follows the Advanced Structure for Data Analysis of The Turing Way and is organized as follows:

  • assets/: Images, figures, and other media files.
  • docs/: Documentation files, including the main README and other markdown files.
  • products/: The final products of the project, such as reports, papers, or presentations.
  • renv/: The R environment for the project, including package dependencies and versions.

Getting Started

We recommend using GitHub Codespaces for the easiest and fastest setup. It gives you a pre-configured, cloud-based development environment with everything ready to go directly in your browser.

Quick Start with GitHub Codespaces

  1. Fork this repository to your GitHub account (if needed).
Fork the repository
  1. Click the green <> Code button at the top right of this repository.

  2. Select the Codespaces tab and click Create codespace on main.

Create Codespace
  1. GitHub will now build a container that includes:

    • Node.js (via npm)
    • Python with uv
    • R with renv
    • Quarto
  2. Once the Codespace is ready, you can preview the documentation locally inside the Codespace with:

    • Open a terminal in the Codespace (Terminal > New Terminal).
    • Run the following command to install all dependencies and preview the project:

bash uv run quarto preview

Terminal

Local Setup

Recommended for advanced users ### Prerequisites Make sure the following tools are installed locally: - [Node.js](https://nodejs.org/en/download/) - [R](https://cran.r-project.org/) and Rtools (on Windows) - [uv (Python manager)](https://github.com/astral-sh/uv#installation) - [Quarto](https://quarto.org/docs/get-started/) > _Note: `uv` automatically manages a Python version if none is installed._ ### Local setup steps ```bash # 1. Install Node.js dependencies npm install # 2. Setup Python environment uv sync # 3. Setup R environment Rscript -e 'install.packages("renv"); renv::restore()' # 4. Preview documentation uv run quarto preview ```

Use

Check that all files are properly formatted.

bash npm run check

Format all files.

bash npm run format

Run the wizard to write meaningful commit messages.

bash npm run commit

Run the wizard to create a CHANGELOG.md.

bash npm run changelog

Preview the documentation.

bash uv run quarto preview

Support

This project is maintained by @Stadt-Geschichte-Basel. Please understand that we can't provide individual support via email. We also believe that help is much more valuable when it's shared publicly, so more people can benefit from it.

| Type | Platforms | | -------------------------------------- | ------------------------------------------------------------------------------------------------------------ | | Bug Reports | GitHub Issue Tracker | | Report bad data | GitHub Issue Tracker | | Docs Issue | GitHub Issue Tracker | | Feature Requests | GitHub Issue Tracker | | Report a security vulnerability | See SECURITY.md | | General Questions | GitHub Discussions |

Roadmap

See https://github.com/orgs/Stadt-Geschichte-Basel/projects/5 for the current roadmap.

Contributing

All contributions to this repository are welcome! If you find errors or problems with the data, or if you want to add new data or features, please open an issue or pull request. Please read CONTRIBUTING.md for details on our code of conduct and the process for submitting pull requests.

Versioning

We use SemVer for versioning. The available versions are listed in the tags on this repository.

Authors and acknowledgment

See also the list of contributors who contributed to this project.

License

The data in this repository is released under the Creative Commons Attribution 4.0 International (CC BY 4.0) License - see the LICENSE-CCBY file for details. By using this data, you agree to give appropriate credit to the original author(s) and to indicate if any modifications have been made.

The code in this repository is released under the GNU Affero General Public License v3.0 - see the LICENSE-AGPL file for details. By using this code, you agree to make any modifications available under the same license.

Owner

  • Name: Stadt.Geschichte.Basel
  • Login: Stadt-Geschichte-Basel
  • Kind: organization
  • Email: info@stadtgeschichtebasel.ch
  • Location: Switzerland

Wir schreiben Basler Geschichte!

GitHub Events

Total
  • Issues event: 34
  • Issue comment event: 54
  • Push event: 35
  • Pull request review comment event: 55
  • Pull request review event: 83
  • Pull request event: 44
  • Fork event: 2
  • Create event: 6
Last Year
  • Issues event: 34
  • Issue comment event: 54
  • Push event: 35
  • Pull request review comment event: 55
  • Pull request review event: 83
  • Pull request event: 44
  • Fork event: 2
  • Create event: 6

Issues and Pull Requests

Last synced: 6 months ago

All Time
  • Total issues: 18
  • Total pull requests: 21
  • Average time to close issues: 16 days
  • Average time to close pull requests: 7 days
  • Total issue authors: 3
  • Total pull request authors: 2
  • Average comments per issue: 0.67
  • Average comments per pull request: 1.81
  • Merged pull requests: 19
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 18
  • Pull requests: 21
  • Average time to close issues: 16 days
  • Average time to close pull requests: 7 days
  • Issue authors: 3
  • Pull request authors: 2
  • Average comments per issue: 0.67
  • Average comments per pull request: 1.81
  • Merged pull requests: 19
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
  • maehr (13)
  • noelleschnegg (3)
  • mtwente (2)
Pull Request Authors
  • maehr (12)
  • mtwente (8)
  • dependabot[bot] (3)
Top Labels
Issue Labels
bug (5) enhancement (1)
Pull Request Labels
dependencies (3) enhancement (1)

Dependencies

.github/workflows/changelog.yaml actions
  • actions/checkout v4 composite
  • orhun/git-cliff-action v2 composite
.github/workflows/greetings.yml actions
  • actions/first-interaction v1 composite
.github/workflows/quarto-publish.yml actions
  • actions/checkout v4 composite
  • quarto-dev/quarto-actions/publish v2 composite
  • quarto-dev/quarto-actions/setup v2 composite
package.json npm
  • commitizen ^4.3.0 development
  • cz ^1.8.2 development
  • cz-conventional-changelog ^3.3.0 development
  • git-cliff ^2.2.1 development
  • husky ^9.0.11 development
  • prettier ^3.2.5 development
pnpm-lock.yaml npm
  • code-frame@7.24.2
  • config-validator@19.0.3
  • conventional-commits-parser@5.0.0
  • execute-rule@19.0.0
  • helper-validator-identifier@7.24.5
  • highlight@7.24.5
  • load@19.2.0
  • node@20.12.10
  • resolve-extends@19.1.0
  • types@19.0.3