Searchlight: keep people in context when searching across an owner
まだ誰も着手していません。
評価
調査の方向性
This is design research, not a code change. Start from the owner-wide concept search row that links to /search/ with an owner filter, then look at how the Repositories tab renders Search through its url prop. Compare the options (stay on the repository page, land on the owner page, or a results view inside the current page) against the oclapi2 /concepts/ owner filter, since there is no /orgs/:org/concepts/ route. Done means the options are compared with their API and UI work, mockups exist, and the team's decision is recorded on the issue.
索引モデルが issue の本文から書いたものです。
説明
Choosing the owner-wide concept search takes you off the organization, user or repository page and over to global search with an owner filter. The goal of OpenConceptLab/ocl_issues#2987 was to stay in context. Research and mock up how to do that, for the team to decide on before any build.
What's there now:
- The row goes to
/search/?filters={"owner":"CIEL","ownerType":"Organization"}&q=hem&type=concepts. - Organization and user pages have no Concepts tab.
Searchcan already render inside a page through itsurlprop, which is how the Repositories tab works.- oclapi2 has no
/orgs/:org/concepts/route; today's search uses the owner filter on/concepts/.
Questions for the team:
- What does "same context" mean from a repository page: stay on that page, or land on the owner's page?
- Where do results go: a Concepts tab on the owner's page, a results view inside the current page, or somewhere else?
- Can people widen or clear the scope from there, as they can in global search, and do mappings need to be included?
Acceptance criteria
- Options are compared, with the API and UI work each needs. All keep today's rule: private repositories appear only for people who can already see them.
- Mockups of the preferred options.
- The team reviews them, and the decision is recorded here.
- Build tickets are filed.
Related: OpenConceptLab/ocl_issues#2987, OpenConceptLab/ocl_issues#2997 (a scope selector could change how people reach this).
- 主要言語
- 言語のデータがありません
- スター
- 4
- フォーク
- 2
- 平均マージ
- 2時間 12分
- マージ済み PR（30日）
- 1
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
OpenConceptLab/ocl_issues のほかの issue
-
component/fhir type/bug
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
OpenConceptLab/ocl_issues#3026 ·
-
component/api decision/human-review signal/needs-access signal/quick-win signal/small-scope signal/well-specified stage/triaged type/bug
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
OpenConceptLab/ocl_issues#3012 · コメント 2 件 ·
-
component/design-system decision/ai-ready signal/low-risk signal/quick-win signal/small-scope signal/well-specified stage/triaged type/docs
難易度 2/5 半日 初心者へのやさしさ 70/100
OpenConceptLab/ocl_issues#2983 · コメント 1 件 ·
-
component/mapper decision/ai-ready signal/low-risk signal/quick-win signal/small-scope signal/well-specified stage/triaged type/bug
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
OpenConceptLab/ocl_issues#2966 · コメント 2 件 ·
-
component/mapper component/web decision/human-review signal/low-risk signal/needs-human signal/quick-win signal/small-scope signal/well-specified stage/triaged type/bug
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
OpenConceptLab/ocl_issues#2920 · コメント 1 件 ·
OpenConceptLab/ocl_issues の issue をすべて見る
似ている issue
-
Selectmenu changes selection after its native select is disabled while open対応中かも @Xapollon430 が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
-
feature request good first issue
難易度 2/5 1〜3時間 初心者へのやさしさ 88/100
TabularisDB/tabularis#1513 ·
メンテナーはふだん 2 日以内に返信
-
bug priority: medium
難易度 2/5 1〜3時間 初心者へのやさしさ 62/100
storytold/pdfcraft#7140 · コメント 1 件 ·
メンテナーはふだん 2 日以内に返信
-
requests support
難易度 2/5 1〜3時間 初心者へのやさしさ 67/100
メンテナーはふだん 2 日以内に返信
-
bug lane: fast
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
unicef/adt-studio#1107 ·
メンテナーはふだん 2 日以内に返信