Skip to content
This repository has been archived by the owner on Jul 6, 2023. It is now read-only.

Documentation : usage of flat file database unclear #50

Open
almereyda opened this issue Aug 10, 2014 · 2 comments
Open

Documentation : usage of flat file database unclear #50

almereyda opened this issue Aug 10, 2014 · 2 comments

Comments

@almereyda
Copy link
Contributor

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 of CONTENT_PATH within Metacademy, but I doubt it is being called by Django or within the context of the Makefile.

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, as loaddata is being used, but dumpdata not.

Is kmap intended to evolve into that direction, of an editor?

Additionally: Would it make sense to decouple the application from the storage layer and investigate triple/quad stores(any SPARQL capable RDF store, levelgraph, LDP/LDF/Hydra...), graph databases (Neo4j, ArrangoDB) or even more intermediary systems like Falkland CMS or Federated Wiki in regards of the ease they might deliver?

@cjrd
Copy link
Member

cjrd commented Aug 10, 2014

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?

@zmughal
Copy link

zmughal commented Apr 3, 2015

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants