Open main menu

Property talk:P1476



published title of a work, such as a newspaper article, a literary work, a website, or a performance work
Representsoriginal title (Q1294573), title (Q783521)
Data typeMonolingual text
Domainwork (Q386724), cross-reference (Q1302249), Supreme Commander for the Allied Powers Instruction Note (Q11242653), order (Q567696), collection (Q2668072), publication (Q732577), version, edition, or translation (Q3331189), occurrence (Q1190554), collection (Q59294612), box set (Q394970), album series (Q20671381) and item of collection or exhibition (Q18593264)
Allowed values(?i)((?!\b(<br>|<br />|<br/>|</br>)).)*(?i)((?!\b(<i>|</i>)).)*(?i)((?!\b(<em>|</em>|<strong>|</strong>|<b>|</b>)).)*(?i)((?!\b(<p>|</p>)).)*([^\[].+[^\]].|.{1,3}|)
ExampleNature (Q180445)Nature
Tracking: usageCategory:Pages using Wikidata property P1476 (Q23909058)
See alsosubtitle (P1680), official name (P1448), native label (P1705), has edition (P747), named as (P1810)
Proposal discussionProposal discussion
Current uses24,259,286
Format “[^<]*: value must be formatted using this pattern (PCRE syntax). (Help)
Exceptions are possible as rare values may exist. Known exceptions: <script>alert("!Mediengruppe Bitnik");</script> (Q43981055), <|°_°|> (Q20648570)
List of this constraint violations: Database reports/Constraint violations/P1476#Format, SPARQL, SPARQL (new)
Format “(?i)((?!\b(<br>|<br />|<br/>|</br>)).)*: value must be formatted using this pattern (PCRE syntax). (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P1476#Format, SPARQL, SPARQL (new)
Format “(?i)((?!\b(<i>|</i>)).)*: value must be formatted using this pattern (PCRE syntax). (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P1476#Format, SPARQL, SPARQL (new)
Format “(?i)((?!\b(<em>|</em>|<strong>|</strong>|<b>|</b>)).)*: value must be formatted using this pattern (PCRE syntax). (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P1476#Format, SPARQL, SPARQL (new)
Format “(?i)((?!\b(<p>|</p>)).)*: value must be formatted using this pattern (PCRE syntax). (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P1476#Format, SPARQL, SPARQL (new)
Format “([^\[].+[^\]].|.{1,3}|): value must be formatted using this pattern (PCRE syntax). (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P1476#Format, SPARQL, SPARQL (new)
Format “(?i)((?!\b(ISBN)).)*: value must be formatted using this pattern (PCRE syntax). (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P1476#Format, SPARQL, SPARQL (new)
Format “(?i)((?!\b(1[05-9]\d\d.[12]\d\d\d)).)*: value must be formatted using this pattern (PCRE syntax). (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P1476#Format, SPARQL, SPARQL (new)
Format “(?i)((?!\b(obituary|in memoriam)).)*: value must be formatted using this pattern (PCRE syntax). (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P1476#Format, SPARQL, SPARQL (new)
Format “(?i)((?!\b(ormula: see text)).)*: value must be formatted using this pattern (PCRE syntax). (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P1476#Format, SPARQL, SPARQL (new)
Format “[^$]*: value must be formatted using this pattern (PCRE syntax). (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P1476#Format, SPARQL, SPARQL (new)
Pattern ^(.+)<BR>(.+)$ will be automatically replaced to \1 \2.
Testing: TODO list

This property is being used by:

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


Any allowances for titles with no language?Edit

Is this intended to replace P357? Or can that property be used if the title has no discernible language? -Moogsi (talk) 17:37, 4 October 2014 (UTC)

For the records: P357 (P357) had been deleted (see Wikidata:Requests for deletions/Archive/2015/Properties/1#P357). So yes, this property replace P357 and yes, it can be used « if the title has no discernible language ». Cdlt, VIGNERON (talk) 14:54, 2 October 2018 (UTC)

Language part of the titleEdit

I see that now the language of the title has become part of the title, so that anybody doing a copy-and-paste is going to end up with the wrong title. Why this weird and confusing approach? Why not just have a separate field for the language? - Brya (talk) 06:04, 9 January 2015 (UTC)

@Brya: That's not true. The language is not part of the title as you can see using the API: [1]--Jobu0101 (talk) 11:49, 16 April 2015 (UTC)
Ah, what you are saying is that what my eyes see (and what presumably every user sees), they are not seeing because an API says so? Sure! - Brya (talk) 16:28, 16 April 2015 (UTC)
@Brya: I'm not talking about your eyes. I'm talking about how data is stored in Wikidata: The language is definitely not stored within the title string but separately like you originally wished. --Jobu0101 (talk) 16:55, 16 April 2015 (UTC)
Well, eyes are what I use (and so does mostly everybody) to check and correct content. If eyes were not important why put it onscreen at all? - Brya (talk) 05:30, 17 April 2015 (UTC)
I think the key is to use eyes and brain simultaneously. If title and language is printed on screen in the same line this doesn't imply that they are stored as one string. Also note that you don't enter them into the same field when you assign P1476. Finally, my API example shows that they are indeed stored separately as they should. --Jobu0101 (talk) 16:13, 22 April 2015 (UTC)
It is not possible to use eyes separately from the brain. If title and language are printed on-screen in the same line the title cannot be easily checked or corrected; and that pretty much negates the whole idea of having it on-screen. - Brya (talk) 16:24, 22 April 2015 (UTC)
@Jobu0101: It should be possible to ease the brain's work by telling the eyes that it's two different pieces of data. Any easy way to do that would be to display the language with a smaller font-size, a lighter color or a font-style itallic. Just as it is done for language fallbacks. But differently, otherwise those might be mistaken - Zorglub27 (talk) 09:36, 9 June 2015 (UTC)
Ask the designers to do so. But this does not only apply to the title property here but to all fields using Monolingual texts. --Jobu0101 (talk) 09:43, 9 June 2015 (UTC)

Original title (originally asked in Wikidata:Project chat)Edit

How do we capture the concept of the original title of a film/book/etc in Wikidata? --Jobu0101 (talk) 18:21, 14 April 2015 (UTC)

title (P1476). Sample at Q15624215. --- Jura 18:27, 14 April 2015 (UTC)
For me isn't clear how to use title (P1476). Why must be Monolingual text? Original title isn't the same in all language? (except maybe for the transliteration) --ValterVB (talk) 19:16, 14 April 2015 (UTC)
The original title is the same in all languages and it may differ from all local titles. --Jobu0101 (talk) 19:45, 14 April 2015 (UTC)
So title (P1476) is not what I'm looking for since this is used for the local titles. --Jobu0101 (talk) 19:48, 14 April 2015 (UTC)
title (P1476) is for the title of the film/book/etc. that is the subject of the article. For books each translation should have it's own item with it's own title (P1476) statement. Use has edition (P747) to link to the item for the translated edition and edition or translation of (P629) to link back. For films the same should apply. Since each dubbed versions has it's own title, voice actors, release date etc. so each dubbed version should be a separate item.
If there is a good case to be made for an edition of a film having multiple official titles then title (P1476) can have multiple values. Some of these may be in the same language (e.g. "Star Wars" and "Star Wars: A New Hope"). Use the Label for unofficial local titles which don't appear on the film/book itself. Filceolaire (talk) 00:04, 15 April 2015 (UTC)
@Filceolaire: So then I misinterpreted the concept of title (P1476). For example it was wrong what I did in Q172241. But somehow nobody cares and reverts it. How can I find items which use title (P1476)? Query: claim[1476] does not work. --Jobu0101 (talk) 06:12, 15 April 2015 (UTC)
Jobu0101 not necessarily wrong - especially if we have not yet created a separate item for the german language version of that film - provided that german title has some official status. Once upon a time the german language version of a film would appear in german cinemas. Today we get a DVD with multiple soundtracks. Is that one edition with multiple sound tracks or separate editions sharing a disc? For me it comes down to the statements we want to state. If we aren't bothered about listing the voice actors then we can probably put off creating the extra items for now - especially as we have a statement that the original language of the work is English. Filceolaire (talk) 22:15, 15 April 2015 (UTC)
@Filceolaire: I don't like this mishmash. In future Wikidata will help us more and more to generate parts of Wikipedia articles and keep the information there up to date. Therefore it is necessary to receive the original title by a simple API query. This means if we allow the title (P1476) property to have several titles we have to create a new property for the original title or (what I think is the better approach) introduce some qualifier which marks the original title as an original one. --Jobu0101 (talk) 07:03, 16 April 2015 (UTC)
Jobu0101 I agree this is a bit of a mish mash. It is further confused by the fact that in many cases the original title is not the one by which the work is generally known - see Diary of Anne Frank (Q6911). There are movies where multiple language versions were prepared and released at the same time so it is hard to say which is the 'original' language of the work. I believe this is common for video games as well. How to express all these options in statements is not obvious. Filceolaire (talk) 05:01, 18 April 2015 (UTC)
@Filceolaire: So do you have recommendations on how to proceed? --Jobu0101 (talk) 14:56, 18 April 2015 (UTC)
I will look into this discussion a bit more in the next days. Just some things I want to mention. Let's say Korean movies usually have original titles written in Hangeul, the Korean alphabet. In the Wikipedia infoboxes, the title therefore is transcripted. So, somehow a property for the tracription of the original title is needed, I guess. It will be also the same with Japanese, Chinese or Russian movies. Furthermore, till about the 1980ies, Korean movie titles were expressed in Chinese characters (Hanja). The title still was Korean, of course, however, the used characters were Chinese characters. However, in the Korean Movie Database for example, the original titles are usually written in Hangeul. Maybe this could lead to confusion. My third note is that today, nearly all Korean movies have an "international title". Means: the producers decide additionally to the original title a title for international activities. However, let's say the movie later is released in Germany, too, it maybe doesn't choose the international title but just a third localized title. Maybe these "international titles" should be recognized with a property, too, or maybe not... --Christian140 (talk) 18:18, 20 April 2015 (UTC)
@Christian140, Jobu0101: You miss part of the concept: if the Korean movie is available in Germany, this often mean that the movie is translated. In this case we have a translated version and a new item is necessary like it is the case for translated books. For the question of transcription, we have to think to use a qualifier or to consider the different types of transcriptions as language in the language menu of the monolingual datatype. Snipre (talk) 16:00, 22 April 2015 (UTC)
What if the original movie is available in Germany but only with subtitles? Do we also have to create a new item in this case? And which item should be linked to German Wikipedia? The new item or the original one? --Jobu0101 (talk) 16:48, 22 April 2015 (UTC)

I don't quite get the concept either. In case of literary and audio works I see why the separate item may be necessary, but definitely not in the case of (audio)visual works. A painting is the same even if it gets a foreign language title when on display in another country. Films are often under a title in the local language(s) when they don't even have any dialogue, are screened in the original language, are only subtitled, or are on a DVD or blu-ray with five or more different language tracks. The title corresponds to a territory (distribution market) not to a certain dub. If we want to create items for dubs, that's fine (Star Wars Episode V: The Empire Strikes Back (Q181795) has like four and a half Hungarian dubs anyway but were released on DVD only with subtitles until recently). But that is not a translation of the original work in a way the translation of a novel or a different language recording of a song is. – Máté (talk) 15:38, 4 January 2016 (UTC)

The label was changed in English to original title, and I reverted that. This property can be used for editions of a work, and each edition has a specific title, it is what it is, so the concept of "original title" is redundant or an anathema. The above conversation seems to confuse the overarching work, from the editions. The original work will have a title (an original title in a language), the editions will each have a title that may or may not replicate the original work. If something has been dubbed or has subtitles in a different language from the original, that probably should be called an edition of its own, so will have a title of its own for that edition (in my opinion).  — billinghurst sDrewth 04:22, 14 January 2016 (UTC)

Still, it should be made a lot clearer that this is for the (work's or edition's) original language title only, and not for localized titles. If not in the label (although, that is the most effective), then in the description or in comments. – Máté (talk) 06:43, 14 January 2016 (UTC)

Adding name in another languageEdit

Why is it impossible to save the name of this property?--Redaktor (talk) 22:04, 18 May 2015 (UTC)

@Redaktor: What do you mean? --Jobu0101 (talk) 09:41, 9 June 2015 (UTC)
I mean that when I try to edit the title and save the translation into Yiddish (yi) I get a bunch of error messages. --Redaktor (talk) 15:13, 9 June 2015 (UTC)
@Redaktor: Same problem. I let a message on the dev team page here. Snipre (talk) 15:38, 9 June 2015 (UTC)
I think we had the same problem before. Not sure where the report went. Someone had added new constraints (system side) and not adapted all conflicting labels/descriptions. --- Jura 15:44, 9 June 2015 (UTC)

Änderung OriginaltitelEdit

@Succu: [2] Warum? Queryzo (talk) 14:40, 21 December 2015 (UTC)

The name of this property was the generic Title from the beginning as P357 (P357). Your problem is discussed above, I think. --Succu (talk) 14:59, 21 December 2015 (UTC)
The meaning of this property seems to have changed from title of a work [3] to original title. In some language, e.g., Danish, this change has not occurred. I do not see the reason for the change. — Finn Årup Nielsen (fnielsen) (talk) 00:21, 22 April 2016 (UTC)
The contraint of a single value is a recent invention [4]. I think we need to go back to title, - not original title. — Finn Årup Nielsen (fnielsen) (talk) 00:30, 22 April 2016 (UTC)
Why isnt Label sufficent for titles? Queryzo (talk) 06:36, 22 April 2016 (UTC)
@Fnielsen: Even in its title form it was always only meant for a single value. The reason why original was not in the property name, is because that could have been misleading for editions, theatrical productions, etc. the (single!) titles of which do not necessarily coincide with the work's original title. – Máté (talk) 07:24, 22 April 2016 (UTC)
Consider A nude woman doing her hair before a mirror (Q6644913). This may never have had an original title set by the artist. At one point is was referred to at "En nøgen fra ryggen set kvinde sætter sit hår foran et spejl" by the museum. Now the museum calls it "En nøgen kvinde sætter sit hår foran et spejl" and "A nude woman doing her hair before a mirror". These titles can be referenced (as they are) with authoritative sources. — Finn Årup Nielsen (fnielsen) (talk) 07:45, 22 April 2016 (UTC)

Qualifier place of publication (P291)Edit

I've seen in Zootopia (Q15270647) that people had the clever idea to use title (P1476) with qualifier place of publication (P291) in order to represent the different titles of a film in the different countries. I think this is a good solution to the problem which was already discussed above by me over a year ago. The solution of creating a new item for each publication different from the original publication is too effortful so I think using place of publication (P291) as qualifier is a good alternative and should be suggested. Do you agree? --Jobu0101 (talk) 08:47, 28 July 2016 (UTC)

And how would you differentiate the one title which is its current scope? Because matching it with country of origin (P495) wouldn't yield the desired outcome all too often (see int'l co-productions). Probably we would manage better with a separate alternate title property which could be qualified by P291. – Máté (talk) 09:03, 28 July 2016 (UTC)
Good point. I would be okay with a new property for such non-original titles. Instead it would also possible to mark the original title with another qualifier and use value original title (Q1294573). --Jobu0101 (talk) 09:12, 28 July 2016 (UTC)
@Jobu0101, Máté: And how do you want to add the name of the people in case of dubbing ? Snipre (talk) 09:27, 28 July 2016 (UTC)
In that case you may create an individual item. But in most cases you simply want to add a title in another language. --Jobu0101 (talk) 09:30, 28 July 2016 (UTC)
Yeah, dub localizations deserve their own item, but many movies are not dubbed, yet marketed under different titles in other territories. – Máté (talk) 09:38, 28 July 2016 (UTC)
No, we can't work like that: we can't once it is an item because I add that data and once this is not an item because I don't add some data. Just try to think about query. With your proposition it is not possible to get all data with one query as data will be stored in different structures. No need of data if nobody can find it later because the storage of data is not uniform.
@Máté So the structure should be different according to the type of movie: all dubbed movies have to have their own item. Snipre (talk) 09:51, 28 July 2016 (UTC)
I don't know if there is a simple solution. The clearest would be to list titles of dubbed versions on the dub's item, and list the original version's alternate titles across territories on the main item; so yes two structures. However, (a) it is almost impossible to enforce, (b) it doesn't make queries any less complicated, (c) there are issues that complicate things. Issues like The Empires Strikes back has had three to five Hungarian dubs over the years (depending on how you're counting), under at least three somewhat different titles. Also, many movies are released both dubbed and not, often under the same foreign language title. There is a cinema in Budapest that shows films in original language, without any subtitles, yet lists them with their Hungarian title. Oftentimes a single dub is used in multiple territories (Slovakia often uses the Czech dub, and Belgium also borrows from France, and the Netherlands), and multiple language dubs may be used in certain territories. We may just assume, that the alternate title per territory and dubs' (spoken) titles are two different entities, which usually coincide, and record them twice when necessary. This would create duplication which is dreaded in databases, but it would be theoretically justifiable (they are different things, although they look the same). – Máté (talk) 10:12, 28 July 2016 (UTC)
I don't see an advantage of adding it to some other series of item that is difficult to scope.
--- Jura 10:16, 28 July 2016 (UTC)
@Máté: The question is not to know what happens in the reality, the question is to know what is done on WD. In WD depending on the level of information we want to add we have to define a structure and to keep that structure. What kind of movies do we have currently in WD ?
  • Original movies: for each movie, a new item
  • Dubbed movies: for each version (even in the same language), a new item, because we add the names of the voices. If in two different versions of dubbed movies in Hungarian the voices are changing we have to be able to distinguish the differences.
  • Subtitled movies: no consensus until now.
So at the end no need to have special properties for title. Snipre (talk) 14:17, 28 July 2016 (UTC)
@Jobu0101, Máté, Jura1: Better continue the discussion there Snipre (talk) 14:22, 28 July 2016 (UTC)
  • Your three types are a bit odd: many movies get dubbed and we include key information (such as title, available languages, release date) in the main item.
    --- Jura 14:38, 28 July 2016 (UTC)
@Jura1: It is not odd: this is just how we have to work if we want to have one data structure. How do you want to feed data in a WP infobox with different ways to store data ? Just an example: if WP:fr wants to add in its movie infobox the publication date defined as the date where the French version was available in France, how do you proceed ? With my odd classification, one line of code is enough, with any other classification you have to test if the data is store in original version of the film or in specific item created for the French version of the movie. So 2 lines of code for every property. Snipre (talk) 15:13, 28 July 2016 (UTC)
It just not the way we work. If you need two lines of code in LUA, so be it.
--- Jura 15:16, 28 July 2016 (UTC)
Jura That's the way we work for books (see Wikidata:WikiProject_Books#Bibliographic_properties) and this the way we are taking for movies (see Wikidata_talk:WikiProject_Movies). It is a pity that WikiProject_Movies didn't propose a policy for dubbed movies earlier but due to WD development with more and more detailed information added in the items, we have to adapt. And don't expect to see more contributors from WPs joining the WD community if your only reaction to their remarks is "it is not our way to work". Snipre (talk) 15:55, 28 July 2016 (UTC)
Essentially that's what you are saying yourself, without trying to figure out how things work. Really, a pity. Maybe you want to re-read Máté's post. I don't see issues about having detailed items for dubbings or DVDs in libraries, but that's just a different question.
--- Jura 16:19, 28 July 2016 (UTC)
Jura My position about one unique structured way of storing data is not my personal opinion but the position of the Wikproject Books and of some members of the Wikiproject Movies, position defined in order to simplify data extraction. So now whats is your argumention apart "It just not the way we work" ? I have no problem with other position but this should based on more solid argumentation.
I read the comment of Máté and I don't take care of what happens in some cinemas of Hungary. I take care of what happens in WD. So what happens in WD ? The trend about dubbed movies is to add specific data like the ones presented there which means that you can't mix data from several dubbed movies in the same items. So why is it a problem to create in a systematic way items for each dubbed movie ? Why do we need to create multiple claims with long list of qualifiers and special properties when you can solve the problem by separating data in different items ? Snipre (talk) 17:43, 28 July 2016 (UTC)
Simply put: alternate titles (in a foreign language or not, since many films have different English, French, Spanish, or Portuguese titles in different territories) are not attributes of dubbed or subtitled versions. Those versions have their own spoken or written titles, but these alternate titles we are talking about, are not them. They are attributes of the original version. Offtopic: please, when writing in English, do not add a space before question marks, exclamation marks or colons. I know that is the correct French way, but makes it harder for me to read your text.Máté (talk) 18:05, 28 July 2016 (UTC)
I tried an approach for Quebec titles of films. It could probably do for this too. Maybe the Q15270647-approach combined with ranks could work?
--- Jura 10:16, 28 July 2016 (UTC)

How to deal with multingual title ?Edit


I just stumble upon Gwerziou Breiz-Izel (Q20560253) whose title is « Gwerziou Breiz-Izel. Chants populaires de Basse-Bretagne », the first part being in Breton (Q12107) and the second one in French (Q150) (and almost a translation of the first part, but the first word is very specific and difficult to translate). How can I deal with that ? The only solution is can see right now is to split the title in two and to put each part separately... (which will break the single value constraint violations).

Cdlt, VIGNERON (talk) 15:56, 8 August 2016 (UTC)

Language code "mul"?
--- Jura 16:06, 8 August 2016 (UTC)
Isn't the second part better suited for subtitle (P1680) anyway? --Srittau (talk) 19:51, 8 August 2016 (UTC)
+1 Snipre (talk) 21:53, 8 August 2016 (UTC)
-1 --Succu (talk) 22:00, 8 August 2016 (UTC)
Jura1 'mul' is a solution but it's not really meningful or even useful...
Srittau maybe... maybe not... It doesn't seems quite right. Which part would be the subtitle ? the french or the breton ? For a French speaker, the breton part could be the subtitle (or more accurately a surtitle) ; for a Breton speaker, the French part could be the subtitle...
I've got other bilingual books in french and breton in the same situation...
Cdlt, VIGNERON (talk) 07:58, 9 August 2016 (UTC)
It's the applicable solution. If we would use fr or br, that would be inaccurate, incorrect or plain wrong, depending on the point of view.
--- Jura 09:01, 9 August 2016 (UTC)
@VIGNERON: I speak neither French nor Breton, so take everything I say with a big grain of salt. But looking at the way the cover is layed out here or here, I would probably model it as title/sub-title pair if it had an all-English like "Foobar: Popular songs from Basse-Bretagne". --Srittau (talk) 10:24, 9 August 2016 (UTC)

Ontology-alignment, how to associate compositions?Edit

Exact matching with other (external) ontologies is possible, but for class specialization, by statement composition:

  • ...

--Krauss (talk) 11:10, 27 September 2017 (UTC)

Language in case of simple titles like "P" or "III"Edit

What would be the correct language value in cases like III: The Ritual (Q46384970) or P (Q7121254), where the original title isn't in a specific language? --Kam Solusar (talk) 12:09, 22 December 2017 (UTC)

Please have a look at Help:Monolingual_text_languages#Special_language_codes Snipre (talk) 21:00, 22 December 2017 (UTC)

What happened to the type constraint?Edit

I was wondering why this property on Mount Everest (Q513) didn't display a constraint violation. It appears that @Snipre: removed the constraint [5]. Why is that? Should this property be used on any type of item? --- Jura 10:08, 27 November 2018 (UTC)

@Jura: If you look at the list of constraint violations, perhaps you will see cases where the constraint is not correct: edition, scholarly article,... or just read the recommandations of Wikiproject Books for the use of title for edition, and finally just have a look at help:Sources where title can be used as qualifier for some references in items defined as instance of everything but not a work. If you add constraint and just let the number of violations increasing, the constraints is useless. Snipre (talk) 20:31, 27 November 2018 (UTC)
I restored the constraint, let's see how many turn up. There seems to have been some bug, so there was no recent update of the report.
If I found the correct version, there might just have been 8 violations in 20,000 uses.
The absence of a constraint leads people to use it in places where they shouldn't, e.g. Q153. Maybe some fine-tuning is still needed. --- Jura 13:57, 28 November 2018 (UTC)
  • It took some time to get the reports to work again. It's fine now. There seem to be some 2500 violations. Other than the items currently missing any P31, I can't really see any that should have this property. Maybe the constraint should even be more restrictive. --- Jura 15:35, 8 December 2018 (UTC)

Format constraintEdit

Currently the constraint is [^<]* and has some 3160 violations. It finds things like <br/> ([6]) and <i> ([7], but many false positives. Maybe we could try more specific ones.

There are probably other things that shouldn't be in there either.

If the data was added by bot, the bots should be adjusted too.

BTW, there is a proposal for an alternate title format at Wikidata:Property_proposal/title_in_TeX --- Jura 15:35, 8 December 2018 (UTC)

Something is wrong with the regex - disallows English title "Wow"Edit

Hi there! The simple English title "Wow" now throws a format constraint warning, I'm guessing this was not the intention:

The value for title (Wow) should match “set English title in square brackets to deprecated rank and add original language title with normal rank” (regex: ^([^\[].+[^\]].|)$).

Will someone with the necessary regex-chops have a look? Moebeus (talk)

  fixed Thanks for noticing. Should only have found Q30331181, not Q27771822. --- Jura 17:40, 20 December 2018 (UTC)

single valueEdit

I removed the "single-value" constraint because the same object can have different titles in different languages. Amqui (talk) 21:43, 16 January 2019 (UTC)

but it can only have one original title, exeptions are to be defined as exception to constraint (P2303). Queryzo (talk) 12:19, 17 January 2019 (UTC)

@Amqui: I agree with you. But read Wikidata:Project chat/Archive/2019/01#single-value constraint, non-mandatory, references, state it, module... all over again.... Xaris333 (talk) 20:54, 17 January 2019 (UTC)

  • I think in the discussion we addressed all possible issues. Do we have any new ones that came up? --- Jura 14:05, 26 January 2019 (UTC)
If the one work is published at the same time in two different languages, which is often the case with official documents from bilingual or multilingual countries, then both titles are "original titles". Amqui (talk) 20:51, 27 January 2019 (UTC)
  • Nothing currently prevents you from adding this. --- Jura 21:05, 27 January 2019 (UTC)

How to use for paintings?Edit

Currently the description for this property reads "published title of a work, such as a newspaper article, a literary work, a website, or a performance work". How to read this in the context of paintings? For contemporary art, artists assign titles on a regular basis. Clear cut to use title (P1476) here. But how to deal with (predominantly older) works for which the painter didn't assign a title? In these cases art historians generally assign a descriptive title. Just scroll through this list to see some examples or have a look at Mona Lisa (Q12418). I have been holding off using this property and telling other people the same because when to use it is unclear. It doesn't even show up on the most used painting properties yet although recent imports from Commons have increased the numbers. On a scale I see two ends:

  1. Only use title if the artist assigned a title (preferable documented and sourced). Implication would be that we would remove the title statement from a lot of paintings
  2. Use title for every painting. I can run a re-import of the collections and add it to probably 200.000 paintings. But wouldn't this a bit redundant to the labels?

Or maybe somewhere in between? Either way is fine with me, just want to have clarity so we can move on with this. @Marsupium, Jarekt:. Please ping anyone else you think is interested in this. Multichill (talk) 15:21, 31 March 2019 (UTC)

I would add that if we go with option 1 create new property for artwork titles. Labels in most cases for artworks contain artwork titles, but in many cases it is a description as in Belt buckle 5-7th century-MCAH Lausanne-On display 9b (Q29946907), and with labels you can not add a reference to state where you got title from. In most cases we do not know who assigned the title. For example in painting like Portrait of a gentleman with a falcon (Q20537391) we have reference [8], which lists a Title field as "Portrait of a gentleman with a falcon". We can deduce that this title probably did not come from the painter. However in case of The Starry Night (Q45585) (referenced by MOMA), van Gogh might have come up with this title, although probably not in English, or the title is the description of the painting that other created. References do not mention who assigned it. So I would stick to option 2 and try to only add titles we found somewhere. --Jarekt (talk) 16:03, 31 March 2019 (UTC)
  • So obviously what I've put togehter some while ago under Wikidata:WikiProject Visual arts/Item structure#Titles and labels doesn't reflect a common consensus. ;) I tend to support option 2 as well, but haven't thought it through completely. If we follow this we'll probably have to get rid of the single value constraint (Q19474404) which has syntax clarification (P2916) "Non mandatory constraint. Add only title of work in its original language. Multilingual works may have several." since there isn't anything like an original language for many (later assigned) artwork titles.
    If we don't use this property then we need another one for not artist-assigned titles as Jarekt said I think. Also here some interesting input in my eyes from other ontologies: CONA Editorial Guidelines, section 3.3 Titles and Names and less interesting, but still because it's a common standard: CIDOC CRM class E35 Title. --Marsupium (talk) 21:49, 31 March 2019 (UTC), 22:02, 31 March 2019 (UTC)
  • I like option 2 with the best practice of citing the source for the title (which for our purposes will usually be the holding repository, or a catalogue of some sort). - PKM (talk) 01:06, 1 April 2019 (UTC)
I can think of different types of titles: inscribed, used by the artist, by art critics in catalogs, by the museum. There is often no single title. You can use a qualifier, for example used by (P1535)=museum (Q33506) or painter (Q1028181). --Vriullop (talk) 09:42, 1 April 2019 (UTC)
I agree with PKM and would strive for sourcing as many statements to museum or publication/catalog sources as possible. Spinster 💬 17:21, 1 April 2019 (UTC)
The combination used by (P1535) and a reference seems like a good best practice. - PKM (talk) 18:43, 1 April 2019 (UTC)

Multichill (talk) 11:28, 8 August 2014 (UTC), focus on the Netherlands Husky (talk) 11:38, 8 August 2014 (UTC) - Cool, i'd like to focus on building tools to visualise progress. Spinster (talk) 07:00, 9 August 2014 (UTC) Happy to help with manual finetuning that can't be done by bots, and anything else on the 'soft/wet' side of this project. I'm dreaming of complete artists' oeuvres on Wikidata! Rich Farmbrough (talk) Time to learn2Wikidata Jheald (talk) 12:33, 17 August 2014 (UTC) Kippelboy (talk) 07:01, 21 August 2014 (UTC) (Focus on Catalan paintings (subdivision of Spain) Mushroom (talk) 12:27, 21 August 2014 (UTC) Jane023 (talk) 09:11, 3 October 2014 (UTC) work on Dutch 17th-century paintings and landscapes of Haarlem; Most recently, the sum of all "attributed" paintings by Frans Hals, which is nearly done Missvain (talk) 18:51, 18 October 2014 (UTC) (talk) 13:27, 15 November 2014 (UTC) Zolo (talk) 14:57, 23 November 2014 (UTC) Beat Estermann (talk) 10:33, 3 December 2014 (UTC) (Focus on Swiss heritage institutions) Vladimir Alexiev (talk) 15:07, 23 January 2015 (UTC) KRLS (talk) 11:26, 11 February 2015 (UTC) (Focus on Catalan area museums) DivadH (talk) 11:35, 1 March 2015 (UTC) ,happy to help out with any questions in regards to the Europeana API, how to best query it, and/or our metadata Xcia0069 (talk) 11:49, 8 March 2015 (UTC), Work on data related to Gianlorenzo Bernini and Artemisia Gentileschi. Work at Europeana too ! Susannaanas (talk) 07:29, 9 March 2015 (UTC) Wittylama (talk) 17:29, 20 March 2015 (UTC) Fabrice Florin (talk) 02:35, 26 June 2015 (UTC) I can help in California later this year. Vaughn88 (talk) 15:58, 15 July 2015 (UTC) I can help! Raymond Ellis (talk) 19:31, 17 August 2015 (UTC) Hsarrazin (talk) 14:11, 29 August 2015 (UTC) - will give a hand with Creators and AC :) louis-garden (talk) 14:21, 31 August 2015 (UTC) for italian paintings (XIIe-XVIIe) Olivier (talk) 21:46, 8 September 2015 (UTC) Kopiersperre (talk) 11:33, 20 November 2015 (UTC) ProtoplasmaKid (talk) 03:49, 23 February 2016 (UTC) Micru (talk) 11:19, 29 February 2016 (UTC) Stuart Prior (WMUK) (talk) 11:04, 28 April 2016 (UTC) Hannolans (talk) 23:14, 22 October 2016 (UTC) Geraki (talk) 09:52, 24 October 2016 (UTC) (Focus on Greece) PatHadley (talk) 12:16, 3 January 2017 (UTC) MartinPoulter (talk) 14:54, 11 January 2017 (UTC) Working to get data from the University of Oxford (Q34433) and its component institutions shared on Wikidata. Pablísima (talk) 18:07, 8 February 2017 (UTC) Carl Ha (talk) 22:10, 9 February 2017 (UTC) Marsupium (talk) 19:44, 22 May 2017 (UTC) Mauricio V. Genta (talk) 16:15, 26 June 2017 (UTC) Shani Evenstein (talk) 10:26, 26 July 2017 (UTC) Nasty nas (talk) 07:45, 24 August 2017 (UTC) Bodhisattwa (talk) 14:28, 28 October 2017 (UTC) Joalpe (talk) 18:39, 9 November 2017 (UTC) Fuzheado (talk) 18:33, 30 November 2017 (UTC) Sarasays (talk) 20:00, 1 December 2017 (UTC) Thierry Caro (talk) 07:30, 9 December 2017 (UTC) John Samuel 18:29, 21 December 2017 (UTC) Jklamo (talk) 12:06, 31 December 2017 (UTC) Reosarevok (talk) 10:28, 15 February 2018 (UTC), focus on Estonia Ambrosia10 (talk) 19:48, 19 February 2018 (UTC) Subsublibrary (talk) 03:17, 22 February 2018 (UTC) Martingggg (talk) 07:00, 22 February 2018 (UTC), focus on Argentine and Hispanic America Kruusamägi (talk) 16:42, 13 March 2018 (UTC), focus on Estonia SIryn (talk) 10:36, 9 June 2018 (UTC) Jarekt (talk) 13:49, 7 September 2018 (UTC), focus on moving metadata from Commons to Wikidata Walkuraxx (talk) 10:00, 30 November 2018 (UTC) Omotecho (talk) 22:11, 21 January 2019 (UTC), focus on Japan GualdimG (talk) 16:19, 19 February 2019 (UTC) Léna (talk) 08:57, 4 April 2019 (UTC) Yann (talk) 09:53, 9 June 2019 (UTC) Paul Cézanne (Q35548) for a start... Abbe98 (talk) 19:25, 18 June 2019 (UTC) Daniel Mietchen (talk) 15:36, 23 July 2019 (UTC) Have been doing small things here and there — especially improving items around what is depicted on paintings — so might as well sign up.   Notified participants of WikiProject sum of all paintings

Everyone seems to be leaning towards option 2. No need to rush this so I plan to wait at least until the weekend before I do see if more people have an opinion on this. Multichill (talk) 15:54, 2 April 2019 (UTC)
  • Option 2 also, but « (preferable documented and sourced). » as qualifiers and references are what make the difference between a label and a statement. Cheers, VIGNERON (talk) 08:25, 5 April 2019 (UTC)

Ok it's weekend now. I added some title statements for works in the Metropolitan Museum of Art (Q160236) (English) and Rijksmuseum (Q190804) (Dutch and English). Adding multiple languages seems to trip a constraint single value constraint. Adding multiple titles (quite common with paintings) will also trip the constraint. I see plenty of discussion happened around this (see previous topic) and I'm not going to get involved. Currently importing paintings with Web umenia work ID (P5269). I added title to Wikidata:WikiProject sum of all paintings/Property statistics so we have a baseline and updated Wikidata:WikiProject sum of all paintings/Painting authority control properties because we'll be adding it as a constraint to properties. I'll re-run some of the import bots to add the missing titles and to have the properly sourced. Multichill (talk) 17:22, 5 April 2019 (UTC)

Ok, you wanted, titles, you got titles: Over 100.000 paintings now have a title statement (and I'm far from done importing). Full statistics at Wikidata:WikiProject sum of all paintings/Property statistics. Multichill (talk) 17:11, 8 April 2019 (UTC)
Thank you! --Marsupium (talk) 20:25, 8 April 2019 (UTC)

How to categorize the original title of an academic journal that changed names?Edit

I have a few law reviews that have changed official names since they were originally created. When I add the former title with start and end dates I still get a conflict. Is there a good way to capture original title versus a current title in this case?  – The preceding unsigned comment was added by Jdcera (talk • contribs) at 18:40, 20 May 2019‎ (UTC).

Changing constraint on TitleEdit

[The following is copied from Project Chat, where there was no opposition]

Since we now have "suggestion" constraints. I'd like to apply this to the single-value constraint on title (P1476), which specifically states that it's a non-mandatory constraint. Since this is so widely used, I want to confirm that there are no objections to adding suggestion constraint (Q62026391) as constraint status (P2316) on the single-value constraint for title (P1476). - PKM (talk) 21:51, 25 May 2019 (UTC)

@PKM: Agree! For my sake we could even delete that constraint. --Marsupium (talk) 17:41, 1 June 2019 (UTC)
+1 - PKM (talk) 20:07, 1 June 2019 (UTC)
Changed to "suggestion constraint" per no opposition. - PKM (talk) 18:34, 6 June 2019 (UTC)

New qualifiers for this property: title in HTML (P6833) and title in LaTeX (P6835)Edit

title (P1476) only takes a string (and a language code) as input.

Sometimes, titles should include formatting that renders them differently.

The two qualifiers can include that:

If you want to make use of these qualifiers, you could check if one or the other is present and then replace the value of title (P1476) with the value of the qualifier. --- Jura 09:55, 12 June 2019 (UTC)

Constraint prohibiting '[' and ']' should be deprecated or modifiedEdit

([^\[].+[^\]].|.{1,3}|) – this constraint should be deprecated. There are many titles with chemical names (such as [(1R,2S)-2-hydroxy-1-thiopropyl]phosphonate(2-) and many many others) that are perfectly fine. Or maybe this constraint should be modified to prohibit only titles with '[' as the first symbol and ']' as the last symbol in the title. Wostr (talk) 13:16, 18 June 2019 (UTC)

I'm unable to edit the title. Why?Edit

I've discovered an error in the title of Symbiodinium genomes reveal adaptive evolution of functions related to coral-dinoflagellate symbiosis (Q57139220). The first word of the article's title, Symbiodinium, is missing from the title (P1476) property. I cannot add it. I add the term, the link to publish doesn't become an active link. I have rebooted my browser, closed the application, nothing works. Trilotat (talk) 09:39, 2 August 2019 (UTC)

Seems to be a general bug that's currently affecting various properties, see Wikidata:Project chat#Unit box not appearing?. --Kam Solusar (talk) 10:40, 2 August 2019 (UTC)
I don't know how it was resolved, but I can now fix the title in that specific item. I am not, however, making any general statement about the bug (beyond my skillset). Thank you. Trilotat (talk) 18:58, 2 August 2019 (UTC)

Allow multiple title for different languageEdit

A work may be published in multiple languages and more often may have official titles in another language, especially for countries that use more than one official language, therefore, a valid constraint can be language.

Return to "P1476" page.