Wikidata:Property proposal/image revision-id
Jump to navigation
Jump to search
image revision-id
[edit]Originally proposed at Wikidata:Property proposal/Sister projects
On hold
Description | Qualifier to inidicate the particular revision of an image that a statement refers to |
---|---|
Data type | String |
Domain | statements with value: media |
Allowed values | \d+ |
Example 1 | File:Pigot and Co (1842) p2.138 - Map of Lancashire.jpg (revision-sensitive statement) → 279847594 |
Example 2 | File:Larousse,_Plan_de_Paris,_1900_-_David_Rumsey.jpg (revision-sensitive statement) → 180884966 |
Example 3 | File:1768_Jeffreys_Wall_Map_of_India_and_Ceylon_-_Geographicus_-_India-jeffreys-1768.jpg (revision-sensitive statement) → 345654849 |
Planned use | To indicate which revision of a map image has been georeferenced on Commons MapWarper. But further use-cases are likely to emerge. |
See also | Wikimedia import URL (P4656) |
Motivation
[edit]Sometimes it is important to be able to indicate which particular revision of a Commons image a Wikidata or SDC statement refers to. For example, georeferencing information will fail to be correct if an image has been cropped. A mechanism is therefore necessary to be able to specify a particular version of a Commons file. Jheald (talk) 13:16, 14 August 2019 (UTC)
Discussion
[edit]- Proposed. Jheald (talk) 13:16, 14 August 2019 (UTC)
- Comment This is not going to work properly, because, when someone will upload a new version, the file will change its version number, but the value in the property may stay the old one. Moreover, there was a discussion with WMF team, that it's not possible to track different versions so they cannot be stored in Wikidata. --Juandev (talk) 20:21, 29 September 2019 (UTC)
- @Juandev: The whole point is that we want the property to point to the old version of the image, because that is the one that the georeferencing was done against, not any later reupload that may potentially have been cropped. Jheald (talk) 22:15, 13 October 2019 (UTC)
- I think the (current) samples give the revision of the file description page, not the image version. --- Jura 09:35, 13 October 2019 (UTC)
- Good spot. @Juandev, Jura1: It ought to be possible somehow to identify an particular upload version. Worst case, one could make the value URL-valued, and eg specify https://upload.wikimedia.org/wikipedia/commons/archive/9/93/20120327114216%21LeKeux_-_Cambridge%2C_c1840_-_Corpus_01_-_memorialsofcambr01wriguoft_0238.jpg for the first version of File:LeKeux_-_Cambridge,_c1840_-_Corpus_01_-_memorialsofcambr01wriguoft_0238.jpg (not that that is a map, but it is a file with several revisions). Jheald (talk) 22:15, 13 October 2019 (UTC)
- Does that work for the current version as well? I think the upload date is probably the only element available in the GUI. Isn't there some hash stored as well? --- Jura 08:03, 14 October 2019 (UTC)
- There is no public id for image version. In theory
timestamp
could be on if we use string as datatype (date doesnt work as its accuracy is YYYYMMDD only) or thelog_id
of the upload. --Zache (talk) 11:38, 18 March 2024 (UTC)
- There is no public id for image version. In theory
- Does that work for the current version as well? I think the upload date is probably the only element available in the GUI. Isn't there some hash stored as well? --- Jura 08:03, 14 October 2019 (UTC)
- Good spot. @Juandev, Jura1: It ought to be possible somehow to identify an particular upload version. Worst case, one could make the value URL-valued, and eg specify https://upload.wikimedia.org/wikipedia/commons/archive/9/93/20120327114216%21LeKeux_-_Cambridge%2C_c1840_-_Corpus_01_-_memorialsofcambr01wriguoft_0238.jpg for the first version of File:LeKeux_-_Cambridge,_c1840_-_Corpus_01_-_memorialsofcambr01wriguoft_0238.jpg (not that that is a map, but it is a file with several revisions). Jheald (talk) 22:15, 13 October 2019 (UTC)
- Slight Support. I understand the argumentation, but during my 15 year old presence I havent encountered such situation.--Juandev (talk) 12:47, 15 November 2019 (UTC)
- Slight Oppose. I do not see the need, and it might not be technically freezable. I am open to change my vote if there is a clear need. --Jarekt (talk) 01:54, 15 May 2020 (UTC)
I marked this proposal as on hold. Currently we have two solutions:
- Wait phab:T28741 to be fixed so file versions have unique identifiers
- Create a property "image timestamp", but 1. we still does not have the datatype unless we store timestamp as string and 2. timestamp may still be not unique.