On Wed, Sep 14, 2016 at 10:07 AM Luca Martinelli <martinelliluca@gmail.com> wrote:

Il 05 set 2016 11:43, "Jan Dittrich" <jan.dittrich@wikimedia.de> ha scritto:
> - What are current workflows with Listeria? I think I remember that people in our interviews (thanks to everyone who participated!) mentioned that the generation process currently needs to be triggered manually. Is that just because there is no automatic way or does it provide you with advantages, too?

Just one thing on this issue. Based on my short experience, the necessity of a manual trigger is half true: ListeriaBot updates every 24 hours or so every automated list. If you change things and you want to see those changes immediately THEN you can ask manually to update now. I don't see this much of a disadvantage actually.


Yes, that's how I set it up.

I contemplated having a bot look through recent changes to update manually changed lists (e.g. query was changed) but it would probably be a few minutes for some lists until they update, which might be more confusing.

A proper extension would likely regenerate the list as part of the edit, so this wouldn't be an issue.

I found people opposed to Listeria lists (in article namespace) for two main reasons:

* The list is wikitext, so it /looks/ like one can edit it, but then it gets overwritten by a bot. If the wikitext representation of a list were just a parser function or extension tag, that problem would not appear (nothing to edit)

* Handcrafted lists. A lot of time went into some of the lists, and while the raw data can often be regenerated from Wikidata, some manually curated lists have fields for notes, special formats for coordinates etc. that are hard to replicate. Allowing custom templates can solve the bespoke rendering, but especially the "notes" column is essentially not reproducible with Wikidata, as it is. A tag-based MediaWIki extension could offer notes per item, maybe, in wikitext.

My 2 Eurocent,
Magnus