SurvLoop is an open data engine used to create, fill, and share complex databases.
Back in the day we created database tables, queries, forms, reports, and pages with Microsoft AccessTM (and probably today, but who would). This is a full content management system that can generate mobile-friendly forms as complex as TurboTaxTM.
Translating each data field's meaning (in English) as you build your database, means computer-friendly API data listings and schema can be auto-generated once you start collecting data. In this way, these have ample documentation for human researchers worldwide.
Because the tools to create complex forms continue to become more useful, it was a logical next step to reuse them to generate complex pages for the rest of a website's main content. The basics needs are just about complete!
Another round of bells and whistles will be completed by ealry 2018. And the goal is to significantly improve all the admin editing tools by the end of 2018.
And hopefully by the end of 2019, almost all of the admin tools will be replaced with SurvLoop-generated forms, to also approach the status of a being self~replicating GUI!
A theme is branching trees, in many directions. Fractals are fun.
SurvLoop is a Laravel-based engine for websites dominated by the collection and publication of open data. This is a database design and survey generation system, though it will increasingly be a flexible tool to solve many web-based problems.
It is currently in continued, heavy development, with much happening here in early 2018, almost ready to go live. I plan to provide more documentation in the coming weeks. Thank you for your interest and patience!
This was originally developed to build the Open Police system. So until the SurvLoop installation processes automates everything, plus the bell & whistle options, please check out the Open Police package for an heavy example of how to extend SurvLoop for your custom needs. (Lighter examples coming online soon!-)
The upcoming Open Police web app is the best live beta demo of the engine's end results, and feedback on that project and the SurvLoop user experience can be via the end of the submission process:
The resulting database designed using the engine, as well as the branching tree which specifies the user's experience: /db/OP
Among other methods, the resulting data can also be provided as XML included an automatically generated schema, eg.