Make Up of the Data Page for the June 14th Demo

[lepeuvedic]

Problem

1. On June 14th, it is highly likely that we will have zero or one automatically connected data source, public and private sources together.
2. We do not even have an endpoint to convey that information to the front-end.
3. The data page currently displays fake and generic data, which is not acceptable for the client.
4. Manual updating of less frequently updated sources (base Empreinte, Agrobalyse) is perfectly acceptable and therefore directly storing the status in the front-end code is also half-way correct, since the front-end will receive updates much more often. Static response from the back-end would also be half-way correct if we can define an endpoint, but weaving a new data path in the front-end might take too much time.

How to Reproduce

1. Authenticate and enter the dashboard
2. Go to the Data page using the side menu.
3. Observe green yellow red nonsensical information for private and public data sources

Desired Behavior

"up to date" is defined as less than one week old for private sources, and it will be the case.

• First Step: Update the static data in the Front End to reflect the following status:
  • Public Databases:
    • Base empreinte : green (up to date, recently accessed)
    • Base agrobalyse : green (up to date, recently accessed)
  • Private Data Sources:
    • GrDF : green (up to date, not recently accessed)
    • Klio : yellow (up to date, not recently accessed)
    • accounting file : for files, the information appears for each blocked file (red, missing mapping) and for the last loaded file of each type if the status was previously green (green means that all the useful data has been loaded from the file).
• Second Step: Define an API endpoint and weave a data path into the front end to no longer have to modify the information in the front end.

It is acceptable if we manually fetch and load client and public data in the SaaS.