This provides the baseline for an annotation system and a tagging system. Things can also be things like messages, groups, and references to other things (via the UUID address). One of “things” a thing can be is a file path, presumably pointing to a particular sample. Keys don’t have to be unique, which allows a single item to have multiple attributes. Every “thing” has a UUID4 tag as the key (I use the uuid4 library by rxi to generate these). Using this structure, I can make things and link things to things. The Zet structure is essentially a key/value database with timestamps. I’m hoping if I keep at this long enough, these sort of relationships and structures between samples and sounds will naturally form.Ī few weeks ago I started building a Generic Zettelkasten (the “zet”) for myself, which is part of the static wiki generator I built for myself about year or so ago. Over time, this network of connections allows for interesting relationships to emerge. Zettelkastens usually have some sort of cross-referencing capabilities. Well, sample libraries are like that as well. ![]() My approach is to try manually catalogue, tag, document, annotate, etc content in a centralized place, and then build out solutions that can integrate with this database format.Ī Zettelkasten is a means for storing and retrieving information in a very granular fashion. The TL DR is that I’m attempting to turn my sample collections into something resembling a centralized Zettelkasten, and storing it in SQLite. ![]() It’s still a growing and evolving, but I think I have a pretty solid foundation. This is finally a relevant thread for me.Īfter years and years of thinking about it, I recently decided to take a stab at building a system for organizing and curating my various sample libraries and collections.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |