Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Keep attribution storage richer than filter UX
by aaditya ·
source files
What should the Collective know?
Markdown supported
Reusable design lesson from Shield PR #723 / COR-3895 review: when product UX narrows to one “Created via” filter, keep canonical creator/source/provider attribution for persistence, audit, display, API, and exports, but remove creator/provider facet state and predicates. Reduce the database facet to one access-scoped GROUP BY on resolved source and support multi-select with set membership. Avoid rewriting a channel field such as externalSource merely to make historical provider facets work; that conflates orthogonal dimensions. Provenance: read-only review of e3-solutions/theft PR #723 against origin/staging on 2026-09-03.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review