Property talk:P6744
Jump to navigation
Jump to search
Documentation
FragDenStaat public body ID
identifier for public bodies from FragDenStaat.de
identifier for public bodies from FragDenStaat.de
[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/P6744#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/P6744#Unique value, SPARQL (every item), SPARQL (by value)
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/P6744#Format, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P6744#Format, SPARQL
Type “government organization (Q2659904), public enterprise (Q17990971), government agency (Q327333), self-regulatory organization (Q536390), educational institution (Q2385804)”: item must contain property “instance of (P31), subclass of (P279)” with classes “government organization (Q2659904), public enterprise (Q17990971), government agency (Q327333), self-regulatory organization (Q536390), educational institution (Q2385804)” 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/P6744#Type Q2659904, Q17990971, Q327333, Q536390, Q2385804, 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/P6744#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/P6744#Scope, SPARQL
"Slug" rather than "ID"
[edit]Although FragDenStaat actually has numeric IDs, we use this property to enter the slug as it appears in the URL. --Nw520 (talk) 12:19, 4 October 2020 (UTC)
New property for IDs?
[edit]Lately, numerical IDs have become part of the canonical URLs for government agencies in FragDenStaat (although they already existed before in the API). Should a new property be proposed to migrate to these numerical (and probably more stable) IDs? --Nw520 (talk) 15:05, 16 December 2021 (UTC)
- @Kristbaum: as proposer of this property: Lately, FragDenStaat has changed the format of its URLs such that it now contains both the numerical ID and the slug of government agencies. Should this property be repurposed to use the (probably more stable) numerical ID (formatter URL (P1630) wouldn't have to be changed for this)? If not, then URL match pattern (P8966) should be updated since lately contributors have been addings IDs rather than slugs to Wikidata. --Nw520 (talk) 00:22, 25 January 2022 (UTC)
- @Nw520: The numeric ID would probably be more stable in the long run, so we should change the property to prefer them. Is there anyone else that should be consulted, or should we just do it? And is there an official position of FragDenStaat on the long term stability of the slugs? – The preceding unsigned comment was added by Kristbaum (talk • contribs) at 22:26, 31. Jan. 2022 (UTC).
- @Kristbaum: Thanks for the reply! The main developer of FragDenStaat stated that the numerical IDs are to be preferred. He also mentioned that using slugs might lead to problems with stability. Therefore, I propose to:
- rename this property back to FragDenStaat public body ID Done
- update formatter URL (P1630) Done
- update URL match pattern (P8966) Done
- update property constraint (P2302)'s format constraint (Q21502404) Done
- and most importantly migrate all current slugs in Wikidata to their numerical counterparts. Done with toollabs:editgroups/b/CB/c090aa53f38
- The Mix'n'Match catalogue will also need to be updated, which I cannot take care of.
- I don't know of any other parties which need to be consulted and I highly doubt that there are. This migration is only a breaking change if your using the slugs with FragDenStaat's API. URLs of FragDenStaat work with both types of identifiers. --Nw520 (talk) 12:01, 1 February 2022 (UTC)
- @Kristbaum: Thanks for the reply! The main developer of FragDenStaat stated that the numerical IDs are to be preferred. He also mentioned that using slugs might lead to problems with stability. Therefore, I propose to:
- @Nw520: The numeric ID would probably be more stable in the long run, so we should change the property to prefer them. Is there anyone else that should be consulted, or should we just do it? And is there an official position of FragDenStaat on the long term stability of the slugs? – The preceding unsigned comment was added by Kristbaum (talk • contribs) at 22:26, 31. Jan. 2022 (UTC).
Categories:
- Germany-related properties
- All Properties
- Properties with external-id-datatype
- Properties used on 1000+ items
- Properties with single value constraints
- Properties with unique value constraints
- Properties with format constraints
- Properties with constraints on type
- Properties with entity type constraints
- Properties with scope constraints