Property talk:P1707
Latest comment: 2 years ago by Billinghurst in topic Format
DAAO ID
human identifier per Design & Art Australia Online
human identifier per Design & Art Australia Online
[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)
List of violations of this constraint: Database reports/Constraint violations/P1707#Unique value, hourly updated report, 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/P1707#Single value, SPARQL
Type “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/P1707#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/P1707#Item P106, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P1707#Item P106, search, 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/P1707#Item P21, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P1707#Item P21, search, SPARQL
Item “date of birth (P569)”: Items with this property should also have “date of birth (P569)”. (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/P1707#Item P569, SPARQL
Item “place of birth (P19)”: Items with this property should also have “place of birth (P19)”. (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/P1707#Item P19, search, 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/P1707#Format, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P1707#Format, 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/P1707#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/P1707#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.) |
| ||||||||||
| ||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||
Format
editAn id such as collection/new-england-regional-art-museum-armidale-nsw seems to be valid, but violates the current constraint — Martin (MSGJ · talk) 10:50, 11 March 2022 (UTC)
- @99of9: I think you set the current constraint. Could you take a look please? — Martin (MSGJ · talk) 10:52, 11 March 2022 (UTC)
- @MSGJ: Its reasonable to think about, but it also represents a bit of scope creep. At the moment we can safely assume all items that obey the format are the creators rather than the collectors. I take it you're not advocating for the other categories like event/work/recognition listed in the existing format violations: https://www.wikidata.org/wiki/Wikidata:Database_reports/Constraint_violations/P1707#%22Format%22_violations ? Let's also ping the proposer @billinghurst: to comment on the intent. Another option would be to propose a different property for "DAAO collection". If we do need to change the regex on this one, it would just change to "(collection\/)?[a-z\-]\d*". --99of9 (talk) 05:58, 15 March 2022 (UTC)
- @MSGJ, 99of9: It is meant to be a "human" identifier, not a collection/group identifier, as expressed in the domain component of the description. So that would seem to need a different property than what we are looking to describe. Maybe it is the description that needs to be improved to clarify that. — billinghurst sDrewth 09:59, 15 March 2022 (UTC)
- @MSGJ: Its reasonable to think about, but it also represents a bit of scope creep. At the moment we can safely assume all items that obey the format are the creators rather than the collectors. I take it you're not advocating for the other categories like event/work/recognition listed in the existing format violations: https://www.wikidata.org/wiki/Wikidata:Database_reports/Constraint_violations/P1707#%22Format%22_violations ? Let's also ping the proposer @billinghurst: to comment on the intent. Another option would be to propose a different property for "DAAO collection". If we do need to change the regex on this one, it would just change to "(collection\/)?[a-z\-]\d*". --99of9 (talk) 05:58, 15 March 2022 (UTC)