Iteration 01

[42piratas]

Premises

1. Database Priority

• The app must first check for data in the database to optimize ChatGPT token usage, performance, and data consistency.
• If the data is not in the database or is older than <N1> days, the app will query ChatGPT.
• Data retrieved from ChatGPT will be stored or updated in the database before user interaction continues.
• Users always receive information from the database.
• We only update our database as needed. If a country is never selected, no information about elections in that country will be stored. Similarly, if certain data becomes outdated but isn’t requested by any voter, it will remain outdated indefinitely. Except for the property "is-democratic".

2. Transparency:

• All information provided by the app must include links to the respective sources: [*] [*] [*] [*]
• If no elections are scheduled according to all sources, the app must list all sources: [*] [*] [*] [*]
• For non-democratic country messages, all sources must be listed: [*] [*] [*] [*]

3. Democratic/Non-Democratic Flag:

• Every country should be flag as either democratic or non-democratic in the database. This flag should come specifically from one of these sources:

  • Freedom House
  • Economist Intelligence Unit

• The flag should be automatically updated every <N2> days.

Features

1. Select Country:

• Information about scheduled elections should come from:
  • International Foundation for Electoral Systems (IFES)
  • ElectionGuide.org
  • Inter-Parliamentary Union (IPU)
  • International IDEA

NOTE: Let's keep the alternative of going to any country's website in particular for a future on-demand scenario.

• Messages based on the country selected:
  • If a democratic country has no election scheduled: No upcoming elections are scheduled according to our records [*][*][*] (i.e. in this case, add/link all sources)
    • If a non-democratic country is selected: <country> is reportedly a non-democratic country [*][*][*] (i.e. in this case, add/link all sources)
    • If a country with scheduled elections is selected, a modal will display a list of elections (election name and date).
    • If a user selects an election, they are redirected to the respective election page (Iteration 02).

Footer

• All website's pages should display a footer that contains:
  • Shield/button DONATE -> check this issue.
  • Shield/button BUIDL pointing to https://github.com/42piratas/VOTEgpt/blob/main/CONTRIBUTE.md
  • Shield/button GPL-3.0 pointing to https://github.com/42piratas/VOTEgpt/blob/main/LICENSE.txt

Other Home Page Elements

• Link/button How it works pointing to https://github.com/42piratas/VOTEgpt/wiki
• Link/button Feedback/Report pointing to https://github.com/42piratas/VOTEgpt/issues/new

[thiagopbraga]

Some comments:

Database Priority

We can use a version control table in the database where we can record the last update day. This way we would speed up this verification. is 1 day?

Transparency

The referral link comes from the chatgpt search return, correct?

Democratic/Non-Democratic Flag

We can create a table with all countries with some information like that, and in future use this informations for filters

Select Country

In this case I think we can do something more organic, I haven't found any updated API that provides this data yet but I can look for it. But as it will be on demand, we can do it organically too.

[42piratas]

@thiagopbraga

1 - Yes, we need a table for countries with multiple properties, including smth like "is-democratic"; 2 - Yes, all properties must have records on "created-at" and "upadted-at"; 3 - Different properties may have different "data-life-time". For example, "is-democratic" may be updated every 06 months while the list of candidates within a election may be updated every 01 week, and candidates profile's info may need to be updated every 03 days or so. Thus, every property may have a different "data-life-time" rule. All these rules/variables should be found (user-friendly named) in a single place for easy maintenance (I suppose config.py is that place, but I could be wrong); 4 - Yes, sources come from ChatGPT as well, except when certain info comes from APIs; then, we should know ourselves the source/links; 5 - Yes, whenever possible (i.e. when we retrieve data from specific sites, like for "is-democratic" and for the list of scheduled elections in each country) we should retrieve the information through direct APIs rather than through ChatGPT. But when certain sources don't have APIs and there's no other way to crawl their data, we can query ChatGPT to specifically retrieve information from that specific source;

[42piratas]

@thiagopbraga fyi, I updated the first msg of this thread under Premises/Database Priority by adding the following:

- We only update our database as needed. If a country is never selected, no information about elections in that country will be stored. Similarly, if certain data becomes outdated but isn’t requested by any voter, it will remain outdated indefinitely. Except for the property "is-democratic".

[42piratas]

@thiagopbraga Based on our discussions yesterday, for this first version, in favor of simplification, pls let's do like this:

• We only display elections scheduled to a future date. If there was a election "yesterday", it should not be displayed.
• GPT-prompts will only look ahead for 6-months. If there's an election scheduled to 7 months in the future, it won't be returned by the prompts.

I'll update the prompts accordingly, and I will create issues to deal with such cases (and others that we discussed yesterday) in future versions.