Fix lua and xml backup

[eloiferrer]

MaRDI Pull Request

Changes:

• Adding Lua development packages to fix this php warning:

Warning: PHP Startup: Unable to load dynamic library 'luasandbox' 
(tried: /usr/local/lib/php/extensions/no-debug-non-zts-20210902/luasandbox 
(/usr/local/lib/php/extensions/no-debug-non-zts-20210902/luasandbox: cannot open shared object file: No such file or directory), 
/usr/local/lib/php/extensions/no-debug-non-zts-20210902/luasandbox.so (liblua5.1.so.0: cannot open shared object file: No such file or directory)) in Unknown on line 0

• Filter namespaces in XML backup to include only those <= 3000. See NamespaceInfo.

Instructions for PR review:

• Conceptual Review (Logic etc...)
• Code Review (Review your implementation)
• Checkout (Test changes locally)

Checklist for this PR:

• Reviewers and Assignee specified.
• All related issues are linked.

[physikerwelt]

This is ok, but I think it would recommend to reduce the number of namespaces further.

[physikerwelt]

Do we want to have the Wikibase items 120,122 in the XML output. this would be JSON wrapped into XML, I'm not sure if that's super useful. I think it would be better to export as TTL or JSON instead.

[eloiferrer]

I agree that it would be better to export the wikibase entities as JSON, but do you know of an easy way to do that? I couldn't find it here: https://www.mediawiki.org/wiki/Manual:Backing_up_a_wiki
I think the important point is to ignore the namespaces that we currently use for Person:, Publication:, etc. I hope that that will be enough to at least fix the current problem.

[physikerwelt]

I think it will not be sufficient thus I'd go the other way around. If that succeeds we can include 120.

[eloiferrer]

We can use this https://github.com/wikimedia/mediawiki-extensions-Wikibase/blob/master/repo/maintenance/dumpJson.php to dump all the entities as a JSON file.

I am not sure how helpful that is for recovering purposes, though. Is there an easy way to load back all the entities to Wikibase from a JSON file?

[physikerwelt]

This is a good question. I have not checked that. Another option is to have two files. My fear is that when the file gets too big it might take too long to restore things. The advantage of the json files is that they can be read by several other systems. This would provide an easy access path to the data in the far feature without restoring an MW instance. For the text we wrote manually, the effort would be limited. Start a MW instance and restore the pages in a few minutes. However, when it takes very long to restore things, the database imports might be the first choice.

[eloiferrer]

Ok, I'm gonna first merge this version to test how it goes. Later I can try saving the wikibase entities in a different json file.

[physikerwelt]

Sure, give it a try. I hope it completes in less than 24h.