Property talk:P12772

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/P12772#Single value, 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/P12772#Unique value, SPARQL (every item), SPARQL (by value)

Format “[1-9]\d*”: value must be formatted using this pattern (PCRE syntax). (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/P12772#Format, SPARQL

Type “mill (Q44494)”: item must contain property “instance of (P31), subclass of (P279)” with classes “mill (Q44494)” 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/P12772#Type Q44494, 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/P12772#Entity types

Scope is as main value (Q54828448): 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/P12772#Scope, SPARQL

Item “country (P17)”: Items with this property should also have “country (P17)”. (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/P12772#Item P17, search, SPARQL

Item “located in the administrative territorial entity (P131)”: Items with this property should also have “located in the administrative territorial entity (P131)”. (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/P12772#Item P131, search, SPARQL

Item “coordinate location (P625)”: Items with this property should also have “coordinate location (P625)”. (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/P12772#Item P625, SPARQL

Item “image (P18)”: Items with this property should also have “image (P18)”. (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/P12772#Item P18, SPARQL

Item “Commons category (P373)”: Items with this property should also have “Commons category (P373)”. (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/P12772#Item P373, search, SPARQL

Item “source of energy (P618)”: Items with this property should also have “source of energy (P618)”. (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/P12772#Item P618, search, SPARQL

Item “has use (P366)”: Items with this property should also have “has use (P366)”. (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/P12772#Item P366, search, SPARQL

Label required in languages: de: Entities using this property should have labels in one of the following languages: de (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/P12772#Label in 'de' language, search, SPARQL

Label required in languages: en: Entities using this property should have labels in one of the following languages: en (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/P12772#Label in 'en' language, search, SPARQL

Label required in languages: nl: Entities using this property should have labels in one of the following languages: nl (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/P12772#Label in 'nl' language, search, SPARQL

Description required in languages: de: Entities using this property should have descriptions in one of the following languages: de (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/P12772#Description in 'de' language, search, SPARQL

Description required in languages: en: Entities using this property should have descriptions in one of the following languages: en (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/P12772#Description in 'en' language, search, SPARQL

Description required in languages: nl: Entities using this property should have descriptions in one of the following languages: nl (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/P12772#Description in 'nl' language, search, SPARQL

I added a lot of constraints based on Hollandsche Molen ID (P2866). Some might still be very incomplete and might some time to fill up, in that case please add constraint status (P2316) suggestion constraint (Q62026391). Multichill (talk) 16:36, 1 June 2024 (UTC)[reply]

Multichill, the constraint: "Entities with statements for ‎Milldatabase ID should also have a label at least in Dutch language." should be removed since this Database is not in Dutch. --Arnd (talk) 06:56, 2 June 2024 (UTC)[reply]

The Dutch are very active when it comes to (wind)mills. Made it a suggestion. Multichill (talk) 10:12, 2 June 2024 (UTC)[reply]

@Akoopal: can you add this ID to the windmills in the Netherlands? Maybe if you have the data, you can also add it to Mix'n'Match? Multichill (talk) 16:40, 1 June 2024 (UTC)[reply]

@Multichill I will later contact the maintainers of this database to hopefully get an export, and if so, it will be a job for openrefine. Akoopal (talk) 17:36, 1 June 2024 (UTC)[reply]

@Multichill, @Aschroet I have added this ID to 1275 dutch mills based on the Ten-bruggencatenumber and 725 belgium mills based on the molenecho's-id. I think this is what is easily doable with the data that I have. Akoopal (talk) 22:33, 7 June 2024 (UTC)[reply]

@Akoopal:, well done. Thanks a lot. Do you have any idea how we can make milldatabase.org items available for the mentioned Mix'n'Match game? I have never done this. @Multichill, maybe you know. Thanks, --Arnd (talk) 16:48, 8 June 2024 (UTC)[reply]

@Akoopal, Aschroet:, meta:Mix'n'match/Import is not that hard and I did it before. If you have the data, it's pretty straightforward to generate a csv which you can import. André, can you share the data with me? I'll see if I can put it in. Multichill (talk) 17:51, 10 June 2024 (UTC)[reply]

Done for the Netherlands at https://mix-n-match.toolforge.org/#/catalog/6341 . Multichill (talk) 20:27, 11 June 2024 (UTC)[reply]

Very cool. If we want, i can ask for a complete dump of the database. --Arnd (talk) 10:56, 12 June 2024 (UTC)[reply]

Got the whole database now. I'll make another catelog for it, but earliest next week. Multichill (talk) 21:21, 12 June 2024 (UTC)[reply]

Does it make sense, that the addition of [1] could happen in the upper definition instance of (P31), in this case Mühle Sommerfeld (Q40161059)? Reason is, that maybe every Mühle Sommerfeld (Q40161059) has source of energy (P618) wind energy (Q52664317)? Regards, Conny (talk) 12:21, 5 June 2024 (UTC)[reply]

It does. The source of power might change over time, for example when they add a electrical motor in the windmill. It also makes it explicit and easy to query. The source has the data, so easy to fill and to add a reference. Multichill (talk) 17:54, 10 June 2024 (UTC)[reply]

why has this property been given a country DE? Although the website is maintained by a german organisation, the database contains windmills worldwide. Akoopal (talk) 15:54, 11 June 2024 (UTC)[reply]

@Akoopal: you're not the first to notice, see this edit and Help:Ranking#Deprecated_rank. Multichill (talk) 19:21, 11 June 2024 (UTC)[reply]