Feature: Enhance Analaytics module to fetch Ontology visits, User visits, and the Most visited pages in the month

[syphax-bouazzouni]

Changes

• Upgrade our code to the latest release of NCBO: https://github.com/ncbo/ncbo_cron/releases/tag/v5.26.0

  • Add an option to not generate the annotator dictionary on each ontology parsing
  • update ncbo_ontology_archive_old_submissions script
  • update ncbo_ontology_import script, to create contacts if inexistent

• Update the analytics module to use the new version of the Google Analytics client (starting 2023), this needs a new configuration file

  # Google Analytics GA4 config
  config.analytics_path_to_key_file          = "config/your_analytics_key.json"
  config.analytics_property_id                  = "123456789"
  config.analytics_path_to_ga_data_file = "data/your_ga_data.json"  # will be created if not-existent 
  config.analytics_start_date                    = '2015-01-01' # since when we want to fetch Google Analytics  

• Update the Analytics module, to fetch and save, in addition to Ontology visits, now also User visits, and the Most visited pages in the previous month.

• Add a script to import and save Google Analytics UA (2013-2023)

[syphax-bouazzouni]

Hi @mdorf (or @alexskr ), can you provide me information on where I find these JSON files related to the new Google Analytics configuration (it would be also good if you can add samples)

[alexskr]

analytics_pathtoua_data_file file contains exported Google Universal Analytics data. It can be empty if you haven't previously used Google Universal Analytics/old data) data. analytics_path_to_ga_data_file is a file that gets populated by the process and initially can be empty. I have created https://github.com/ncbo/ncbo_cron/issues/71 to update documentation on how to generate yaml file containing exported google universal analytics data.

[syphax-bouazzouni]

analytics_pathtoua_data_file file contains exported Google Universal Analytics data. It can be empty if you haven't previously used Google Universal Analytics/old data) data. analytics_path_to_ga_data_file is a file that gets populated by the process and initially can be empty. I have created ncbo#71 to update documentation on how to generate yaml file containing exported google universal analytics data.

We have used Google Analytics for years so I assume we have Google Universal Analytics data, the question would be where do I find the button "export to JSON"? I didn't not find any easy solution to do it without doing a script that calls there API.

[mdorf]

analytics_pathtoua_data_file file contains exported Google Universal Analytics data. It can be empty if you haven't previously used Google Universal Analytics/old data) data. analytics_path_to_ga_data_file is a file that gets populated by the process and initially can be empty. I have created ncbo#71 to update documentation on how to generate yaml file containing exported google universal analytics data.

We have used Google Analytics for years so I assume we have Google Universal Analytics data, the question would be where do I find the button "export to JSON"? I didn't not find any easy solution to do it without doing a script that calls there API.

Please see #71

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (development@987fba3). Click here to learn what that means.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## development #17 +/- ## ============================================== Coverage ? 55.05% ============================================== Files ? 20 Lines ? 1475 Branches ? 0 ============================================== Hits ? 812 Misses ? 663 Partials ? 0 ``` | [Flag](https://app.codecov.io/gh/ontoportal-lirmm/ncbo_cron/pull/17/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=ontoportal-lirmm) | Coverage Δ | | |---|---|---| | [unittests](https://app.codecov.io/gh/ontoportal-lirmm/ncbo_cron/pull/17/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=ontoportal-lirmm) | `55.05% <0.00%> (?)` | | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=ontoportal-lirmm#carryforward-flags-in-the-pull-request-comment) to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.