Structure du projet refaite

9f72853e · ivan.pavlovic · f9da9f5b · 9f72853e · f9da9f5b · f9da9f5b
Commit 9f72853e authored 6 months ago by ivan.pavlovic
--- a/.gitignore
+++ b/.gitignore
-gptKey
-geminiKey
-claudeKey
+dataSources/PubMed/tmp/*
 .venv
\ No newline at end of file
--- a/ProjectNotes.md
+++ b/ProjectNotes.md
-# NCD: data aggregation and classification
-
-## Remarks
-
-
-
-## TODO
-
-### Must
- Trouver en combien de temps les mesh term sont donnée
- Explorer les model non-superviser (classification de texte)
-
- ~~Mesh term vs keyword~~
- ~~Ou il recherche les term (titre, keywords, meshterms, etc...)~~
- ~~Etudier les operateur (A or B and C) (A or B) and C  A or (B and C)~~
- Service qui tourne en arriere plan qui récupere les données
- Reflechire sur la structure de stockage
-
- Créer un ensemble de validation qui permet de tester la qualité d'un modèle (vrai, proche de vrai, proche de vrai mais faux et complettement faux). Donnée provenantente de pubmed et autre part. Source longue et courte.
-
- Créer un model de score
- Créer un script de test
\ No newline at end of file
--- a/api/__pycache__/pubmedApi.cpython-313.pyc
+++ b/api/__pycache__/pubmedApi.cpython-313.pyc
--- a/api/__pycache__/whoApi.cpython-312.pyc
+++ b/api/__pycache__/whoApi.cpython-312.pyc
--- a/api/data/pubmedData.xml
+++ b/api/data/pubmedData.xml
--- a/api/model/__pycache__/facebook.cpython-312.pyc
+++ b/api/model/__pycache__/facebook.cpython-312.pyc
--- a/api/model/__pycache__/facebookBartLargeMnli.cpython-312.pyc
+++ b/api/model/__pycache__/facebookBartLargeMnli.cpython-312.pyc
--- a/api/model/__pycache__/facebookBartLargeMnli.cpython-313.pyc
+++ b/api/model/__pycache__/facebookBartLargeMnli.cpython-313.pyc
--- a/api/model/test.json
+++ b/api/model/test.json
--- a/api/parser/__pycache__/__init__.cpython-312.pyc
+++ b/api/parser/__pycache__/__init__.cpython-312.pyc
--- a/api/parser/__pycache__/json.cpython-312.pyc
+++ b/api/parser/__pycache__/json.cpython-312.pyc
--- a/api/parser/__pycache__/jsonParser.cpython-312.pyc
+++ b/api/parser/__pycache__/jsonParser.cpython-312.pyc
--- a/api/parser/__pycache__/jsonParser.cpython-313.pyc
+++ b/api/parser/__pycache__/jsonParser.cpython-313.pyc
--- a/api/parser/__pycache__/xlsxParser.cpython-312.pyc
+++ b/api/parser/__pycache__/xlsxParser.cpython-312.pyc
--- a/api/parser/__pycache__/xmlParser.cpython-312.pyc
+++ b/api/parser/__pycache__/xmlParser.cpython-312.pyc
--- a/api/parser/__pycache__/xmlParser.cpython-313.pyc
+++ b/api/parser/__pycache__/xmlParser.cpython-313.pyc
--- a/api/data_num.py
+++ b/api/data_num.py
--- a/PubmedInfo.md
+++ b/PubmedInfo.md
@@ -136,7 +136,7 @@ Example: human[organism] AND topoisomerase[protein name]

 When searching for terms, it is important to pay attention to how the search is structured. For example, if you search for **breast cancer** without quotes, the search engine will look for any occurrence of the terms **"breast"**, **"cancer"**, or the exact phrase **"breast cancer"**. To specifically search for the phrase **breast cancer** as a whole, you need to enclose it in quotation marks (" ").

-![Search with and without quotes](./docImg/SearchQuotationExample.png)
+![Search with and without quotes](./img/SearchQuotationExample.png)

 ### API syntax

@@ -205,7 +205,7 @@ Each field has a field tag (enclosed in square brackets, e.g., [TI] for Title) t

 When no field tags are specified, PubMed searches across all fields. However, it also applies Automatic Term Mapping (ATM) to map your terms to MeSH terms, journal names, author names, and other indexed fields, which helps broaden the search intelligently.

-![ATM exemple during search](./docImg/SearchATMExample.png)
+![ATM exemple during search](./img/SearchATMExample.png)

 ### ATM


--- a/api/doc/data_num.json
+++ b/api/doc/data_num.json
--- a/docImg/SearchATMExample.png
+++ b/docImg/SearchATMExample.png