Organization profiles should be permanent

[jace]

The work-in-progress Organization model in Hasjob is linked to the Organization model in Lastuser. Editing settings in one place affects the other.

Deleting an Organization in Lastuser does not automatically delete in Hasjob since there is no delete journal. However, Flask-Lastuser's ProfileMixin has a update_all_from_lastuser method that iterates through every organization and cross-checks with Lastuser. If Lastuser says the Organization (or User) no longer exists, ProfileMixin deletes it.

This is a problem in Hasjob. We have several use cases where data can be attached to an Organization by a non-owner/non-member, such as by candidates submitting feedback or by moderators. Organization owners should not be able to purge this data by deleting and re-creating organizations.

The basic disconnect is that in Lastuser, an Organization is 100% owned by its owners who can control everything related to it, while in Hasjob it's wiki-like, autogenerated from other activity and an aggregator of data from multiple sources.

[jace]

We abandoned the Organization model in Hasjob and made it the Domain model instead. However, there needs to be a 1:1 connection between the two and this is still pending resolution.