Since it would probably require a migration file to remove the column from the DB, we'll want to do it in another PR. It needs to be removed, so you could just remove the template side code here and that would save any conflicts or issues in making another PR.