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

Development of webservice forms for validation checklists #55

Open
jetschny opened this issue May 16, 2024 · 2 comments
Open

Development of webservice forms for validation checklists #55

jetschny opened this issue May 16, 2024 · 2 comments
Assignees

Comments

@jetschny
Copy link

As for now, several validation checklists are under development or phasing out the UCs.
They are mostly meant to provide guidance and concrete validation steps to follow. Further, the guidance shall be applicable to all current and future use cases execute under FAIRiCUBE and in principle every data science framework. No use case specifics are therefore included and the checklist as the simplified and potentially main output of this deliverable will not contain results of the validation of the processing and ML applications.

It is foreseen to make a webservice form from these checklists with an optional field for comments for each checkbox item and the guidance results with comments can be harvested and provisioned as part of the Knowledge Base services.

A first checklists is available in D3.6
Future checklists will come under D4.6, D5.3, D6.11 ...

Actions arise from this

  • development of web-form that goes beyond MS forms functionality
  • deployment under KB services
  • harvest and provisioning of validation data as part of UC documentation (in KB)
@gmartirano
Copy link

@jetschny, I like the idea.
Proposal: starting from the check-list currently in D3.6, would it make sense to add another column "How to", containing a description of the validation procedure for each item-under-test? The current column "Description" nicely describe "What" and adding "How to" could help.
Comment: your third action "harvest and provisioning of validation data ..." is not entirely clear to me, operationally thinking about how to implement it. Could further brainstorming to start formalising requirements help?

@KathiSchleidt
Copy link
Member

I'm still getting my brain around the validation deliverables and the checklists, but am wondering if such a validation webservice shouldn't be described in the upcoming D1.2 we're trying to get our brains around. After all, D1.2 is the master-task for all separate validation task in each WP and will synchronize, harmonize and collect feedback from all separate validation tasks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants