https://github.com/clowder-framework/clowder2

Clowder v2 (in development)

https://github.com/clowder-framework/clowder2

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 (15.8%) to scientific vocabulary
Last synced: 10 months ago · JSON representation

Repository

Clowder v2 (in development)

Basic Info
  • Host: GitHub
  • Owner: clowder-framework
  • License: apache-2.0
  • Language: TypeScript
  • Default Branch: main
  • Size: 31.4 MB
Statistics
  • Stars: 14
  • Watchers: 10
  • Forks: 6
  • Open Issues: 283
  • Releases: 4
Created about 4 years ago · Last pushed 10 months ago
Metadata Files
Readme Changelog License Codeowners

README.md

Clowder v2 (In active development)

Build Status Slack

For the previous version of Clowder, please see Clowder v1.

Clowder v2 is a reimagining of the Clowder research data management system using a different and newer technology stack. Clowder is a cloud native data management framework to support any research domain. Clowder was developed to help researchers and scientists in data intensive domains manage raw data, complex metadata, and automatic data pipelines.

While the Clowder v1 has worked well over the years, many of the underlying technologies and libraries have not received enough support in recent years and new developers have had a challenging time learning how to contribute to it. Clowder v2 is also an opportunity to leverage our experience working with research data in Clowder and deliver a better solution to common problems researchers encounter when working with data.

Clowder v2 provides:

  • a better user experience and user interface
  • an easier code base to pick up and modify written in Python/FastAPI and Typescript/React
  • new features based on our experience working with researchers

Documentation

The v2 documentation is still work in progress. It's available at https://clowder2.readthedocs.io.

The v1 documentation is not fully compatible with v2, but it does provide some still relevant information. It is available at https://clowder-framework.readthedocs.io. There is a few other documentation links available on the website.

Installation

The easiest way of running Clowder v2 is checking out the code and running docker compose up in the main directory. If you would like to run Clowder with JupyterHub, you can use our script docker-prod.sh to start the services. Run ./docker-prod.sh prod up to start the services and ./docker-prod.sh prod down to stop them.

Helm charts are available for running Clowder v2 on Kubernetes. See the helm directory for more information.

Contributing

We are always looking for contributors. This could be anything from fixing bugs, adding new features, providing new feature requests, reccomending UI/UX improvements, helping with the documentation, or just testing the system and providing feedback. Here are a few ways to get started:

  • Join our Slack channel, introduce yourself, and ask questions about the specific aspects of the system you are interested in.
  • Submit an issue (bug or feature request) on the issue tracker.
  • Submit a pull request with a bug fix or new feature. For larger changes, it's best to open an issue first or ask on Slack to discuss the changes.
  • Develop new information extractors and/or visualizations.

Please follow our code of conduct when interacting with the community.

Support & Contacts

The easiest way to get in touch with us is Slack. This is a public forum. If you prefer email, you can contact us at clowder@lists.illinois.edu.

License

Clowder v2 is licensed under the Apache 2.0 license.

Owner

  • Name: Clowder
  • Login: clowder-framework
  • Kind: organization
  • Email: clowder@lists.illinois.edu

Research data management for long tail data.

GitHub Events

Total
  • Create event: 27
  • Release event: 1
  • Issues event: 22
  • Watch event: 2
  • Delete event: 13
  • Issue comment event: 14
  • Push event: 104
  • Pull request review comment event: 8
  • Pull request review event: 14
  • Pull request event: 31
Last Year
  • Create event: 27
  • Release event: 1
  • Issues event: 22
  • Watch event: 2
  • Delete event: 13
  • Issue comment event: 14
  • Push event: 104
  • Pull request review comment event: 8
  • Pull request review event: 14
  • Pull request event: 31

Issues and Pull Requests

Last synced: 10 months ago

All Time
  • Total issues: 10
  • Total pull requests: 10
  • Average time to close issues: over 2 years
  • Average time to close pull requests: about 1 month
  • Total issue authors: 6
  • Total pull request authors: 6
  • Average comments per issue: 0.8
  • Average comments per pull request: 0.2
  • Merged pull requests: 2
  • Bot issues: 0
  • Bot pull requests: 1
Past Year
  • Issues: 7
  • Pull requests: 10
  • Average time to close issues: N/A
  • Average time to close pull requests: about 1 month
  • Issue authors: 5
  • Pull request authors: 6
  • Average comments per issue: 0.0
  • Average comments per pull request: 0.2
  • Merged pull requests: 2
  • Bot issues: 0
  • Bot pull requests: 1
Top Authors
Issue Authors
  • longshuicy (58)
  • lmarini (36)
  • tcnichol (35)
  • ddey2 (27)
  • FyZoey (25)
  • Vismayak (12)
  • max-zilla (6)
  • sandeep-ps (1)
  • manning-ncsa (1)
  • KastanDay (1)
  • dlebauer (1)
Pull Request Authors
  • longshuicy (58)
  • tcnichol (37)
  • ddey2 (21)
  • lmarini (19)
  • Vismayak (10)
  • max-zilla (4)
  • FyZoey (2)
  • GalMunGral (2)
  • blinkdog (1)
  • markendr (1)
  • alemsh (1)
  • sandeep-ps (1)
  • robkooper (1)
  • bingzhang (1)
Top Labels
Issue Labels
enhancement (44) bug (42) frontend (28) user testing (16) backend (8) epic (5) documentation (3) dataset versioning (3) devops (2) keycloak (1) work around (1)
Pull Request Labels
bug (4) backend (1) enhancement (1) user testing (1) frontend (1)