SQLite Directory deployed on each commit

[costrouc]

This is a WIP. Will add travis ci for build and sqlite database potentially will be stored in github pages? Not sure maybe deployed somewhere with datasette.

All Submissions:

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Data Submissions:

1. Does your submission pass tests?
   • valid yaml
   • follows template for the data type submitting.
2. Have you lint your code locally prior to submission?

New Feature Submissions:

1. Does your submission pass tests?
2. Have you lint your code locally prior to submission?

Changes to Core Features:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you successfully ran tests with your changes locally?

[costrouc]

@alexpawlowski what are your thoughts of this current code? This is a bare minimum working version and it would be nice to know additional thing that would be nice to have. The only dependncy of pyyaml ... which is necessary in this case.

General process. Take all metadata files of a given category (for example "organizers") and flatten the namespaces. Then with the flattened namespaces generate a sqlite table schema and insert each file. Currently tags in groups and group in organizers are skipped becuase lists require a many to many relationship table to be formed (certainly something that could be added).

Future work (could be in this PR).

• integrate with travis to auto commit the sqlite database to github pages?
• integrate with travis to auto publish to heroku/google cloud for rest json api of sqlite database via dataset (this would be extremely neat) see this motivation https://www.youtube.com/watch?v=lmP75mp3-Rg&t=79s
• add support for many to many relationships
• enable full text search https://datasette.readthedocs.io/en/stable/full_text_search.html

Happy to hear your input!

[alexpawlowski]

@costrouc can you add a sample sqlite file? I'd like to see if it meets the format of what @wigging was thinking.

[alexpawlowski]

To make this process simpler @costrouc I have removed tags from the yml files in my latest commit 0b9ebfb. Only @wigging and I were using those, and that information could be pulled from the description of each meetup, or we could add that functionality back (currently not using). In addition spaces have been consolidated.

[alexpawlowski]

Additionally, I have forced the yml files to be consistent, showing entries within each yml file as blank if there isn't a value. (Before if it was blank, the field often wasn't found in the yml file)

[wigging]

This is the SQLite database file (knoxdevs.db) I created for the iOS app.
https://github.com/knoxcocoa/knoxdevs/tree/master/knoxdevs/Database