Can we do this in a way that we can easily reset the system later if needed?

One way of doing this is just have a maintenance script that can be run to populate the test set of data. Then if we ever want to re run it we can just run the maintenance script again. (Maybe 2 maintenance scripts as we will have the repo data and also the client wikipages?)

If we want a solution that allows less hands on resetting of the data / more frequent (such as users being able to reset the data) then we would have to think a little more.

In T224834#5250408, @Addshore wrote:

Can we do this in a way that we can easily reset the system later if needed?

One way of doing this is just have a maintenance script that can be run to populate the test set of data. Then if we ever want to re run it we can just run the maintenance script again. (Maybe 2 maintenance scripts as we will have the repo data and also the client wikipages?)

If we want a solution that allows less hands on resetting of the data / more frequent (such as users being able to reset the data) then we would have to think a little more.

How about “restore” links like on the Wikidata sandbox talk page? (Note that we’ve now decided to use the beta cluster as the test system, not a separate system that we can easily tear down completely.)

That should work, I guess which way to go depends on how many pages we will need to restore to restore the test data. How many entities and how many wikipages.

For now I think we were thinking of four pages: entity, template, lua module, client page.

We created https://en.wikipedia.beta.wmflabs.org/wiki/Data_bridge as the place for the showcase (needs to be changed per the task) but decided to maintain https://de.wikipedia.beta.wmflabs.org/wiki/Data-Bridge as the technical playground (table with one line per value type).

We actually used: https://en.wikipedia.beta.wmflabs.org/wiki/Wikidata (the twitter hashtag)

We looked at it and the current one at https://en.wikipedia.beta.wmflabs.org/wiki/Wikidata is definitely not minimal. It should be really simple so people can easily see what is happening and not have a lot of unnecessary text and code (wikitext, template, Lua module).

Also taking Wikidata is too self-referential and is probably not the best one to take.

Tentative first version: Showcase, Template, Item.

The template surely needs more documentation and has a strange "Pages with script errors" category added to it.

Also, I would like to have a simple Lua module, as discussed in context of T227466. But this may have a lower priority and it depends on how much effort is needed for a sensible implementation.

A (hopefully) simple Lua module exists now as well.

\o/