Add import/export as zip - Githubissues

FlorianPix / climbing_diary

track your climbing activity

GNU General Public License v3.0

2 stars 0 forks source link

Add import/export as zip #75

Closed FlorianPix closed 1 year ago

FlorianPix commented 1 year ago

offer compact and expanded version
the compact version is similar to the db in the way that elements are only saved once and refered to by id
the expanded version saves elements multiple times at each point where they are refered to

compact

name@example.com
- trips
  - trip_name_1
    - trip_name_1.json
    - YYYY-MM-DD_trip_name_1.jpg
  - trip_name_2
  - ...
- spots
- multi_pitch_routes
- single_pitch_routes
- pitches
- ascents

trips expanded (spots that were not added to a trip are omitted)

name@example.com
- trips
  - trip_name_1
    - trip_name_1.json
    - YYYY-MM-DD_trip_name_1.jpg
    - spot_name_1
      - spot_name_1.json
      - YYYY-MM-DD_spot_name_1.jpg
        
        multi_pitch_route_name_1
        
        multi_pitch_route_name_1.json
        
        YYYY-MM-DD_multi_pitch_route_name_1.jpg
        
        pitch_name_1
        
        pitch_name_1.json
        
        YYYY-MM-DD_pitch_name_1.jpg
        
        ascent_name_1
        
        ascent_name_1.json
        
        YYYY-MM-DD_ascent_name_1.jpg
        
        single_pitch_route_name_1
        
        single_pitch_route_name_1.json
        
        YYYY-MM-DD_single_pitch_route_name_1.jpg
        
        ascent_name_1
        
        ascent_name_1.json
        
        YYYY-MM-DD_ascent_name_1.jpg
  - trip_name_2
    - ...
  - ...

FlorianPix commented 1 year ago

842fc1bdae6988a7c13631a5b55d561cc3897c16 added:

compact variant

all images are saved in one folder "img"
all climbing data is saved in one json file with the following structure

{
    "trips": [...],
    "spots": [...],
    "single_pitch_routes": [...],
    "multi_pitch_routes": [...],
    "pitches": [...],
    "ascents": [...]
}

when a user loads the backup data the elements are created as if they were new and therefore get a new id
therefore a temporary translation table between old and new ids is created to reintroduced the relationships between the elements, i.e. trips have spot_ids (the newly created ones and not the old)
the same is true for images (mediaIds)