I am the author of fileregister. fileregister is a cross-machine tagging system (macOS, potentially Linux).
fileregister keeps durable ids (bookmarks) for a file in a plain-text JSONL-file. Now you can move the files around or rename them and the link will not break.
On top of that you have markdown sidecars where you can store additional data to any file. This can serve as a binder of files which belong together. This can be used to build photoalbums or collect files which are spread over the filesystem.
The essential metadata is saved in the attributes of the files so you can search for the file with Spotlight. The macOS-filesystem-anchor can be replaced by a Linux-filesystem-anchor.
As the yellow book of the files is stored in a JSONL-file it can be marshalled (packed) and unmarshalled (unpacked) on another machine and the links remain intact.
Comments
What are the use cases for this? On other words, what problem(s) does it aim to solve?
I am the author of fileregister. fileregister is a cross-machine tagging system (macOS, potentially Linux). fileregister keeps durable ids (bookmarks) for a file in a plain-text JSONL-file. Now you can move the files around or rename them and the link will not break. On top of that you have markdown sidecars where you can store additional data to any file. This can serve as a binder of files which belong together. This can be used to build photoalbums or collect files which are spread over the filesystem. The essential metadata is saved in the attributes of the files so you can search for the file with Spotlight. The macOS-filesystem-anchor can be replaced by a Linux-filesystem-anchor. As the yellow book of the files is stored in a JSONL-file it can be marshalled (packed) and unmarshalled (unpacked) on another machine and the links remain intact.
Reading helps: https://github.com/rhsev/fileregister#what-you-can-do-with-i...