[Wikimedia-l] [Wikitech-l] Reasonator use in Wikipedias

[Martijn Hoekstra]

On Jan 23, 2014 6:42 PM, "Gerard Meijssen" <gerard.meijssen at gmail.com>
wrote:
>
> Hoi,
> Having Reasonator generated content in a "draft" namespace is *NOT* a bad
> idea.
>
>    - I do not know enough about the draft namespace.. Is there a way to
>    discover that an article exists in Draft ??
>    - My personal target for this functionality is very much the smaller
>    projects. By using a "draft" environment I am afraid it becomes easily
too
>    complicated in these environments.
>    - "Red links", are they allowed to point to the draft namespace?
>    - How about disambiguation because, Wikidata is very likely to create
>    ambiguity ... then again, as there is an "auto describe" function, it
is
>    possible to add suffixes like "actor" "politician" etc..
>    - Magnus indicated that providing information to templates is well
>    possible. <grin> he calls it low tech </grin>
>       - So far we prefer to show a label in stead of  a "Qnumber".
>       - We would *REALLY* like to have a personal fall-back chain of
>       languages based on #babel information..
>       - There is no API to read #Babel yet
>       - Obviously this has implications for caching..
>       - HOWEVER as we share this content with Wikidata and all other
>       projects, it can aggregate in one cache.. do not know if that is
> good or bad
>
> Thanks,
>      GerardM
>
>

Pointing redlinks to draft seems like a marvelous idea, and pre-populating
them with wikidata even better.

Having an in between "yellow" link for draft content including wikidata
content, and red link for nothing seems to me like an even better idea, but
dependent on how drafts will turn out in practice.

We could do amazing things with this.

> On 23 January 2014 16:26, Daniel Mietchen <daniel.mietchen at googlemail.com
>wrote:
>
> > What about having the Reasonator sit in the Draft namespace, with a
> > link from the search results or the text preloaded for non-existing
> > pages in the main namespace?
> >
> > Daniel
> > --
> >
> >
http://www.naturkundemuseum-berlin.de/en/institution/mitarbeiter/mietchen-daniel/
> > https://en.wikipedia.org/wiki/User:Daniel_Mietchen/Publications
> > http://okfn.org
> > http://wikimedia.org
> >
> >
> > On Thu, Jan 23, 2014 at 4:12 PM, Magnus Manske
> > <magnusmanske at googlemail.com> wrote:
> > > Hi Andy,
> > >
> > > I thought about that as well. Besides the intro text, the info box
would
> > be
> > > the main "attraction"; but if infoboxes were to fall back on wikidata
> > > information, which they could technically already do, all we'd have
to do
> > > is add a blank infobox, and it should automatically fill up with the
> > > wikidata information. In light of that, writing code to fill an
infobox
> > > with values form wikidata to paste into the article seems ... low-tech
> > ;-)
> > >
> > > Cheers,
> > > Magnus
> > >
> > >
> > > On Thu, Jan 23, 2014 at 3:05 PM, Andy Mabbett <
andy at pigsonthewing.org.uk
> > >wrote:
> > >
> > >> On 22 January 2014 08:35, Gerard Meijssen <gerard.meijssen at gmail.com>
> > >> wrote:
> > >>
> > >> > There are many ways to skin a cat. The most obvious
> > >> > one is to add a {{Reasonator}} template as a place
> > >> > holder in a Wikipedia. Another is to capture a not
> > >> > found or a red link and insert Reasonator info. What
> > >> > I am trying to do is to give a sense of direction. I am
> > >> > not indicating how it will be done for sure.
> > >>
> > >> [I'm not on the devs list, so trimmed from the CC]
> > >>
> > >> I would like people to be able to "subst" that template (or have a
big
> > >> button that does the same thing), and have some code draft a stub
> > >> article based on the statements in Wikidata, say:
> > >>
> > >>      "X was a German painter born in [[Munich]] on
> > >>      27 May 1801. He died in [[Berlin]] on 3
> > >>      March 1899"
> > >>
> > >> with formatted references, a reflist template, and a pre-populated
> > >> infobox. It would be delivered in preview state, allowing further
> > >> editing before publication.
> > >>
> > >> A suitably prominent warning would alert editors that they still bear
> > >> responsibility for ensuring that the subject is notable, and the
> > >> article fit for publication, according to local standards. A hidden
> > >> category and/or an edit tag would allow tracking.
> > >>
> > >> Because of the complexity of this task, we could pilot it for one
type
> > >> of subject (say, buildings, or people, or even a subset of one of
> > >> those) in one or two languages.
> > >>
> > >> --
> > >> Andy Mabbett
> > >> @pigsonthewing
> > >> http://pigsonthewing.org.uk
> > >>
> > >> _______________________________________________
> > >> Wikimedia-l mailing list
> > >> Wikimedia-l at lists.wikimedia.org
> > >> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
,
> > >> <mailto:wikimedia-l-request at lists.wikimedia.org?subject=unsubscribe>
> > >>
> > >
> > >
> > >
> > > --
> > > undefined
> > > _______________________________________________
> > > Wikimedia-l mailing list
> > > Wikimedia-l at lists.wikimedia.org
> > > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > <mailto:wikimedia-l-request at lists.wikimedia.org?subject=unsubscribe>
> >
> > _______________________________________________
> > Wikimedia-l mailing list
> > Wikimedia-l at lists.wikimedia.org
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > <mailto:wikimedia-l-request at lists.wikimedia.org?subject=unsubscribe>
> >
> _______________________________________________
> Wikimedia-l mailing list
> Wikimedia-l at lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
<mailto:wikimedia-l-request at lists.wikimedia.org?subject=unsubscribe>