Tagging Aware Portlets

1. The 9th International Conference on Web Engineering June 25th, 2009 Tagging Aware Portlets Oscar Díaz, Sandy Pérez and Cristóbal Arellano ONEKIN Research Group University of the Basque Country San Sebastián (Spain)

2. Agenda • Background • Problem statement • Tagging through portals can lead to tagging data scattering • Contribution • Portal tagging commodity • Conclusions

3. Background What is a corporate portal? What is social tagging? Corporate portal + social tagging What is a portlet?

4. Personalization Localization A web application whose main focus is on integration and pesonalization Aggregation of content Content Management Messaging & Collaboration Enterprise Search Security Content Presentation Customization & Personalization Workflow E-mail Discussions Calendar Wiki Blogs What Is a Corporate Portal? Browser Portal Content Management Aggregation of content Enterprise Search Messaging & Collaboration Content Presentation Security Workflow Customization & Personalization

5. web2.0 Peter javascript Bob ajax ajax What Is Social Tagging? • Social Tagging = <resource,user,tag> • <Ajax: The Definitive Guide,Peter,ajax> • <Ajax: The Definitive Guide,Peter,javascript> • <Ajax: The Definitive Guide,Bob,web2.0> • <Ajax: The Definitive Guide,Bob,ajax>

6. Portals & Social Tagging: Company Perspective • Advantages • Harnessing collective intelligence • Creating links to connect information together • Intelligent content suggestions • Effective enterprise search and discovery • The DOGEAR experience • Enterprise tagging service saves IBM $4.6 million a year.

7. Portals & Social Tagging: Employee Viewpoint • Advantages: • Future retrieval • Contribution and sharing • Attract attention • Play and competition • Self presentation • Opinion expression (Marlow et al.)

8. What Is a Portlet? • A Java technology based Web component. • Managed by a portlet container. • Processes requests and generates dynamic content. • Are used by portals as pluggable user interface components that provide the presentation layer of Information Systems. …

9. Remote Portlets www.amazon.com I N T E R N E T Producer provides portlets as presentation-oriented web services that can be used by aggregation engines. Consumer consumes presentation- oriented web services offered by content producers. ? dblp.uni-trier.de

10. Presentation-oriented web services Traditional Web Services Portlets as Presentation-Oriented Web Services INTERNET INTERNET

11. Problem Statement Antecedents The problem

12. Tagging through Dedicated Sites (e.g. Delicious) • Delicious is self-sufficient. • all is needed for tagging (i.e. resources, users & tags) is kept within the tagging site • Delicious is self-centered. • all Delicious care about is its own resources, users and tags. • No links exist with other tagging sites.

13. Tagging through a Portal • Current approaches: • Tagging as part of an integrated application • Tagging as a portal functionality

14. A third-party provider offers tagging capabilities on its own (e.g. amazon) Drawbacks… collective intelligence is created outside the company every provider is a tagging island Tagging as Part of an Integrated Application REMOTE Resource REMOTE Resource Tag User User Tag < , , > INTERNET

15. The portal offers tagging for its own content (this is the current approach) Advantage collective intelligence is retained in the context of the organization Disadvantage tagging is restricted to those resources within the realm of the portal. Tagging as a Portal Functionality LOCAL Resource LOCAL Resource Tag Tag User User < , , > INTERNET

16. Tagging data is scattered!! At the portal for local resources At the remote place1 for resources at place1 At the remote place2 for resources at place2 Problem Statement Tag User User LOCAL Resource Tag LOCAL Resource < , , > REMOTE Resource REMOTE Resource Tag User Tag User < , , > INTERNET

17. Contribution Portal tagging commodity Challenges & their solutions

18. Portal Tagging Commodity: What Is a Commodity? • A commodity is a general functionality to be used by other services • Services realized through portlets

19. Homogenous tagging of resources no matter where they reside Tagging data of external resources (e.g. amazon books) does not leak outside the company Portal Tagging Commodity:Vision & Aims Tag User User LOCAL Resource Tag LOCAL Resource < , , > REMOTE Resource REMOTE Resource Tag User Tag User < , , > INTERNET

20. Homogenous Tagging of Resources tag user INTERNET INTERNET resource <publication> resource <book>

21. Tagging Data Retention within the Organization tag user tag user INTERNET INTERNET resource <book>

22. Portal Tagging Commodity: Design Requirement • Tagging must be conducted at the place tag-able resources are rendered (i.e. the portlet)

23. Vision Realization: Challenges • Tag-able resource identification • What can be tagged? • Tagging functionality location • Where is tagging conducted? • Location transparency • Tagging data query span over all resources no matter where they are located

24. Challenge: Tag-able Resource Identification • How can portlets make the portal aware of their tag-able resources?

25. The main means for portlet-to-portal communication is the markup fragment We propose to annotate this markup with tagging concerns using RDFa To this end, an ontology –PartOnt– is defined, which should serve to indicate what to tag Facing the Challenge … user tag INTERNET resource

26. Example: Identifying Tag-able Resources <div xmlns:books=“http://www.amazon.com/books/” xmlns:partont=“http://www.onekin.org/.../partont.rdfs#”> <table about="[books:${book.ISBN}]"> <tr> <td><img src="http://..."/></td> <td> <table> <tr> <td><strong>Ajax: The Definitive Guide </strong></td> </tr> <tr><td>by Anthony T. Holdener</td></tr> </table> </td> </tr> </table> … </div> <table> <tr> <td><img src="http://..."/></td> <td> <table> <tr> <td><strong>Ajax: The Definitive Guide </strong></td> </tr> <tr> <td>by Anthony T. Holdener</td> </tr> </table> </td> </tr> </table>

27. Challenge: Tagging Functionality Location • Tagging must be conducted at the place tag-able resources are rendered (i.e. the portlet markup fragment). • However, portlets should not deliver their own tagging functionality which should be provided by the portal. • That is, portals own the tagging front-end (i.e. tagging widgets) that needs to be injected into the portlet markup. • How can the portal know where to inject these widgets?

28. Facing the Challenge … • The PartOnt ontology should also serve to indicate where to tag. • To this end, a Hook class is included, with a subclass TagListHook that denotes an extension point for adding markup to show/update the tag list.

29. <div xmlns:books=“http://www.amazon.com/books/” xmlns:partont=“http://www.onekin.org/.../partont.rdfs#”> <table about="[books:${book.ISBN}]"> <tr> <td><img src="http://..."/></td> <td> <table> <tr> <td><strong>Ajax: The Definitive Guide </strong></td> </tr> <tr><td>by Anthony T. Holdener</td></tr> <tr> <td> <divrel="partont:relatedWith" typeof="partont:TaglistHook" style="display: none;"/> </td> </tr> </table> </td> </tr> </table> … </div> Facing the Challenge … <div xmlns:books=“http://www.amazon.com/books/” xmlns:partont=“http://www.onekin.org/.../partont.rdfs#”> <table about="[books:${book.ISBN}]"> <tr> <td><img src="http://..."/></td> <td> <table> <tr> <td><strong>Ajax: The Definitive Guide </strong></td> </tr> <tr><td>by Anthony T. Holdener</td></tr> </table> </td> </tr> </table> … </div>

30. The PartOnt Ontology

31. Challenge: Location Transparency • E.g. A query for resources being tagged as “forDevelProject” should deliver… • books (LibraryPortlet) • publications (AllWebJournalPortlet) • post blogs (locally provided), etc • …being tagged as used in this project.

32. However… • External resources are outside the portal realm • Amazon’s books belong to Amazon • A portlet-based portal hands presentation over the portlets. • So, a mean is needed for the user to express the query and expand it across resources, no matter their location.

33. Facing the Challenge … • Expressing the query… • A new portlet –TagBarPortlet– has been built. • This portlet renders the tags available in the tagging repository, and permits the user to select one of them. • Expanding the query across resources… • To this end, we use the event mechanism available in the Portlet Specification.

34. Conclusions

35. Conclusions • A tagging commodity for portals has been proposed (and implemented in Liferay) • Advantages: • Portal ownership of tagging data • Folksonomy consistency

36. Thanks for your attention! Pleeeeeeeeeeeeease ASK FOR A DEMO!!