Open almereyda opened 10 years ago
Hi Jon,
You're right, it's not clear how to contribute content. We previously used a flat-file DB to create data, but a few months ago we switched to a GUI editing system -- hence the migration technique and outdated documentation.
You can access this GUI at /graphs/edit/new or http://www.metacademy.org/graphs/edit/new (you'll need an account in order to have your contributions saved).
I'm going to send out editing instructions for beta users soon, I'll include you in this email =)
Also, it probably does make sense to migrate to a semantic data store at some point, but I'm not entirely sure why this would be worth the substantial migration effort. Any thoughts?
Where is the database? I am interested in seeing if I can make it semantic. After looking at the flat files repo, at least some of it can be a straight forward mapping.
By browsing the code and the other repository (
metacademy-content
) it becomes evident, there is a way to (a) create and (b) use a flat file database and to (c) migrate it to the django database.Unfortunately, the instructions over at the content repository seem to be a little dated. The current application README also doesn't state a word about the
-content
repo. I suppose it is still used, by looking at the use ofCONTENT_PATH
within Metacademy, but I doubt it is being called by Django or within the context of theMakefile
.I would love to create my own concepts and fit them into my own roadmaps. As an editor is lacking for the moment, I had a look at the SQLite database and immediately gave up.
Migrating from flat files appears to be an option, though. If I could only understand how to use them or even how to create a JSON like the fixture initially being loaded during
make
, asloaddata
is being used, butdumpdata
not.