-
Notifications
You must be signed in to change notification settings - Fork 0
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
Standard.csv merge service #206
Comments
So at dev.data.solidarityeconomy.coop/coops-uk/standard.csv find the csv published for co-ops uk data, but Are the paths different for some reason? @wu-lee |
Where can I find the standard.csv for current dotcoop data? @wu-lee |
It should be there now - the SeOpenData gem was an older version which didn't publish this file, I updated it. |
Dropping this out of the two Epics relating to the Turtle island confereces, as it is a proposed merge solution that is unlikley to be used now. |
Closing this as obsolete @wu-lee |
Is your feature request related to a problem? Please describe.
Merging data about co-ops from different sources can be done in many ways. It has been made easy by the efforts we have put into considering standards for the data we publish, however we have not written any data merging functionality for the data factory and we publish only one map demonstate co-op data set merging, and there, the merging was carried out within Airtable.
Describe the solution you'd like
A function which can be easily called from the data factory that can take the following files:
and merges the 2 csv files where the resultant csv file has the following characteristics:
Describe alternatives you've considered
We have considered doing merging on a co-op by co-op basis as the user selects a co-op, with a Sparql enabled micro service but we believe this may not be very responsive.
Additional context
For ease of incorporation into the Data Factory, the function should be written in Ruby, but there are other factors to consider, so we should consider the options.
There are many other types of merge we can imagine needing in the near future, so it may be worth considering functionality a little more generic than strictly required for this type of merge, if the cost was not too high.
The text was updated successfully, but these errors were encountered: