Property talk:P3124
Latest comment: 4 months ago by Korektysta in topic Deprecation
Documentation
Polish scientist ID
identifier for a scientist, in the Polish Government's Information Processing Centre database
identifier for a scientist, in the Polish Government's Information Processing Centre database
[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)
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/P3124#Unique value, SPARQL (every item), SPARQL (by value)
Single value: this property generally contains a single value. (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/P3124#Single value, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3124#Format, hourly updated report, 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/P3124#Item P31, hourly updated report, search, SPARQLType “human (Q5)”: item must contain property “instance of (P31)” with classes “human (Q5)” or their subclasses (defined using subclass of (P279)). (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/P3124#Type Q5, SPARQL
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/P3124#Item P106, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3124#Item P106, 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/P3124#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/P3124#Scope, SPARQL
Label required in languages: pl: Entities using this property should have labels in one of the following languages: pl (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/P3124#Label in 'pl' language, search, SPARQL
|
|
Wider scope for this property
edit@Pigsonthewing, Strakhov, ChristianKl:
Actually this identifier has a wider scope. It refers to:
- scientists
- scientific institutions
- scientific research
- scientific publications
- scientific conferences, fairs and exhibitions
in Poland. See: [1]
Although most P3124 identifiers form a statement in items for humans they are also valid for items like universities, faculties etc.
It might be useful to rename this property and adjust constraints accordingly. Kpjas (talk) 18:32, 4 March 2020 (UTC)
EDIT: URLs for institutions, research, publications and conferences differ (need to be changed). Kpjas (talk) 06:36, 5 March 2020 (UTC)
- @Kpjas: The identifier itself does not have a wider scope, however, I agree it makes sense to have more identifier properties referring to Polish Science (Q97032597) for the things you mention. —Uzume (talk) 22:20, 3 December 2020 (UTC)
Deprecation
editI got a response for the ticket https://helpdesk.opi.org.pl/#/ticket-details/system-user/85305 that usage of the IDs of the old database in the new database is not possible. Korektysta (talk) 12:23, 2 April 2024 (UTC)