DKAN

Not exactly. We're still thinking about the best way to integrate efforts here with DKAN efforts—ideas are still evolving. After speaking with people at the sprint today, it's beginning to see like there are essentially three strategies for making sites opendata compliant:

• Use open data to quickly generate a node type, view, and manually populate dataset nodes. This is for an MVP (minimal viable product)
• Use DKAN dataset to set up a few content types, and bring in more robust features like mapping tools, organic groups, internal node references, etc.
• Use the DKAN distribution to provide a full-on data portal.

We'd like to find a way to have the Open Data feature play well with the DKAN Dataset module. The two current ideas are:

1. Allow DKAN Dataset to extend the Open Data features definitions
2. Provide a migration path between Open Data and DKAN so that sites can use Open Data to quickly comply by Nov 9, and then move to DKAN as their site matures

The first option seems to get trickier the more with think about it. The main issue that is we allow DKAN to change an existing field, the data stored in that field will be lost. We're considering bundling a migrate class that would aid in easily transitioning from Open Data to DKAN.