You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stanbol.apache.org by Raffaele Palmieri <ra...@gmail.com> on 2014/02/18 16:50:44 UTC

Content hub & Cms adapter

Hi to all,
I see that Cms Adapter and Content Hub modules are no longer present in the
trunk, while they are still present in release 0.12.
Have been merged or moved to other modules, or are no longer in
development?
Thank you in advance,
cheers,
Raffaele.

Re: Content hub & Cms adapter

Posted by Reto Gmür <re...@wymiwyg.com>.
Hi Rafa

I think the most descriptive technical document or using the RES API is the
ontology used which  is here:
https://github.com/fusepool/fusepool-ecs/blob/master/ontologies/src/main/resources/eu/fusepool/ecs/ontologies/ecs.ttl

As for the implementation ECS stores everything in RDF. The contents of the
documents as well as some selected metadata are stored in the content graph
which is indexed used Clerezza CRIS which uses lucene.

The advantage is that there is no disconnect between the RDF and the index.
Also by not exposing Solr endpoints there is no way to circumvent Stanbol
security accessing the data.

I hope that I demo instance to check out the UI (which is in a separate
project).

Cheers,
Reto



On Thu, Feb 20, 2014 at 6:33 PM, Rafa Haro <rh...@apache.org> wrote:

> Hi Reto and all,
>
> I'm quite interested in fusepool alternative but so far I'm not been able
> to find more (maybe technical) details in order to have a formed opinion
> about its differences with current ContentHub. I would like to see
> ContentHub and CMS Adapter components back in the trunk, so what do you
> think about open a discussion for further and necessary improvements in
> both components. First of all, I really would like to understand better the
> fusepool approach as Semantic content store.
>
> For CMS Adapter, we have been widely working with Apache ManifoldCF and in
> my opinion this project fits perfectly for fulfilling CMS Adapter
> requirements. Current features could be "easily" reproduced using Manifold
> and the advantage of using this project is the availability of a large
> ready-to-use connectors for several data sources and content repositories.
> I can provide here more details if it is needed.
>
> Cheers,
> Rafa
>
> El 18/02/14 17:17, Reto Gmür escribió:
>
>  Hi Raffaele
>>
>> The contenthub developer didn't show up for a long time so it was never
>> migrated to the 1.0 branch.
>>
>> You might be interested in https://github.com/fusepool/fusepool-ecs and
>> it's fronted for drill down search
>> https://github.com/fusepool/fusepool-firstswim they provide similar
>> functionality as contenthub but the facets are actually RDF entities while
>> in contenthub they only existed within Solr.
>>
>> If there is interest the fusepool project would be afaict be more than
>> happy to contribute these two projects to Stanbol.
>>
>> Cheers,
>> Reto
>>
>>
>>
>>
>>
>> On Tue, Feb 18, 2014 at 4:50 PM, Raffaele Palmieri <
>> raffaele.palmieri@gmail.com> wrote:
>>
>>  Hi to all,
>>> I see that Cms Adapter and Content Hub modules are no longer present in
>>> the
>>> trunk, while they are still present in release 0.12.
>>> Have been merged or moved to other modules, or are no longer in
>>> development?
>>> Thank you in advance,
>>> cheers,
>>> Raffaele.
>>>
>>>
>

Re: Content hub & Cms adapter

Posted by Rafa Haro <rh...@apache.org>.
Hi Reto and all,

I'm quite interested in fusepool alternative but so far I'm not been 
able to find more (maybe technical) details in order to have a formed 
opinion about its differences with current ContentHub. I would like to 
see ContentHub and CMS Adapter components back in the trunk, so what do 
you think about open a discussion for further and necessary improvements 
in both components. First of all, I really would like to understand 
better the fusepool approach as Semantic content store.

For CMS Adapter, we have been widely working with Apache ManifoldCF and 
in my opinion this project fits perfectly for fulfilling CMS Adapter 
requirements. Current features could be "easily" reproduced using 
Manifold and the advantage of using this project is the availability of 
a large ready-to-use connectors for several data sources and content 
repositories. I can provide here more details if it is needed.

Cheers,
Rafa

El 18/02/14 17:17, Reto Gmür escribió:
> Hi Raffaele
>
> The contenthub developer didn't show up for a long time so it was never
> migrated to the 1.0 branch.
>
> You might be interested in https://github.com/fusepool/fusepool-ecs and
> it's fronted for drill down search
> https://github.com/fusepool/fusepool-firstswim they provide similar
> functionality as contenthub but the facets are actually RDF entities while
> in contenthub they only existed within Solr.
>
> If there is interest the fusepool project would be afaict be more than
> happy to contribute these two projects to Stanbol.
>
> Cheers,
> Reto
>
>
>
>
>
> On Tue, Feb 18, 2014 at 4:50 PM, Raffaele Palmieri <
> raffaele.palmieri@gmail.com> wrote:
>
>> Hi to all,
>> I see that Cms Adapter and Content Hub modules are no longer present in the
>> trunk, while they are still present in release 0.12.
>> Have been merged or moved to other modules, or are no longer in
>> development?
>> Thank you in advance,
>> cheers,
>> Raffaele.
>>


Re: Content hub & Cms adapter

Posted by Reto Gmür <re...@apache.org>.
Hi Raffaele

The contenthub developer didn't show up for a long time so it was never
migrated to the 1.0 branch.

You might be interested in https://github.com/fusepool/fusepool-ecs and
it's fronted for drill down search
https://github.com/fusepool/fusepool-firstswim they provide similar
functionality as contenthub but the facets are actually RDF entities while
in contenthub they only existed within Solr.

If there is interest the fusepool project would be afaict be more than
happy to contribute these two projects to Stanbol.

Cheers,
Reto





On Tue, Feb 18, 2014 at 4:50 PM, Raffaele Palmieri <
raffaele.palmieri@gmail.com> wrote:

> Hi to all,
> I see that Cms Adapter and Content Hub modules are no longer present in the
> trunk, while they are still present in release 0.12.
> Have been merged or moved to other modules, or are no longer in
> development?
> Thank you in advance,
> cheers,
> Raffaele.
>