GA4GH Web components are the reusable custom elements that can be utilized in your web apps & web pages independently irrespective of what framework/library you are using to build the frontend.
Is your feature request related to a problem? Please describe.
One problem with cloud-based analysis in the life sciences is that most data is not yet available in cloud-compatible storage solutions, and data being generated is still largely managed on legacy compute centers or invidiual researcher's laptops. Therefore, web portals that try to operationalize GA4GH Cloud-based analytics, such as Krini will need the ability to upload or import data into a storage backend that the web portal can interact with. This will require a client that directly interacts with such a storage backend.
Describe the solution you'd like
Implement a Web Component for the S3-based object store MinIO. The client should support basic operations on data (put/sync, delete, manage permissions) to address the use cases mentioned above. Note that this may require the use/packaging of multiple reusable child components or the reuse of already exisiting ones. Before starting the implementation, please draft a brief design proposal. Include how you imagine the compoment to interact with components #32 and #34.
Is your feature request related to a problem? Please describe.
One problem with cloud-based analysis in the life sciences is that most data is not yet available in cloud-compatible storage solutions, and data being generated is still largely managed on legacy compute centers or invidiual researcher's laptops. Therefore, web portals that try to operationalize GA4GH Cloud-based analytics, such as Krini will need the ability to upload or import data into a storage backend that the web portal can interact with. This will require a client that directly interacts with such a storage backend.
Describe the solution you'd like
Implement a Web Component for the S3-based object store MinIO. The client should support basic operations on data (put/sync, delete, manage permissions) to address the use cases mentioned above. Note that this may require the use/packaging of multiple reusable child components or the reuse of already exisiting ones. Before starting the implementation, please draft a brief design proposal. Include how you imagine the compoment to interact with components #32 and #34.