You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, meta-osselot tries to map a recipe to a single curated project. This means, that recipes that rely on more than one project will inevitably end up with un-curated data, even if both projects by themselves are available within the Osselot database.
I am not sure how much of a need there is for this use-case.
If this is something we want to support, we would probably have to add the ability to specify more than one OSSELOT_NAME and OSSELOT_VERSION for each recipe.
The text was updated successfully, but these errors were encountered:
Currently, meta-osselot tries to map a recipe to a single curated project. This means, that recipes that rely on more than one project will inevitably end up with un-curated data, even if both projects by themselves are available within the Osselot database.
I am not sure how much of a need there is for this use-case.
If this is something we want to support, we would probably have to add the ability to specify more than one OSSELOT_NAME and OSSELOT_VERSION for each recipe.
The text was updated successfully, but these errors were encountered: