Property talk:P1214

From Wikidata
Jump to navigation Jump to search

Documentation

Riksdagen person-ID
identifier at data.riksdagen.se
DescriptionThe identifier for people in the Swedish Riksdag (Parliament) database
Applicable "stated in" valueSwedish Parliament database (Q21592569)
Data typeExternal identifier
Domainperson (note: this should be moved to the property statements)
Allowed values\d{9,13} (numeric string,9 to 13 digits)
ExampleMaria Arnholm (Q3540867)0758652610
Elisa Abascal Reyes (Q4933527)0643844865712
Sourcehttp://data.riksdagen.se/Data/Ledamoter
Formatter URLhttps://data.riksdagen.se/personlista/?iid=$1&utformat=html
https://data.riksdagen.se/person/$1
https://www.riksdagen.se/sv/ledamoter-partier/ledamot/_$1
Tracking: usageCategory:Pages using Wikidata property P1214 (Q55089903)
Related to country Sweden (Q34) (See 117 others)
See alsoelectoral district (P768), PACE member ID (P1331), Swedish Parliament person GUID (P8388), Swedish Riksdag document ID (P8433), SWERIK ID (P12192)
Lists
Proposal discussionProposal discussion
Current uses
Total5,948
Main statement2,11935.6% of uses
Qualifier2<0.1% of uses
Reference3,82764.3% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Distinct values: this property likely contains a value that is different from all other items. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1214#Unique value, hourly updated report, SPARQL (every item), SPARQL (by value)
Single value: this property generally contains a single value. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1214#Single value, hourly updated report, SPARQL
Format “0\d{9,12}: value must be formatted using this pattern (PCRE syntax). (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P1214#Format, SPARQL
Item “sex or gender (P21): Items with this property should also have “sex or gender (P21)”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1214#Item P21, hourly updated report, search, SPARQL
Item “country of citizenship (P27): Sweden (Q34): Items with this property should also have “country of citizenship (P27): Sweden (Q34)”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1214#Item P27, hourly updated report, search, SPARQL
Item “occupation (P106): politician (Q82955): Items with this property should also have “occupation (P106): politician (Q82955)”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1214#Item P106, hourly updated report, search, SPARQL
Item “member of political party (P102): Items with this property should also have “member of political party (P102)”. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P1214#Item P102, search, SPARQL
Item “date of birth (P569): Items with this property should also have “date of birth (P569)”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1214#Item P569, hourly updated report, SPARQL
Item “given name (P735): Items with this property should also have “given name (P735)”. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P1214#Item P735, search, SPARQL
Item “instance of (P31): human (Q5): Items with this property should also have “instance of (P31): human (Q5)”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1214#Item P31, hourly updated report, search, SPARQL
Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P1214#Entity types
Scope is as main value (Q54828448), as reference (Q54828450): the property must be used by specified way only (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P1214#Scope, SPARQL
Pattern ^([\da-f]{8}-[\da-f]{4}-[\da-f]{4}-[\da-f]{4}-[\da-f]{12})$ will be automatically replaced to \1 and moved to Swedish Parliament person GUID (P8388) property.
Testing: TODO list


new ID

[edit]

Riksdagen tells us to change value see T235521

- Salgo60 (talk) 17:07, 15 October 2019 (UTC)[reply]

@Jura1: please explain why or call me 0046705937579. I had a meeting last month with the people at the Swedish Parlament IT department see T235527 they will run in parallell the old and new id (is a guid) and then it will be killed
I have created a task for me to convert them see T235521
- Salgo60 (talk) 23:21, 23 November 2019 (UTC)[reply]
We don't delete information from Wikidata once the source websites is discontinued or changed. Wikidata users should still be able to use the (old) identifiers.
For the new identifier, please use Wikidata:Property proposal. --- Jura 23:31, 23 November 2019 (UTC)[reply]
@Jura1: Lydia had on telegram Wikidata a mature discussion about what to do with depreciated data and it depends...
I know this dataset good and has followed your advice in other user stories like Libris-URI (P5587) see request link that is a new parameter replacing e.g. SELIBR ID (P906)
This user case is
  • The owner of the data tell us we have the wrong data
  • The current value works in parallell with the old value
  • I have seen so far no one external using Wikidata values directly and compared to Libris-URI (P5587) its very few users
  • We have already started to convert some ....
- Salgo60 (talk)
Maybe Lydia could comment here. She rarely edits and I think the creation of a phabricator ticket might have been an error: developers aren't involved in content decisions. --- Jura 00:10, 24 November 2019 (UTC)[reply]

position held (P39) and work location

[edit]

Is there a problem with the way the constraints were defined? Why were they removed? --- Jura 21:28, 23 November 2019 (UTC)[reply]

You can have an ID without being a member of the Riksdag (examples : Q4949040, Q16595498, Q4979205, Q234872). --Rashinseita (talk) 21:34, 23 November 2019 (UTC)[reply]
So it would be member or minister (also Stockholm) or MEP (not Stockholm)? --- Jura 21:41, 23 November 2019 (UTC)[reply]
Yes, I agree with that. (I didn't see other cases). --Rashinseita (talk) 09:17, 24 November 2019 (UTC)[reply]
Fixed the constraint. Finds people like Q5992996 who lacked a P39. --- Jura 21:37, 29 November 2019 (UTC)[reply]

Repair needed

[edit]

It appears that the content has become partially unusable as some of the identifiers of this property were overwritten and are no longer in Wikidata. Users attempting to process database dumps get this identifier (see explanation by @Popperipopp: at Wikidata:Property_proposal/Riksdagen_person_guid).

The proposed way to solve is it to create a separate property for the other identifier and restore the old data. Accordingly, please support the proposal at Wikidata:Property_proposal/Riksdagen_person_guid.

@Rashinseita, Esquilo, Lokal Profil: as you contributed to this property. --- Jura 08:55, 14 June 2020 (UTC)[reply]

So far I have not seen a single "new" 36-byte identifier actually work (as in the link leading to data and not a 404). All "old" (all digit) identifiers I have seen have worked. That is why I have replaced "new" identifiers with "old" ones when I come across one. /ℇsquilo 11:44, 14 June 2020 (UTC)[reply]
Not sure why this is. Have identifiers changed? If you go to this page and select a person from the first drop down you land on a page that uses the new style ID in the url. Also, the liked images and person pages use the new style. Seems more future proof to have both. Belteshassar (talk) 10:40, 22 June 2020 (UTC)[reply]
Ainali Belteshassar so9q Vätte Popperipopp Tulipasylvestris Esquilo Daniel Mietchen — with focus on topics related to research (Q42240) VisbyStar Haxpett QubeCube Marcus.linneberg Vitplister Spisen Sollentuna Myohmy671 Autom S4b1nuz E.656 JoranL

Notified participants of WikiProject Sweden --- Jura 09:40, 22 June 2020 (UTC)[reply]

@ℇsquilo, Belteshassar, Popperipopp, Jura, Ainali: please give example of errors and let me know which direction we move so can I try to fix it...

- Salgo60 (talk) 12:14, 22 June 2020 (UTC)[reply]

From what I've seen, the "old" identifier is always present in data dumps and API calls from data.riksdagen.se whereas the "new" identifier is sometimes present. I see no reason to replace the current identifier with the new one. Who knows how long it will take Riksdagen to complete their updates? With that said, I think it's a good idea to add a new Wikidata property for the new identifier, clearly stating that it is, in fact, different from the old one. Mixing the two complicates things considerably when merging data from Riksdagen with Wikidata items. Popperipopp (talk) 12:49, 22 June 2020 (UTC)[reply]
@Popperipopp: give examples so can I ask the people at data.riksdagen.se they are easy speaking with and can easy tell us why it is in one way or the other...
I guess they dont give new members the old id
- Salgo60 (talk) 12:55, 22 June 2020 (UTC)[reply]
The CSV file with MPs 1990- found on the page Ledamöter only has the old identifiers. Popperipopp (talk) 13:10, 22 June 2020 (UTC)[reply]
Ok then I suggest we create a new property see Wikidata:Property_proposal/Riksdagen_person_guid I did a Swedish video of what Popperipopp found and I guess its easier have two separate properties - Salgo60 (talk) 14:39, 22 June 2020 (UTC)[reply]
Well, I'm glad this is finally sorted out, whatever the reasons for the detour. --- Jura 14:54, 22 June 2020 (UTC)[reply]