Content deleted Content added
→Bug in fetching referenced data: multiple dates of birth |
→Bug in fetching referenced data: prefer to use a local parameter for such a case |
||
Line 279:
:::: {{reply to |Mike Peel|label=Mike}} As far as I know, you can have many of each rank as you wish. The question is how should we deal with the case where multiple values of the property exist with the same rank? We would want to return as a list multiple values of most fields, e.g. occupation, but surely we wouldn't want multiple dates of birth returned? --[[User:RexxS|RexxS]] ([[User talk:RexxS|talk]]) 20:56, 28 January 2017 (UTC)
::::: Apparently sometimes multiple dates of birth do need to be returned, e.g. from [[:d:Q885424]]. So maybe just return all of the referenced statements for the highest rank available? Thanks. [[User:Mike Peel|Mike Peel]] ([[User talk:Mike Peel|talk]]) 22:52, 6 February 2017 (UTC)
:::::: I'd prefer to use a local parameter for such a case. We could then have "3 or 9 August 1858", rather than the list that the call would naturally return: "3 August 1858, 9 August 1858". That's because the call doesn't know that we would write the list of dates in the former way for disputed dates of birth. I could certainly make the list output with "or" separating the dates, but shorthand styles like "3 or 9 August 1858" and "30 July or 9 August 1858" are a lot more work to program, and hence more room for errors and edge cases, and I'd want to see a lot more testing in sandbox if we went down that route. --[[User:RexxS|RexxS]] ([[User talk:RexxS|talk]]) 04:34, 7 February 2017 (UTC)
== Unsafe use of labels ==
| |||