Wikidata

Wikidata:WikiProject Supertemplates

Developpers

edit

Tickets

edit

Generalities

edit
  • Subject on the French talk page of Wikidata
  • Multilingual Templates and Modules
  • Plantilla:Infotaula persona on CA Wiki
  • Object : develop rich infoboxes and tables, in numerous languages, without problems
  • Proposal for tests (just examples) :
    • CA Wiki, a big Wikipedia
    • LB Wiki, a small Wikipedia
    • RU Wiki, a cyrillic alphabet
    • BN Wiki, non latin alphabet and figures
    • AR Wiki, a Wikipedia where we write from the right to the left
  • Idea of principle : a property readable must have its subpage of documentation[1]
  • Make a very clear dissociation between what the contributor-writer wants to find and the coding, domain of the programmer. Go straight to the point at the first click. Navigate by instinct.
  • Search the Wikipedia archive to find out what the problems were with the arrival of Wikidata (apart from the resistance to change) so as not to repeat the same mistakes.
  • Put the problems on the table and solve them together. Make tickets, as Amazon does ("safety saves"). Devote time to solving problems.
  • Babel : first step to a new user => define its languages => adaptation of Wikidata.
  • ca:Mòdul:CreateStatement

Notes

edit
  • The key of success is our possibility to work in different languages, so you can add at the URL of this page ?uselang=XX to see the adaptations in different languages. Personnaly, I generaly do HI TI SI, it refers to HI Wiki, TI Wiki and SI Wiki.
  • It might be interesting to ask the Wikimedia Foundation for the necessary financial means to hire, for example, a few translators for a given language if there were to be a lack of speakers.
  • Tracking categories can be interesting to permit translations, see Category:Articles with missing Wikidata information (Q16737095).
  • Also see Category:Wikipedia categories tracking data using Wikidata (Q21981953) and the example of FR Wiki to have an idea to the use of Wikidata property by property.
  • Don't forget one point : we can't promise saving of time for little Wikipedias, because at the beginning there will be a huge work to add translations on Wikidata. So during monthes, it will not take less time to create an article by using datas from Wikidata. At a critical threshold of translation, it will become advantageous.
  • Make an automatic categorization : death in november 2019, interred at XX cemetery, birth at Madrid... less work for smaller Wikipedias = more time to create articles.
    • OK, but optionally, setting up by installation parameter. Now, cawiki infoboxes set "live people", "deaths by year" and "lack of images by type" categories for everybody, but it should be customizable.
  • Developping a technical function that permit to display on a page all fields of the infobox to transle for a given language. Consider the page should stay because new properties are created and new are added to the algorithm. Once translated, the property disappears from the page.
  • Have a translatable list of first all properties excluding identifiers, second the 5000 most used and more strategic items, to propose it at local communities : they should have the possibility to work in their languages.

First templates

edit

Other templates

edit

Future

edit

Ideas to templates we can develop in the future :

Interface for users

edit

function (Q15810910)

edit

Here link to the different templates : infoboxes and tables. Because we have to be able to welcome each person in spite of their mother tongue, we must do without text and use either images, logos or Wikidata elements.

Idea: create new black and white logos to portray a person's infobox, a geographic infobox, and a population evolution. Possibly have a portrait format. Do without any writing. See a sample of some ones already used in ca:Ajuda:Infotaules. The portrait could be the occasion to make a return for Wikipe-tan more than ten years after, and why not create Wikida-tan.

documentation science (Q1235196)

edit

This is the heart of the project for the largest number of contributors: if you have people who can add an infobox, they are also powerful relays to perform updates. So we must be able to detail how to fill each property with general examples first but also with specific cases.

edit

The documentation must be accessible as soon as you click on the link at the bottom of the infobox or table. It may be interesting to rank via the property number, displayed in a table that would always remain at the top of each page of the documentation. Otherwise, it is always possible to keep a header.

Note to discuss, from amadalvarez

Until now, I (we?) oriented template documentations in the same way as did when we had manual parameters. Usually, each parameter become a line in infobox, a specific piece of information and if we had a multi-value, we entered all together in one parameter with a line break included inside. When WD was incorporated, we simply added the correspondent property code at side the old descriptions. It was enough while we handle "basic properties" to replace old parameters. However, now the information displayed is more complex and show a combination of properties and qualifiers. We must explain how to fill/update WD not as it is structured (data model) but as the editor see and understand a "block of concepts" and from this point of view drive him/her to the impacted properties. As we have changed the approach to handle the information, our editors have a comprehension gap between how they enter information to get what they want to see. In addition, as the infoboxes become a core from different information profiles (person instead of artists or politicians) they must have a guide to know what are the "usual blocks" for the profile they look for. In conclusion, I proposed organize documentation (still do not know the best format) up to down:

  1. Class of item/topic/article >> managed by "Infobox xxxx"
  2. Concept blocks available
  3. Properties and qualifiers involved. This level could be covered by template:statement+ or template:claim simplified (work in progress)
sample of this proposal
edit

Sample of this concept (now in cawiki, because the template:Statement+ has been modified. When changes were accepted in WD version, sample will be translated)

  • Property description (the most elemental piece): P119, P166, etc.
  • Conceptual block (level to show to editors), that gather one or more properties descriptions: Death block
  • Infobox description (Full documentation). There are two proposals to evaluate: Infobox person

___________ End note __________________________

Wikidata:WikiProject Supertemplates (Supertemplates is just an exemple, the project can have another name)

Documentation science
Wikidata property

I don't know how we do to make a link to Wikidata:WikiProject Supertemplates/doc/P6 with Template:P. I don't know if it is necessary.

Statement+

edit

Template:Statement+ will be used to display the different examples in the documentation. I think it is the best way for an user to learn. Moreover we should not have problems with translations.

Example for country of citizenship (P27) :

country of citizenship
Normal rank Bolivia edit
0 references
add reference
add value

More than just documentation, it is also an opportunity to be precise enough for changes of nationality following the disappearance of the USSR, East Germany, Czechoslovakia ... finally set dates after consultation with people who regularly work on these issues.

yellow Documentation science
Has list
Classification scheme

place of burial (P119): location of grave, resting place, place of ash-scattering, etc. (e.g., town/city or cemetery) for a person or animal. There may be several places: e.g., re-burials, parts of body buried separately.

edit

Jeanne Hébuterne (Q235605): French painter (1898–1920)

edit
place of burial
  Père Lachaise Cemetery edit
start time
burial plot reference 96
coordinate location 48°51'35.2904"N, 2°23'54.6554"E
0 references
add reference
  Cimetière parisien de Bagneux edit
start time
end time
0 references
add reference
      example: Jeanne Hébuterne
  item-requires-statement constraint → date of death

  subject type constraint = human, animal, fictional character
  value-type constraint = geographic entity, établissement public de santé
  multi-value constraint →

  • Père Lachaise Cemetery → preferred rank
  • Cimetière parisien de Bagneux → normal rank
add value
edit

On day 3, 3rd novembre 2019, three navboxes were created for documentation. A color code exists : yellow, orange and red.

A mother category, Category:WikiProject Supertemplates, has been created. On 5th november, documentation was added to templates, and more content.

translation (Q7553)

edit

Create some links to thematic lists. The first inevitably will translate the properties and properties of the identifiers.

Then we should try to translate about 5000 elements, so as to ensure a comfortable base for any newcomer.

Inspiration for Wikidata:WikiProject Cycling/Kit to translate/Championships and Wikidata:WikiProject Cycling/Kit to translate

reference data type (Q1334113)

edit

Create a page made of examples to show how to source on Wikidata, examples can avoid writing in a particular language.

  1. ↑ An error on FR Wiki in 2015 was the lack of documentation.
Retrieved from "https://www.wikidata.org/w/index.php?title=Wikidata:WikiProject_Supertemplates&oldid=2032368248"