
Add another mount path to the existing network collection entry in digiKam when different computers reach the same photo root through different paths. The Plus control beside that entry is intended for alternate network mounts. It does not grant permission to run several clients concurrently against one common database.
Key Takeaways
- A collection identity and its machine-specific mount path are different.
- Each alternative must resolve to the same photo root, not just a similarly named folder.
- The manual's shared-database arrangement excludes simultaneous client use.
Establish which root each computer actually sees
Before changing digiKam, open the mounted share through the operating system. Identify a few existing files at different depths beneath the intended root. Compare relative paths, recognizable content and file properties across the computers.
For example, a hypothetical Windows drive mapping and a Linux mount might both lead to the same archive. If one points to the archive's parent and the other to a year subfolder, they are not equivalent roots even when both show photographs.
Do not import another archive merely to make an empty view look populated. The external-library identity guide illustrates why selecting the wrong library can look like missing photographs, although its Apple-specific controls do not apply to digiKam.
Extend the registered network entry
Open Settings > Configure digiKam > Collections. Locate the entry under Collections on Network Shares. The Collections Settings manual documents the Plus button beside its path for appending another mount location.
Add the other system's path to this registered collection rather than assuming that repeated Add Collection operations express the same association. Use a path that the relevant client can actually resolve. Record which computer uses each location so later troubleshooting does not confuse an unavailable mount with a missing database record.
The separate Update Path control handles changed collection properties and identifiers. Do not substitute it automatically when the requirement is to preserve several valid network mount alternatives.
Verify identity without creating a second problem
Close other clients using the common database before the proposed check. On one client, confirm the expected root and inspect the selected sample photographs, relative subfolders and existing organizational information. Close it normally before checking the next client.
The manual explicitly warns that its shared network resources do not permit multiple clients at the same time with a common database. Successful path resolution is therefore not evidence of safe concurrent editing. Do not turn this mapping procedure into a multiuser database setup claim.
Keep availability and archive coverage separate
If a path does not resolve outside digiKam, repair the mount or access arrangement first. The collection mapping cannot supply absent source bytes. Check write access separately when metadata or image changes are required.
Likewise, a database containing ratings or albums is not a backup of the photographs. Use the catalog-versus-original coverage distinction when documenting the archive, while following digiKam's own storage rules.
Accept the mapping when the clients sequentially identify the same root and known records without adding unintended duplicate collection entries. No network migration or database-sharing test is claimed here.
Related tasks
- Why Did Photos Open an Empty Library After I Disconnected My Drive?
- Does a Lightroom Classic Catalog Backup Include My Original Photos?
Sources and scope
- digiKam Manual: Collections Settings: Collections have local/removable/network roots and identifiers. Update Path maintains collection mapping. Multiple mount paths do not authorize simultaneous clients on one database. Cloud placeholders are unsupported.
Based on official documentation retrieved and actually opened on October 23, 2026 (Asia/Shanghai). The examples and acceptance procedures are proposed, not application tests. Web-tool readable source extracts are retained in research/photo-data-076-080-web-evidence.json; no raw HTTP status is inferred from search availability.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: Pignatta / Pixabay, Pixabay Content License. This is an illustrative source photograph, not an application screenshot or a generated test result.