Property talk:P8758
Jump to navigation
Jump to search
Documentation
Persée article ID
identifier for an article on Persée
identifier for an article on Persée
[create Create a translatable help page (preferably in English) for this property to be included here]
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/P8758#Single value, SPARQL
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/P8758#Unique value, hourly updated report, SPARQL (every item), SPARQL (by value)Type “scholarly article (Q13442814)”: item must contain property “instance of (P31)” with classes “scholarly article (Q13442814)” 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/P8758#Type Q13442814, SPARQL
Format “
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). [a-z0-9]{3,5}_\d{4}-[\dx]{4}_[1-2]\d{3}_[a-z]{3}_\d*_\d*(?:_\d*(?:_t\d{1,2}_\d*_\d*_\d*)?)?
”: value must be formatted using this pattern (PCRE syntax). (Help)List of violations of this constraint: Database reports/Constraint violations/P8758#Format, SPARQL
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/P8758#Scope, 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/P8758#Entity types
Violation de contraintes
[edit]Bonjour @Thierry Caro, Pamputt:,
Je viens de créer Q105698070 qui utilise Persée article ID (P8758) et j'ai une violation de contraintes de format. Du coup, je regarde de plus près et je me rends que le problème vient de la contrainte qui est trop stricte : actuellement 22 des 26 utilisations la violent alors que tout ces liens me semblent corrects.
La regex actuelle [a-z0-9]{3,4}_\d{4}-[\dx]{4}_[1-2]\d{3}_num_[1-9]\d_[1-9]_[1-9]\d*
ne correspond qu'au début de mon identifiant abpo_0003-391x_1957_num_64_4_2034 et oubli la fin _t1_0505_0000_1 mais si je retire cette fin la page n'existe pas. Est-ce un oubli ? un cas particulier ? autre chose ?
Cdlt, VIGNERON (talk) 09:50, 27 February 2021 (UTC)
- Personnellement, je ne sais pas. C'est sans doute une erreur dans l'écriture de la contrainte, oui. Thierry Caro (talk) 15:54, 27 February 2021 (UTC)
- @VIGNERON: Just so you know, I have just changed the regex constraint to
[a-z0-9]{3,4}_\d{4}-[\dx]{4}_[1-2]\d{3}_num_\d*_\d*_\d*(?:_t\d_\d*_\d*_\d*)?
, which should now work with longer article IDs such as that of the article you mentioned. (At the same time, I fixed a separate problem I noticed myself with volume numbers, even without the_tn_
part;[1-9]\d
doesn't allow "1" nor "100"). Monster Iestyn (talk) 19:33, 4 December 2021 (UTC)- @Monster Iestyn: thanks a lot. It seems to be all good now. Cheers, VIGNERON (talk) 20:41, 4 December 2021 (UTC)
- Hi Monster Iestyn, for info, I had a similar problem for Q116730783 where the identifier "antiq_0770-2817_1983_num_52_1_2106_t1_0578_0000_1" violated the format constraint... I changed the beggining of the regex to
[a-z0-9]{3,4}
and it's ok now. That said, we should take a deeper look at this constraint to make sure we don't capture again correct identifiers. Cheers, VIGNERON en résidence (talk) 12:55, 9 February 2023 (UTC)- @VIGNERON en résidence: Thanks for letting me know. I think that probably fixed some of the other article items listed at Wikidata:Database reports/Constraint violations/P8758#"Format" violations, but maybe not other ones... For instance I just noticed that the value "reg_0035-2039_2013_num_126_2_8149_t16_0660_0000_2" at Q102104622 doesn't fit the format, I'll try to fix that now. Monster Iestyn (talk) 13:34, 9 February 2023 (UTC)
- I've now changed the regex constraint format to
[a-z0-9]{3,5}_\d{4}-[\dx]{4}_[1-2]\d{3}_[a-z]{3}_\d*_\d*(?:_\d*(?:_t\d{1,2}_\d*_\d*_\d*)?)?
:[a-z]{3}
replacesnum
(because some values havesup
orhos
instead),t\d{1,2}
allows for up to two digits aftert
, and finally items such as Q105947634 (value "galip_0072-0100_1972_sup_7_1") have only two numbers aftersup
, etc., so I have made the third number optional. Monster Iestyn (talk) 13:50, 9 February 2023 (UTC)
- I've now changed the regex constraint format to
- @VIGNERON en résidence: Thanks for letting me know. I think that probably fixed some of the other article items listed at Wikidata:Database reports/Constraint violations/P8758#"Format" violations, but maybe not other ones... For instance I just noticed that the value "reg_0035-2039_2013_num_126_2_8149_t16_0660_0000_2" at Q102104622 doesn't fit the format, I'll try to fix that now. Monster Iestyn (talk) 13:34, 9 February 2023 (UTC)
- Hi Monster Iestyn, for info, I had a similar problem for Q116730783 where the identifier "antiq_0770-2817_1983_num_52_1_2106_t1_0578_0000_1" violated the format constraint... I changed the beggining of the regex to
- @Monster Iestyn: thanks a lot. It seems to be all good now. Cheers, VIGNERON (talk) 20:41, 4 December 2021 (UTC)
- @VIGNERON: Just so you know, I have just changed the regex constraint to
Categories:
- France-related properties
- All Properties
- Properties with external-id-datatype
- Properties used on 10000+ items
- Properties with single value constraints
- Properties with unique value constraints
- Properties with constraints on type
- Properties with format constraints
- Properties with scope constraints
- Properties with entity type constraints