Property talk:P1261

From Wikidata
Jump to navigation Jump to search

Documentation

Scandinavian Runic-text Database ID
database about runic inscriptions (including runestones), mainly in Sweden, but stones in all of Europe, Greenland and U.S. can be found here
DescriptionRundata (Q492230) is a database about runestones, mainly in Sweden, but stones in all of Europe, Greenland and U.S. can be found here.
Associated itemUppsala University (Q185246)
Applicable "stated in" valueRundata (Q492230)
Data typeExternal identifier
Template parametersignum in sv:Mall:Runinskriftsfakta
Domain
According to this template: Runestones
According to statements in the property:
runestone (Q815241), group of Norse runestones (Q24570142), runic inscription (Q7379880) or mask stone (Q1766565)
When possible, data should only be stored as statements
Allowed values((Öl|Ög|Sö|Sm|Vg|U|Vs|Nä|Vr|Gs|Hs|M|Ån|D|Hr|J|Lp|Ds|Bo|G|By|DR|DE|E|F|FI|FR|GR|IM|IR|IS|IT|LV|N|NL|Or|PL|RU|Sc|Sh|UA) .+|)
ExampleRök Runestone (Q472975) → Ög 136
Uppland Runic Inscription 932 (Q7899135) → U 932
Östergötlands runinskrifter ATA4905/48 (Q10727999) → Ög ATA4905/48
Sourcehttp://www.nordiska.uu.se/forskn/samnord.htm
Related to country Sweden (Q34) (See 117 others)
Lists
Proposal discussionProposal discussion
Current uses
Total3,339
Main statement3,33499.9% of uses
Qualifier50.1% of uses
Search for values
[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/P1261#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). Known exceptions: Östergötlands runinskrifter 205-206 (Q10727944)
List of violations of this constraint: Database reports/Constraint violations/P1261#Single value, SPARQL
Format “((Öl|Ög|Sö|Sm|Vg|U|Vs|Nä|Vr|Gs|Hs|M|Ån|D|Hr|J|Lp|Ds|Bo|G|By|DR|DE|E|F|FI|FR|GR|IM|IR|IS|IT|LV|N|NL|Or|PL|RU|Sc|Sh|UA) .+|): value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P1261#Format, hourly updated report, 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/P1261#Item P17, search, 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/P1261#Item P18, 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/P1261#Item P625, 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/P1261#Item P131, search, SPARQL
Conflicts with “instance of (P31): Wikimedia disambiguation page (Q4167410): this property must not be used with the listed properties and values. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1261#Conflicts with P31, hourly updated report, search, 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/P1261#Entity types
Item “Swedish Open Cultural Heritage URI (P1260): Items with this property should also have “Swedish Open Cultural Heritage URI (P1260)”. (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/P1261#Item P1260, search, SPARQL
This property is being used by:

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Q815241 constraint[edit]

Note that the {{Constraint:Item|property=P31|item=Q815241}} - constraint is most likely to restrictive. The database contains runic inscriptions, these can be on runestones but also on other surfaces (as "graffiti" on Bysantine ruins, on preserved wood etc.). /André Costa (WMSE) (talk) 14:38, 1 May 2015 (UTC)[reply]

Let's see what it does and adapt it depending on the output. --- Jura 14:39, 1 May 2015 (UTC)[reply]
"Should also have image (P18)" will also be difficult in some cases.
P387 (P387) maybe can be added! The datatype is string, so it does not have the problems the monolingual datatype has. -- Innocent bystander (talk) 08:13, 2 May 2015 (UTC)[reply]
Well, there are "must have", "likely to have" and "nice to have" constraints. The first ones can be marked "mandatory", the last ones shouldn't be added if there are too many errors. --- Jura 08:18, 2 May 2015 (UTC)[reply]
For inscriptions, Uppland Runic Inscription 932 (Q7899135) uses P438 (P438) which seems more appropriate (although that property is apparently being replaced with inscription (P1684), which is unfortunate as it requires you to define a language which doesn't seem entirely appropriate for ancient texts where language determination is largely based on interpretation).
We could use image (P18): no value for inscriptions that haven't been documented and are now considered lost (with sources and an "as of" qualifier in case the inscriptions turn up again). That would take care of many violations, although caution is warranted. Väsk (talk) 15:42, 2 May 2015 (UTC)[reply]
There is the possibility to create new language (and script) codes just for Wikidata. Maybe one or several should be requested. --- Jura 16:35, 2 May 2015 (UTC)[reply]
I wasn't aware of P438 (P438). Some stones are written (at least partly) in a kind of code, for example the stone in Rök. Do we have any property for interpretations? Many of these were done in the 19th century, so they are not always copyrighted. -- Innocent bystander (talk) 05:03, 3 May 2015 (UTC)[reply]

Can anybody explain how to use this?[edit]

E.g. in https://commons.wikimedia.org/wiki/File:Sundby_U_81_r%C3%A4ttv%C3%A4nd.jpeg how do I add U 81 to the Rundata property? @ديفيد عادل وهبة خليل 2: Macuser (talk) 22:03, 2 November 2019 (UTC)[reply]