Reading/Web/Desktop Improvements/Features/Search/ko

우리는 우리 프로젝트의 모든 편집자들이 자신들이 찾는 문서를 빠르고 효율적으로 찾는 기능을 보유하길 원합니다. 우리의 검색 기능은 이것에 필수적이지만 현재의 우리 연구 경험은 몇 가지 문제와 개선의 여지가 있습니다. 먼저, 검색이 페이지 위에서 표준적이지 않은 위치에 있어서 과거에 사이트 경험이 전혀 없는 사용자가 찾기가 어렵고 이미 해당 위치를 알고 있는 사용자이더라도 쉽게 잊어버립니다. 둘째로, 검색을 하는 중에 지금은 표시되는 검색 결과의 문맥을 제공하지 않기 때문에 올바른 결과를 찾기 위해 상당한 시간이 소요될 수 있습니다.

우리의 목표는 찾기 더 쉽고 사용하기 더 빠르도록 검색 경험을 개선하는 것입니다. 특히 우리는 다음을 원합니다


 * 더 눈에 띄는 위치로 이동시킴으로써 검색을 더 찾기 쉽게 만듭니다
 * 개선된 검색 결과 스캔을 위해 이미지와 기타 맥락 정보를 포함하여 검색을 사용하기 더 쉽게 만듭니다

출시 계획
We began deploying the first iteration of these changes, moving the search bar to its new location, September 2020 to Office Wiki and Test Wiki, followed by our early adopter wikis. We will deploy the second iteration of the new search experience (built in vue.js) in January 2021. This iteration will add images and content descriptions where applicable to the search results. 더 자세한 정보의 경우 메인 기능 문서를 참고하십시오.

기능 설명 및 요건

 * 검색 표시줄은 페이지 헤더의 새 위치로 이동됩니다.
 * 검색 표시줄에는 (가능한 경우) 문서의 설명뿐 아니라 (가능한 경우) 페이지의 문서가 포함됩니다. 페이지 설명은 개별 위키의 정책에 따라 로컬 위키의 설명이거나 위키데이터의 설명이 됩니다.

목표
A user test was performed using usertesting.com which focused on the following:


 * Indentifying any major usability issues that we may have overlooked
 * Learning more about search behavior by identifying the breakdown in terms of how people submit their search:
 * (a) click on a suggested result
 * (b) press `enter` on their keyboard
 * (c) click the `Search` button
 * To see what people think the “Search” button will do
 * To see what people think the “Search pages containing X” will do

연구
On usertesting.com we had people do various tasks, some of which required them to search for various articles (without explicitly telling them to use the search box). There were two groups:

그룹 1


 * 17 people
 * People in group 1 searched for //Egypt//, //Cave art//, //Banana//, and //Purple//

그룹 2


 * 15 people
 * People in group 2 searched for //Electricity//, //Banana//, //Willow trees//, //Romeo and Juliet//, and //Purple//

There was a mix of ages and geographies in both groups:

발견

 * 0 people had issues using search
 * There were a total of 117 searches submitted:
 * 86 were submitted via a suggested result
 * 19 were submitted via the `enter` key
 * 12 were submitted via the `Search` button
 * Regarding what people thought clicking the `Search` button would do:
 * 16 of 23 people who answered thought it would take them to the first result
 * 7 of 23 people who answered thought it would take them to a list of results
 * note: all people assumed that `enter` and the `Search` button do the same thing
 * Regarding what people thought clicking the `Search for pages containing Purple` would do:
 * 25 of the 25 people who answered thought it would take them to a list of pages that have the word "purple" in them

참고:

It was ambiguous how they were supposed to get there. 7 out of 10 people tried to find an "Egypt" link within the Pancake article
 * in the first study people started on the Pancake article and were then asked to go to the article about Egypt.
 * one person wondered why the Cave art search result didn't have an image — made me wonder if the articles that don't have images look lower quality next to the ones that do?
 * in two cases the search results loaded quite slowly and the people used the `Search` button
 * few people used their keyboard to navigate down to suggested search results (maybe 2 or 3)

양적 테스트
Two A/B tests will be performed on the early adopter wikis:


 * A comparison of the old location of the search bar vs the new location of the search bar
 * A comparison of the old search widget vs the new search widget

We will be tracking the following metrics:


 * Search Sessions initiated
 * Search Sessions completed

Our target is a 2.5% increase for each change for an overall 5% increase in search sessions initiated

제한
There is a current bug with the new implementation of search. If you start a search then resize your browser, the search results stay open but do not move with the search. It is only when you run another search that the results reposition. We will be fixing this upon the introduction of the new search widget.