Skip to content

Conversation

@chris48s
Copy link
Member

@chris48s chris48s commented Jan 8, 2026

The scope of this PR is just to do the behind the scenes bits.
So in this PR I have:

  • added DB fields to store sopn names on the membership
  • added thos fields to the admin/API/CSV outputs
  • populated the fields (as best we can) when we bulk add from SOPN
  • added/updated tests for that functionality

This is a chunk of work that is worth reviewing and deploying, but it is not 100% of what we want to do here.

The second bit of work here will be to allow the user to modify these fields through the frontend and provide some way to discover profiles which are missing this data

I'll do those in a follow up PR (or maybe 2 follow up PRs)

@chris48s chris48s marked this pull request as draft January 8, 2026 12:51
@chris48s chris48s force-pushed the sopn-name1-20260108 branch from 24e8667 to 6af70c9 Compare January 12, 2026 15:24
@chris48s chris48s changed the title add sopn name field add sopn name fields Jan 12, 2026
@chris48s chris48s mentioned this pull request Feb 3, 2026
@chris48s

This comment was marked as outdated.

@chris48s chris48s force-pushed the sopn-name1-20260108 branch from 49827a3 to f1e559c Compare February 4, 2026 15:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants