Steps towards submitting the product to GA4GH about refget HOT 6 OPEN

Note these should be considered not in order

from refget.

It would be nice to have the compliance suite output report follow this schema so that it can be easily integrated into the testbed platform in the future.
I plan to move all the reusable components in the DRS compliance suite (https://github.com/ga4gh/drs-compliance-suite/tree/yp_add_test_cases_object_endpoint) to a common repo. But unfortunately, we are not there yet. In the meantime, I am available to discuss/ brainstorm so we are on the same page and are not duplicating any efforts.

from refget.

Hi @yash-puligundla can you give us an update on this? I think we're ready for some help with starting to implement a compliance suite at this point.

from refget.

Hi @nsheff. As of now, we haven't proceeded with migrating the common code into a library.
Could you please provide an estimate of the timeframe within which you would like this common code library to be available?

I'm also looping in @jppay, our new team lead, to this conversation.

from refget.

@andrewyatz can you talk about timeline here? I think we're wanting to move forward on this now, and I think we were targeting something in January, but I'm not exactly sure what that is. Can you give us a timeline and a bit more specifics on this?

from refget.

For information here are the documentation that we filled in for the RefGet v2 product approval:

• Product approval questionnaire: https://docs.google.com/document/d/1p-zlQrhCCBHOo6BCmhuIjFWXJz9ScV2R/edit
• REWS & DSWS: https://docs.google.com/document/d/1ZAhUJ2Ns0VCOiHmIt8Glr17w2COlvXrp/edit#heading=h.gjdgxs
• Timeline: https://docs.google.com/document/d/1SpnyONLNta21ZVW97oiVYrYeujcnVGhR/edit#heading=h.gjdgxs

Note that the forms might have changed.

from refget.