Hello,
I submitted bug 56763[1] just now, then realized that this is a part of a
larger issue: what is {{#property: }} expected to output.
Theoretically, there could be two extreme answers: raw data as a string, or
whatever wikitext which could be rendered as what *readers* love best.
I guess
Hoi
Remember that the stings need to be identifief for their language and by
implication script. They can be a mix and match from multiple languages..
Thanks,
GerardM
Op 8 nov. 2013 09:13 schreef Liangent liang...@gmail.com:
Hello,
I submitted bug 56763[1] just now, then realized that
Hello,
we’d like to work on Lua bindings for Wikidata. I have set up a page to gather
ideas and suggestions for what people want to see:
https://www.wikidata.org/wiki/Wikidata:Lua_enhancements
Your contributions would make me very, very happy.
Cheers,
Jens
--
Jens Ohlig
Software developer
Actually the problem isn't that you can only have one link from a
wikisource work from a wikidata item. We have separate wikidata items
for each edition of a work (because these have different metadata) so
multiple editions of the same work on a wikisource link to different
wikidata items.
This
You bring up a good point. Is there anyway to have the interwiki links that
show up on the sidebar point to a page with a different q# ID then the
should? If we can do that we can have every version of a given book all
point to a disambiguation page that lists all of the versions. I can't
think of
The sitelinks are not used directly, they are aggregated by using the work
item as a central hub. Basically the algorithm is:
1.- query all edition-items that are connected to the same work-item using
edition of
2.- make a list of all the sitelinks used on each one of these
edition-items (1
