Hi Som,

if you use the Contenthub to submit content you can access the results by using

* the RESTful API of the Contenthub featured search
{stanbol}/contenthub/contenthub/search/featured
* by using SPARQL with the {stanbol}/sparql endpoint to query in the
enhancements of all submitted ContentItems
* by using the Solr RESTful API at
{stanbol}/solr/default/contenthub/select?q=*:*

best
Rupert

On Tue, Mar 5, 2013 at 6:00 AM, Reto Bachmann-Gmür <[email protected]> wrote:
> Hi Som
>
> The stanbol enhancer is a stateless service. Neither the submitted data nor
> the computed enhancements are stored. The contenthub is a stanbol component
> that actually stores enhancements as well as the uploaded documents.
>
> For an example on how to store data persistently as well as how to access
> the data in the entityhub referenced and managed sites you can have a look
> at the skeleton project created by the statefull-webmodule archetype. The
> data in the entityhub should be accessed via the entityhub API so to be
> independent of the use storage backend.
>
> See
> http://mail-archives.apache.org/mod_mbox/stanbol-dev/201302.mbox/%3ccalvhuexpggyhnaonwcbpt2wgov4kjfkca5fhlq7sgbjkcm1...@mail.gmail.com%3Efor
> archetype usage instructions.
>
> Cheers,
> Reto
>
> On Tue, Mar 5, 2013 at 5:36 AM, Som Satpathy <[email protected]> wrote:
>
>> Hi All,
>>
>> I have a general query regarding persistence of content and their
>> enhancements in Stanbol. Based on my readings so far, I understand that all
>> new content posted into an enhancement chain are persisted along with their
>> enhancements in a Solr index (the default one being called contenthub). Am
>> I correct in my understanding?
>>
>> If yes, I have been trying to figure out where exactly can I locate the
>> Solr index in my Stanbol instance. I would appreciate if any of you could
>> throw more light on this?
>>
>> Thanks,
>> Som
>>



--
| Rupert Westenthaler             [email protected]
| Bodenlehenstraße 11                             ++43-699-11108907
| A-5500 Bischofshofen

Reply via email to