Skip to content

Latest commit

 

History

History
59 lines (42 loc) · 2.88 KB

File metadata and controls

59 lines (42 loc) · 2.88 KB

Contributing to Voc4Cat

Thank you for your interest in contributing to the Voc4Cat vocabulary! This SKOS vocabulary covers catalysis disciplines and welcomes contributions from the community.

Quick Start

  1. Request a range of IDs (for new concepts): Create an issue
  2. Download the current vocabulary Excel file: voc4cat.xlsx
  3. Edit the Excel file to add/modify concepts
  4. Submit your Excel file in a pull request:
    • Create a new branch for the changes in your fork and switch to it
    • Place file in inbox-excel-vocabs/ folder
    • Keep the filename as voc4cat.xlsx
    • Create a PR and describe your changes in the PR description

For more details, see How to contribute?

Important Guidelines

  • Small contributions welcome: Even single concept additions are valuable
  • Break up large changes: Split contributions of 50+ concepts into smaller chunks (~20 changes each)
  • Use Excel workflow only: Never edit Turtle (.ttl) files directly
  • ID ranges required: Request your ID range before adding new concepts
  • Use feature branches: Create a new branch for your changes instead of committing to your fork's main branch
  • Classify concepts properly: Ensure new concepts are linked to the hierarchy via broader concepts

Documentation

For detailed guidelines and step-by-step instructions, see:

What Happens Next?

(next after quick start)

  1. CI/CD pipeline automatically processes your Excel file
  2. Turtle files are generated and validated
  3. Automated checks provide helpful feedback:
    • Detects PRs from main branch (suggests using feature branches)
    • Identifies organization account issues that will block CI
    • GitHub Copilot may provide additional review guidance
  4. Updated Excel file is created from the processed data
  5. Reviewers will check your contribution
  6. Upon approval, your changes are merged and published

Note: Automated checks are informational and won't block your PR (except organization accounts due to GitHub limitations).

Questions or Issues?

License

All vocabulary contributions are released under CC0-1.0 license (public domain).