Semi interesting post from Search Technologies (aka Paul Score) about
indexing wikipedia data:
http://www.searchtechnologies.com/wikipedia-azure-search
Takeaways:
* Automated entity detection, categorizing into person/place/organization
* Offers search facets by wikipedia category and by entity detection
* Multiple scoring profiles offered which change the weight between title
and description (content? not clear)
Hi Discovery,
Do you know if the major search engines consider whether one of our images
is a "featured" image (or has passed other quality reviews) when they rank
our images in their search results? I suspect that Google does but I don't
know with certainty. If they don't, you might suggest to them that they
should.
Thanks,
Pine
Hi Discovery,
Following up on conversation from last week's Metrics Meeting:
* If user 1 enters search term X in language A on a.wikipedia.org and there
are no article or redirect title results on that wiki for X, can we show
them search results for X automatically translated into other languages on
wikis where an article or redirect does exist for the translated term?
* If user 2 enters search term Y in language b on c.wikipedia.org and there
are no article or redirect title results on that wiki for Y, can we show
them search results for Y on b.wikipedia.org?
* What is the status of integrating Wiktionary search results into
Wikipedia search results?
* Have there been any initiatives to integrate Wikivoyage, Wikispecies,
Wikisource, Commons, and other project search results into Wikipedia search
results, including with options for multilingual search as mentioned above?
Thanks!
Pine
This week, phabricator changed the terminology it uses for managing
dependencies between tasks. What has been called "Blocking"/"Blocked by" is
now called "Parent"/"Subtask". Ignoring phab terminology for a minute, here
are the two basic cases these terms are covering:
1. *Sequential dependencies.* For example, if "Implement feature X" needed
to be complete before "Document feature X", then the implementation task
would Block the document task, and the document task would be blocked by
the implement task.
2. *Composition relationships/task breakdown.* For example, if "deploy
feature X" consisted of "implement feature X" and "document feature X",
then the deploy task might be a parent, while the implement and document
tasks would be subtasks.
Until recently, phab has used the blocking/blocked by term to cover both
cases. A parent task would be blocked by its subtasks. There was a command
to create a subtask, which would create the appropriate blocking
relationships.
Now, phab uses the parent/subtask terminology to cover both cases. In the
sequential tasks case, the endpoint would be considered the parent, so in
the example above, "document" would be the parent, and "implement" would be
its subtask. Note that a task may have multiple "parents".
A nice feature they added is the ability to manage the parent/subtask
relationship from either end. While editing a task, you can change its
subtasks or its parents. Previously, you could only edit one direction.
I created T139181 as a task to update our wiki phab documentation.
Kevin Smith
Agile Coach, Wikimedia Foundation