Verification to OTP

[Karyum]

This means having 2 kinds of data, ones that are verified ( verified as in an admin approved adding it to the API ) and unverified.
only verified data should be shown/rendered in the OTP child apps ( like Nazareth events ).

to implement a feature like this we might need these changes:

• change the API's database schema (places, events) to have an extra key of verified (which would be Boolean ) verified key to Event and Place #179
  Note: the data would be added to the database even if not yet verified.
• send an email to the OTP admins so they could verify the data. Investigate sending emails #178
• A new route in the API which changes the verified key in the data to true. /verifed route for content verification  #181
• Changes to the way Nazareth events renders data render verified content only  nazareth-events#182
• OTP data entry:
  • add the status of the data (verified unverified). Status of the content OTP-Data-Entry#104
  • add an ability for the admins to verify data from the app

have i missed anything @des-des ?

[des-des]

@Karyum You nailed it!