Duplicate sequences between the server and this PC: recognise, compare, keep apart or merge and sync #73

Open
opened 2026-11-16 17:10:25 +01:00 by Alby96 · 1 comment
Owner

Owner request (2026-11-16), verbatim:

Potrei avere la stessa sequenza prima caricata sul server e poi ancora presente sul computer se indico una cartella di lavoro o una cartella per delle sequenze locali. In questo caso il software deve riconoscere i doppioni ed eventuali differenze e farti scegliere cosa fare. Deve essere una gestione avanzata che riconosce differenze, chiede se mantenere le due cartelle o integrarle e poi sincronizzarle, ecc ecc.

What is asked:

  • Recognise duplicates. The same sequence may exist on a server (uploaded earlier) and on this PC, in the local archive or in a work or local-sequences folder the user points Chronos at.
  • Show the differences:
    • photos only on one side, and changed photos;
    • title and metadata;
    • project edits and versions;
    • renders;
    • deleted photos.
  • Let the user choose:
    • keep the two copies apart;
    • integrate them into one and keep them in sync afterwards;
    • other choices to be designed.
  • Destructive steps follow the house rule: a dry-run plan, hash verification, then an explicit user action.

Plan, design and questions: to follow in docs/requests/2026-11-16-owner-review-6.md.

Owner request (2026-11-16), verbatim: > Potrei avere la stessa sequenza prima caricata sul server e poi ancora presente sul computer se indico una cartella di lavoro o una cartella per delle sequenze locali. In questo caso il software deve riconoscere i doppioni ed eventuali differenze e farti scegliere cosa fare. Deve essere una gestione avanzata che riconosce differenze, chiede se mantenere le due cartelle o integrarle e poi sincronizzarle, ecc ecc. What is asked: - **Recognise duplicates.** The same sequence may exist on a server (uploaded earlier) and on this PC, in the local archive or in a work or local-sequences folder the user points Chronos at. - **Show the differences:** - photos only on one side, and changed photos; - title and metadata; - project edits and versions; - renders; - deleted photos. - **Let the user choose:** - keep the two copies apart; - integrate them into one and keep them in sync afterwards; - other choices to be designed. - **Destructive steps follow the house rule:** a dry-run plan, hash verification, then an explicit user action. Plan, design and questions: to follow in `docs/requests/2026-11-16-owner-review-6.md`.
Alby96 added this to the v1.2.0 milestone 2026-11-16 17:10:25 +01:00
Alby96 added the enhancementarea/desktoparea/server labels 2026-11-16 17:10:25 +01:00
Alby96 added this to the Road to 1.0 project 2026-11-16 17:10:29 +01:00
Alby96 moved this to In Progress in Road to 1.0 on 2026-11-16 17:10:29 +01:00
Author
Owner

Owner answers (2026-11-16):

  1. Detection is a setting, default Ask always. The other choices are: link when the copies are identical, or link when half or more of the photos are shared. "Keep separate" is remembered.
  2. Integrate means completing both copies. Each side receives the photos it lacks, the differences are settled once, then the copies stay linked and in sync. Two copies on this PC are merged into one sequence, and the other folder goes to the archive trash after hash verification.
  3. Photos only on one side, or differing, is a setting, default Union: a differing photo is kept in both versions and can be dropped to the trash. The other choices are: choose per photo, or one side wins.
  4. Title, tags, rating, notes and settings are settled line by line.
  5. Non-Main projects are a choice in the dialog, default copy across with their history, renamed <name> (<PC>) when the name is taken. This amends BRIEF §14.5.
  6. After integrating, new photos move automatically both ways, paused on metered connections. A deletion on one side is shown and applied here only on confirmation.
  7. A folder of local sequences is added with Adopt folder…: it becomes an archive and is compared with the server and the other archives.
  8. Upload all local skips suspected duplicates and flags them.

Code map: today the ids never match between this PC and a server. Links come only from an upload or download, or from a silent match (same first second, same camera, at least 50 % shared). The server never files into the target a photo that another sequence already holds. No merge engine exists.

Owner answers (2026-11-16): 1. **Detection** is a setting, default **Ask always**. The other choices are: link when the copies are identical, or link when half or more of the photos are shared. "Keep separate" is remembered. 2. **Integrate** means completing both copies. Each side receives the photos it lacks, the differences are settled once, then the copies stay linked and in sync. Two copies on this PC are merged into one sequence, and the other folder goes to the archive trash after hash verification. 3. **Photos only on one side, or differing**, is a setting, default **Union**: a differing photo is kept in both versions and can be dropped to the trash. The other choices are: choose per photo, or one side wins. 4. **Title, tags, rating, notes and settings** are settled line by line. 5. **Non-Main projects** are a choice in the dialog, default **copy across** with their history, renamed `<name> (<PC>)` when the name is taken. This amends BRIEF §14.5. 6. **After integrating**, new photos move automatically both ways, paused on metered connections. A deletion on one side is shown and applied here only on confirmation. 7. **A folder of local sequences** is added with *Adopt folder…*: it becomes an archive and is compared with the server and the other archives. 8. **Upload all local** skips suspected duplicates and flags them. Code map: today the ids never match between this PC and a server. Links come only from an upload or download, or from a silent match (same first second, same camera, at least 50 % shared). The server never files into the target a photo that another sequence already holds. No merge engine exists.
Sign in to join this conversation.