@Lectrician1: Why was this duplicated here? Do you plan to update the wiki page to link to this Phab task? Thanks.

Duplicated here because it's a good feature request. The page does have the phab task linked, its just that its changes just need to be marked for translation.

Hi, I would like to provide a use case for this proposal.

Recently, I and other people are searching contents from Leiden University archive and Tropenmuseum archive in Commons about a specific city in Indonesia. They are great source material from 1940s and before. For example:

• https://commons.wikimedia.org/w/index.php?title=Special:MediaSearch&search=bogor+deepcat%3A%22Collections+of+Leiden+University+Library%22&go=Lanjut&type=image (2.448 results)
• https://commons.wikimedia.org/w/index.php?title=Special:MediaSearch&search=bogor+deepcat%3A%22Images+from+the+Tropenmuseum%22&fulltext=Search&prefix=File%3ACOLLECTIE+TROPENMUSEUM&type=image (1.083 results)

The problem arise when I want to filter the general search result by date of the pictures

• https://commons.wikimedia.org/w/index.php?title=Special:MediaSearch&search=bogor&fulltext=Cari&type=image (34.897 results)

Let's say I want to find the recent images (post 1940s) of this city, or images from pre-20th century, ideally, the requested filter would allow me to find the images I'm looking for.

If we include iiprop=extmetadata and sort based on DateTimeOriginal, it seems like the format varies a lot. Do you know of any existing extensions that can convert it into a standardized format, making it easier for us to read and use? Do you see any performance issue here with additional extmetadata?

Edit: conversation with @Cparle, provided

1. adding iiprop=extmetadata to the XHR query on the search page to retrieve metadata, particularly the DateTimeOriginal from the date field in Template:Information. However, DateTimeOriginal is derived from a non-standard format in the Information template, making consistent processing challenging. There are potentially thousands of search results and you'd have to get them all and then sort them for the sort to work properly (atm we only get gsrlimit=40 at a time)

2. To enable sorting on the Elasticsearch side, a date property would need to be added to the search index. A post-upload hook to process the Information template and populate the index with the date, along with running this process on existing images. OR part of the job can be done through a community-written bot that copy the date from the template into structured data.