1

Ontopia/Liferay integration

TMRA 2010, Leipzig, 2010-10-01

Lars Marius Garshol, <larsga@bouvet.no>Matthias Fischer, <matthias.fischer@fhtw-berlin.de>

2

Agenda

• The integration: why and what• Demo• Conclusion

3

Why and what

4

Why integrate?

• Ontopia• Semantic

technology• Complex metadata• Tools for

conversion/manipulation/creation

• Very limited content support

• Liferay• CMS• Users, permissions,

...• Content features– versioning, ...

• Very limited metadata support

Content from Liferay,metadata from Ontopia

5

How it works

• We want to describe Liferay content in Topic Maps

• In a topic map, everything is topics• Therefore, we need topics for our Liferay

content• The integration creates this for us

automatically

6

Creating and annotating content

Liferay Ontopia

A Liferay Tutorial

A Liferay Tutorial

Liferay

CMS

Liferay, Inc.

USALiferay CE

Liferay EE

Installing Liferay CE

Installing Liferay CE

7

In short

• Create your content in Liferay• Organize it in the topic map

8

Current status

• Prototype integration built by Matthias Fischer– later polished by Lars Marius Garshol– now in a working and fairly well-tested state– has been installed successfully by third

parties

• Working now:– synchronization of users and communities– web content (with structures)– wiki content (partly)– some display portlets

9

Demo

10

Set up your ontology

• Include ready-made Liferay ontology as part of your ontology– make associations across as necessary

11

Write content, as usual

Click save and continue

12

Now you can tag from the topic map

Select topics here. Which fields and topicsare displayed is configurable in Ontopoly.(This is Ontopoly, embedded in Liferay.)

13

Tagged

14

The article topic The integration has created this topic forus and will keep it in sync as we makechanges in Liferay.

15

An example front page

Normal Liferay portlets

YahooTree portlet

Data shown is Los, a governmental classificationscheme published in XTM. The YahooTree portletneeds just two tolog queries to produce this output.

16

Topic page

• Put together from three portlets• Very simple configuration– basically just one tolog query for the whole

page– one association type for the related-topics

portlet

17

Article page

• No configuration at all

18

Status

• This is just an outline, but shows how you can put together a simple site from ready-made components

• A number of components still missing– a similar articles portlet (started)– a search portlet– a breadcrumb portlet (maybe)– a tree view portlet– ...

19

Similar topics

• Takes an input topic– generally an article

• Finds other topics which have similar classifications– sorted by similarity– configurable cutoff

• Currently in progress

http://code.google.com/p/ontopia/source/browse/trunk/ontopia/src/java/net/ontopia/topicmaps/nav2/portlets/pojos/SimilarTopics.java

20

Search portlet

• Actually two portlets– one for the search form– another for the search results

• Also requires search integration with Liferay– achievable by implementing a tolog plug-in

predicate

• Needs to support some configuration– like what topic types to make searchable

21

Breadcrumb portlet

• Many sites want these, so should support it

• Not clear how it should work, however– upwards taxonomy traversal must be part of it– but probably not enough

• Still waiting for ideas on this one

22

TreeView portlet

• Normal hierarchy display• Already exists as a Java

component• Just need to wrap as a

portlet with configuration etc

23

Conclusion

• We believe that the combination of– CMS support via the data integration, and– display support via ready-made portlets

• make it far easier to develop portals with Ontopia