This document discusses options for an open data platform and summarizes key considerations. It notes major advances in tools for search, visualization, deployment, authentication, and the semantic web. While commercial support is not adverse, an open platform is preferred to leverage leading tools and allow for extensions. The development plan outlines using established libraries and technologies like Elasticsearch, Google Charts, and AWS. Current work focuses on mapping and schemas, with additional visualization, authentication, and distribution features in the backlog.

1. Gangplank

2. Name....

3. Drivers
●
Should our open data platform be closed source?
●
Massive advances in tools
●
●
●
●
●
●
●
●
Elasticsearch for faceted search
Visualisation – Gcharts/d3js.org/others
AWS for deployments
Shibboleth Authentication
Google/OpenRefine
Network Effect - Schema Mapping
PubSubHubBub
SemWeb / 4Store / other triple store

4. Drivers
●
●
Not adverse to commercial support
But to leverage leading edge tools, we need a
platform we can extend

5. Development plan
●
DRY
●
CSV/TSV Libraries
●
Elasticsearch as a storage mechanism
●
Google Charts
●
AWS as deployment
●
Wire together in less than a day – Functional CSV
upload, Download, Review.

6. Current Work / Backlog
●
Active
–
●
Mapping and Schemas
Backlog
–
Visualisation
–
Shibboleth
–
Redbridge Download Agent
–
Pubsubhubbub

7. Demo