Change Details

While considering the use case for something like frWS's https://fr.wikisource.org/wiki/Utilisateur:BookwormBot, it occurs that it would be useful if this kind of data could be generated on the fly using some kind of tag in the Wikicode, which would drastically reduce the number of moving parts. For example, `<indexstatus index="Foo.djvu" count="0,4"/>` returns the total number of pages at status 0 and 4 in the given index. However, I am not sure that such a thing wouldn't be too much server overhead, as opposed to an "asynchronous" task that updates a data table? @Tpt: any concept of if this would be impractical on the server end?

While considering the use case for something like frWS's https://fr.wikisource.org/wiki/Utilisateur:BookwormBot for tracking proofread status of a set of indexes, it occurs that it would be useful if this kind of data could be generated on the fly using some kind of tag in the Wikicode, which would drastically reduce the number of moving parts. For example, `<indexstatus index="Foo.djvu" count="0,4"/>` returns the total number of pages at status 0 and 4 in the given index. However, I am not sure that such a thing wouldn't be too much server overhead, as opposed to an "asynchronous" task that updates a data table? @Tpt: any concept of if this would be impractical on the server end?

While considering the use case for something like frWS's https://fr.wikisource.org/wiki/Utilisateur:BookwormBot for tracking proofread status of a set of indexes, it occurs that it would be useful if this kind of data could be generated on the fly using some kind of tag in the Wikicode, which would drastically reduce the number of moving parts. For example, `<indexstatus index="Foo.djvu" count="0,4"/>` returns the total number of pages at status 0 and 4 in the given index. However, I am not sure that such a thing wouldn't be too much server overhead, as opposed to an "asynchronous" task that updates a data table? @Tpt: any concept of if this would be impractical on the server end?