Property talk:P3127

From Wikidata
Jump to navigation Jump to search

Documentation

Latindex ID
deprecated property, use P12376 instead
Descriptionidentifier of a journal in Latindex
Associated itemLatindex (Q6496562)
Data typeExternal identifier
Domain
According to this template: periodical (Q1002697)
According to statements in the property:
periodical (Q1002697)
When possible, data should only be stored as statements
Allowed values[1-9]\d*
ExampleBulletin Hispanique (Q23739791)20156
Acta Biologica Venezuelica (Q3229252)3686
Avances en Química (Q24935648)16160
Sourcehttp://www.latindex.org
Formatter URLhttps://www.latindex.org/latindex/ficha?folio=$1
Tracking: usageCategory:Pages using Wikidata property P3127 (Q26464639)
See alsoLatindex 2022 ID (P12376)
Lists
Proposal discussionProposal discussion
Current uses
Total872
Main statement86599.2% of uses
Qualifier30.3% of uses
Reference40.5% 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)
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/P3127#Unique value, SPARQL (every item), SPARQL (by value)
Type “periodical (Q1002697): item must contain property “instance of (P31)” with classes “periodical (Q1002697)” or their subclasses (defined using subclass of (P279)). (Help)
List of violations of this constraint: Database reports/Constraint violations/P3127#Type Q1002697, hourly updated report, SPARQL
Format “[1-9]\d*: value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P3127#Format, hourly updated report, SPARQL
Item “ISSN (P236): Items with this property should also have “ISSN (P236)”. (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/P3127#Item P236, search, SPARQL
Item “language of work or name (P407): Items with this property should also have “language of work or name (P407)”. (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/P3127#Item P407, search, SPARQL
Item “title (P1476): Items with this property should also have “title (P1476)”. (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/P3127#Item P1476, 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/P3127#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/P3127#Scope, SPARQL
This property is being used by:

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Proposal to deprecate this property[edit]

I am sorry I have forgotten to discuss the problem here in the first attempt. More than one year ago, I described a very big problem with these identifiers, which Latindex modified in 2022 without redirection nor validation mechanism. See Wikidata:Property_proposal/Latindex_2022_ID The problem is still going, and my diagnostic of a large amount of bad identifiers is, to the best of my knowledge, still present.

So maybe you could read and share your opinion about a new property Latindex 2022 ID? GAllegre (talk) 21:41, 13 January 2024 (UTC)[reply]