The content tree can be made out of CHILD relationships, content items can be mapped to nodes of a certain type (e.g. folder, file, image, pages, etc.), content item properties like name, date and type-specific data could be mapped to node properties.
File operations (add, move, copy, delete) alter relationships and create/delete nodes. Access control can be realized with the ACL pattern [1] as described in the Neo4j wiki). IMHO, every ECM use case can be easily modeled with a graph DB. Axel [1] http://wiki.neo4j.org/content/ACL Am 20.01.2011 20:50, schrieb kyle adams: > How would you translate a content model and the processes around that > content model to the graph DB design? > On Jan 20, 2011 2:46 PM, "Axel Morgner"<[email protected]> wrote: >> Hi Kyle, >> >> currently I'm working on a ECM solution based on Neo4j which will be >> released as open source soon. >> >> Do you have any specific questions? >> >> Greetings >> >> Axel >> >> Am 20.01.2011 19:38, schrieb kyle adams: >>> Neos4j is very intriguing, but I'm not sure how it would fit into > existing >>> (or new for that matter) ECM use cases. Any ideas? >>> >>> -- *Kyle * >>> _______________________________________________ >>> Neo4j mailing list >>> [email protected] >>> https://lists.neo4j.org/mailman/listinfo/user >> >> _______________________________________________ >> Neo4j mailing list >> [email protected] >> https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user -- Axel Morgner Creative Solutions - Software Engineering GUI& UX Design - Project Management c/o inxire GmbH Hanauer Landstr. 293a 60314 Frankfurt Germany Phone +49 151 40522060 E-mail [email protected] Web http://www.morgner.de _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
