Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: Store library data in separate location #819

Open
3 tasks done
MachCoyote opened this issue Feb 26, 2025 · 3 comments
Open
3 tasks done

[Feature Request]: Store library data in separate location #819

MachCoyote opened this issue Feb 26, 2025 · 3 comments
Labels
Priority: Medium An issue that shouldn't be be saved for last TagStudio: Library Relating to the TagStudio library system Type: Enhancement New feature or request Type: File System File system interactions
Milestone

Comments

@MachCoyote
Copy link

Checklist

  • I am using an up-to-date version.
  • I have read the documentation.
  • I have searched existing issues.

Description

Library data is currently stored in a .TagStudio folder inside the folder of the library in question. This somewhat undermines the goal of not using sidecar files and contributes to folder clutter, especially at scale. It would be nice to be able to store library data in a centralized location, or perhaps at the root of the drive.

Solution

Allow the user to define a directory where all Tag Studio library data is stored.

Alternatives

Place all Tag Studio library data at the root of the drive, rather than the root of the library folder.

@MachCoyote MachCoyote added the Type: Enhancement New feature or request label Feb 26, 2025
@CyanVoxel CyanVoxel added TagStudio: Library Relating to the TagStudio library system Priority: Medium An issue that shouldn't be be saved for last Type: File System File system interactions labels Feb 26, 2025
@CyanVoxel CyanVoxel moved this to 🍀 Backlog in TagStudio Development Feb 26, 2025
@CyanVoxel CyanVoxel added this to the Alpha v9.6 milestone Feb 26, 2025
@Tishj
Copy link

Tishj commented Feb 26, 2025

So all libraries will need a unique identifier to avoid collision?
I don't fully understand why you want this feature.

Whether it's ~/.TagStudio/<identifier>/tagstudio.sqlite or <library_path/.TagStudio/tagstudio.sqlite you'll still need the same amount of folders, they'd just be closer together

If this was talking about metadata that is shared across libraries then I agree, but that already exists
I'm not sure where it lives on Unix but for Windows it lives in appdata

@Tishj
Copy link

Tishj commented Feb 26, 2025

It makes some sense when we're talking about decoupling the library from the folder, which I think is proposed in a separate issue. So a library doesn't necessarily have just a 1-to-1 relation with a folder.

@MachCoyote
Copy link
Author

you'll still need the same amount of folders, they'd just be closer together

That's kinda the point. It's not really about raw folder count, more about distribution and not having a ton of .TagStudio folders scattered throughout my filesystem which I have to see whenever I'm browsing through it.
My "Assets" folder is for my assets and my assets only, not their tag data too.
To me using these ""sidecar folders"" aren't much different from using sidecar files, just to a much lesser extent.
If they're off in a specific folder somewhere the user never needs to see or interact with them unless neccessary.
Centralizing it would also make it simpler to backup all of my tag studio library data in one go.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Medium An issue that shouldn't be be saved for last TagStudio: Library Relating to the TagStudio library system Type: Enhancement New feature or request Type: File System File system interactions
Projects
Status: 🍀 Backlog
Development

No branches or pull requests

3 participants