I don't understand your other request

Moderator: Forum Moderator
And nope, they don't disappear or anything, pressing submit does nothing but give you the list of ID's, which you will then need to give to me. I'll then feed them into a script later that ensures they are properly removed (Properly removed = Removed in the same way as if you clicked "Remove" on all of them, ensuring proper tracking of when and how they were removed, as well as the ability to bring them back.)And add the ID and names to the index page too, perhaps.
Why?It would be possible to make it permanent
Great job, S !!!Sobuno wrote:... I have deleted the ones you mentioned from the list (Not deleted them from the database yet though, it requires a bit more work) as well as any duplicate groups that only contained one resource.
Then my suggestion is to just let them stay. Eventually a new resource may spawn with the error name and then we knowMonty Burns wrote:My next question is what do we do about resources not in the 30k Crate (Wind, Geothermal etc.) as there is no real way of checking their validity.
Sobuno wrote:It would be useful for old resources if someone inputted an old resource and it turned out that the resource that had been present in the database all along was named incorrectly. Other than that, no use for old resources, yes.
I agree. What impact on the server and the submit time would it have?
I assume there is no way to let the submission exit quickly but a background check raises an alert dialog somewhat later? Or are the web browser that smart these days? --- I haven't done much web-coding lately, nowadays it is chiefly C/C++, Python, and Java.
But it's not something I'll be implementing right now. I am also still considering the spelling mistake filter through the use of that levenshtein function I have previously mentioned (http://php.net/manual/en/function.levenshtein.php).
That would be useful and because it just has to cover the current resources it is also quick. A question nags me though, what about false positives and how to treat these.
Another approach, also quite dynamic, would be to run a daily cron job for everything that is reported that day that generate a public text file per galaxy for doubles. Let doubles from previous days stay until they are fixed. Link (or include) it at Current Resources and link also to this forum where players can report what is correct and what is wrong about "old" resources but they can edit the current resources if they need to.
There is a risk that less knowledgeable players do not remove but rather mark unavailable the resource they mistakenly added. That would be covered by such a nightly scan because it does not go away from the list.
It would also be possible to email players (real email) that have added a double and ask them to correct or remove the resource. Why email? Because I know by experience that many submitters never visit the forum and hence they never realize they have a PM in the Inbox.
That is one way, to take away all entries under Energy -- that is the only resource class that is excluded, is it not?Monty Burns wrote:Yes but perhaps they should not show up in the list at all to prevent confusion?
Oky doky then, here is everything up to H done for Sunrunner...Sobuno wrote:Posting it here is fine, it's just a list of ID numbers for resources that are going to be deleted anyway
You can do it in parts, I have deleted the ones you mentioned from the list (Not deleted them from the database yet though, it requires a bit more work) as well as any duplicate groups that only contained one resource.
Users browsing this forum: No registered users and 5 guests