Page MenuHomePhabricator

🦄 Create `KnowledgeEquityResponse` Laravel Model in Platform API
Closed, ResolvedPublic

Description

Create a new model in PlatformApi for the knowledge equity response.

Rational for creating a new model over putting it in the exiting WikiProfile model:

+ Data has different levels of access controls
+ We (potentially) want separate edit timestamps for this compared to the rest of the profile
+ Logically easier to reason about
- Anton will have to do a JOIN when querying the database
- In hindsight we named the current profile incorrectly / it contains to many different concerns under the same name

Database fields on the new model (if any of these change, update T419208)

INT wikiId
ENUM selectedOption <one of 'yes' 'no' 'unsure', 'unsaid'>
VARCHAR(3000) freeTextResponse

Useful links:

Event Timeline

Ollie.Shotton_WMDE renamed this task from 🦄 Create KnowledgeEquityResponse Laravel Model in Platform API to 🦄 Create `KnowledgeEquityResponse` Laravel Model in Platform API.Mar 6 2026, 12:25 PM
Tarrow changed the task status from Open to Stalled.Mar 11 2026, 4:49 PM

Waiting to hear from @Anton.Kokh on the question of: "do we want to store KnowledgeEquityResponses over time? e.g. if users edit the response later do we want to keep the history of their first response for you to analyse?"

@Tarrow From the product's perspective, I think it would be useful.
It would also be consistent with the way the intended use block on the dashboard already works: we earlier discovered that the updated_at timestamp in wiki_profile is redundant since a new record is created in wiki_profile every time an update happens. If you plan to reuse the wiki_profile table for different blocks that will appear on the dashboard, I think it makes sense that they all follow the same logic.

Anton.Kokh changed the task status from Stalled to Open.Mar 12 2026, 9:16 AM

tarrow closed https://github.com/wbstack/api/pull/1067

Create KnowledgeEquityResponse Model and Migration