Dataset description should support markdown and long-form

[JJediny]

Some datasets may need more description and some potential forks could require tweeting the yaml content...

Consider adding a markdown editor to the edit form, the output of which could be combined with the yaml as a single payload to github for the commit:

• https://github.com/NextStepWebs/simplemde-markdown-editor

yaml + --- + markdown === dataset.md --> Github API

Instead of using a hard coded JS web form, we've been considering using a webform that gets generated from a json schema whose output is yaml. This would allow projects/programs with their own established standards or using a common standard like data.json to be the yml model.

• https://github.com/project-open-data/datajson-editor

[timwis]

1. Interesting idea, and I can definitely see the merit in it. That's a nice editor, too. Thanks for the suggestion, definitely sounds doable.
2. Hah, it sounds like we're thinking about the same things. I posted this idea in prose.io's repo a couple weeks ago that sounds pretty similar. This project was what got me thinking of that, but I later got the idea to just build something specific for this project (the HTML form), which would be a bit easier for non-technical users, but less generic/universal like what you mentioned. Definitely interested in the idea though, happy to chat more about it and work on it with you.

[timwis]

Hope it's okay that I've changed the title. Let's chat about your second idea verbally this week.

[JJediny]

Whiteboarding session with @philipashlock

Blue == Current JKAN form/workflow
Red == Proposed JSON schema based editor/workflow
Green == Questions/Issues outstanding also related to Issue #62

[timwis]

Woah - that looks like some great ideas put on a whiteboard, but I feel like I might be less equipped to understand it without the narrative that assumedly accompanied it. Perhaps you can walk us through it a bit?