Export/Import functionality per Exercise

[l00mi]

To make sure uses can save their exercises for later uses and to make it possible to exchange exercises between different instances of the platform we need an export on the level of an exercise.

Not sure if there is a unique Exercise ID? This would be use full if an exercises is imported again on the same platform, to propose it as an update and not have a duplicate.

Also the unique IDs generated by Meteor should be globally unique, so no need to try to come up with something more clever.

[StrubT]

I'll think about it some more and come up with a solution as soon as I have a have a working export/import process.

[l00mi]

Hmm.. This issue is about the export / import process? We like to push this strongly, because it will relax the fear of loosing exercises by the users creating them.

[StrubT]

OK, WILCO. Who is afraid?
But in this case, we probably have to create not just a single import/export but a bulk export as well.
What collections of exercises would you like to be able to export? Just your own? A whole category? A whole language? All of them?

[l00mi]

We were discussing that we might have something like a exercises inventory in the far future. Where exercises can be catalogued and there is a nice interface inside progressor to fetch them. All this might even be based on github, a bit like npm works.

But anyway I think we should have a json file per exercise. I like the idea to export multiple exercises, this should but then trigger the download of multiple json files (or a zip with multiple json files). So that each exercises can be handled separately.

[l00mi]

Once working we might looking into producing valid json-ld.
http://json-ld.org/

[StrubT]

But if you want to export one exercise per file, would that mean I should exclude any references (category, author, editor, release status)?
An imported exercise would then have to be assigned to a category and would be treated as a private exercise of the importer.

[l00mi]

Hmm, I would prefer that this kind of metadata is included in plain-text in this file.

Which means that the import needs to do some logic like looking for the category and referencing correctly or creating a new category.

[StrubT]

• export
• basic import
• advanced import features
  • assign new category

[StrubT]

@l00mi: added basic import functionality (cannot yet re-assign category)
deployed to BFH test environment