[BACK-END] Folder and files organization of application is a mess

[beayache]

User scenario:

• Today, the back-end data are saved in a single directory
• It is hard to find the data correctly during development phase

Issue:

• Each part/assembly json files are saved in a single folder per object, in a common directory (bocket)

Expected behavior:

• Create a folder structure that carries and classify the data into the back-end: "organization folder" > "workspace folder" > "assembly folder" > "part folder" OR "organization folder" > "workspace folder" > "part folder" (if there is no assembly)

Data involved:

• All

[RePloZ]

I need more information about the file lifecycle (archive + 3D) @beayache @guillaume2pit

[RePloZ]

[MAJ] : New Files Organization finished

[beayache]

Intégrer la proposition d'organisation dans le DAT après implémentation SVP