Commons talk:Structured data

Structured Commons

About

Get involved

GLAM and culture

SPARQL

Modeling

Discussion

Welcome to the general talk page of Structured Data on Wikimedia Commons. See also specialized talk pages about data modeling and about Lua.

	SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 7 days.

Emails

Why am I now receiving unsolicited emails about this? I complained back in 2021 about the intrusive notifications, and now someone has the lack of awareness to start emailing me to do an interview. Who in Wikimedia authorised this? STOP. Cnbrb (talk) 09:19, 19 October 2024 (UTC)

Why would a person doing research interviews have any idea that you asked someone else not to contact you? - Jmabel ! talk 14:01, 19 October 2024 (UTC)

If you read what I wrote, you might get an inkling that being pestered about this project is not entirely welcome. And that's not how privacy works. Why would a person doing research interviews assume that I want to receive emails about something I have already expressed disinterest in? Sounds like lax use of personal data to me. Cnbrb (talk) 15:48, 19 October 2024 (UTC)

On your user page is the invitation "Email this user". If you do not wish to receive unsolicited emails you can turn that off in your account preferences. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:29, 20 October 2024 (UTC)

"Publish changes" does nothing

I have changed the geocoordinates of File:Kreuzung L489 - panoramio.jpg in wikitext, because I know better than Panoramio where this picture has been taken. However, now I'm getting the Commons:Structured_data/Reconciliation warning. Switching to the SDC tab, I can add the new coordinates and remove the old ones, but the "Publish changes" button does nothing. No HTTP request. There is an error in the developer console saying Error: View mediainfoview does not exist, but this error already appears when loading the page. "Remove all" removes the coordinates from the list, but no corresponding HTTP request happens, and when reloading the page, the coordinates are back to the way they were, including the discrepancy warning. Scytale (talk) 22:54, 28 October 2024 (UTC)

Modeling video / audio / pdf / djvu files

language of the work, etc. what properties should i be using? also, a bot should take care of some of these. RoyZuo (talk) 14:27, 19 November 2024 (UTC)

@RoyZuo: I just want to make sure before I give any longer answer: are you familiar with Commons:Structured data/Properties table? Seems to me that most (though not all) of what is relevant to a photograph would also be relevant to a video. And the answers for video are going to be different for a PDF (and for a PDF of a written document are going to be different from a PDF that is just a collection of images), so you are really asking several separate questions here. - Jmabel ! talk 22:16, 19 November 2024 (UTC)

are you?

did i say i asked a single question? RoyZuo (talk) 11:12, 1 January 2025 (UTC)

How to record the time/date when a video is made, if it spans over multiple days? starting a recording at 23:59:00 31 dec 2022 and ending at 00:00:10 02 jan 2023, how would that be recorded in sdc?

How to display/record that in the date parameter of {{Information}}? RoyZuo (talk) 11:15, 1 January 2025 (UTC)

Derivatives

I have been wondering for some time how the information on derivatives is correctly provided. The starting point is the crop tool, which basically provokes violations of the license conditions. The information is usually not customized. In addition, a bot like User:BotMultichillT comes very quickly and transfers the inadequate information directly into the structured data. Sources, information on the persons who created the derivation and other information relating to the license are missing. I have tried to correct the information for one derivation (File:2019 BMW i3 (Giga Turbine style 429 wheel).jpg) that I know of. But I don't know whether this is correct. I even doubt it, because I'm not really familiar with the structures from Wikidata. Can someone perhaps give me a hint? --XRay 💬 11:38, 30 November 2024 (UTC)

Important to distinguish crops from derivatives in general. Both may affect "depicts," but crops never change where and when the image was created, and with what equipment, and rarely (if ever) create new intellectual property rights, but may require indicating who did the crop where the original license says that derivatives must not be made to appear to be entirely the work of the original author. But the latter does not always apply: for example CC-0, PD, or just cropping out a border. - Jmabel ! talk 17:50, 30 November 2024 (UTC)

Basically, I think it is important that all information is as correct as possible. As a photographer, I decide what a photo should look like. Derivations of any kind are permitted and possible under license. In my opinion, however, it is not acceptable if the person who created the derivative is not named - in other words, if the terms of the license are not adhered to. The person is responsible for the derivative. This is important to me and can also have legal consequences, because not every excerpt is legally permitted. (See for example File:Louvre at night centered.jpg.) However, the question remains as to what the structured data should look like. (The background: I want to use the structured data of the derivatives of my photos in a meaningful way.) --XRay 💬 18:11, 30 November 2024 (UTC)

To be a little more specific: I am concerned with the following properties:

• creator (P170) The name of the person who creates the derivative should be added to the author of the origin file with a suitable qualifier.
• source of file (P7482) Should be a link to the origin file. Only if the photographer of the original file uploaded the derivative it should be original creation by uploader (Q66458942).
• based on (P144) should be set with one or more origins.
• extracted from (P7009) for extracted/cropped images.
• inception (P571) should contain the date of the origin and the date of the derivative.

But: How to set this properties? How to fix the crop tool? How to fix the bots like User:BotMultichillT or User:SchlurcherBot?

--XRay 💬 06:59, 1 December 2024 (UTC)

@XRay: I have similar considerations. On my user page, I keep a log of categories, where I feel the SDCs are not sufficient as of now. These are: Other versions (like SVG), retouched versions and other derivatives like crops. I'm happy to update my bot as soon we have something like an aligned modeling specification for this. Here the problem starts for me already is why can extracted from (P7009) not be added to files manually? Why is it greyed out if added by bots? Can we fix this first and then use it? --Schlurcher (talk) 22:44, 1 December 2024 (UTC)

There seem to be a special Wikimedia type of commonsMedia: https://www.wikidata.org/w/index.php?title=Special:ListProperties/commonsMedia&limit=500&offset=50. These directly link to Commons files (but however cannot be added by the structured data UI). extracted from (P7009) is of type commonsMedia, but based on (P144) is not. Should we use for the latter based on media (P12346) instead, which is again of type commonsMedia? --Schlurcher (talk) 08:03, 9 December 2024 (UTC)

OpenRefine - Commons upload validations

As you may know, OpenRefine lets users upload media files to Commons in batch. Because some of the uploads done in this way add too little metadata to the uploaded files, we are considering introducing more pre-upload checks to prevent that. We need your help to determine which metadata fields should be required for any file uploaded via OpenRefine. Are these guidelines still up to date and accurate? Based on this information, we would require the users to provide:

• A caption
• An inception (P571) statement
• A source of file (P7482) statement
• A creator (P170) statement
• A copyright status (P6216) statement

We would not require copyright license (P275) as this statement is not required for works in the public domain, and we don't anticipate being able to be able to express this conditional dependency.

We also looked into adding constraints on the wikitext associated to the media files but this is likely too complicated to implement reliably, as some required parts could be added via different sorts of templates, which OpenRefine isn't able to expand before upload.

What do you think of this plan? Can you think of any case where it would be fine to upload a file without one of the 5 fields mentioned above? Do you think OpenRefine should only warn the user about those missing fields, or even prevent the upload entirely if those fields are not provided? SunilNOpenRefine (talk) 04:41, 11 December 2024 (UTC)

Deleted Wikidata entities used in SDC

There are a number of deleted Wikidata items that are still in use in SDC; see d:Wikidata:Database reports/Deleted Wikidata entities used in SDC. One item is used by 33357 files! Seventy-eight are used on over 50 files. I've opened a discussion at d:Wikidata:Project chat#Deleted items still in use elsewhere. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:18, 28 December 2024 (UTC)

And absolutely no way to know what they were. Probably we need someone from Wikidata to take a look at this to see if some of these should be undeleted because of use here, especially the heavily used ones. - Jmabel ! talk 23:56, 28 December 2024 (UTC)

Most of them are spam, but some indeed might need to be restored. Ymblanter (talk) 08:25, 29 December 2024 (UTC)

As I demonstrate in the linked discussion, we know what some of them were via the Wayback Machine. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:01, 29 December 2024 (UTC)

Who's developing models?

Who should be contacted when a model is needed? Seems to me there're 3 groups of users invovled which do not necessarily overlap: commons users (who're developing models by themselves?), wikidata users who decide which properties and items are created and deleted and how they are used, and mediawiki developers who develop the software. RoyZuo (talk) 11:24, 1 January 2025 (UTC)