Closed wmeyers closed 10 years ago
Refinery reads from etsource/data/datasets
. @antw and @dennisschoenmakers, is this the final location from which atlas
and refinery
read the csv's, or is this just a convenient location for now?
is this the final location from which atlas and refinery read the csv's, or is this just a convenient location for now?
I don't know if this exact location is permanent or temporary, but I do think the CSVs belong in ETSource. After all, the queries live in ETSource...
When we finally kill InputExcel, everything in ETSource's data
directory will be moved to the top directory, i.e. data/nodes
becomes nodes
, data/datasets
becomes datasets
, etc.
If the current arrangement isn't ideal, does anyone have suggestions for what we could improve?
On the other hand:
etsource
. etsource
It's a bit of a dilemma, because on the one hand it makes complete sense to put the CSV's in etsource
, since that's where the queries live. On the other hand it seems logical to keep them with wherever the Excel analyses are going to be living. I think keeping them in two places produces some risk of deviation between what we think is used by Refinery, between what is actually there. So I guess we should choose.
@antw, I'm not trying to get a definite answer from you at the moment on what it should be, but just would like to hear your ideas. I think this is also something that @dennisschoenmakers and @AlexanderWirtz have an important say in.
I believe this issue can be closed, @wmeyers ?
Seems like a good idea. Closing!
@antw, we are now thinking about the file structure in which the Excel analyses are going to output the csv's with EB, shares, etc. We are thinking of a separate repository, but I'm not sure if that's what you intended. Have you and @dennisschoenmakers thought about this?
@ChaelKruip and @jorisberkhout should also be aware of this ticket.