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]: Relational Tags, tags that refer to files #638

Open
3 tasks done
DominikAgejev opened this issue Dec 11, 2024 · 1 comment
Open
3 tasks done

[Feature Request]: Relational Tags, tags that refer to files #638

DominikAgejev opened this issue Dec 11, 2024 · 1 comment
Labels
TagStudio: Tags Relating to the TagStudio tag system Type: Enhancement New feature or request Type: Wontfix This will not be worked on

Comments

@DominikAgejev
Copy link

DominikAgejev commented Dec 11, 2024

Checklist

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

Description

I would like to store the same text in multiple languages and also easily view and switch between the multiple versions. I'd also like to be able to connect sequels with a tag that has the relation coded in and not just represented using text.

To that end I suggest adding the capability for tags to refer to files (denoted with square brackets), for example:

Translation of [De Genesi ad litteram]
Excerpt/Quote from [Garcia Moreno]
Volume {II} of [The Sincere Christian]

The [file] part of the tag should be clickable and immediately present that file in the library along with all related files while clicking the whole tag should filter the library for the specific relation (for example all translations of a specific book).

Solution

No response

Alternatives

The obvious workaround is to just write out the desired tag (e.g. Translation of Summa Theologiae), however, this does not connect the files in any way so that if one wants to find the original version one has to search for it manually.

@DominikAgejev DominikAgejev added the Type: Enhancement New feature or request label Dec 11, 2024
@CyanVoxel
Copy link
Member

While I support the idea of file backlinks in something like text fields, this would be a bad idea for tags themselves.

Tags are meant to be representations of attributes and contain relationships between other attributes, which then get applied to file entries. Having links to local files stored within tags breaks this description model. A file is not an attribute, and a link to a file in a tag name is not a concrete relationship - Is the tag "inheriting" the file? Is the tag "composed" of the file? Is the file "composed" of the tag? What would any of those relationships even look like? This also causes issues with sharable tags/tag packs - If you share a tag that references a file, that link is now immediately broken.

What you're looking for can also be simply achieved with two tags each: For example, "Translation of [De Genesi ad litteram]" can be broken up into "Translation" and "De Genesi ad litteram" tags. Clicking on or searching for "Translation" will filter the library for all translations, searching for "De Genesi ad litteram" will get you all results for that book, and searching for both will get you only translations of that specific book.

Backlinks in text fields however I feel are perfectly fine, as there's no real relationship descriptions going on here and text fields serve just to attach additional notes and info to files themselves. In your case, along with the tags mentioned above you could have links on the translated files that link back to the original copy to make it easier to jump to that specific file in your library.

@CyanVoxel CyanVoxel added Type: Wontfix This will not be worked on TagStudio: Tags Relating to the TagStudio tag system labels Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TagStudio: Tags Relating to the TagStudio tag system Type: Enhancement New feature or request Type: Wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants