Hi all. I am the “nice, friendly, and very competent informatics expert” (thanks to Dilaton!) that supported the installation of the Q2A test site on the laptop of Dilaton. I have been made an author of this blog by Dilaton so that I may report here about my progress directly to this community. I will support Dilaton and this community for the technical setup of the new site. Actually, I am writing a php-script for the migration of SE-dumps into Q2A and got the following results:
Good news first: It was possible to migrate users, questions, answers and comments properly into the database of Q2A. The posts look fine, beside of some curious LaTex phrases (identical to the original text in the dump) that I do not yet understand (although I know LaTex very well). I will care later about that. The posts are searchable; the database seems to be build completely correct. Also the statistics (number of questions and answers and the related points for them) for each user is correct.
User emails and passwords in the SE-dump are encrypted. We will have to setup a process, which allows all old users to reclaim their original posts, while hackers and trolls remain outside. This will not be very simple. Maybe, the “forgotten password” utility will provide a means for that, but then, the correct email addresses of the users will be required. Maybe, somebody of you has an idea?
There is an issue in the introduction of the original SE.TP votes. Q2A stores votes related to the posts (questions and answers) and additionally to the users that gave the vote. It does not allow a user to vote more than once for a post. The relation of the votes to the users is only visible to the administrator. However, the SE.TP dump does not provide this relation. There is only a relation between votes and posts, the voting user is unknown. I order to insert these votes, I had to create several thousand dummy users, each one voting only for one post, and at the end to delete all these users. After that, the corresponding points for the users and their statistic are properly set, as long as the admin does not recount the posts in the database. However, this recalculation could be required sometimes to keep the database free of corruptions. Maybe I should provide a script to the admin that resets these old votes after such a recount.
As a next step I will care about the issues in the compilation of LaTex within the markdown editor. I hope that is not required to write a new markdown editor 😉