Wikidata:Property proposal/LinkedIn personal profile ID

LinkedIn personal profile ID

Originally proposed at Wikidata:Property proposal/Authority control

Done: LinkedIn personal profile ID (P6634) (Talk and documentation)

Description	Identifier for people on the LinkedIn website
Represents	LinkedIn (Q213660)
Data type	External identifier
Domain	human (Q5)
Example	Joan Rivers (Q240933) → joan-rivers-ba163a15 Deborah Lehr (Q50308926) → deborahlehr Hélène Gasnault (Q42310145) → hélène-gasnault-a2543562
External links	Use in sister projects: [ar] • [de] • [en] • [es] • [fr] • [he] • [it] • [ja] • [ko] • [nl] • [pl] • [pt] • [ru] • [sv] • [vi] • [zh] • [commons] • [species] • [wd] • [en.wikt] • [fr.wikt].
Planned use	To replace P2035 (P2035)
Number of IDs in source	100,000s
Expected completeness	always incomplete (Q21873886)
Formatter URL	https://www.linkedin.com/in/$1/
Robot and gadget jobs	Bot conversion from P2035 (P2035)

Motivation

To replace P2035 (P2035), as discussed at Wikidata:Project chat#LinkedIn personal profile URLs and earlier discussions linked from there.

LinkedIn have changed their profile URLs, from unpredictable country-specific and other values to a standard which allows us to use an external-id property type and apply a formatter URL, with better constraints, etc. For example:

https://de.linkedin.com/in/ponzetto

is now:

https://www.linkedin.com/in/ponzetto/

A bot or scripted tools will copy over the existing values, and remove the old ones, after which the old property will be proposed for deletion. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:32, 15 March 2019 (UTC)[reply]

Discussion

Support Much better than random URL strings, and easier to manage over time if LinkedIn makes further changes. - PKM (talk) 22:26, 15 March 2019 (UTC)[reply]
Support David (talk) 06:48, 16 March 2019 (UTC)[reply]
Oppose we already have a property for this allowing easy entry and maintenance. --- Jura 08:49, 16 March 2019 (UTC)[reply]
Support For consistency with most other external identifiers. LaddΩ chat ;) 17:09, 16 March 2019 (UTC)[reply]
Support. OK. This makes sense. Thierry Caro (talk) 17:15, 16 March 2019 (UTC)[reply]
Support: an ID is IMHO better than a full URL. (I furthermore would love the same for Academia profiles...) Nomen ad hoc (talk) 17:52, 16 March 2019 (UTC).[reply]
Support --LydiaPintscher (talk) 18:18, 16 March 2019 (UTC)[reply]
- Comment: I don't think we should change the existing property so significantly. It's not good for anyone reusing the existing property already and relying on it being a URL. This is a breaking change I think we should avoid. --LydiaPintscher (talk) 15:45, 18 March 2019 (UTC)[reply]
Oppose per Jura in part; I agree that it's useful to switch to using the personal profile ID, but if every personal profile URL maps to a unique ID, why not just reuse the original property for this purpose? Mahir256 (talk) 01:12, 17 March 2019 (UTC)[reply]
- @Mahir256: external-id and URL are two distinct datatypes, a new property is needed. ArthurPSmith (talk) 14:39, 18 March 2019 (UTC)[reply]
Support Obvious data normalization step --Vladimir Alexiev (talk) 13:00, 17 March 2019 (UTC)[reply]
Support in principle, but I agree with Jura and Mahir256 — I'd prefer converting the existing P2035 (P2035) to an external ID, rather than creating a new one which essentially duplicates its function. --Waldir (talk) 16:51, 17 March 2019 (UTC)[reply]
Question for those proposing to reuse the existing property, would you just leave the existing values as format violations until converted? Also, once we specify a formatter URL, existing links would not work until they are converted. - PKM (talk) 20:01, 17 March 2019 (UTC)[reply]
Support having a property with just the identifier instead of the full URL, similar to LinkedIn company or organization ID (P4264). As noted above by ArthurPSmith and also in a discussion at Property talk:P2035 § Identifier, it appears the current property cannot be reused because P2035 (P2035) has the data type url while the new property would be data type external-id. -- Zyxw (talk) 15:25, 18 March 2019 (UTC)[reply]
Support This would be an improvement. Simon Cobb (User:Sic19 ; talk page) 18:45, 20 March 2019 (UTC)[reply]
Support --Kristbaum (talk) 12:39, 22 March 2019 (UTC)[reply]
Comment Note that P2035 (P2035) is used by many templates in multiple wikis (at least el, en, uk, ca, da, he ro, ru, but very likely in many more). In case of change all these needs to be notified & fixed, we do not live in ivory tower.--Jklamo (talk) 15:09, 22 March 2019 (UTC)[reply]