I notice that CDLCs are getting updates all the time, and the authors are usually pretty good about listing some manner of 'v1.0' type tags. However, that versioning isn't always built into the filename, and even for those that do so it is a very manual process of cross-checking that you have the latest and greatest. Any tips or obvious things I'm missing on keeping things at the bleeding edge?

I have the feeling that most people are doing what I do, which is check the database a couple of times a day, with the database sorted by latest updated/added. When I see a song I already have, I check it out to see if it hasn't been updated.

 

Not all that efficient, I suppose. But it's like going to the candy store every day.

It is easier if the file dosn't have the version inside his name to keep it simple inside the RS dlc folder but as long as their isn't any format for the file name it will be messy with everyone naming the file the way they want.

How about if only the final version of a CDLC has NO version number?

Possibly, but what if an author doesn't follow this? Then you are still stuck checking manually :)

 

I was thinking more along the lines of having the search site maintain a "github"-like song version database. Each user would downlad a copy of this 'database' (it might just be a text file) which would have all the songs and their current version. You could run a simple tool to compare your text file with the online database to see what has been updated since your last update, go grab updates for the songs you care about, then update to the latest online snapshot. Obviously, this isn't a full solution, but it automates a little bit of it.