[Feature] Quickly hide/unhide External Libraries from Timeline

[BugsWorld]

The feature

A toggle that we can turn on to quickly hide all assets related to a specific External library. This is extremely useful when you wanna browse your timeline in different "modes". So for example you want to scroll through your timeline and see only your Family memories, so you hide all other libraries and keep the Family one only. Or you want to browse your personal pictures only through the timeline, so you only keep that one on. You get the idea, very useful, very neat.

To take it a step further, it would be nice if one user could share a specific library with another user in a way that would add all the pictures to the user's timeline and not just under the "Sharing" tab.

Platform

• Server
• Web
• Mobile

[aisbergde]

It's a very good idea. Assets could be moved between libraries. It is on the road map to use fingerprints to detect, if it is the same asset or not. And if the source folder for the upload would be saved, then we could move for example screenshots into a separate library.

I want to extend the idea:
if we could assign custom tags and filter by them, then the external libraries are just special cases: each library can have its own tag, which is automatically assigned to all assets. Then I even don't need to move assets between libraries. We would only need a good system to filter by tags.

[gschintgen]

This feature would also be very useful for a mixed usecase in combination with e.g. Digikam:

• Use background backup for everyday operation and immediate cross-device availability.
• Periodically, e.g. after a vacation, transfer/manage/tag/edit/curate/etc in Digikam and the re-add the finalized collection in Immich as read-only external library.
• Remove the originals in Immich's upload library.

It's that last step that could be made more convenient by temporarily hiding external libraries: It'd be easier to see which assets are only the unmanaged backups in the default upload library.

I know that may not be the intended all-Immich workflow, but I'd guess that a sizable number of Immich users do try to make it work in combination with external management tools.

And there is of course the usecase given by OP which I fully agree with.