• Create history tables
• Create triggers
• Write a script to verify the consistency of schemas, triggers and unique keys (so that we don't forget about this in the future).

Some statements first appear in website articles. We should have an Entity type for that.

Loyalty should be an indicator of where a person's allegiance lies. In contrast to the person's current membership, loyalty should take into account memberships in previous years (with decreasing weights) and family ties.

Sources of inspiration from StackExchange / StackOverflow:

• flagging (Stack Overflow)
• flagging (Stack Exchange)
• review queues

• flag awards and caps;
• ability to retract a flag;
• queue table with objectType, objectId, queueType fields;
• flag resolution mechanism (requires one or several votes);
• customizable resolution requirements (for sites in early stages);
• put objects in queue / remove objects from queue on certain conditions;
• ability to skip a review item (forever);
• queue for new items from users under a reputation threshold;

It can currently be done by logging out and back in as a test user. Should be a mini-form in the user menu.

The only way to select a color is by using the palette, which makes it impossible to obtain a specific hex code.

Some answers should not be deleted hastily - new user posts, low quality posts. There should be a grace period when users can work to improve their answers.

See what SO/SE do.

To be used during reviews.

• Why and how are some answers deleted?

In particular, when reviewing a new user message / late answer, the reviewer can currently close the question with no explanation. The reviewer should be forced to enter some free text or choose a canned response.

Should just redirect to editing the object with the given ID.

(Obviously this is an ongoing effort, but it's OK to close this issue once we have an initial version.)

To alert the developer when Config.php.sample changes, when database patches are available etc.

Keep track on who made each change. Add a modUserId field with similar mechanics to modDate.

Not clear if we'll ever use the hierarchy, but it's cheap to implement.

• add entity type: company (to track association relations)
• add more relation types: close relative, distant relative, associate in company
• add an interface for relation links (to have accountability for relations we claim)
• script to suggest adding reciprocal relations

See link1 link2 link3 for information on SO's policies.

• Add a markdown field (should it allow embedded images?)
• Add external links, e.g. to the entity's Wikipedia page.

E.g. nicknames for persons or initials for parties. Should appear in search results.

SE approach

Instead of "wikipedia.org" the link text could read "wikipedia". We probably need a mapping table.

Currently the search box breaks horribly because it depends on Select2. Provide a text input for users without javascript.

Show a big colored verdict like true or false.

How many verdicts should there be? Clearly true and false, but possibly partially true, undecidable and more.

To what object does the verdict belong? When a user posts an answer, they would probably like to issue a verdict along with the answer. Alternatively (or concurrently) the statement itself may have a verdict field.

Who should be allowed to assign verdicts to statements? The owner? Any person with enough reputation? Should it be applied automatically when an answer has an overwhelming majority of upvotes?

Should the verdict be linked to one particular answer? Or perhaps several?

should be reusable on

• the statement page
• the answer review page

They will probably need to be moderated, possibly before publication (depending on reputation).

Evaluate if it's feasible to remove most of our bloated JS and use components from http://microjs.com/.

Bootstrap looks the hardest to remove and it requires jQuery too.

@david-batranu might be interested.

• insertion point is wrong;
• focus and cursor position after insertion are wrong;
• should warn about unsaved changes when navigating away;
• if possible, should intercept file drops on the entire document and paste them in the text area.

This avoids the inherent ambiguity that sometimes arises when the same English phrase needs to be translated in Romanian as either feminine or masculine.

We can potentially make them dofollow for statements adjudicated as true.

Merge the entity_link, statement_source and relation_source tables.

Once the developer changes his reputation, either refresh the page or make it clear that changes will only become visible upon refresh.

See A Theory of Moderaion

• Add database bit
• Display it on user profile (perhaps also on user links)
• Implement Flag::WEIGHT_MODERATOR (single vote resolution of reviews)

• display something reasonable for entities with no relationships (e.g. newly created entities);
• write a help page so that loyalty figures are less mysterious;
• add the WORKS_FOR relation type and include it in the loyalty calculator;
• display something reasonable for people who are not members of any party (they will still have a loyalty);

Our relations table can only capture memberships. Figure out a schema for other positions - ministries, committees and so forth. Could be as simple as free text + start date + end date.

Should search entities, statements and tags. Should offer autocompletion via AJAX