Property talk:P4354
Jump to navigation
Jump to search
Documentation
search formatter URL
web page search URL; URI template from which "$1" can be automatically replaced with the string to be searched for. $1 can be whatever you want.
web page search URL; URI template from which "$1" can be automatically replaced with the string to be searched for. $1 can be whatever you want.
Represents | URL format string (Q114728334), search URL (Q114767863) | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Data type | String | ||||||||||||
Domain | According to this template:
websites & web services; Wikidata external ID properties
According to statements in the property:
When possible, data should only be stored as statementsWikidata property for an identifier (Q19847637), identifier (Q853614), web service (Q193424), search engine (Q4182287), search engine (Q19541), mobile app (Q620615), service on Internet (Q1668024), application (Q166142), software (Q7397), GLAM (Q1030034) or catalogue (Q2352616) | ||||||||||||
Allowed values | According to this template:
Search URLs, with "$1" replacing the search string
According to statements in the property:
When possible, data should only be stored as statementshttps?://[^<>]+ | ||||||||||||
Example | ORCID iD (Q51044) → https://orcid.org/orcid-search/quick-search/?searchQuery=$1 Google Search (Q9366) → https://www.google.com/search?q=$1 ORCID iD (P496) → https://orcid.org/orcid-search/quick-search/?searchQuery=$1 IMDb ID (P345) → https://www.imdb.com/find?q=$1 Dapodikdasmen ID (P5884) → https://dapo.kemdikbud.go.id/api/getHasilPencarian?keyword=$1 | ||||||||||||
See also | formatter URL (P1630), online catalog URL (P8768), word lookup (P8942), general property-based URL formatter (P8183) | ||||||||||||
Lists |
| ||||||||||||
Proposal discussion | Proposal discussion | ||||||||||||
Current uses |
| ||||||||||||
Search for values |
[create Create a translatable help page (preferably in English) for this property to be included here]
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/P4354#Format, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P4354#Format, SPARQL
Allowed entity types are Wikibase item (Q29934200), Wikibase property (Q29934218): 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/P4354#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/P4354#Scope, SPARQL
Type “Wikidata property for an identifier (Q19847637), identifier (Q853614), web service (Q193424), search engine (Q4182287), search engine (Q19541), mobile app (Q620615), service on Internet (Q1668024), application (Q166142), software (Q7397), GLAM (Q1030034), catalogue (Q2352616)”: item must contain property “instance of (P31)” with classes “Wikidata property for an identifier (Q19847637), identifier (Q853614), web service (Q193424), search engine (Q4182287), search engine (Q19541), mobile app (Q620615), service on Internet (Q1668024), application (Q166142), software (Q7397), GLAM (Q1030034), catalogue (Q2352616)” 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/P4354#Type Q19847637, Q853614, Q193424, Q4182287, Q19541, Q620615, Q1668024, Q166142, Q7397, Q1030034, Q2352616, SPARQL
Required qualifier “language of work or name (P407)”: this property should be used with the listed qualifier. (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/P4354#mandatory qualifier, SPARQL
Qualifiers “title (P1476), language of work or name (P407), reason for deprecated rank (P2241), reason for preferred rank (P7452), archive URL (P1065), syntax clarification (P2916), archive date (P2960), applies to part, aspect, or form (P518), platform (P400), software version identifier (P348), edition number (P393), start time (P580), end time (P582), country (P17), applies to jurisdiction (P1001), file format (P2701), writing system (P282), retrieved (P813)”: 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/P4354#allowed qualifiers, SPARQL
Why string?
[edit]This property can't work as URL for now. --125.38.13.10 08:39, 25 March 2019 (UTC)
- A bit late, but this property is a string instead of a URL because it is only the pattern to create a URL, and doesn't represent a real location on the Internet. -wd-Ryan (Talk/Edits) 18:39, 19 October 2022 (UTC)
- @Wd-Ryan: Agreed, and the expression "formatter URL" may actually be a bit misleading, as it could be interpreted as a URL where you can obtain a formatter. I would rather have picked "URL formatter" (a formatter that is used to generate a URL), but as it's not very important to me, and there may be different opinions on the wording, I'm not going to suggest relabeling all the properties and items using these words.
- I would however recommend making search formatter URL (P4354) and other properties of the same kind sub-properties of formatter URL (P1630) instead of URL (P2699) only, to make all URL formatter properties easily located (
?property wdt:P1647* wd:P1630
). This change should not remove any implicit sub-property relations, only add to them, as formatter URL (P1630) should remain a sub-property of URL (P2699) (or maybe it shouldn't, precisely because it yields a template rather than a true URL, but in that case the same should apply to all its sub-properties as well). No objections to this recommendation (and resulting change), I hope? SM5POR (talk) 09:31, 13 November 2022 (UTC)- @SM5POR: That sounds good to me. -wd-Ryan (Talk/Edits) 16:44, 13 November 2022 (UTC)
Categories:
- All Properties
- Properties with string-datatype
- Properties used on 1000+ items
- Properties with format constraints
- Properties with entity type constraints
- Properties with scope constraints
- Properties with constraints on type
- Properties with required qualifiers constraints
- Properties with qualifiers constraints