nextcloud / nextcloud/maps

external storage: photo-scan bug

Open
#274 8 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
598
Forks
113
PR merge metrics
No merged PRs in 30d

Description

Describe the bug
when using external storage: you have to run the initial maps:scan-photos for every user

To Reproduce
Steps to reproduce the behavior:

  1. create an external storage folder with photos with gps-tag in it for more than one user
  2. scan the photos for one specific user with occ maps:scan-photos userid
  3. the photos appear only for that specific user in the maps app

Expected behavior
the scanned photos should appear for all users with access to the external storage folder

Desktop (please complete the following information):
Nextcloud 17.0.2
maps app 0.1.4

Additional context
The problem with that is, if you have a large external storage folder, with many photos, you had to scan this folder for every user again, which is not that efficient.
So a better way would be connecting the information to the external storage id -> so if you have access to that external storage folder, you will automatically see the photos on the map, if they were scanned before - no matter with which userid you have scanned that folder.

BTW: I guess the same problem would appear while using the groupfolders-app

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 tracing the occ maps:scan-photos userid entry point and how scanned photos are associated with external storage access. Reproduce with one external folder shared by multiple users, then verify that a single scan makes the photos visible to every user with access, including a group folder if supported.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.