search

OpenEnergyPlatform / data-preprocessing

Repository for data formatting, import of data, data and metadata review, and data curation.
GNU Affero General Public License v3.0
10 stars 7 forks source link

Review: Scenario-data for UMAS oemof_B3 #103

Closed hedwiglieselotte closed 1 year ago

hedwiglieselotte commented 2 years ago

Scenario-data for UMAS oemof_B3

I'm submitting an open dataset with a corresponding OEMetadata string for review. Please see review_process.md for technical detail.

Workflow checklist

  1. GitHub

    • [x] I have submitted this issue to have metadata and data review documented (Issue #NR)
    • [ ] Create a new review-branch and push OEMetadata to new branch (review/project_nameofdata#NR). If this step is too difficult, attach a file with the metadata as a comment in this issue and let the reviewer know.

  2. OEP

    • [ ] Upload data to the OEP in schema model_draft (see upload tutorial)
    • [ ] Link URL of data in this issue (model_draft.project_nameofdata)

  3. Start a Review

    • [ ] Start a pull request (PR) from review-branch to master
    • [ ] Assign a reviewer and get in contact

  4. Reviewer section

    • [ ] A reviewer starts working on the issue
    • [ ] Review data license
    • [ ] A reviewer finished working on this issue (and awarded a badge)
    • [ ] Update metadata on table
    • [ ] Data moved to its final schema
    • [ ] Add OEP tags to table
    • [ ] Merge PR and delete review-branch
    • [ ] Document final links of metadata and data in issue description
    • [ ] Close issue

Metadata and data for review

Here are the links to my data and metadata. Naming follows the pattern model_draft.project_nameofdata: Metadata: https://github.com/OpenEnergyPlatform/data-preprocessing/blob/review/project_nameofdata/data-review/project_nameofdata.json Data: https://openenergy-platform.org/dataedit/view/model_draft/project_nameofdata

Reviewed and published metadata and data

Final naming and location of the data and metadata after the review are as follows: schema.tablename