The backend logic for /data-sourcesPOST is currently relying on variable column permission logic which was set up for situations where different users have different permissions (Read vs. Write vs. None) for different database columns.
Now that /data-sourcesPOST has a schema which limits what can be written to, this is unnecessary.
Requirements
Remove the backend variable column permission logic from /data-sourcesPOST backend
Tests
Update test to test that can be done by standard user
Context
/data-sourcesPOSTis currently relying on variable column permission logic which was set up for situations where different users have different permissions (Read vs. Write vs. None) for different database columns./data-sourcesPOSThas a schema which limits what can be written to, this is unnecessary.Requirements
/data-sourcesPOSTbackendTests
Docs
Open questions