-
Notifications
You must be signed in to change notification settings - Fork 50
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
Implement a Data Source Interface and add the data from the FOSSASIA and Freifunk Api to loklak through the interface #206
Comments
the server part which receives this information is described in loklak/loklak_server#35 |
FOSSASIA/Freifunk API data consist of community json files that follow this specification https://github.com/fossasia/api.fossasia.net/blob/master/specs/1.0.1.json. To be short, this is the complete list of properties :
List of all available jsons : |
To integrate FOSSASIA/Freifunk API data into loklak, a few questions come up :
Just to clarify things a bit, API data consist of a lot of information about a community, like names, location, services. From the name and location, a community map was built, and now we want to add some filters to it (by country, by tech area..). Sometimes we want to retrieve data directly from services as well (rss, ics feeds..). |
What is your proposal?
We are just getting started with it.
How can we pump all this data to loklak? Actually we diverted from the original meaning of "API" a bit and also included more to it. In my opinion - let's focus with the API on the core topic and let other services display the data e.g. the Freifunk blog, Loklak and others. |
@sudheesh001 Why has this been closed? Where can I test the implementation? |
@mariobehling I think this got closed because of the term |
@sudheesh001 I think you meant |
…ources Issues : #205 #206 Server side requirements : loklak/loklak_server#35 loklak/loklak_server#37 loklak/loklak_server#58 (implemented) loklak/loklak_server#59 (implemented)
This went live http://test.loklak.net/dataConnect |
this push servlet is following the two-steps mechanism described by #74 to push json. it is required to implement fossasia/loklak_webclient#206.
This is what current implementation looks like, with loklak_server new feature loklak/loklak_server#83: TODO :
|
This feature can be reviewed at http://loklak-client.danghaian.com/dataConnect |
@zyzo Nice! loklak-client seems to be down though. Cannot test. |
My bad, @mariobehling could you please test again ? |
There is an unknown problem with twitter auth indeed, but the datasource interface can currently work without logging in to twitter. |
Ok, a few questions. I could see my connections without logging in.
|
In short the interface is a visual way to construct push query to |
|
This is really just a json file that serves http://cmap-fossasia-api.herokuapp.com/ffGeoJson.json, nothing important (It is Then, user will be able to add pure fossasia api data.
Import and user shoudn't appear, I will remove them. They exist because SourceType was used for a different purpose SourceType.java.
As explained in http://loklak.org/api.html#geojsonpush, the mapping rule (parameter loklak/loklak_server#55 (comment) |
Interface to add fossasia api data : If no format is specified in route parameter EDIT : Live at http://loklak-client.danghaian.com/addConnection/fossasia_api |
Currently loklak-client is not available. If the format is not specified, we should have a validation form, that automatically matches the right format. This can be a follow up issue. Regarding the import of API data, please have a look how other services like mailchimp do this: http://kb.mailchimp.com/lists/growth/import-subscribers-to-a-list |
Ok, let's iterate and get this going in the above way first. Thanks! |
It is now possible to add Freifunk & FOSSASIA data via the interface. Please refer to : |
Here is an idea draft how data can be added through the interface.
![loklak-datasources-connect-services](https://cloud.githubusercontent.com/assets/1583873/8267842/8eb5f954-176f-11e5-8fa4-7c98fe2f9c9a.png)
This issue is related to #205
The text was updated successfully, but these errors were encountered: