Save tag data and metadata in a separate file
For instance, have a text file Hello.tgd with a folder Hello, or Hello.jpg.tgd for Hello.jpg, which can store both the tags for a file, and let us add notes about a file. This would also let us keep hyperlinks to the file constant even when the tags change. (If a note was made here about every hyperlink TO this file, it could also auto-update links to the file when we move it)
Implelmented in the PRO version
-
Heather Green commented
Oh, and sorry, I forgot to add something to my below comment.
If you know that the files which you need to have unchanging filenames (so that you can hyperlink to or share them) are going to be files which you will need to edit/change in the future, here is what you can do. Once you have finished duplicating your files (see below comment), create shortcuts (.LNK files) to each of those duplicated files. Now, cut your newly created shortcuts and paste them into the original folder which holds your tagged files. And now you will have to put those same tags on your new shortcut files and delete the old tagged files. :( Sorry, I don't know of any other way to do this, so it could take some time. The good news is that if you haven't tagged your files yet, you can go ahead and do all of these steps and not have to spend any time retagging your shortcuts since you've already been tagging those from the beginning. Good luck!!! -
Heather Green commented
OK so here is a temporary workaround concerning not breaking hyperlinks (or just having duplicate files that do not have tons of tags in filename for reasons such as sharing).
It's now easier to move files around in TagSpaces, so once you have finished tagging your files and need copies of those files which will have unchanging filenames, first: select all of the files. Now, click on the Copy or Move Selected Files button (looks like 2 pieces of paper). Now select or create your target path, which I recommend to be a folder created specifically to hold these files only. In TagSpaces, navigate to the folder you just now chose and select all of the files in it (can be done by pressing Toggle Select All Files button). Now, press the Add or Remove Tags for Selected Files button and click the red Clean Tags button which is in the bottom left-hand corner of the window that pops up. After confirming this action, all of the tags will be removed from your duplicate files, thus instantly removing all of the bracketed tags from your files' filenames.
While doing this does require you to hold duplicate files on your system, it's the only workaround possible right now to quickly be able to keep copies of files which will NOT have filenames that are constantly changing but still be able to change the tags of the original files. Since doing this will take up space, please make sure you only keep the duplicates when you need to, i.e. when you know you will need to link to these files or share them with others. I hope this has been helpful to people and hopefully TagSpace Dev will decide to save tag data in a separate file as Mishel Johns has suggested so that we can hyperlink and share files easily. ;) -
AdminIlian (Dev, TagSpaces) commented
since version 1.8.6 you can export your tag groups and import them for a given location. For details please refer to http://www.tagspaces.org/tagspaces-1.8.6-released/
-
Greg Smith commented
This functionality is very important to me. I know nothing about the technical considerations re: individual metadata files vs a database, but being consistent and easy to back-up are what I want to see.
-
Stefan Infp commented
This feature would be amazing. I hope it will be developed.
-
Ernst Blaauw commented
By implementing this function, TagSpaces would become usable with a Version Control System like svn or git. That would be great!
-
Max Pittsley commented
I agree. The fact that changing tags breaks hyperlinks is a **huge** problem.
There's another post that also suggests using metadata on file formats that support it <https://tagspaces.uservoice.com/forums/213931-general/suggestions/5948854-use-metadata-where-possible>, but I don't think this is the right approach. This would create inconsistency, and doesn't solve the problem for the type of files where it would matter most (HTML, MD).
I would support the approach of having fork data/meta files a la Mac OSX or Unity3D that are named the same as and sit alongside the files that they describe, as suggested by Mishel.
Another possibility is having one tag database file that resides in the root of each Location. For this, it would be best to choose the most efficient storage engine (so not YAML, perhaps SQLite).
I haven't had a look at the source code yet, but if this app is architected responsibly, adding the ability to save tags into a database or fork file rather than into filenames would only require refactoring a single class, only a few methods.
-
Duarte Farrajota Ramos commented
Perhaps support something like XMP metadata?
That way tags don't change file name which will allow external file linking, and there is no need for a database. There is also the XMP sidecar if one would like to support an already existing standard for external metadata filesMore about it here http://en.wikipedia.org/wiki/Extensible_Metadata_Platform
Something ID3 tag support for media files that don't support XMP would also be great. -
Claudius Ellsel commented
The problem then is that one has many files that just save information. I would then suggest to save everything in a database file, but this is not intended, afaik. Maybe this could be optional.