201:
the template's "text=" should be changed to "month needed" or "day needed", respectively. A more generic "title=" which fits all three cases could be "An editor has requested that a specific part of the date preceding this tag should be added for specificity.", but "title=" could have three different displays instead: "The preceding date may require its year.", "An editor has requested that the preceding date's month be added for specificity, if it is known.", and "An editor has requested that the preceding date's day be added for specificity, if it is known.".
22:
115:
245:
Using a "when?" tag might be confusing in that case. I'll admit that the day is probably not very important, but there could be some cases where it's desired (if it's possible to provide it). Also, I forgot to mention in my original post that if this is implemented the template will need renaming. Maybe "specify date" since "clarify date" already exists (and is a redirect to "when"). Thanks for your reply.
220:
bespoke (non-templated) talk message should probably be used. We don't want to encourage people asking for details that just aren't critical, and while year was deemed sufficiently critical, month and day weren't. What use case is so prevalent we need a template for "Month needed" that can't be handled by existing templates such as
219:
Let's first ask ourselves "why was this template created to be so specific?" I think year is a crucial piece of information (except of course for ancient events where pinpointing even the right century might be good enough!) For those rare instances when a specific month (or even day) is necessary, a
200:
I propose that this template be changed so that it can display one of the following: "year needed" (as it does now, by default, to not break previous usages of the template), "month needed", and "day needed". There should be a parameter which, if "month" or "day" (or "m" or "d" is entered into it,
244:
I proposed this change because I sometimes come across articles which say – for example – "in the autumn of (year)". Stating a season isn't that precise; I'd like to be able to add "month needed" after such instances so that someone who can verify the source can add the month name for precision.
72:, a collaborative effort to improve and manage Knowledge (XXG)'s inline footnote, cleanup and dispute templates. If you would like to participate, you can visit the project page, where you can join the project and see a list of open tasks.
76:
135:. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by
162:
271:
178:
68:
53:
140:
132:
143:}} to notify an administrator or template editor to make the requested edit. Usually, any contributor may edit the template's
33:
126:
173:
250:
209:
145:
39:
136:
120:
246:
205:
235:
183:
175:
265:
231:
224:
150:
176:
254:
239:
213:
181:
109:
15:
193:
Proposal to make this template more general-purpose for dates
180:
174:
230:? (I'm not involved with the creation of this template)
166:
157:
75:Some discussion of this template may take place at
32:does not require a rating on Knowledge (XXG)'s
165:subpage. You can create the testcases subpage
8:
204:Please let me know what you think. Regards,
86:Knowledge (XXG):WikiProject Inline Templates
47:
155:Any contributor may edit the template's
133:heavily used or highly visible template
49:
89:Template:WikiProject Inline Templates
66:This template is within the scope of
21:
19:
7:
38:It is of interest to the following
272:WikiProject Inline Templates pages
14:
161:. This template does not have a
113:
20:
1:
255:18:45, 5 February 2021 (UTC)
240:09:32, 5 February 2021 (UTC)
214:06:43, 5 February 2021 (UTC)
69:WikiProject Inline Templates
288:
92:Inline Templates articles
59:
46:
141:edit template-protected
77:the project's talk page
149:to add usage notes or
139:, editors may use {{
121:Template:Year needed
79:, rather than here.
34:content assessment
190:
189:
108:
107:
104:
103:
100:
99:
279:
229:
223:
184:
131:because it is a
117:
116:
110:
94:
93:
90:
87:
84:
83:Inline Templates
61:
60:
54:Inline Templates
48:
25:
24:
23:
16:
287:
286:
282:
281:
280:
278:
277:
276:
262:
261:
227:
221:
195:
186:
185:
179:
114:
91:
88:
85:
82:
81:
12:
11:
5:
285:
283:
275:
274:
264:
263:
260:
259:
258:
257:
247:DesertPipeline
206:DesertPipeline
194:
191:
188:
187:
182:
177:
172:
171:
118:
106:
105:
102:
101:
98:
97:
95:
73:
64:
57:
56:
51:
44:
43:
37:
26:
13:
10:
9:
6:
4:
3:
2:
284:
273:
270:
269:
267:
256:
252:
248:
243:
242:
241:
237:
233:
226:
218:
217:
216:
215:
211:
207:
202:
198:
192:
170:
168:
164:
160:
159:
152:
148:
147:
146:documentation
142:
138:
134:
130:
128:
122:
119:
112:
111:
96:
80:
78:
71:
70:
65:
63:
62:
58:
55:
52:
50:
45:
41:
35:
31:
27:
18:
17:
203:
199:
196:
156:
154:
144:
129:from editing
125:permanently
124:
74:
67:
40:WikiProjects
29:
151:categories
163:testcases
137:consensus
127:protected
266:Category
232:CapnZapp
30:template
158:sandbox
36:scale.
28:This
251:talk
236:talk
225:When
210:talk
197:Hi,
167:here
123:is
268::
253:)
238:)
228:}}
222:{{
212:)
169:.
153:.
249:(
234:(
208:(
42::
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.