Property talk:P11118

From Wikidata
Jump to navigation Jump to search

Documentation

Larousse Online French Dictionary ID
identifier for a Lexeme in online Larousse French dictionary
[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)
List of violations of this constraint: Database reports/Constraint violations/P11118#Single value, hourly updated report, SPARQL
Allowed entity types are Wikibase lexeme (Q51885771): 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/P11118#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/P11118#Scope, SPARQL
Lexeme language: French (Q150): this property should only be applied to lexemes with these languages (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/P11118#language
Qualifiers “subject form (P5830), grammatical gender (P5185), subject sense (P6072): this property should be used only with the listed qualifiers. (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/P11118#allowed qualifiers, SPARQL
Format “[1-9][0-9]*#[1-9][0-9]*: value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P11118#Format, hourly updated report, SPARQL

URL-encoding[edit]

It seems the URL-encoding is broken with URL having fragment identifier (Q1440450). The link generated is leading to 403 because the hash-mark is escaped to %23 when it should be keept as #. However, identifiers with 2 parts separated by a hash-mark are correct ; the issue is only with the way we generate URL from them. See phab:T160281. — Metamorforme42 (talk) 08:18, 19 October 2022 (UTC)[reply]

Please also note that template:property documentation generate them correctly. — Metamorforme42 (talk) 08:20, 19 October 2022 (UTC)[reply]
I tried a workaround using Wikidata External ID redirector (Q108047563). According to Property_talk:P1630#Formatter_URL_cached, it can take up to 24h before this change is taken into account and then items need to be purged/edited. Will see tomorrow… — Metamorforme42 (talk) 12:24, 19 October 2022 (UTC)[reply]
Thanks a lot for your work on this property! Links are OK now (even though it's sad to need to use a workaround). I'm updating my bot to handle this dictionary, along with other ones, and mass import IDs. Cheers, — Envlh (talk) 10:24, 20 October 2022 (UTC)[reply]
@Metamorforme42: Please avoid adding IDs on existing lexemes during the initial import of the bot, it will duplicate them. It's fine on new items. Cheers, — Envlh (talk) 14:23, 20 October 2022 (UTC)[reply]
Oh, ok. I will wait and check for duplicate once the run is finished. Thanks. — Metamorforme42 (talk) 14:30, 20 October 2022 (UTC)[reply]
By the way, I found some mismatchs: doubleur (L691370) and promoteur (L27248). For the second, I added an exception to the single-value constraint (using grammatical gender (P5185) as separator). I guess the same issue will be on cuisinière (L28230), and more generally on this kind of lexeme having multiple senses with once beeing an occupation, and one other not an occupation. Maybe we should consider splitting such lexemes instead but I am not sure it is always appropriate… — Metamorforme42 (talk) 15:58, 20 October 2022 (UTC)[reply]
Yes, the matching is really basic: lemma + lexical category (+ gender for nouns), so there are some false positives. I'm not sure for the splitting, we can think about it. I paused the import for tonight because of maxlag issues on Wikidata. In the meantime, crawling of the dictionary continues (it will take 4 days to be completed), and I'll improve the matching. Cheers, — Envlh (talk) 20:25, 20 October 2022 (UTC)[reply]
Initial import is done. Feel free to work on this property, without risk for the bot to duplicate values. I'll continue to work on it to improve the matching (about 50 small lexical categories from Larousse are not handled at the moment, and matching nouns need a rework). Cheers, — Envlh (talk) 07:17, 24 October 2022 (UTC)[reply]