Wikidata:Property proposal/Split P883 (US state ID) into two properties - alpha and numeric

FIPS string code for US states per former FIPS 5-2 standard. edit

Originally proposed at Wikidata:Property proposal/Place

Done: FIPS 5-2 alpha code (US states) (P5086) (Talk and documentation)

Description	FIPS string code for US states per former FIPS 5-2 standard.
Data type	External identifier
Domain	places: US states and certain other associated areas
Allowed values	[A-Z]{2}
Example	Michigan (Q1166) -> MI

Originally proposed at Wikidata:Property proposal/Place

Done: FIPS 5-2 numeric code (US states) (P5087) (Talk and documentation)

Description	FIPS numeric code for US states per former FIPS 5-2 standard.
Data type	External identifier
Domain	places: US states and certain other associated areas
Allowed values	\d{2}
Example	Michigan (Q1166) -> 26

Motivation

The existing P883 (P883) has both string and numeric values, making it much harder to work with than any other regular "one Identifier - one value" properties. I think we should split them up, just like it was initially proposed by the original author @Danrok:. We could also reuse the existing property for the string value, and move the numeric value into a new property. CC: @Docu:, @Aude:. Yurik (talk) 23:32, 27 January 2018 (UTC)[reply]

Discussion

Support Sure. Mahir256 (talk) 20:39, 28 January 2018 (UTC)[reply]
- @Mahir256: should we keep the existing one for a string only, and introduce the new one only for numbers? --Yurik (talk) 23:39, 28 January 2018 (UTC)[reply]
Not done stale request, open questions
--- Jura 07:34, 19 April 2018 (UTC)[reply]
@Jura1: can you help with it? E.g. create the new property (I think a single new property for the numeric value would be good). Thx! --Yurik (talk) 11:53, 19 April 2018 (UTC)[reply]
I'm not sure what you prefer. However, if P883 is kept, but repurposed, this may break some uses. So creating two new properties seems the cleaner approach.
--- Jura 12:08, 19 April 2018 (UTC)[reply]
@Jura1: this is more of limiting the usage, not repurposing. The property in it's dual-use format has very little utility because it makes usage very complicated. Keeping both properties on each object seems bad, as it may introduce inconsistencies, increase maintenance load, and we don't have any reasonable notification system if a property is going obsolete. So we might as well narrow down its usage. --Yurik (talk) 12:33, 19 April 2018 (UTC)[reply]
Once the two new ones created, the old one can be deleted. In any case, you will introduce some discontinuity. By creating just one, people might be lead to believe that it still works as before. In both approaches, you will end up with two properties on each item.
--- Jura 13:41, 19 April 2018 (UTC)[reply]
@Jura1: agree. Could you create the two new props? Thx! --Yurik (talk) 14:11, 19 April 2018 (UTC)[reply]
I set it to ready.
--- Jura 15:13, 19 April 2018 (UTC)[reply]

@Yurik, Jura1, Mahir256: Done: FIPS 5-2 alpha code (US states) (P5086) and FIPS 5-2 numeric code (US states) (P5087). − Pintoch (talk) 09:28, 22 April 2018 (UTC)[reply]

@Pintoch:, I just uploaded data for all of them using quick statements. I think we can now delete the old one. --Yurik (talk) 20:30, 22 April 2018 (UTC)[reply]

p.s. Here's a link to query comparing the old and the new - [1] --Yurik (talk) 20:45, 22 April 2018 (UTC)[reply]

Great! Feel free to propose the property for deletion atWikidata:Properties_for_deletion − Pintoch (talk) 21:13, 22 April 2018 (UTC)[reply]