Database structure for recommendations.

[stuartlynn]

Design the tables to represent recommendations. key columns will include

• name : name of the resource
• url: Where the resource lives
• type : blog / github / dashboard etc
• submitor : person who submitted the resource
• approved: if the resource was approved or not
• automatic: is this an automatically generated resource or a user submitted one.

Then we prob need a a many to one join column between datasets and resources.

[jpsyx]

Blocked until recommendations feature is scoped

[jpsyx]

Switching to "frozen" because there are no imminent plans on scoping, but this is in the roadmap.