README.md

-# SAÉ 303 JO
+# Projet SAÉ 303
 
+Code pour le projet de la SAÉ 303 : Concevoir des visualisations de données pour le web et un support animé
 
+## Contenu
 
-## Getting started
-
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
-
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
-
-## Add your files
-
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
-
-```
-cd existing_repo
-git remote add origin https://etulab.univ-amu.fr/gonzalez-l.a/sae-303-jo.git
-git branch -M main
-git push -uf origin main
-```
-
-## Integrate with your tools
-
-- [ ] [Set up project integrations](https://etulab.univ-amu.fr/gonzalez-l.a/sae-303-jo/-/settings/integrations)
-
-## Collaborate with your team
-
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
-
-## Test and Deploy
-
-Use the built-in continuous integration in GitLab.
-
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
-
-***
-
-# Editing this README
-
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
-
-## Suggestions for a good README
-
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
-
-## Name
-Choose a self-explaining name for your project.
-
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
+Ce dossier contient les fichiers nécessaires pour faire marcher une version préliminaire de l'application web. Le fichier `sae303.sql` contient la base de données.
 
 ## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
 
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
+Instructions pour un déploiement local de développement sur votre ordinateur ou pour un déploiement de production sur le serveur web pédagogique.
 
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
+### Développement
 
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
+Vous avez besoin de XAMPP pour un déploiement. Étapes :
 
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
+1. Créez une base de données appelée `sae303` avec phpMyAdmin et importez le fichier `sae303.sql`.
+2. Copiez ce répertoire dans votre dossier `htdocs`.
+3. Le site web est accessible localement à l'adresse URL `http://localhost/sae303/index.php`.
 
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
+Vous trouverez plus d'explications [ici](https://aldo-gonzalez-lorenzo.pedaweb.univ-amu.fr/2021/r213-tp1.html).
 
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+### Production
 
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
+Étapes :
 
-## License
-For open source projects, say how it is licensed.
+1. Allez sur [phpMyAdmin](https://a-pedagoarles-mmi.aix.univ-amu.fr/phpmyadmin/), connectez-vous et importez le fichier `sae303.sql` sur votre base de données.
+2. Copiez ce répertoire dans votre dossier avec FileZilla.
+3. Modifiez vos coordonnées dans le fichier `include/php/functions.php`, lignes 16 et 17.
+4. Modifiez la ligne 28 du fichier `include/php/functions.php` pour faire la connexion vers la base de données du serveur web.
 
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
+Vous trouverez plus d'explications [ici](https://aldo-gonzalez-lorenzo.pedaweb.univ-amu.fr/2021/r213-tp2.html).

data/README.md

+# Data
+
+Outils pour générer la base de données avec les statistiques des Jeux Olympiques.
+
+## Objectif
+
+Un site web pour afficher des données sur les jeux olympiques. Quelques exemples de données à visualiser : nombre de médailles par pays, nombre de records par pays, pourcentage de médailles gagnées par pays, pyramide d'age des athlètes (ou des spectateurs), nombre d'athlètes par pays, nombre de records par année, classement des athlètes les plus médaillés, frise chronologique avec les records dans une discipline. 
+
+Voir comme exemple [Olympedia](https://www.olympedia.org/)
+
+## Données brutes
+
+Quelques jeux de données :
+
+- `https://data.education.gouv.fr/explore/dataset/paris-2024-results-medals-oly-eng/information/` contient seulement les podiums de chaque discipline. Il est très bien.
+- `https://data.education.gouv.fr/explore/dataset/paris-2024-liste-athletes-engages-olypara/information/` contient tous les athlètes. Je ne vois pas l'utilité pour l'instant.
+- `https://www.kaggle.com/datasets/piterfm/paris-2024-olympic-summer-games` me semble beaucoup trop complet.
+- `https://www.kaggle.com/datasets/heesoo37/120-years-of-olympic-history-athletes-and-results` pas utilisé
+- `https://github.com/KeithGalli/Olympics-Dataset` pas utilisé
\ No newline at end of file

data/make-sql.py

+import json
+import random
+
+labels = {
+	'name': {'comment': "Nom de l'athlète", 'type': 'varchar(100)'},
+	'gender': {'comment': "Genre de l'athlète", 'type': 'varchar(1)'},
+	'discipline': {'comment': "Discipline", 'type': 'varchar(100)'},
+	'code_discipline': {'comment': "Code de la discipline", 'type': 'varchar(4)'},
+	'event': {'comment': "Sport", 'type': 'varchar(100)'},
+	'country': {'comment': "Pays", 'type': 'varchar(100)'},
+	'country_code': {'comment': "Code du pays", 'type': 'varchar(4)'},
+	'medal_type': {'comment': "Type de la médaille", 'type': 'varchar(20)'},
+	'medal_code': {'comment': "Code de la médaille", 'type': 'int(1)'},
+	'medal_date': {'comment': "Date de la médaille", 'type': 'varchar(10)'},
+	# 'url_event': {'comment': "URL des résultats", 'type': 'varchar(100)'},
+}
+
+
+beginning = """SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";
+START TRANSACTION;
+SET time_zone = "+00:00";
+
+/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
+/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
+/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
+/*!40101 SET NAMES utf8mb4 */;
+"""
+
+ending = """
+/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
+/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
+/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;"""
+
+insert_into = 'INSERT INTO `joparis2024` (`id`, ' + ', '.join(f'`{k}`' for k in labels) + ') VALUES\n'
+
+
+def make_row(medal, i) -> str:
+	"""Faire une ligne de code SQL"""
+	values = [i]
+	for key in labels:
+		if 'varchar' in labels[key]['type']:
+			if key in medal and medal[key] is not None:
+				string = medal[key].replace('"', '')
+				value = f'"{string}"'
+			else:
+				value = '""'
+		else:
+			value = medal[key] if key in medal else 0
+		values.append(value)
+	return '(' + ', '.join(f'{v}' for v in values) + ')'
+	# return f'({i}, "{fields["acad_mies"]}", "{fields["acc_ab"]}", "{fields["acc_aca_orig"]}", "{fields["ville_etab"]}", "{fields["lib_for_voe_ins"]}"),\n'
+
+
+if __name__ == "__main__":
+
+	with open('data/paris-2024-results-medals-oly-eng.json', 'r') as f:
+		data = json.load(f)
+
+	lines = [beginning]
+	lines.append("DROP TABLE IF EXISTS `joparis2024`;\n")
+	lines.append("CREATE TABLE IF NOT EXISTS `joparis2024` (\n")
+	lines.append("  `id` int(11) NOT NULL AUTO_INCREMENT,\n")
+	for k, v in labels.items():
+		lines.append(f'  `{k}` {v["type"]} NOT NULL COMMENT "{v["comment"]}",\n')
+	lines.append("  PRIMARY KEY (`id`)")
+	lines.append("\n) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;\n\n")
+	lines.append(insert_into)
+
+	for i, datum in enumerate(data):
+		if i % 100 == 99:
+			lines.append(make_row(datum, i+1) + ";\n")
+			lines.append(insert_into)
+		elif i == len(data) - 1:
+			lines.append(make_row(datum, i+1) + ";\n")
+		else:
+			lines.append(make_row(datum, i+1) + ",\n")
+
+	lines.append(ending)
+
+	with open('sae303.sql', 'w') as writer:
+		writer.writelines(lines)