Okay, we've now touched on one of my to-do's for the weekend.
I JUST created this top level last week. In the course of creating a top level, that is directly related to clean up, I run a query to correct each story's disclaimer, according to which subcat it happens to be in. I've not yet gotten to this step. The ONLY time I don't do this, is for crossover stuff, until we''re done sorting and MOVING the crossover stuff around. And that, only where I've gotten sub sub cats based on the specific crossovers. Frankly, I haven't the TIME to edit each individual story like that, and fix it site wide UNLESS I use a query to do it, based on criteria which allows me to correct multiple stories at one time.
Having said that, I did just that, a couple years ago, throughout the site. After that, it fell back on the user to see to it that the field is properly filled out, once again. By the way, running that site wide, and tailoring the query to each and every different area, took me a little over a week, as I did this after work, when I got home. That was a one time thing. Just as, when I run this query where categories have been moved to this new top level, that correction is ALSO a one time thing. I'll push up my timetable a bit, and go ahead and do this for the new top level when I get home today, rather than waiting a couple days for when I have it scheduled.
Yes, I do schedule my activities, as I have many, many things that I'm the only one doing, because they require direct db access to do them. There can be only one person working in the database directly at any given time, so I can't apportion the tasks out. Not without kicking whoever else (me) happens to be working in it, out. As I'm in the database off and on near continually when I AM home, you can all see why that would not be a good thing. It'd make me right testy it would, since I'm always in the middle of doing SOMETHING.
As to moving the Bible to this new top level, that I can't do. The King James version is copyrighted in perpetuity, everywhere. What this means, is that if I or anyone else finds ANY instance of existing copyright to a published work, unless and until that copyright expires, it cannot be moved to this top level.
Finally, while we all agree having to state the obvious is an annoyance, it's something we have to do regardless. Going back to Apollo's example of hot coffee having to be labeled, we all remember the McDonald's lawsuit which made that a necessity, don't we?
Think about it. Any person realizes hot liquid will scald, if it spills on to you. Yet, because, at the time, they did not label their cups (no one did) with Caution: Hot Liquid, this person who scalded herself AFTER buying a fresh cup of HOT coffee and spilling it on herself while still in the drive thru, was able to sue and win a settlement. So now, as a result, all vendors who sell take out of hot liquids, have to have cups which are labeled Caution: Hot Liquid.
Much the same thing applies to the disclaimer thing. Yes, we all KNOW this is primarily a fanfiction site. However, we also have our originals section, and real person fiction section. With having true stories able to be published in originals, and the real person thing, we HAVE to state 'this is fiction'. Look in the front of any book you buy, and you'll see the same sort of language. Look at the end of a movie or tv show when the credits roll. Again, there is always a disclaimer. As Apollo mentioned earlier, the disclaimer thing is not new. It's something that's had to be done for a number of years, since late 2004 I believe (Apollo can tell you for certain). With this being early 2011, that's six plus years that this has been in place.