I’m familiar with Liferay (though I worked on a similar project called uPortal) and content management systems and while the VIVO project will natively support TDB and a fuseki fronted triple store, it’s content management capabilities are good for managing the ontology how resources can be viewed on the site (e.g. What properties will display for a Person) it doesn’t really have the Portal aspect you get with something like Liferay or the flexibility you’d get to create a website like you can do with a CMS like Drupal.
Something that we (and others) have done with VIVO is to use it to manage the data and then use a different platform as a front end (such as Drupal or Blacklight) to provide the end user view of the data. For example, we have faculty profiles in our VIVO instance and a bunch of different department sites that want to show faculty information on their department web sites. Each of those departmental web sites has their own branding and some are using Drupal while others are using a proprietary content management system based on Coldfusion. So we put a fuseki endpoint in front of the triple store then I developed a service that manages “canned” sparql queries and exposes a persistent URL that does something like “give me a list of all faculty in the Chemistry department (along with their user id and full name) and I want the results as JSON. The CMS knows how to render the JSON as a list of Faculty with a link that calls my service and asks for a “detail view” of a specific faculty member with all the semantically related data such as publications, courses taught, etc. I would think that a similar system could be built using Liferay by writing portlets which just make requests to a system like VIVO that managed the semantic data. On 2/11/16, 8:55 AM, "Darko Androcec" <[email protected]> wrote: >Hi, > >thanks all for your answer. By a web portal I mean something like CMS >(content management system), e.g. Liferay, but with native semantic >support. So, something like semantic content management system. For now, >I have found OntoWiki, but it does not natively support Apache Jena >triple store and Fuseki. > >If you have some good tool in mind, I will be glad to take a look at it. > >Thanks, >Darko > >On 10.2.2016. 15:11, John A. Fereira wrote: >> What do you mean by a web portal and what do you want to do with it. >> >> The VIVO project (vivoweb.org) supports TDB and a triple store fronted by >> Fuseki but requires a small configuration change to specify that TDB or a >> Sparql (fuseki) triple will be used by the application. >> >> >> >> >> >> On 2/10/16, 8:59 AM, "Darko Androcec" <[email protected]> wrote: >> >>> Hi all, >>> >>> I am looking whether some web portal exists that natively supports Jena >>> TDB and Fuseki (triple store and SPARQL)? I have experimented with >>> OntoWiki, but it does not support Jena backend. >>> >>> Thanks, Darko >
