You are going to write an animated map story for Mundu (https://mundu.app), a globe on which historical events appear one by one, each in its own place, in time order. I want a story about: <<< PUT YOUR SUBJECT HERE >>> Reply with one link, on its own line, and after it a short paragraph on the story you chose to tell and what you had to leave out. Nothing else. You will need to look one page up on the web — see step 2. Everything else you can do however you like. STEP 1 — CHOOSE THE EVENTS ──────────────────────────────────────────────────────────────────────────── Between 15 and 50 events. Fifty is the ceiling and it is also the target: fill it. The detail is the whole point — a story made of the six turning points everyone can already name is a poster, not a story. * Each event must have its own article on English Wikipedia. Write down the article title exactly as it appears there. * Each event must have a PLACE you can put on a map, and a DATE. A battle, a treaty signed in a named city, a landing, a founding, a first performance, a death. For a thing rather than an event — a dish, an invention, a word — use the place and the moment where it takes the form the story is about. * Spread them over the whole span, and over the map when the subject allows it. The globe is the medium: a story that never leaves one city has nothing to show. * Order them by date, oldest first. For each one, note: the article title, a weight from 1 to 10 (how much it matters to THIS story — it becomes the size of the dot, so use the range), a group (the side, faction or phase it belongs to: 2 to 5 groups, reused verbatim, each gets a colour and a line in the legend), the date, and the coordinates. CAPTIONS, ONLY WHERE THEY EARN THEIR PLACE. Under every event Mundu already shows Wikidata's own one-line description, in the reader's language, and it costs the link nothing: "Battle of Waterloo — 1815 battle during the War of the Seventh Coalition" needs no help from you. Write a caption where that would leave the reader wondering what actually happened — the turn, the surprise, the reason this event belongs to THIS story. At most 70 characters, written like the label under an exhibit in a good museum. Leave the others empty. Be strict about it, because captions are the heaviest thing in the link: fifty of them outweigh everything else put together, and a link too long to paste into a chat is a story nobody passes on. Fifty events with captions where they are needed come to around 3,000 characters; with one on every event, to twice that. Write the place and the date yourself for every event. Where Wikidata holds them for that item they are used instead, so an unnecessary one costs twenty characters — a missing one costs the whole event, which is dropped on arrival. STEP 2 — LOOK UP THE Q-NUMBERS. DO NOT WRITE THEM FROM MEMORY ──────────────────────────────────────────────────────────────────────────── This is the one step that is not optional, and the one place where this can go badly wrong. A Q-number recalled from memory does not fail loudly: it resolves to some other real thing, and the reader sees a confident dot with the wrong name. Measured on a real attempt: fifty dishes, all fifty names right, forty- four Q-numbers wrong — the tamale came out as a lake in Slovakia, hummus as a German punk band, tiramisù as The Simpsons Movie. You do not need code and you do not need fifty requests. Open ONE page: the Wikipedia API, with all your titles separated by | (up to 50 at a time), and read the Q-numbers off the JSON. https://en.wikipedia.org/w/api.php?action=query&format=json&redirects=1&prop=pageprops&ppprop=wikibase_item&titles=Hummus|Falafel|Battle+of+Waterloo The answer holds, for each page, `pageprops.wikibase_item` — that is the Q-number. Two things to watch: * `normalized` and `redirects` map what you asked for onto the title that answered: "Tamales" arrives as "Tamale", and the Q-number is filed under the second. Follow the chain before reading it off. * A page with `"missing"` and no pageprops means there is no article under that exact title. Find the real title and ask again, or drop the event. Do not substitute a Q-number you think is right. Any web tool will do — fetch, browse, search. If you would rather open one page per event, `https://www.wikidata.org/wiki/Q241987` shows the item's name at the top and that works too, just fifty times over. If you cannot open web pages at all, do not invent the numbers and do not give me a link: tell me plainly that you have no way to look them up, and stop. Fifty confident dots naming the wrong things is worse than no story. STEP 3 — BUILD THE LINK ──────────────────────────────────────────────────────────────────────────── https://mundu.app/app/?t=TITLE&d=SUBTITLE&k=GROUPS&c=CAPTIONS&s=SEQUENCE t the title, 2 to 6 words d one line, at most 90 characters, saying what we are about to watch k the groups, separated by * c the captions, separated by *, in the same order as the sequence and EMPTY where an event has none: `c=first**third` leaves the middle one bare. At most 70 characters each, and never a * inside one. Leave `c` out altogether if the story needs no captions at all. s the events, in chronological order, joined by - URL-encode the text (a space becomes +). Inside s leave the punctuation - * ! ( ) @ , readable — the sequence is meant to be legible to a human. An event is the Q-number you looked up, followed — in any order — by: (lon,lat) where it happened. Longitude FIRST, decimal degrees, negative west and south: (4.4125,50.6803) is Waterloo. @DDMMYYYY when it happened. Digits only, no separators: @18061815 18 June 1815 @061815 June 1815, day unknown @1815 1815, month unknown @-0057 58 BC — a minus sign and astronomical numbering, in which 1 BC is the year 0, so 58 BC is -0057 *8 the weight, 1 to 10. !2 the group: its position in k, counting from 0. So one event, and a sequence: Q48314(4.4125,50.6803)@18061815*10!0 s=Q134114(16.7625,49.1281)@02121805*9!0-Q179250(23.90,54.90)@24061812*10!1 Mundu reads the Q-number and fetches the event's name, its description and its article in the reader's own language — which is exactly why the Q-number has to be the right one. What you write in the link is the place, the date, the weight and the group. One more thing about dates: for a battle or a treaty, Wikidata's own date wins and yours only adds precision inside the same year. But for a person, a city or anything that lasts, Wikidata holds a birth or a founding, and there your date is the one that counts — so write it. STEP 4 — THE CLOSING PARAGRAPH ──────────────────────────────────────────────────────────────────────────── After the link, in a few sentences: what story you chose to tell inside the subject, what you left out and why, and — plainly — any event whose Q-number you could not confirm or whose date you had to reason out rather than read.