Searchlight: keep people in context when searching across an owner

Aperta
  • Qualcosa non va?
#2,998 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
15/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Ambito
frontend, search

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

component/web decision/human-review signal/low-risk signal/needs-human signal/small-scope stage/triaged type/feature

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.
  • Search can already render inside a page through its url prop, 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).

Lingua principale
Nessun dato sulla lingua
Stelle
4
Fork
2
Merge medio
2h 12m
PR unite (30g)
1

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di OpenConceptLab/ocl_issues

Tutte le issue di OpenConceptLab/ocl_issues

Issue simili

Altre issue su Web Dev

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.