Property talk:P4293
Documentation
identifier for a folder in the ZBW Pressemappe 20. Jahrhundert (20th century press archive)
List of violations of this constraint: Database reports/Constraint violations/P4293#Single value, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P4293#Unique value, SPARQL (every item), SPARQL (by value)
(pe|co)/[0-9]{6}|(sh|wa)/[0-9]{6},[0-9]{6}
”: value must be formatted using this pattern (PCRE syntax). (Help)List of violations of this constraint: Database reports/Constraint violations/P4293#Item P31, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P4293#Entity types
(Help)
Violations query:
SELECT ?item ?value { ?item wdt:P4293 ?value. BIND (SUBSTR(?value, 1, 2) AS ?prefix). FILTER (?prefix IN ("pe")). FILTER NOT EXISTS { ?item wdt:P31 wd:Q5. } FILTER NOT EXISTS { ?item wdt:P214 ?viaf. } FILTER NOT EXISTS { ?item wdt:P227 ?Normdatei. } FILTER NOT EXISTS { ?item wdt:P31/wdt:P279* wd:Q8436. } }
List of this constraint violations: Database reports/Complex constraint violations/P4293#Check item with `pe` prefix
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Count folder IDs by type
[edit]select (str(count(distinct ?pm20Id)) as ?idCount) ?type
where {
?wd wdt:P4293 ?pm20Id .
bind(substr(?pm20Id, 0, 3) as ?type)
}
group by ?type
order by ?type
Suggestion for inexactly matching companies / institutions
[edit]Having a look into the Mix-n-match catalogs for international and German PM20 company folders, there are several automatically suggested matches which don't match exactly the proposed Wikidata item. Just two examples from the top of the latter list:
- In [1], the PM20 folder is about Rheinisch-Westfälische Kalkwerke, existing up to 1999, which is a predecessor of the proposed item Rheinkalk (Q2147848), formed in 1999 in a merger of the former with other companies.
- In [2], the PM20 folder is about Kampnagel (a Hamburg machine plant, existing till 1981). The abandoned ensemble of buildings was transformed into the culture centre Kampnagel (Q1640333), proposed as a match by M-n-m.
Simply adding the external identier to the items would conflict with the actual definition of these items. On the other hand, just removing the proposed links would be a waste: The material in the PM20 folders could be helpful for Wikipedia authors (the according WP articles have sections about the history of the company or the building). Furthermore, when later-on an exactly matching item for the former company is created, a link could be moved to that item.
So the suggestion is to add the exernal identifier for the PM20 folder with the mapping relation type (P4390) qualifier related match (Q39894604). In a later step (after working through the M-n-m catalogs in order to identify and map all existing items), missing company items can be generated automatically from PM20 metadata (to which I have access). That should include items for all companies for which only a "related" item exists. These items will show up in the constraint violation list and/or with a specific query and can be manually resolved by inserting an appropriate link (e.g., predecessor/successor) between the Wikidata items and then removing the "related match" to the PM20 folder. Jneubert (talk) 08:53, 7 June 2018 (UTC)
- @Xaimo, Maxwan, Karlum, Cavaliere_grande: Notifying the people who are working on the PM20 company catalogs. Jneubert (talk) 08:56, 7 June 2018 (UTC)
- @Jneubert: Your proposal seems reasonable to me, that is the sort of thing we created those relation types for. ArthurPSmith (talk) 13:39, 7 June 2018 (UTC)
- After having applied that pattern for some time, another use case is: a comany in PM20, with it's founder as an item in Wikidata, derived from a Wikipedia page which covers both. To keep track of the inexact assignments, I use this query:
- -- Jneubert (talk) 05:49, 7 August 2018 (UTC)Try it!
select ?item ?itemLabel ?relation ?relationLabel ?pm20 where { ?item p:P4293 ?statement . ?statement pq:P4390 ?relation ; ps:P4293 ?pm20Id . filter(isLiteral(?pm20Id)) bind(uri(concat('http://purl.org/pressemappe20/folder/', ?pm20Id)) as ?pm20) service wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en,de" } }
I like @Jneubert: suggestion to use mapping relation type (P4390) qualifier related match (Q39894604). I can use the same for many AAT matches, where AAT has "culture" whereas WD has only "peoples" or even "language". However @Magnus Manske: is there a way to support this pattern from MnM directly? Posted as https://www.wikidata.org/wiki/Topic:Ukh1v2rq50ff3bld --Vladimir Alexiev (talk) 11:17, 10 September 2018 (UTC)
Removed country (P17) Germany (Q183) and {Germany properties}
[edit]... because the archive is not about Germany in particular, but covers multiple countries and international topics - see en:20th_Century_Press_Archives. (Pinging @Thierry_Caro:, who had added the property.) Jneubert (talk) 16:20, 17 July 2018 (UTC)
- country (P17) is used on many properties that are in the same situation. Thierry Caro (talk) 17:52, 17 July 2018 (UTC)
- I've seen examples of the property use in the template. As far as I can see, most of the properties cover specifics of Germany (politicans, athletes, railway stations, etc.), and country (P17) makes sense there. But take the id of the Animal sound archive in Berlin Tierstimmenarchiv ID (P5397) - the very first example for the property is about the Bornean orangutan (Q599672). So the relation to Germany seems to be only by seat and by history of the institution, and that is covered completely in the related item Animal Sound Archive (Q2432535) for the institution. Jneubert (talk) 18:27, 18 July 2018 (UTC)
Property scope extended
[edit]Added "as qualifier", so that the property can be used to hint from an PM20 film section ID (P11822) entry to an folder id (if one exist), which may contain additional information, e.g. the total temporal coverage. --Jneubert (talk) 18:42, 21 July 2023 (UTC)
- All Properties
- Properties with external-id-datatype
- Properties used on 10000+ items
- Properties with single value constraints
- Properties with unique value constraints
- Properties with format constraints
- Properties with scope constraints
- Properties with constraints on items using them
- Properties with entity type constraints
- Properties with complex constraints