[Feature] Shared External Library with faces/people and moving photos to it / expanded partner sharing

[mbuzina]

I have searched the existing feature requests, both open and closed, to make sure this is not a duplicate request.

• Yes

The feature

I think a classical use case of shared photo management is a family where there is a large curated photo base, which is shared among all and an individual storage for every family member. Synology photos does this, but not perfectly, immich provides some of the functionality, but not all.

My proposal is:

• allow specifying an external (or internal) library as shared among all (or selected) users. For bonus points provide detailed access levels (allow adding, changing, etc.). This is an extended partner sharing, the shared library should provide all functionality a current personal library does, this includes faces & people, tags, locations and memories. For my use case having a single shared library would be enough, others may want multiple with different access rights.
• If you are member of a shared library, it is integrated with your personal one. Your timeline shows both (all) personal and shared libraries, tags, people, folders, ... all show the merged result.
• Images (and if possible all objects like people, tags, ...) show a small overlay icon if they are personal or shared (or both, only possible for non images)
• Images can be moved between the shared and the personal library. This can be shown as a simple drop down, showing all possible library locations (I would not duplicate photos). Moving should handle image+live photo and stacked images well.
• Moving an image will initially use the libraries storage template (each library should get their own template) and images stored in an external library (with individual folders) allows moving photos between folders.
• Tags, faces, people, location move or duplicate with their images. If I move a photo from personal to shared, the persons, tags etc. are added to the shared library, if they are not available there yet and vice versa. orphaned persons, tags, etc. can be removed either directly or via a job.

A few things probably need to be defined (how to handle a person with multiple faces in several libraries, the vector can probably only be based on all faces), but I think implementing this would put immich in front of all other solutions.

Platform

• Server
• Web
• Mobile

[bo0tzz]

#12614