moroz1999 wrote: ↑Tue Apr 10, 2018 9:34 pmI've sent you contacts in private message. Please ask me if you need to contact anybody, I can help in some cases.
Thanks a lot! Since you also have similar plans, I will certainly involve you in these discussions too. So we can find the solution that works best for everyone.
moroz1999 wrote: ↑Tue Apr 10, 2018 9:34 pmEinar Saukas wrote: ↑Tue Apr 10, 2018 3:19 amSomething else we need to decide is, if it makes more sense for you to integrate with all sites separately, or integrate them with ZXDB first so ZX-Art can simply obtain this information from a single source afterwards. Again, let's talk about it in further detail to find out the best solution for everybody involved.
That's the most complicated question really. Ralf has really got the point: new software has been added to different databases constantly as we are speaking, so even if you import one of archives, the week after you'll have to repeat it and somehow deal with the fact that same software gets added into different non-related databases.
ZXDB already deals with integrations that need to be updated periodically, such as RZX Archive and ZXSR. It's not too much of a problem, we just need to be careful on establishing a good process for each case.
moroz1999 wrote: ↑Tue Apr 10, 2018 9:34 pmI'm going to resolve it this way:
1. I'll hold the unique guids for each author, alias, group, production and release from each database. This will allow me to run the import procedure more than once, so only the added information would have been imported.
What does "production" mean?
I agree about the others.
moroz1999 wrote: ↑Tue Apr 10, 2018 9:34 pm2. For every new file I'll check the file's MD5, and if it already exists in database, I'll just save an additional guid, not make a duplicate.
Also if a file disappears from ZXDB, it means the file was considered obsolete and replaced with a better version, so it may be better for you to replace it too.
Therefore it may work better for you if you simply drop all files from ZXDB, then import them all again. If any additional information you have (like comments) is associated with releases instead of individual files, then reimporting all files won't affect anything on your side.
moroz1999 wrote: ↑Tue Apr 10, 2018 9:34 pm3. For every new file non-existing in database, I'll try to find the existing author and author's existing software (by name+year) and add a new release to the existing software.
This won't be necessary for new files reimported from ZXDB, because each one of them will already have ENTRY_ID and RELEASE_SEQ.
It won't be necessary for TOSEC files either, because you can obtain the ENTRY_ID for each of them from ZX Pokemaster.
It may not be necessary for Russian sites because, if ZXDB integrates with them, you should be able to obtain this information from ZXDB too. That's something we will need to decide.
moroz1999 wrote: ↑Tue Apr 10, 2018 9:34 pmThis means that I'll gather all the cracks, versions, mods and rereleases. Also, every sync procedure would be run periodically, I will need to manually fix the sync errors and improve the algorithms.
ZXDB aims to have everything (versions, mods and re-releases), except cracks. And TOSEC aims to have everything including cracks, associated with ZXDB through ZX Pokemaster. Also ZXDB aims to keep information about corresponding information in every other site. Therefore importing data from ZXDB would give you all information you need for integrating with everybody else with minimum effort.
There's still a lot of work to be done before we get there, but we are moving faster than ever