MerginMaps / MerginMaps/work-packages

Pictures syncronization for work-package <> main project broken?

Open
#72 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
11
Forks
6
PR merge metrics
No merged PRs in 30d

Description

probably related to https://github.com/MerginMaps/work-packages/issues/69

I've setup a Work-packages test project, added some points and pictures in the main project.

I've added my config:

file: Survey_points.gpkg

tables:
  - name: Survey_points
    method: filter-column
    filter-column-name: WS

work-packages:
  - name: WS1
    value: 1
    mergin-project: my-space/workspace-Ws1
  - name: WS2
    value: 2
    mergin-project: my-space/workspace-Ws2

Run the script workpackages script via docker docker run -i -t lutraconsulting/mergin-work-packages my-space/Workspace-master

  1. Issue: all existing pictures are synced to both new projects
    -> i would have expected, each child project only gets the pictures relevant for the work package

I then add points and pictures from the mergin app in both workspaces.

  1. Issue: the points are synced back to the main project but the pictures i take are not
    -> I would have expected the pictures to end up in the main repo as well.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with the provided YAML configuration and Docker command, using points and pictures in the main and child projects. Compare which pictures are sent to each work package and whether newly captured pictures return to the main project. Done means pictures are filtered to the relevant work package and synchronize back as expected.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, python
Domain
backend, data
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.