Halfak created this task.
Halfak added subscribers: Halfak, aude.
Halfak added a project: Wikidata.
Halfak moved this task to incoming on the Wikidata workboard.
Herald added subscribers: StudiesWorld, Aklapper.

TASK DESCRIPTION
  (Originally asked about this in #wikidata @ freenode, but making a ticket 
based on @aude's advice)
  
  I'm working with a research team at the University of Minnesota that is 
developing a strategy for robustly identifying main/sub-article relationships. 
E.g. [en:United States](https://en.wikipedia.org/wiki/United_States) and 
[en:History of the United 
States](https://en.wikipedia.org/wiki/History_of_the_United_States)  vs. 
[Q3](https://www.wikidata.org/wiki/Q30) and 
[Q131110](https://www.wikidata.org/wiki/Q131110).  They initially started 
working on this because it was important for algorithms that learn 
relationships between concepts cross-language where one language Wikipedia 
would split a topic into multiple articles and another would only have a single 
article. 
  
  Right now, you can somewhat identify these relationships with templates used 
in the wikis.  E.g. English Wikipedia uses `{{main}}` and `{{see also}}` for 
different types of relationships.  It seems like it would be useful to capture 
this in a structured way and Wikidata would be the Right(TM) place.  These 
researchers may be in a good position to provide some initial imports or 
wikidata game-like proposed relationships. 
  
  The property [P1269 -- facet 
of](https://www.wikidata.org/wiki/Property:P1269) seems like one viable option 
for capturing this.

TASK DETAIL
  https://phabricator.wikimedia.org/T117875

WORKBOARD
  https://phabricator.wikimedia.org/project/board/71/

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Halfak
Cc: Aklapper, StudiesWorld, aude, Halfak, Wikidata-bugs, Mbch331



_______________________________________________
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

Reply via email to