User talk:Filceolaire

Jump to: navigation, search

About this board

Previous discussion was archived at User talk:Filceolaire/Archive 1 on 2015-08-10.

By clicking "Add topic", you agree to our Terms of Use and agree to irrevocably release your text under the CC BY-SA 3.0 License and GFDL
Mateusz Konieczny (talkcontribs)

I nominated this property for deletion - see

Reply to "Property:P402"

Structured Data on Commons Newsletter, July 19, 2017

MediaWiki message delivery (talkcontribs)

Welcome to the newsletter for Structured Data on Wikimedia Commons! You can update your subscription to the newsletter. Do inform others who you think will want to be involved in the project!

Structured Data on Wikimedia Commons?

The millions of files on Wikimedia Commons are described with a lot of information or (meta)data. With the project Structured Data on Wikimedia Commons, this data is structured more, and is made machine-readable. This will make it easier to view, search (also multilingually), edit, organize and re-use the files on Commons.

In early 2017, the Sloan Foundation funded this project (see documentation). Development takes place in 2017–2020. It involves staff from the Wikimedia Foundation and Wikimedia Deutschland (WMDE) and many volunteers. To achieve this, Wikibase support is added to Wikimedia Commons. Wikibase is the technology that is also used for Wikidata.

Recent developments: groundwork

  • A new and crucial technical step (federation) now makes it possible to reference data from one Wikibase website in another. Because of this, it will be possible to use Wikidata's items and properties to describe media files on Commons.
  • Another important piece of groundwork is under development: so-called Multi-Content Revisions. This feature allows structured data to be stored alongside wiki text, so that one wiki page can contain several types of content.

Team updates

  • Amanda Bittaker was hired as Program Manager for Structured Data on Wikimedia Commons. Amanda will take care of the overall management of the project.
  • Sandra Fauconnier (known as Spinster in her volunteer capacity) is the new Community Liaison. She will support the collaboration between the communities (Commons, Wikidata, GLAM) and the product development teams at the Wikimedia Foundation and Wikimedia Deutschland.
  • We have open positions for a UX designer and a Product Manager!

Talking with communities and allies

  • Long-term feedback from GLAMs. Besides the Wikimedia community, many external cultural and knowledge institutions (GLAMs - Galleries, Libraries, Archives and Museums) are interested in Structured Data on Commons and are willing to provide feedback on the long-term plans for the project. Alex Stinson, GLAM strategist at the Wikimedia Foundation, is currently in contact with Europeana, DPLA, the Smithsonian and the National Archives of the United States. Alex is also looking for other GLAM institutions who might be able to advise on the long term. If you know of an institution or partner that may be appropriate for consultation, do get in touch with Alex.
  • Jonathan Morgan, design researcher, is starting to work on two projects:

What comes next?

  • The Structured Data on Commons team meets in the week after Wikimania to lay the groundwork for the next steps. This includes new backend development and design work, for better and more clear integration of the structured data in pages on Wikimedia Commons.
  • The project's information pages on Wikimedia Commons will receive a long overdue update in the upcoming months. The team will also work on more and better communication channels. Feedback, wishes and tips are welcome at the project's general talk page.

Get involved

Many greetings from SandraF (WMF) (talk), Community Liaison for this project! 13:55, 19 July 2017 (UTC)

Reply to "Structured Data on Commons Newsletter, July 19, 2017"
Mike Peel (talkcontribs)

Hi Joe. One of the last parameters needed for is a "dome" parameter, which could be along the lines of "Spherical", "Cyclindrical", "25m diameter", "no", and so forth - see . I don't think there's a current Wikidata property that can cover this. Do you have any suggestions about how to go about creating a new property to cover this? Thanks. ~~~~ (talkcontribs)

Hi, I'm Joe's daughter, and am very sorry to say he passed away on January 29th. I hope you can find an answer to your query.

Reply to "Dome property"
ArthurPSmith (talkcontribs)

P2371 is ready (you commented there)

Reply to "FAO risk status"
Mbch331 (talkcontribs)

indigenous to (P2341) is ready

Reply to "indigenious to"
Mbch331 (talkcontribs)

Why are you removing part of (P361): inner planets (Q3504248) from Earth (Q2)? According to enwiki and nlwiki (and maybe more, have only checked those 2) Earth is part of the inner planets.

TomT0m (talkcontribs)

inner planet is a type of planet. Earth would be a part of the solar system as a physical system. Please read Markus' comments : Wikidata:Requests_for_comment/Refining_"part_of" §Proposal for slightly different division and usage guidelines

Mbch331 (talkcontribs)

Than the inverse property needs to be removed as well (the has part (P527) on inner planets (Q3504248)).

Filceolaire (talkcontribs)

There is a list/class of inner planets. Earth is one of them. It is an <instance of:inner planets> because it is one of the inner planets. (instance of means a thing/instance that is one of a class of similar things.)

Earth is <part of:solar system> (part of means thing/instance which is part of an agglomeration of non-similar things/instances that make up a bigger thing/instance).

If we had an item for the "inner solar system" that included all the planets, moons, asteroids etc. inside the orbit of Mars then you could say the Earth was <part of:inner solar system>

Reply to "Q2"
Tobias1984 (talkcontribs)

Danish parish code (P2290) is ready for use.

Reply to "Danish parish code"
Tobias1984 (talkcontribs)

price (P2284) can now be used.

Reply to "price"
Almondega (talkcontribs)

Hi, could I write in Portuguese? My English is terrible :/. É possível que a Template:Constraint:Single value funcione apenas para valores não obsoletos (no deprecated values)? Por exemplo, a propriedade CAS registry number (P231) deve ter apenas um valor não obsoleto, mas pode ter vários valores obsoletos para um mesmo item. Haveria alguma forma da restrição funcionar desse modo? -Almondega (talk) 11:31, 27 October 2015 (UTC)

Filceolaire (talkcontribs)

Veja Help:Classificação. Se a valor era correcto no passado deve ter Classificação "normal" mas ou valor corrente deve ter Classificação "preferida".

Sorry about my Portuguese. Hope this helps.

Filceolaire (talkcontribs)

Veja Help:Classificação.

Ou valor corrente devia ser "preferida"

Os valores velhos devia ser "normal" (pois não são errados)

Hope this helps. Sorry about my Portuguese

Reply to "Template:Constraint:Single value"
Almondega (talkcontribs)

 Done life expectancy (P2250) --Almondega (talk) 00:22, 22 October 2015 (UTC)

Reply to "{{P|2250}}"