Wikidata:Property proposal/SWERIK Person ID
SWERIK Person ID
[edit]Originally proposed at Wikidata:Property proposal/Person
| Description | Identifiers used for Swedish Politicians (e.g. Members of Parliament, Ministers) in the SWERIK project |
|---|---|
| Data type | External identifier |
| Domain | Human (Q5) |
| Allowed values | a-z0-9- |
| Example 1 | Olof Palme (Q53713) --> i-DKX1MP4aaNtFZSpMKXCwY |
| Example 2 | Fredrik von Otter (Q52969) --> i-FhLSLTTgMvsYGQ25DUwcvz |
| Example 3 | Arvid Lindman (Q53294)--> i-Fnu186BGHvvTJDuB7t6zMb |
| Planned use | Populate identifier to relevant Wikidata entries Linked data: SWERIK metadata database and Wikidata entries |
| Expected completeness | eventually complete (Q21873974) |
| Formatter URL | https://swerik-project.github.io/person-catalog/$1 |
Motivation
[edit]One aim of the project Swedish Riksdag 1867–2022: An Ecosystem of Linked Open Data (SWERIK) is to enhance open, linked metadata on Swedish politicians who have participated in the parliament. The project infrastructure itself is built explicitly around existing Wikidata infrastructure in that the SWERIK database is built and updated by querying Wikidata directly; additions and corrections by the SWERIK team are contributed directly to Wikidata and re-queried to update the SWERIK data set.
Wikidata IDs, however, are dynamic, and with each update, a handful of errors occur due to mismatched IDs in the dynamic database and static quality control files. Similarly, the SWERIK currently keeps track of metadata categories that are not (yet) recognized as properties, meaning that these static data need to be synced manually with the dynamic database. The proposal then is to add a unique persistent identifier as a Wikidata property for Swedish politicians who have a role in the parliament and populate that property. The persistent ID will be constructed using UUID version 4 with an “i-” prefix so that it can be used as an ID attribute within XML schemas.
Other persistent IDs exist for Swedish politicians, but do not have sufficient temporal coverage. The SWERIK ID will facilitate queries from and contributions to Wikidata, linking data, e.g. with other external identifiers, and reduce potential for the introduction of errors to the data due non-persistent identifiers. Finally, adding this external identifier will contribute to the FAIR-ness of research data produced in the SWERIK project, particularly in that it enhances interoperability and reusability of data by providing stable primary keys. - – The preceding unsigned comment was added by BobBorges (talk • contribs) at 17 november 2023 kl. 11.11 (UTC).
Discussion
[edit]
Support very important that we get research projects having same as Wikidata and persistent identifiers… next step is that we start handle sources and mismatches/ Simple Knowledge Organization System (Q2288360) see project feedback - Salgo60 (talk) 13:49, 17 November 2023 (UTC)
- candidates for same as WD today I miss landing pages that also support metadata following PROV
- Would be nice if we could use tools like Wikidata:Mismatch Finder
- Support - QubeCube (talk) 17:43, 17 November 2023 (UTC)
- Support--So9q (talk) 06:08, 18 November 2023 (UTC)
- Support - VisbyStar (talk) 09:45, 18 November 2023 (UTC)
- @BobBorges, Salgo60, QubeCube, So9q, VisbyStar:
Done SWERIK ID (P12192), but please provide a formatter URL. Jonathan Groß (talk) 19:43, 29 November 2023 (UTC)
- I opened an issue about the missing formatter URL here https://github.com/welfare-state-analytics/riksdagen-corpus/issues/426 So9q (talk) 03:55, 30 November 2023 (UTC)
- formatter url is coming soon... BobBorges (talk) 10:16, 4 January 2024 (UTC)
- I opened an issue about the missing formatter URL here https://github.com/welfare-state-analytics/riksdagen-corpus/issues/426 So9q (talk) 03:55, 30 November 2023 (UTC)
- BobBorges we added a formatter url to the json data you have - that is better than nothing - as wd cache a lot those formatter url string will take time untill its avaliable on all objects or you can purge the object to get it working....
- I checked your json and add language code/sources and also book/page in Two-Chamber Parliament 1867–1970. (Q110346241) they are mentioned in you have it for free in wd and you never knows when it will be deleted in wd
- if you do a landing page add also what protocols they are mentioned in you can easy add a tab in wikipedia see view it tool and have it easy accessible for people reading wikipedia....
- VisbyStar also added third-party formatter URL (P3303) see change that is good for a tool like Wikidata:Entity_Explosion see how Swedish Literature Bank Author ID (P5101) is set up --> we can easy jump between different sources and also see the api data
- the examples above didnt use the correct id we corrected Wikidata property example (P1855) on SWERIK ID (P12192)
- good luck FYI I hope this is my last edit in wikidata ever...
- - Salgo60 (talk) 09:26, 17 January 2024 (UTC)
- @Salgo60 I didn't quite understand why you mentioned json files, but now I see that the formatter url is pointing to the source code of the swerik website instead of the actual website. I tested the apache redirects submitted to W3 and they seemed to point to our website, not the underlying json files. Do we have any idea why this is? Here's an example: `https://swerik-project.github.io/person-catalog/i-EZEtDK9JHw3Gk7dkPLEyuw/`
- And ofc we add more info to the json files progressively, party, alt names, i-ort, bio-band references, etc., I just wanted to get something up and running as quickly as I could. BobBorges (talk) 19:26, 1 February 2024 (UTC)
- https://swerik-project.github.io/person-catalog/i-EZEtDK9JHw3Gk7dkPLEyuw/
- ugh, the back ticks get into the url :| BobBorges (talk) 19:28, 1 February 2024 (UTC)
- BobBorges we added a formatter url to the json data you have - that is better than nothing - as wd cache a lot those formatter url string will take time untill its avaliable on all objects or you can purge the object to get it working....