The more I understand the design model of Perkeep, I feel the same that it could be used as the distributed back end for a variety of NoSQL database models including Graphs.
For a Graph DB, I think you would need an in memory db that sits above Perkeep which abstracts the away the mechanics and extends performance. The Graph DB consistency mechanisms would be the tricky part to get right. My first thought would be to start with IndraDB <https://github.com/indradb/indradb>. Looks like a very promising project. On Saturday, 20 October 2018 06:29:21 UTC-4, dan.kortschak wrote: > > The initial design criterion is to get something that I can use for > recording my research in a reasonably way. A wiki is sort of what is > wanted, but the links between topics don't have attributes other than > connectedness between them. I want to encode things like "supports", > "refutes", "suggests", "depends" etc. This allows graphical analysis of > the results, hypotheses and conclusions. > > The approach to storage that perkeep has is a good fit because of the > native deduplication and the immutability of data. > > > On Sat, 2018-10-20 at 11:44 +0200, Simon B. wrote: > > > > > > I'm attempting to construct a science lab > > > notebook system that keeps experimental results, result > > > interpretations > > > and other notes in a way that can be used to store and extract > > > argument > > > graphs for research projects. > > > > > To be shared among users? Topics? Needs a timeline for lookup? Would > > a > > wiki-like system backed up to get timeline feature and permanent > > persistence be a good fit? > > > > > > > > > -- You received this message because you are subscribed to the Google Groups "Perkeep" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
