Hi Rick,

I'm storing binary content in the file system and keep a pointer to the 
file (url) as a node property.

Greetings

Axel



On 21.01.2011 00:00, Rick Bullotta wrote:
> Axel, are you storing the actual content in Neo or in the file system
> directly (or some other datastore)?  I've been told not to use Neo for
> blob/large text storage. Curious what approach you're taking.
>
> Best,
>
> Rick
>
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On
> Behalf Of Axel Morgner
> Sent: Thursday, January 20, 2011 3:15 PM
> To: [email protected]
> Subject: Re: [Neo4j] Neos4j and ECM
>
> 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
>

_______________________________________________
Neo4j mailing list
[email protected]
https://lists.neo4j.org/mailman/listinfo/user

Reply via email to