Wikidata Bridge/Research/ja

現在の試作版
現在の試作版の閲覧はこちら (version 1.0)

試作版の現状をまとめます. あくまでも表示用の画像であって、すべての機能が完成したわけではない点にご注意ください. 画面の指示に従うと別の画像が表示され、そこに現れるボタンやリンクをクリックしても機能しません. 機能の最終決定ではありませんが、開発の状況を提示しています. また調査結果と利用者のフィードバックを受けて、試作版は常に進化しています.

ぜひ試して皆さんのフィードバックをこちらのスレッドに投稿してください！

足りないものは？ 未解決の問題は？
ウィキデータを基礎情報ボックスに活用すると、たくさんの利点があり、その一部を紹介します.
 * 情報の陳腐化を減らす
 * プロジェクト間で基礎情報ボックスの (無作為な) データの矛盾の低減
 * ウィキデータ上のデータ品質向上
 * すべてのウィキ読者に、より多くのデータを提供 (特に規模の小さなウィキ)
 * ウィキペディアのプロジェクト間では、編集者1人が管理するデータ総量を低減
 * 他のウィキメディアのプロジェクト群から見て、ウィキデータの親しみが向上

But unfortunately the way it is currently done is not convenient for most editors, especially those who are not yet familiar with Wikidata and its data structure.

We want to make easier to use Wikidata’s data in the other Wikimedia projects by making possible to edit the data directly from there, therefore giving editors a sense of agency and connectedness with Wikidata. It’s important that this should not lead in an increase in vandalism or bad edits done it good faith to Wikidata.

How do we work?
We follow a user-centered design approach which means that we base our decisions on what we think will give the people using the feature in the end the best user experience.

To find out what the users need, we define personas and conduct research.
 * We usually do this by conducting interviews with people that will likely use the feature or will be affected by it in some way. We ask about their current workflows that will be affected by the changes as well as things that work well for them currently and problems they’re facing. Overall our goal is to get a good understanding of how we can best improve the situation for them so they can have a more efficient and satisfactory editing experience. For the exact research we conducted for Wikidata Bridge please see the feedback loop section below.
 * From this research we also develop personas which means we create fictional representatives of the user groups that we encountered during the interviews. This helps us to keep the focus of who we are making this product for and try and make design decisions in their best interest.
 * Based on the information we gather from the interviews we come up with a concrete design and interaction that integrates well into the existing UI and solves the problem in the best way.

Unfortunately what we imagine does not always end up being developed exactly as envisioned because there are usually technical constraints and resource constraints that we need to take into account. This means that we will be in discussion with the product team and the engineering team to figure out the best way we can make this work. For more information on how we ended up with the current version please see the feedback loop section below.

We then start thinking about user journeys. What are the things that the personas would like to be able to do and how should this journey look. We will then define these journeys and settle on a few main ones that we want to tackle first.

We will start out small with what we call MVP (minimal viable product). This means we don’t make the full cruise ship right away, but start of with a small paddle boat to see whether we have the right idea on how to approach the feature. The reason for this is, this way we can include many iterations and feedback loops to ensure that we are on the right path and are actually solving the problem we set out to solve. Starting with a product that from the start includes all extra features will take a lot of time and we’d run the risk of finding out too late, after a lot of resources have already been put into building it, that this is actually not the right approach to the issue.

このプロジェクトでは利用者の人物像を主に2人、想定して開発を進めました.
 * 人物設定 (ペルソナ) と利用者の体験の模式図
 * メリッサ. ウィキペディアの編集者で活発に作業する人
 * ジョセフ. 他人の編集に反応して修正する人

Our minimal viable product contains the following user journeys:
 * Changing the value of a simple statement (eg. date or number of inhabitants, not a value that links to another Item)
 * Updating the value of a simple statement

Our minimal viable product has the following scope:
 * Has to work independently of the Visual Editor
 * We focus only on items connected via sitelink
 * Only for the fields that are using wikidata

On further iterations, we plan to work on:
 * Reference adding and editing
 * Adding statements

Everything else is not planned for now and will have to be discussed again in the future.

過去の調査

 * これまでのフィードバックと返信
 * 2015年10月分 第1回フィードバックと返信
 * 2017年5月-6月分 フィードバック (ウィキデータ)
 * 2018年2月-3月分 フィードバックと返信 (ドイツ語版ウィキペディア)
 * その他、イベント中に多数の聞き取り調査や協議を実施 (ウィキマニア、ウィキコン、ハッカソンなど…)


 * 実装済みの機能ほか：
 * WE-Framework: 基礎情報ボックス編集ツール (ロシア語版ウィキペディア)
 * 「ウィキデータを編集」するリンクやアイコンは複数のウィキで実装済み. 例えばカタロニア語版、スペイン語版、フランス語版.
 * 基礎情報ボックスにウィキデータを援用するテンプレート (英語版ウィキペディア)：w:en:Module:WikidataIB


 * 過去の試作版：
 * 2017年と2018年の開発分はフィードバック に基づく. (英語版とドイツ語版)

Why did we move away from this prototype? This prototype was developed as part of a thesis where engineering expertise and resources had not been considered yet. Most of the features seen in the prototype are still things that we would like to do along the line but are not part of the first iteration. This is explained in more detail in the “how we work” section above.

''未掲載分の追加はお任せします. いつも活動するウィキで話し合ってみませんか？''
 * 以下はウィキペディア上で進んだウィキデータの議論の総覧です.
 * 英語版. Wikipedia:Wikidata
 * 2018年のコメント募集（ウィキデータを基礎情報ボックスに導入する案について）Infobox RfC
 * フランス語版. Wikipédia:Wikidata
 * ウィキデータのプロジェクト総覧. ウィキデータに関するウィキペディアのヘルプページ総覧