https://github.com/aksw/leipzig.dataweek.de

Live: https://dataweek.de/ - Staging: https://staging.dataweek.de/

https://github.com/aksw/leipzig.dataweek.de

Science Score: 26.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
  • Academic email domains
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (9.8%) to scientific vocabulary
Last synced: 9 months ago · JSON representation

Repository

Live: https://dataweek.de/ - Staging: https://staging.dataweek.de/

Basic Info
  • Host: GitHub
  • Owner: AKSW
  • Language: JavaScript
  • Default Branch: develop
  • Homepage: https://dataweek.de/
  • Size: 722 MB
Statistics
  • Stars: 2
  • Watchers: 18
  • Forks: 1
  • Open Issues: 6
  • Releases: 0
Created about 5 years ago · Last pushed 10 months ago
Metadata Files
Readme Changelog

README.md

Das ist die Seite der DataWeek in Leipzig

| URL | Source Branch | Target Branch | Workflow | Description | |---------|---------------|---------------|----------|-------------| | https://dataweek.de/ | main | page-live | build.yml | Live | | https://staging.dataweek.de/ | develop | page-staging | preview-yml | Staging/development preview for the Live page | | https://next.dataweek.de/ | next | page-next | New Layout development area | | https://2022.dataweek.de/ | past/2022 | page-2022 | Archived page from 2022 | | | feature/newLayout | | Static branch of the new layout |

A source branch is built with an actions workflow and the result is pushed to the respective target branch.

The setup of the build workflow is as follows:

Build Workflow

Local setup

Requirements

  • Git
  • Task
  • Docker or Podman
  • Optionally:
    • Python (for serve resp. watch and pictures:scale resp. pictures:scale:preconditions)
    • entr (for watch resp. build:watch)

Build the page

task build

Serve the page

task serve

Since jekyll only watches pages but not the layouts and data there is no automatic rebuild. You have to run task build serve again, if you perform changes.

Development Setup

Additional requirement: entr

task watch

Serves the page and rebuilds it when changes happen in the directory.

Get the data

To work with the data you need to clone https://github.com/AKSW/leipzig.dataweek.de-model/. This is done with

task sync-data

Trouble Shooting

Working on a single resource

Use the restriction_file feature (Jekyll RDF Documentation).

If you work on a single resource respectively the corresponding layout the build time might be to long for active development. In this case the restriction: in the _config.yml file can be out-commented and replaced by a restriction_file: restriction_file.txt setting. The restriction file would just contain the resource(s) you are working on, e.g.:

<https://2023.dataweek.de/2023-06-26/>

Owner

  • Name: AKSW Research Group @ University of Leipzig
  • Login: AKSW
  • Kind: organization
  • Location: Leipzig

GitHub Events

Total
  • Issues event: 144
  • Issue comment event: 50
  • Push event: 816
  • Pull request event: 126
Last Year
  • Issues event: 144
  • Issue comment event: 50
  • Push event: 816
  • Pull request event: 126

Issues and Pull Requests

Last synced: 10 months ago

All Time
  • Total issues: 129
  • Total pull requests: 119
  • Average time to close issues: 2 days
  • Average time to close pull requests: about 5 hours
  • Total issue authors: 5
  • Total pull request authors: 3
  • Average comments per issue: 0.53
  • Average comments per pull request: 0.03
  • Merged pull requests: 102
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 73
  • Pull requests: 64
  • Average time to close issues: 2 days
  • Average time to close pull requests: about 4 hours
  • Issue authors: 3
  • Pull request authors: 2
  • Average comments per issue: 0.56
  • Average comments per pull request: 0.02
  • Merged pull requests: 54
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
  • JuliaHolze (120)
  • NievesECC (12)
  • splattater (9)
  • varoe90 (2)
  • white-gecko (1)
Pull Request Authors
  • splattater (98)
  • JuliaHolze (45)
  • white-gecko (3)
Top Labels
Issue Labels
Pull Request Labels

Dependencies

Gemfile rubygems
  • jekyll-rdf ~> 3.2 development
  • i18n >= 0
  • jekyll >= 4.2
  • webrick ~> 1.7
.github/workflows/build.yml actions
  • actions/checkout v3 composite
  • arduino/setup-task v1 composite
  • peaceiris/actions-gh-pages v3 composite
.github/workflows/past-2022.yml actions
  • actions/checkout v2 composite
  • arduino/setup-task v1 composite
  • peaceiris/actions-gh-pages v3 composite
.github/workflows/past-2023.yml actions
  • actions/checkout v3 composite
  • arduino/setup-task v1 composite
  • peaceiris/actions-gh-pages v3 composite
.github/workflows/preview.yml actions
  • actions/checkout v3 composite
  • arduino/setup-task v1 composite
  • peaceiris/actions-gh-pages v3 composite
.github/workflows/past-2024.yml actions
  • actions/checkout v4 composite
  • arduino/setup-task v2 composite
  • peaceiris/actions-gh-pages v4 composite
.github/workflows/past-2025.yml actions
  • actions/checkout v4 composite
  • arduino/setup-task v2 composite
  • peaceiris/actions-gh-pages v4 composite