Proposed API structure

[MansMeg]

Hi!

Here is my proposed structure of the data repository apis. Feel free to comment.

[BobBorges]

Quality estimation is also a kind of test and uses similar conceptual workflows. I'm not sure I see the point in a separate folder. Instead:

test/                    # quality estimation code goes here along with integrity tests
test/data                # data goes here
test/quality-estimates   # versioned quality estimations

[ninpnin]

I would keep the gold standard data in its own folder.. test is very generic and only partially applicable

[MansMeg]

Ok. Whats your suggested solution Väinö?

[ninpnin]

Add a gold-standard folder

[MansMeg]

So your suggestion is like this (I called gold standard data quality-data):

test/                    # quality estimation code goes here along with integrity tests
test/test-data                # data used in data integration tests goes here
test/quality-estimates   # versioned quality estimations
test/quality-data   # data used for quality estimation goes here

[fredrik1984]

@ninpnin what do you think of this Väinö?

[ninpnin]

Sorry this is very late, but I would have the gold standard completely outside the test folder. What do you think?

[MansMeg]

How would you store it?

[ninpnin]

Have a quality-data folder in the project root, at the same level as test etc. But I'm not necessarily planning to die on this hill

[MansMeg]

I agree with you here. So maybe have something like this:

/quality/... -> scripts used for quality estimation /quality/data/... -> data used for quality estimation /quality/estimates/... -> estimates by version stored for easy access

ie mirror the test folder structure.

[MansMeg]

Now I have updated the file with the decision we discussed. @fredrik1984 , you can now merge this.