Jump to content

Wikidata Bridge/調査

From mediawiki.org
This page is a translated version of the page Wikidata Bridge/Research and the translation is 68% complete.
Languages:
ウィキデータ ブリッジ
基礎情報ボックスからウィキデータのデータを直接編集

現在の試作版


現在の試作版より。利用者は必ず、既存の値が誤りか要更新か指定を求められる。
現在の試作版（スクリーンショット）

現在の試作版の閲覧はこちら (version 4.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人、想定して開発を進めました。

この開発製品 (機能) を実行可能にするには、少なくとも次の利用者体験 (user journeys) を盛り込みます。

  • 単純な文の値を変更（例：日付や住民数など他のアイテムにリンクしない値）
  • 単純な文の値を更新

実行可能な最小の製品に与える目標は以下のとおりです:

  • ビジュアルエディタとは必ず独立して動作させる
  • 対象はサイトリンクで接続された項目のみ
  • フィールドのうちウィキデータを使用するものに限定

工程をさらに繰り返した末には、以下の課題に取り組む予定です:

  • 出典の追加・編集
  • 文の追加

上記以外は現状では未計画であり、将来、ふたたび協議する必要があります。

過去の調査

これまでのフィードバックと返信
実装済みの機能ほか
過去の試作版

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.

以下はウィキペディア上で進んだウィキデータの議論の総覧です。

未掲載分の追加はお任せします。いつも活動するウィキで話し合ってみませんか？

Retrieved from "https://www.mediawiki.org/w/index.php?title=Wikidata_Bridge/Research/ja&oldid=4344616"