[SUGGESTION] Import Tag list

[tylerkade]

Having a ton of fun playing around with the program so far.
I think implementing an 'import tag' feature would be beneficial down the line, which would allow the community to share their entire tag set-ups, letting new users quickly get started.

[Loran425]

Are there any sample tag libraries/formats that would be better to start with I would mind looking at building an importer but I'm not sure what style/format we'd be looking at as the basis.

[Qronikarz]

which would allow the community to share their entire tag set-ups

It kind of reminds me of Tag Repositories that Hydrus program uses. Maybe it could be looked at to implement something similar.

Are there any sample tag libraries/formats that would be better to start with

Do you mean like in general from other programs?

It would be best first to settle on tag importing/exporting for TagStudio itself before making an importer for other programs, but if you want I can recommend few programs with tag support.

[Loran425]

I guess I was thinking this was asking for a way to import a preexisting tag list, and for that we'd need to know what format they'd be coming from.

If bulk tag creation is the point it might be possible to just do something like a table view where you could add multiple tags at once except for maybe subtags.

As for exporting/importing tags created in tag studio that would be pretty cool and fairly simple to implement if that's all we're looking for is shareability of a tag library

[Sythelux]

I have a program that does export sidecar files along with the original file and I know we don't want to introduce sidecar files here, but it be neat if we had an importer for sidecar files.

the format is really just:
.ending.txt or .txt
and the content is just a comma separated list of tags.

[CyanVoxel]

I have a program that does export sidecar files along with the original file and I know we don't want to introduce sidecar files here, but it be neat if we had an importer for sidecar files.

the format is really just: .ending.txt or .txt and the content is just a comma separated list of tags.

More import options is always nice, especially from other systems like sidecar files! There's currently some existing code that's capable of doing this, but is laying dormant until I have a proper interface for it. Preferably with some configurable options, like filename patterns and expected data structures like a plain text list, JSON object, Eagle sidecar, etc. This is part of a greater "macro" system I have planned that will let you trigger these sorts of operations conditionally and automatically, for example when importing new files.

[Qronikarz]

I have a program that does export sidecar files along with the original file and I know we don't want to introduce sidecar files here, but it be neat if we had an importer for sidecar files.

You would need different importer for every program. Sidecar files can have different structures. TagSpaces stores sidecars in .ts folder and every file is in JSON format there.
But I still stand by my opinion that first we need TagStudio to have a working import/export of it's own before attempting import/export of others (there's a lot of other tagging programs)

[Computerdores]

But I still stand by my opinion that first we need TagStudio to have a working import/export of it's own before attempting import/export of others (there's a lot of other tagging programs)

I would even go as far as to say that, once TagStudio has a format to import/export from, it would be better to not implement any other formats directly in TagStudio and instead have standanlone tool(s) that convert to and from this format.

[Sythelux]

and instead have standanlone tool(s) that convert to and from this format

This would be fine too. If TagStudio has a solid import and export API I could imagine writing a tool at least for the files how I have them and provide it as an example.