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
we would like to have a separate hub, which can host templates, studies, and services (distinction is increasingly artificial, but that is another discussion). it draws its content from (potentially multiple) repositories. for items that do not contain heavy data, these repositories are likely to be based on github/gitlab.
once the hub has been made aware of certain repositories, it is possible to browse, search and field items, based on meta-data and popularity (general and user-specific). criteria can include usage frequency, degree of V&V...
this can then be leveraged from within osparc to search for studies, templates, and services.
note: it can also be a good platform on which to build versioning functionality.
note: we could also have Binder-like functionality to open a search result in oSPARC.
note: the hub is also the 'app store'
note: pull requests in github/gitlab are a valuable workflow for QA (peer reviews, automatic validation...)
implementation idea: hub points to repository. git contains light-weight version-controlled information (incl. scripts) that points to data repositories (S3) and docker registeries.
repositories can be private or public, controlling access, e.g., for privacy or licensing. same is true for data.
The text was updated successfully, but these errors were encountered:
we would like to have a separate hub, which can host templates, studies, and services (distinction is increasingly artificial, but that is another discussion). it draws its content from (potentially multiple) repositories. for items that do not contain heavy data, these repositories are likely to be based on github/gitlab.
once the hub has been made aware of certain repositories, it is possible to browse, search and field items, based on meta-data and popularity (general and user-specific). criteria can include usage frequency, degree of V&V...
this can then be leveraged from within osparc to search for studies, templates, and services.
note: it can also be a good platform on which to build versioning functionality.
note: we could also have Binder-like functionality to open a search result in oSPARC.
note: the hub is also the 'app store'
note: pull requests in github/gitlab are a valuable workflow for QA (peer reviews, automatic validation...)
for illustration, check:
implementation idea: hub points to repository. git contains light-weight version-controlled information (incl. scripts) that points to data repositories (S3) and docker registeries.
repositories can be private or public, controlling access, e.g., for privacy or licensing. same is true for data.
The text was updated successfully, but these errors were encountered: