Store, expose and link other ID's

[Neil Carmichael]

Store, expose and link other ID's  for the members such as

Beamish peerage database person ID
Companies House officer ID
Hansard (1803–2005) ID
OpenSanctions ID
parliament.uk member ID
Rush Parliamentary Archive ID
TheyWorkForYou ID
UK Parliament identifier
UK Parliament thesaurus ID
Who's Who UK ID
The Peerage person ID

Most of which can be found in WIkidata, see https://www.wikidata.org/wiki/Q333020 as an example

[Q Ian MacQuarrie]

Unsubscribe please from all theyworkforyou maillists. Thanks...

Sent from Outlook for Android

---

From: Neil Carmichael <back...@hotmail.com>
Sent: Wednesday, March 22, 2023 8:58:07 AM
To: TheyWorkForYou <theywor...@mysociety.org>
Subject: [theyworkforyou] Store, expose and link other ID's

 

--
You received this message because you are subscribed to the Google Groups "TheyWorkForYou" group.
To unsubscribe from this group and stop receiving emails from it, send an email to theyworkforyo...@mysociety.org.
To view this discussion on the web visit https://groups.google.com/a/mysociety.org/d/msgid/theyworkforyou/30dd6b29-70b7-4806-8d8b-ed355e92418en%40mysociety.org.

[Matthew Somerville]

Hi,

Given Wikidata already includes all these identifiers, I don't think we'd want to add the maintenance load to try and have them in TheyWorkForYou as well. Better to make sure Wikidata has all the TheyWorkForYou IDs in it, then it can be used to correlate between the various different sources that you mention where needed. Where we need the IDs ourselves (e.g. Parliament's ID for matching up our parsing), they are included in our XML data.

ATB,

Matthew

--