How to Handle Complex Tagging in RavenDB
In the RavenDB mailing list, we got a question about tagging. In this case, the application need:
1. Tags have identity ("set" has a different meaning if I'm talking math, music or sports).
2. I want to know who tagged what and when.
3. I want to do this once, as a service, so i don’t need have ids in each document i want to tag. In my app, there are many such document types.
Let us see how we can approach this in RavenDB. We are going to do it like so:
Note that because tags have identity, we store only the tag id inside the tagged object, along with the required information about who & when it was tagged.
Now, let us try to have some fun with this. Let us say that I want to be able to show, given a specific album, all the albums that have any of the same tags as the specified album.
We start by defining the following index:
Note that the naming convention matches what we would expect using the default Linq convention, so we can easily query this index using Linq.
And now we want to query it, which, assuming that we are starting with albums/1, will look like:
This translate to “show me all of the albums that share any of the specified tags, except albums/1”.
And this is pretty much it, to be fair. Oh, if you want to show the tags names you’ll have to include the actual tags documents, but there really isn’t anything complex going on.
But what about the 3rd requirement?
Well, it isn’t really meaningful. You can move this Tags collection to a the layer super type, but if you want to be able to do nice tagging with RavenDB, this is probably the easiest way to go.
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)