Serpent wrote:Ok I just noticed there's a new tag for Slavic. Would it be possible for you to change my items from #sla to #07?
Does the database show anything for Finno-Ugric (#02)?
(also it still says December 2017 on top
)
The dates at the top are hardcoded in the HTML and I didn't bother with that since it doesn't imped the functionality. It needs to be changed so it reads that from the DB also. If anyone is interested in updating the code it is here:
https://github.com/language-learners/superchallengebothum... Can't change them since they don't exist in the DB. So this will take a little explaining. When the SC started in May 2018, the 2017 version was running on the the server and I couldn't log in to stop it. I created the new 2018 database and started off the collector job and it was collecting all the tweets and putting them into the new DB, but the old one was also running and sticking them into the old DB. So the tweets were going into two different databases. But on the webpage you could see 2017 data and 2018 data. The problem is that the tags being displayed on the site were being taken from the old DB, but didn't exist in the new one. The new collector would have been trying to send you a message saying that doesn't exist and you can't report on it, but the old one accepted it.
There seems to have been a modification to the twitter API done by the company sometime last year which stops the collector from sending you messages. Used to be it would reply with something like "Serpent read X pages in Y language" or "You're not signed up for that language", but because of this API change twitter isn't displaying these messages.
Language families has been a painful hack ever since we tried it out last year. Mostly because of conflicting ISO codes and the fact it wasn't originally designed to be able to handle three character designators. I did seriously consider not allowing language families this year, but because of popular appeal I figure it was ok. If we'd not had this snafu with not being able to modify the DB configuration it would have been OK, because you'd have known the tags which the DB supports.
I will look at your problem and see if I can do a data dump from one DB and an upload into the other. Can you tell me how many records we're talking about? Also if anyone else is having problems with language families could you let me know?