DemonGoddess

Moved to Hellsing>Crossovers

done

Thing is, by editing, your story is no longer bumped to the top of the list. That was fixed MONTHS ago. That sort of a review would be considered a flame. Delete it from your review board. As to the original troll review referenced in this topic, I'll get the pertinent data to the right people, and delete the review. I'll also delete the blank review.

pffft. Doesn't matter how much we disagree with each other, that has no bearing on whether or not a user is kicked. Certainly isn't a REASON to. Again, as a guest poster, there are posts you've not seen which are actually relevant and pertinent to this discussion. I have asked repeatedly for patience while we go through this very large database (in those other posts I'm referencing), and correct many many things. That's not too much to ask, now is it? Would you rather that we not bust our asses AFTER we get off work, in order to stabilize this thing? So we can have a crash like what occurred in 2003? THAT is exactly where we WERE headed. I have addressed the search engine question numerous times. So here I go again. The search engine, such as it is, was by design made for a much smaller database. It is not made to handle the load of a 6GB database, which is what we have. Due to major changes in coding languages which RUN these programs, in order to make a better search engine, it has to be rewritten. When it is rewritten (which is in progress), the query language itself has also changed tremendously from the time that this original program was written, so the queries themselves within the script need completely redone in order to work in a manner which will allow more thorough search of the database, without OVERLOADING the database. If, for example, the current search engine was given more search options, it is LIKELY that it would open up too many connections to the database itself. When that happens, the SQL server resets. When the SQL server resets, ALL the programs go down for 15 minutes to an hour. For obvious reasons, there is no tweaking we can do to the current search engine. That's exactly why it's being replaced. However, it does take time to make sure that once that module is written, that it is compatible to what is already there. Not only that, it takes time to WRITE this sub routine in the first place. Realistically, it will not be ready to launch until the beta version of the new program is. That is simply due to the fact that there are incompatibilities between the version of language this was written in years ago, and the version that we have to work with now.

moved to temp subcat, to be inserted into tables in the right subdomain.

There is a very DIM reference to the location at the end of the story. Last sentence. But, good call nonetheless, were it not for that ONE sentence, yes this one would've been moved.

fixed

Once again, you people that are complaining are missing the entire POINT here. You complain without knowing just what the hell exactly we're up against, with the database itself, and old outdated software. You complain thinking that because ff.net is the way it is, that we should then be the same way as them. With software, and everything. You don't BOTHER to read the rest of what actually is going on and being done, other things posted that are and were far worse about this elsewhere in this forum (insofar as post content), nor are you willing to factor in the time involved in the task itself. You'd rather just gripe. and gripe. and gripe some more.

http://books.adult-fanfiction.org/story.php?no=544183013 Chapters 3 and 4

As you had posted to this topic, I naturally thought you were referencing the topic title, as you'd not specified the archive. However, I will bring that to her attention so it can be fixed in the archive as well.

http://books.adult-fanfiction.org/story.php?no=600005548 to go to NE/German/Books

user emailed, link to challenge forum provided, challenges deleted from archive.

author deleted them. thank you, by the way, for doing that.

deleted review

What we could do, is for the ones with the oddball word/format errors like you found, post those separately from the no author data. There was a time, for awhile, where the upload function went squirrelly and kind of scrambled things in the chapter; and you'll be seeing many stories just like the one you pointed out in this topic. I will get to them, but they're a bit more time intensive. So, for now, I've done the no author data glitches. Those are fixed. I went through chapters 1 through 5 of the 2003 fic linked to, could you double check and make sure I got all the glitches?

Okay, moved 'em all to their special subcategory, until manta2g can get them placed in their proper subdomain.

Good god. Can't I even go to work?? ANYWAY..... This is really enough on this. The horse is dead, quit beating it already. I have said REPEATEDLY patience is needed. If no one wants to be patient and wait for the work to be done, subdomain by subomain, fine. Be impatient. No, I don't think those OMC/OFC cats really made sense, however, we (the ones helping me sort through all this) haven't even GOTTEN there yet. Until we GET there, REALLY see exactly what is what, then a determination can and will be made as to further categories added, and/or the death of small pair specific categories. There is only so much that can be done in any given 24 hour period, and there are only a FEW of us who are doing this work. And it is WORK. Something that is apparent, is that some are not wanting to be aware that not only do I have a full time plus job away from the site, so do all my volunteers. You know, we need time to eat, sleep and do other things BESIDES this. So, while we're certainly moving as fast as we can, it's not an instantaneous process. It never WAS an instantaneous process. It IRKS me that I see people who apparently think that we (the volunteers and I) are not deserving of having a LIFE aside from this task. I could be irresponsible and immature about all this and just walk away. But, that's not my nature. So, if some people can't wait while we do our work, I really don't know what else to tell you. No, I'm not moving up the schedule and doing things out of the order I've set up either. If I were to do that, there would be subdomains which are are my personal favorites which would've been attended to first. As that's not how it's set up, all of you can wait, just like I have to wait to get to my personal favorites. Since HP is sequentially in the menu before any of them? Guess what? I get to wait longer than you do. Now, I'm done ranting. It's time for me to get to work. Again. As always.

That's enough of that here in the Searching forum. By all means, continue your discussion in forum, but do it in the parts set up for it. I'm moving this to where it actually should go. --- Now that this is moved.... What I am seeing from you is an extreme LACK of patience. If you read any of what has been posted about this at all, you'll see that this is ongoing, and that there are many things being done. There's only one of us actually moving the stuff around (me), and the other two are very busy with rewriting the code itself. In order to bring in improvements like a search engine that actually works, for example? The old code has to be brought up to latest language version standards. Period. Or this thing will crash. What the recategorizing and then further resorting is doing is STABILIZING this database, which is huge, by the way. By stabilizing the database, this means that the techs here are then able to have the time to actually do the even more important coding replacements. I have had to babysit the database for the archive DAILY for MONTHS, in order to keep it from crashing. I'm not the only one who does this, by the way. So you see, stabilization of the database was and is critical. On a great number of levels.

Haven't gotten to the indepth reorganization yet. We've started THAT now. If you read what's posted in the announcements section about this, you'll see that the way it's being done is methodical. We'll be getting to each section, but please remember that we're looking at 100,000 individual STORIES throughout all these subdomains. That's alot to sort through. Not to mention, we're looking at several different things PER STORY uploaded. As to the search function...yes, the one we have is bloody awful. However, there are plans to replace it in the future. It worked for the size this all was way back in the beginning, but does NOT work in the way we need with the size we are now. We're definitely aware of this, it's on a very long list of "to do's" that are being addressed.

Review id # 2035456837 Review board

php chat programs tend to eat up resources more than a little. However, we can still look into different options and alternatives.

Challenges/Requests There's a very good reason WHY those categories were removed throughout the archive, and guest posting enabled in forum for the replacements for them. It has everything to do with how each program handles posted chapter data inserts. The archive treats each chapter (post) as a file, whereas the forum does not. So, what that means is each posted chapter is actually larger than it really should be, because it is a file within a database table row, while a post in forum is a text area in a forum row. It makes that data insert much larger than it actually SHOULD be. *sighs* the joys of outdated archaic programs.... If you're still in the validation queue, that would be why you're not allowed to do anything yet if you've tried logging in. You have to make sure you check spam/junk mail folders for forum validation mail as well, since mail programs commonly put a forum user validation email in those types of folders. There's a second step to that, where the user is then put into an admin validation queue, so that user information can be verified.

The new federal building and courthouse in SF

First of all, once again I'd like to thank those of you who've so kindly volunteered to help. It's going to make this task much easier. We'll be doing this a subdomain at a time, and a top level IN that subdomain at a time. Keep an eye on this post for when we're ready to move on the next section. What we will be doing: For each story that you will be looking at, you'll be looking at and then doing the following: Misplaced or not Check briefly the story content to be sure it's in the right subcategory and/or subdomain. If it's not, then post a topic in Misplaced Stories with a link to it, and then tell me where it actually should be. It'll be moved to a special category that will be created for these stories, to be reinserted later to the tables in the subdomain it belongs to. If it's simply in the wrong category in the same subdomain, I can move it immediately. Let me know which category / subcategory it actually it belongs to and there it will go. Trolls If the fiction is an obvious troll fic, then put a link to it in the Trolls subforum. That way, the archive mods are aware of it, and can deal with both the user and the ficcie. Glitched The other thing you'll want to do with each story, (multi page stories), is follow the page links and check and see if the author is linked to still in the chapter. There are many, many glitched stories, where there is author data everywhere, including in the first couple chapters, then all of a sudden the author link disappears. When this happens, the author can't even access the chapter. If you find something like this, post it in the Glitched Stories forum, and say which chapter or chapters are affected. The chapter can then be fixed so that it is once again linked to the author. At some point in 2003 (also 2005 & 2006), many of you may remember when the database was corrupted. This was as the result of database crashes, and the glitches you see are in what was able to be restored, but was corrupted from the crash. Those will be stories with consistent weird wording errors, like "pounpounding" and other words you see like that. Post those in a separate topic, per story, with reference as to which chapter the glitch is in. Those actually will end up having to be edited directly in the table, provided that the chapter data isn't so long the db won't allow it. But, at least those that I can fix, will be fixed. Orphan Stories Orphan stories are stories which have NO author data attached to them. Generally those are caused by the user having been deleted at some point, usually for a TOS violation, but the fiction still remains in the archive. Those need to be deleted. So, again, links to the stories, and then all the tables with associated data from that story will have it removed. I don't just delete a story, I also have to delete chapters, reviews, and ratings. Those are four separate tables. 'un' Stories If the story content is something like an RP, RP request, challenge/request, beta request, searching for a fic; put a link to it in the "un" stories forum. Those will ALL be deleted. Duplicate Stories When looking in a category page listing, you'll sometimes see a duplicate story. There's quite a lot of that throughout the archive. With those, provide a link to each story, and then I'll be merging the data from one to the other, so the other keeps all the reviews, the ratings will increased exponentially according to the data in the other story, and the VIEWS will be increased according to what is there for the story data being merged. Once that's all done, the duplicate story will then be deleted. Of course, as long as it's all where it's supposed to be, and there's nothing else weird about it, that needs extra attention? Move on to the next story in the subcategory you're working on. Review Boards Next, we'll be eyeballing the review boards. Because some authors allow anonymous reviews, the software simply has no way to combat spambots. So, should you see spam posts in a review board, provide a link to that board in the Spam Activity forum, and reference the review number or numbers. Those will be deleted. If you spot a flamer in the user's review board, post that in forum where one would report a TOS violation. Again, the archive mods will see to it that it gets handled appropriately. We will be starting in the BOOKS subdomain, top level category A through F. Please post in response to this topic, which of the subcategories you'll be taking on. That way, there isn't duplication of work. Also, once you're done with the subcategories you've selected, if there are more available to work, you can choose more, or wait 'til we get to the next top level category. That's entirely up to you, and how much time you honestly have for this. None of you should feel obligated to take on more than your real life permits you, so please keep that in mind when selecting your work categories. Happy hunting!

Hellsing was made a top level category for a reason. It had enough stories to where it earned it's place on the main Anime archive page. Just as with the other categories which are now top level categories. The stories are all there, just as they were before. In order to move them around within that part of the archive, so that your story ends up in it's more proper category, read this particular FAQ. Looking at your profile, they would now go to the Crossovers category that is a sub of the Hellsing top level category.