neo4j-contrib
change the edit page to allow full fledged editing + add status
Perhaps we can make the manage re-use the submission page layout for the edit page, so that we can also adapt tags, images, authors or other things? And only add the field for the status?
I see a couple of problems with re-using the submission page:
- We don't need (I think) the same required fields checking / stars
- The submission page is a bit of a hack and a non-trivial cypher query is done to create the Gist, Person, Domain, and UseCase nodes.
It would be much cleaner to have separate pages for managing gists, people, domains, etc... That actually makes me think that the neo4j-meta_model project might be ideal. I've actually just recently gotten it to a minimum viable product state. I'll try deploying it to heroku and point it at the database and you can have a look at what I mean.
Which required fields do we not need?
I was just speaking about the UI, not the endpoint creating stuff. Actually one could separate that out into nice, separate queries. That endpoint would be updating anyway, only not necessarily creating new stuff.
Maybe we need the same required fields. I guess I was thinking an admin page should be more flexible, but I'm not sure why I thought that.
And I would love to separate them into separate queries, but callbacks in node make doing a query and then doing another query based on that awkward, and the way that models/querying are set up in the graphgist-cms project make it even more awkward.
I set this up quickly as an example:
https://infinite-temple-4355.herokuapp.com/
For the basic auth credentials, look at the heroku config for the graphgist-cms (I reused the username/pass). Clicking on "view" for gists is broken, for some reason which I'm looking at, but edit works. Feel free to peek into the admin section, but it is also a bit buggy.
I've fixed the bug with the gists not displaying. Let me know what you think. I've got lots of thoughts on where to take the project, but do you think it works as a basic CRUD UI?
Does GraphineDB do regular backups, or do you need to export to make a backup? I was wondering because your other issue about thinking that data was lost made me nervous and the neo4j-meta_model UI makes it easier to mess with the data