Tag Cache renamed

[bascule]

... I think the problem is database is too generic of a term to be given proper noun status.

That's absolutely the point. In this world of search, it really has to be more unique than that, otherwise no-one will be able to find it. even Tag Cache was bad enough, because some people split it and some concatenated it.

How about TagNavi or TagNavigator; that would also be consistent with the configuration file names...

[Febs]

I think Linus is right.

In terms of search, I think that it would be comparatively easy to find information relating to "Database" compared to "TagNavi" or any of the other terms that have been suggested.

[Arj]

Did a quick search on this site for both 'tagcache' and 'database'.  Got similar numbers of hits and most hits for either referred to the tagging database or ID3 database.  However, 'database' also gets hits for 'feature request database.'  I think that, when searching, 'database' stands a better chance of getting false hits for what you want when looking for topics on the tagging database.  Its a pretty generic word, even when talking about the context of DAPs.

I think it would be better to have a descriptive name that brands the tagging database, although I haven't got a brilliant suggestion (yet).

[Febs]

The problem with a "descriptive name that brands the tagging database" is that you need to know the "descriptive name" to find information about it.  A user new to Rockbox may think to do a search for "database."  A user new to Rockbox would never think to do a search for "RockNavi" or anything like it.

I would rather use a generic word and run the risk of having searches return too many results than to use an unintuitive word and have searches return no results.  Overinclusive results can be narrowed with a more refined search.  For example, I did an advanced search of ("tag" and "database") and all of the results related to the tag database/tag cache.  

[ilikedirt]

I think "database" is just fine and much better than TagCache. I much prefer that to stylo-cryptic names ala RockNavi (which could mean almost anything if you ask me)  or something. Just like Linus said, what would you expect a "database" on a DAP to be? An id3 tag database - just like on any other DAP.

[bascule]

* bascule  waves white flag

Having now installed the latest CVS version, The Database option does seem to fit well in the menus etc., however, I'm still a bit concerned about differentiation in the documentation, but c'est la vie...

[Llorean]

Being called "Database" now, rather than an explicit metadata/audio related name, perhaps it could also provide advanced features for the playlist catalog (making use of the extended M3U features or comments within them).

[Mikerman]

TagDataBase seems logical to me. It doesn't flow as well at TagCache or TagBase, but there is no mistaking what it is.

Just brainstorming for a moment on something descriptive and yet, yes, catchy--

TagDab?

(I'm not convinced of that myself, but thought it might get some creative juices going.)

[Sherv]

Hahahah, TagDab! A generic "MP3 Database" suits me fine...

[Mikerman]

Hey, just say it 79 times fast and it grows on you ...

[Genre9mp3]

The only reason I didn't want TagCache to be renamed was that I was used to that name and because I always thought it was smart. I realise though that the name wasn't accurate so the renaming was the right thing to do. Please, no more "catchy" alternatives. I'm sure that TagCache was the best on that aspect.

[Cassandra]

I think I'd be inclined to call it the "Track database", since it contains information about each track on the player.  Simple, functional, and intuitive.