Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Retrieve study descriptors from oeo instead of a static list #1718

Open
1 task
jh-RLI opened this issue Jun 13, 2024 · 3 comments
Open
1 task

Retrieve study descriptors from oeo instead of a static list #1718

jh-RLI opened this issue Jun 13, 2024 · 3 comments
Labels
enhancement Scenario Bundle Feature of the oeplatform. Urgency-M urgency level: medium

Comments

@jh-RLI
Copy link
Contributor

jh-RLI commented Jun 13, 2024

Description of the issue

After #1507 it became clear that we can currently only implement a static list that identifies classes from the oeo as study descriptors for the scenario bundles in the OEKG. As @l-emele described, an annotation could be implemented in the oeo that specifies descriptors.

Ideas of solution

Retrive all study descriptors from oeo based on the "descriptor" annotation.

Workflow checklist

@jh-RLI jh-RLI added enhancement Scenario Bundle Feature of the oeplatform. labels Jun 13, 2024
@jh-RLI jh-RLI changed the title Retrieve study descriptors form oeo instead of static list Retrieve study descriptors from oeo instead of a static list Jun 13, 2024
@jh-RLI jh-RLI added the Urgency-M urgency level: medium label Jul 26, 2024
@stap-m
Copy link
Contributor

stap-m commented Aug 16, 2024

I created a PR with a new annotation and added the annotation to all classes that we wanted as study descriptors so far, see OpenEnergyPlatform/oekg#19.

@stap-m
Copy link
Contributor

stap-m commented Aug 19, 2024

The annotations are merged into the oeo dev-branch now. The next release to main is planned for Oct 1st. Can you work with the dev branch as well or should we schedule an extra release, if we want to have it for SIROP?

@jh-RLI
Copy link
Contributor Author

jh-RLI commented Aug 19, 2024

Great :) I can work with the oeo-dev branch. We mainly use the oeo-full.owl file in the OEP. I assume it is generated for each oeo release version?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Scenario Bundle Feature of the oeplatform. Urgency-M urgency level: medium
Projects
Development

No branches or pull requests

2 participants