Property talk:P2427

Latest comment: 4 years ago by Shervinafshar in topic Establishment Dates with Wrong Calendar Label

Documentation

GRID ID
institutional identifier from the GRID.ac global research identifier database
Associated itemDigital Science (Q26424202)
Applicable "stated in" valueGRID (Q27768150)
Data typeExternal identifier
Domainorganization (Q43229), facility (Q13226383), fixed construction (Q811430), publication (Q732577), research project (Q1298668) or administrative territorial entity (Q56061)
Allowed valuesgrid\.\d{4,6}\.[0-9a-f]{1,2}
ExampleUniversity of Western Australia (Q1517021) → grid.1012.2
Republic of Korea National Red Cross (Q7314493) → grid.454116.3
Sourcehttps://www.grid.ac/
Tracking: usageCategory:Pages using Wikidata property P2427 (Q56056020)
See alsoEU Participant Identification Code (P5785), ROR ID (P6782), Ringgold ID (P3500)
Lists
Proposal discussionProposal discussion
Current uses
Total218,957
Main statement103,984 out of 102,392 (102% complete)47.5% of uses
Qualifier6<0.1% of uses
Reference114,96752.5% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Format “grid\.\d{4,6}\.[0-9a-f]{1,2}: value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P2427#Format, hourly updated report, SPARQL
Distinct values: this property likely contains a value that is different from all other items. (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/P2427#Unique value, SPARQL (every item), SPARQL (by value)
Single best value: this property generally contains a single value. If there are several, one would have preferred rank (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/P2427#single best value, 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/P2427#Entity types

Unique constraint

edit

User:Ivan A. Krestinin has already removed the mandatory flag from the single value constraint. But looking at the constraint violations, it seems that GRID has does not even try to have unique IDs. Therefore I suggest we completely remove the constraint. --Srittau (talk) 12:00, 10 January 2016 (UTC)Reply

After cleaning up most of the multinationals, I have emailed GRID to show them the remaining list of identifiers, and here is their reply:

We have looked through the 229 potential merge candidates you have submitted and we identified 60 duplicates and have redirected them to the correct entry. In addition we have also added missing Wikidata ids to the corresponding GRID entry. Unfortunately all of these changes and corrections will not be visible to you until our next data release. Again, thank you for this input, it has been very helpful and we appreciate the time and effort you put into improving our data very much.

I think we could use this to split the remaining items with duplicate ids into separate items, now that we know that they have been confirmed by GRID. (We seem to have the same notion of organization). Any idea how to proceed? − Pintoch (talk) 10:57, 18 April 2017 (UTC)Reply

Did they tell you which 60 were agreed on as duplicates? Otherwise it sounds like we have to wait for the next release (early May?) ArthurPSmith (talk) 13:57, 18 April 2017 (UTC)Reply
Right, as they said they had "redirected" them I thought HTTP redirections were already in place on grid.ac, but indeed we'll have to wait a bit. − Pintoch (talk) 16:57, 18 April 2017 (UTC)Reply
@Pintoch: the new release is out (somehow dated a week ago, I'm sure it wasn't up then though?)!! I hope to be looking at it the next few days and see if I can figure out how many of those dups have been fixed. ArthurPSmith (talk) 20:23, 31 May 2017 (UTC)Reply
@ArthurPSmith: Great! Is there any better way to detect merges than simply checking for HTTP redirects on the web interface? − Pintoch (talk) 21:00, 31 May 2017 (UTC)Reply
the grid.json dump file has merged id's listed with no name and a "redirect" field - for example for grid.481551.c it has the entry:
 {"id":"grid.481551.c","status":"redirected","redirect":"grid.410484.d"}
there are 400 new ones with this release (2374 redirected in May, 1963 in April release), so definitely many updates there! ArthurPSmith (talk) 12:25, 1 June 2017 (UTC)Reply
By the way I've started some of the cleanup on this (by hand basically - there are a bit over 200 cases to look at). Some of the new redirects seem to be GRID deciding not to include some smaller entities and only point to the larger ones - an example is grid.420437.6 - National Oceanographic Data Center (Q6974619) which has been redirected to grid.454206.1 - National Centers for Environmental Information (Q21015842) - I'm leaving that alone as the old ID was previously valid, but the formatter URL now takes you to the parent organization. Maybe we should delete these GRID id's though? But cases where there were two GRID id's on one wikidata item, or only the old ID that has been updated, I'm removing the old one and ensuring the new one is there. ArthurPSmith (talk) 19:03, 1 June 2017 (UTC)Reply
FYI I've finished what I thought was needed on cleaning up the redirect iD's. I believe all the remaining redirected GRID ID's in wikidata are cases where GRID has merged two or more records that we probably don't want to merge; none of them should have more than one ID per wikidata item any longer. ArthurPSmith (talk)

Bad claims imported from DB

edit

Saw several, here is one example:

  1. https://www.wikidata.org/w/index.php?title=Q1813740&diff=698226083&oldid=620545690

85.180.90.183 18:16, 18 June 2018 (UTC)Reply

if it's an accurate representation of what is stated in the source, then the statement should be marked deprecated with an appropriate annotation, not removed. You can also contact the source database here (GRID has a ticket system for tracking such requests) to get anything you feel is wrong corrected. ArthurPSmith (talk) 19:02, 18 June 2018 (UTC)Reply

Establishment Dates with Wrong Calendar Label

edit

Dates of establishment are available for many Iranian organization listed in GRID data sets. However the dates are in Solar Hijri and not Gregorian. I suggest these references to be removed or bulk calculated and reimported. Examples: Q30265263 (on GRID.ac), Q33122101 (on GRID.ac). I reported this issue to that database maintainers as well. Shervinafshar (talk) 04:10, 13 April 2020 (UTC)Reply

@Shervinafshar: Oops! Yes indeed. Do you have a guess how many are a problem? ArthurPSmith (talk) 18:00, 13 April 2020 (UTC)Reply
@ArthurPSmith: turns out there are not many of them which are incorrect: https://w.wiki/Mkg . I don't know in SPARQL how to exclude those without GRID reference so there are few int the results set of this query which are legit; eg. Q47690 or Q273874. Shervinafshar (talk) 00:41, 14 April 2020 (UTC)Reply
Return to "P2427" page.
  NODES
admin 3
Idea 1
idea 1
Project 4