Hi Fabian, as I wrote, currently it seems that all the enhancements are stored in one triple collection that is configured somewhere in the code, I have still to find out where exactly. The use case is simply to being able to use a different triple collection/graph so that all the enhancements extracted by a chain will be stored in that triple collection. This can be achieved in two ways
- as an additional parameter when a document is sent to a contenthub so that the user could choose the chain the document must go through and the graph in which he/she wants to store the enhancements - as a configuration property of chains to be set from the Felix console In the second way, maybe the easiest one, it would mean to add a property to enhancement engine or chain to configure the URI of the triple collection to use. I have to figure out to do that at run time from the Felix console but it should be possible as components that are EnhancementEngine, that have a configuration policy "optional" already have properties like name and ranking. Chains have configuration policy "require" so maybe it would be better to add to them such property. Best Luigi 2013/2/19 Fabian Christ <[email protected]> > Hi, > > could you describe your use case? When would such a property makes > sense and what is the desired behavior that you have in mind? > > Best, > - Fabian > > 2013/2/19 Luigi Selmi <[email protected]>: > > Hello, > > > > it seems that all enhancements are stored in a single triple collection > > org.apache.contenthub.enhancements. It will be useful to add a property > to > > chains/enhancers to be set at run time from the felix Console to address > > different triple collections. Does it make sense ? > > > > Best > > > > Luigi > > > > -- > Fabian > http://twitter.com/fctwitt >
