Why we tag: motivations for annotation in mobile and online media
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Comparing tagging vocabularies among four enterprise tag-based services
Proceedings of the 2007 international ACM conference on Supporting group work
Social tagging roles: publishers, evangelists, leaders
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
Motivations for social networking at work
Proceedings of the 2008 ACM conference on Computer supported cooperative work
| Hi-index | 0.00 |
A corporate portal supports a community of users on cohesively managing a shared set of resources. Such management should also include social tagging, i.e. the practice of collaboratively creating and managing tags to annotate and categorize content. This task involves to know both what to tag (hence, the rendering of the resource content) and how to tag (i.e. the tagging functionality itself). Traditionally both efforts are accomplished by the same application (Flickr is a case in point). However, portals decouple these endeavours. Tagging functionality is up to the portal, but content rendering can be outsourced to third-party applications: the portlets. Portlets are Web applications that transparently render their markup through a portal. The portal is a mere conduit for the portlet markup, being unaware of what this markup conveys. This work addresses how to make portlets tagging-aware, i.e. portlets that can be seamlessly plugged into the portal tagging infrastructure. The main challenge rests on consistency at both the back-end (i.e. use of a common structure for tagging data, e.g. a common set of tags), and the front-end (i.e. tagging interactions to be achieved seamlessly across the portal using similar rendering guidelines). Portlet events and RDFa annotations are used to meet this requirement. A running example in WebSynergy illustrates the feasibility of the approach.