Change Details

both title and description are often written in similar ways. where the title might be the short version of the description. Both strings are often composed of values that are known and and filled in in the table. Think things like Date (different ways of writing), time, location, location names on diffefetn levels like neigborhood, vilage name up to bugger local othorities names. also depict labels are afften relevant. or time of day like down, dusk, night, ... there are probably more i am now not thinking of. please propose all you can think of to me. Also these strings with variables should be savable in the form of templates for reuse. also suggest themplates form previous file titles used in previous completed uploads. give me a list of variables that we could use. also keep in mind the language of labels from items. Also when edditing it should show varaible names. and when the cell is unfocused it should show the values of the variables to give the user the grip and trust their template is working properly. ask me clarificaiton questions

== Summary == Title and description (caption) are often written in similar ways — the title is frequently a short version of the description, and both are typically **composed from values that are already known and filled in elsewhere in the table**. Today the user types each cell from scratch, even when 80% of the content is mechanical recombination of existing fields. This task proposes a **variable-substitution system** for title and description (and possibly other text fields), with **savable, reusable templates** built from those variables. == Round 1: design proposal (this round, no code) == Before any implementation, the implementer should produce a written proposal covering: * **A complete list of available variables** — every field/value in a row that could plausibly be substituted into a template. The user has named some examples (date in different formats, time, location names at different administrative levels, depicts labels, time of day like dawn/dusk/night) and explicitly asks the implementer to "propose all you can think of." * **A template syntax** — what does a variable reference look like in the cell? (e.g. `{date:long}`, `{location:village}`, `{depicts:0}` — propose). * **Format modifiers** — for variables like date, multiple format outputs need to be reachable (`2026-05-10`, `May 10, 2026`, `10 May 2026`, etc.). Propose a modifier syntax. * **Multilingual labels** — depicts labels and location names have a language. The user explicitly flags this as a constraint: "keep in mind the language of labels from items." Propose how the language is selected (current UI language? per-template?). * **Editing UX** — when a cell is being edited, it should show variable **names** (raw template). When unfocused, it should show the substituted **values** so the user can trust their template works. Propose how this toggles visually. * **Template persistence** — templates should be savable for reuse. Where do they live (per-user, cross-device → wiki user-store Preferences.json)? How are they listed / picked / edited? * **"Suggested" templates from past uploads** — the user wants the system to surface templates inferred from previous completed uploads ("you've used `{date:long} – {depicts:0} in {location:village}` 12 times"). Propose how/whether this is detected. == Clarification questions to surface == After drafting the proposal, post it as a Phab comment and **explicitly ask the maintainer (Daanvr) for clarification on the open design choices**. The user has explicitly invited this: "ask me clarification questions". Examples of questions to raise (add your own as the proposal solidifies): * Which fields should be substitutable? (Just title + description, or also author/source/categories?) * Variable syntax preference? * How aggressive should "suggested templates from history" be — explicit panel, or quietly surfaced as autocomplete? * Relationship to T425881 (wikitext-templates, currently in Reviewing) — they're conceptually adjacent (both deal with "templates"); confirm they're independent systems or that one wraps the other. == Out of scope (for the round-1 proposal) == * Any code changes. This round is design/proposal only. * AI-generated suggestions for individual cells (separate concern; not what's being asked here). == Round 2 (after maintainer responds): implementation == Once the maintainer answers the clarification questions on Phab, the task is re-dispatched (or this same agent resumes via a new run) with locked-in design and proceeds through the normal implementer workflow. == Source == User feedback session, 2026-05-10. The user explicitly asked: "give me a list of variables that we could use" and "ask me clarification questions".

both t== Summary == Title and descriiption (caption) are often written in similar ways. — the title is frequently a short version of the description, and both are typically **composed from values that are already known and filled in elsewhere in the table**. Today the user types each cell from scratch, where the title might be the short version of the description.even when 80% of the content is mechanical recombination of existing fields. This task proposes a **variable-substitution system** for title and description (and possibly other text fields), Both strings are often composed of values that are known and and filled in in the twith **savable., Think things like Date (different ways of writing)reusable templates** built from those variables. == Round 1: design proposal (this round, timeno code) == Before any implementation, location,the implementer should produce a written proposal covering: * **A complete list of available variables** — every field/value in a row that could plausibly be substituted into a template. locationThe user has names on diffefetn levels like neigborhoodd some examples (date in different formats, vilage name up to bugger local othorities names.time, also depict labels are afften relevant.location names at different administrative levels, or time of day like downdepicts labels, dusk,time of day like dawn/dusk/night) and explicitly asks the implementer to "propose all you can think of." * **A template syntax** — what does a variable reference look like in the cell? night,(e.g. ...`{date:long}`, there are probably more i am now not thinking of.`{location:village}`, please propose all you can think of to me`{depicts:0}` — propose). Also these strings with variables should be savable in the form of templates for reuse.* **Format modifiers** — for variables like date, multiple format outputs need to be reachable (`2026-05-10`, `May 10, 2026`, `10 May 2026`, etc.). Propose a modifier syntax. * **Multilingual labels** — depicts labels and location names have a language. The user explicitly flags this as a constraint: "keep in mind the language of labels from items." Propose how the language is selected (current UI language? per-template?). * **Editing UX** — when a cell is being edited, it should show variable **names** (raw template). When unfocused, it should show the substituted **values** so the user can trust their template works. Propose how this toggles visually. * **Template persistence** — templates should be savable for reuse. Where do they live (per-user, cross-device → wiki user-store Preferences.json)? How are they listed / picked / edited? * **"Suggested" templates from past uploads** — the user wants the system to surface templates inferred from previous completed uploads ("you've used `{date:long} – {depicts:0} in {location:village}` 12 times"). Propose how/whether this is detected. == Clarification questions to surface == After drafting the proposal, post it as a Phab comment and **explicitly ask the maintainer (Daanvr) for clarification on the open design choices**. The user has explicitly invited this: "ask me clarification questions". Examples of questions to raise (add your own as the proposal solidifies): * Which fields should be substitutable? (Just title + description, or also author/source/categories?) * Variable syntax preference? * How aggressive should "suggested templates from history" be — explicit panel, or quietly surfaced as autocomplete? * Relationship to T425881 (wikitext-templates, currently in Reviewing) — they're conceptually adjacent (both deal with "templates"); confirm they're independent systems or that one wraps the other. == Out of scope (for the round-1 proposal) == * Any code changes. This round is design/proposal only. * AI-generated suggestions for individual cells (separate concern; also suggest themplates form previous file titles used in previous conot what's being asked here). == Round 2 (after maintainer responds): impleted uploads.mentation == give me a list of variableOnce the maintainer answers that we could use.e clarification questions on Phab, also keep in mind the language of labels from itemsthe task is re-dispatched (or this same agent resumes via a new run) with locked-in design and proceeds through the normal implementer workflow. Also when edditing it should show varaible names. and when the cell is unfocused it should show the values of the variables to give the user the grip and trust their template is working properly.== Source == ask me clarificaiton questionsUser feedback session, 2026-05-10. The user explicitly asked: "give me a list of variables that we could use" and "ask me clarification questions".