1.
Tags and facets, tags and languages. Peter Van Dijck http://petervandijck.net

3.
Challenge: Findability of long tail video <ul><li>An unsolved problem. </li></ul><ul><li>Video eats attention. </li></ul>

6.
A few principles: <ul><li>Always be easy . Entering a tag should stay simple. </li></ul><ul><li>The work of the few impacts many. Wikipedia is edited mostly by a small group of people. </li></ul><ul><li>Babysteps : A little semantics goes a long way. Leverage it. </li></ul>

10.
We plan to let users select facets here.

12.
Refine by: People: Ilse (12) Johnny (3) Peter (3) Jay Dedman (4) Event: Vloggercon (12) Gates (8) Language: English (230) Spanish (8)

13.
What we didn’t do <ul><li>There were a lot of options and possibilities to add structure and semantics. </li></ul><ul><li>We kept it simple: a tag has only 1 facet – which is the same for all users. </li></ul><ul><li>Users can’t select facets just yet. </li></ul>

14.
What we did: <ul><li>Add minimal structure : tag has a parent-id. </li></ul><ul><li>Add semantics : Place, Language, Event, People, Topic. </li></ul><ul><ul><li>You can’t let users create facets and keep their facet-ness. </li></ul></ul>

15.
(Who is cindy sheenan?) Movies with: Cindy and Ilse (12) Cindy and Johnny (3) Cindy and Peter (3) Cindy and Jay Dedman (4) Event: Vloggercon (12)

17.
Even more leverage …

21.
3 levels of leveraging semantics <ul><li>The fact that parents are facets means we can use faceted browsing. (Regardless of the content of those facets.) </li></ul><ul><li>The content of the facets (people, …) lets us customize the UI and provide additional structure around each. (Events on a timeline, pictures of people, …) </li></ul><ul><li>We can also infer (guess) more information from the semantics and an algorithm of relatedness (“Gates happened in Central Park”). </li></ul>

22.
All this from the simplest of structures and a sprinkling of semantics Parent Tag “ People” “Places” “Events”

23.
Some trickyness follows…

26.
Semantic crashes <ul><li>Conclusion: careful with duplicate semantics in the system. </li></ul>

27.
Localizing the folksonomy <ul><li>Should we even translate folksonomies? </li></ul><ul><li>Tags seem to work better when they’re in limited communities, “tag namespaces”. </li></ul>

29.
The plan for Mefeedia: <ul><li>Don’t translate tags. </li></ul><ul><li>Don’t copy tags – new language = new community. Possible complaints: </li></ul><ul><ul><li>“ My tags don’t show up in the Spanish version”. </li></ul></ul><ul><li>I could perhaps use names (“People”) in multiple languages (that have Latin charsets). => Semantics might help with localization. </li></ul>

30.
Other approaches …

33.
For geography: <a href=&quot;http://www.edgeio.com/tag/zip:94301&quot; rel=&quot;tag&quot;>94301</a> <a href=&quot;http://www.edgeio.com/tag/city:Palo%20Alto&quot; rel=&quot;tag&quot;>Palo Alto</a> <a href=&quot;http://www.edgeio.com/tag/country:USA&quot; rel=&quot;tag&quot;>USA</a>

34.
What people are doing <ul><li>Providing “generic” data structures for users (Del.icio.us). </li></ul><ul><li>Semantics through algorithms (Flickr). </li></ul><ul><li>Define certain tags or structure (taxonomy) through clustering algorithms (Edgeio) </li></ul>

35.
I notice … <ul><li>A hesitance against hardcoding semantics . (“It won’t scale”) </li></ul><ul><li>A hesitance against manual work (“It won’t scale”) </li></ul>

36.
What I learnt <ul><li>Mix it up. A small amount of semantics, on top of minimal structure, with a little manual work, can work wonders. </li></ul>

37.
References <ul><li>[email_address] </li></ul><ul><li>http://petervandijck.com </li></ul><ul><li>http://mefeedia.com </li></ul><ul><li>http://mefeedia.com/labs-infer/infer.php </li></ul><ul><li>http://www.everything2.com/ </li></ul><ul><li>http://bailando.sims.berkeley.edu/flamenco-metadata-guide.html </li></ul>