Open main menu

Wikidata talk:WikiProject Books

Marc 21 to WikidataEdit

Hi everyone. The National Library of Uruguay has around 165.000 entries of edition items that are described on the MARC 21 (Q3919686) format, Before start trying to map that standard to wd properties i wanted to know if anyone recalls if someone did it before of if there is any documentation of that process anywhere. Regards and thanks!--Zeroth (talk) 11:01, 19 January 2019 (UTC)

Notified WikiProject Books participants. --Zeroth (talk) 13:07, 20 January 2019 (UTC)
@Zeroth: There is some mapping from UNIMARC to Wikidata, described here. Kcoyle (talk) 20:20, 18 May 2019 (UTC)
Thank you @Kcoyle:!, i'll check that.--Zeroth (talk) 16:11, 19 May 2019 (UTC)

Novel used with instance of (P31) instead of genre (P136)Edit

@EncycloPetey: believes that there’s a consensus to use genres as a statement for instance of (P31) instead of genre (P136). Given that I failed to find that specific discussion, and that I haven’t bumped into anybody else doing this type of edits, I think a clarification is needed. --Andreasm háblame / just talk to me 23:32, 3 March 2019 (UTC)

Incorrect. I have never advocated the use of genres as a statement for instance of (P31). What I have advocated is the use of novel (Q8261), which is a subclass of fiction literature (Q38072107), which in turn is a subclass of literary work (Q7725634). This is also laid out clearly in the FABiO chart at Wikidata:WikiProject Books/Works, as we discussed at length, where again "novel" is listed as a subclass of "literary work". --EncycloPetey (talk) 23:53, 3 March 2019 (UTC)
I assume the confusion arises because novel (Q8261) is both a subclass of literary work (Q7725634) and instance of genre (Q483394). Although both statements are correct, the data structure would become clearer if we restrict ourselves to one of the two variants. --Pasleim (talk) 10:09, 4 March 2019 (UTC)
From WP-EN: "A novel is a relatively long work of narrative fiction, normally written in prose form, and which is typically published as a book". This definition shows the problem with the use of novel as a literary genre:
  • "a relatively long work": "long" here is a format (physical) attribute, not a conceptual one. novella (Q149537), novelette (Q472808) and short story (Q49084) differ form novel (Q8261) only by the size (measured in number of words) of the literary work, not "thematically". They all are "narrative fiction, normally written in prose".
  • "typically published as a book": not really, there are a lot of novels (for example many science fiction novels) first published as serializations in magazines, and not every serialized novel has been later published as a book. The confusion between "book" and "novel" is what lies at the heart of this discussion, and the point is that books and novels are completely separate things: not every novel is published as a book, and therefore novels are not a subset of books.
Take for example a well-known novel such as Fahrenheit 451 (Q202009). It has been classified as philosophical novel (Q2016518) and dystopian novel (Q26928598). But what about The Ones Who Walk Away from Omelas (Q7755107)? That's also a philosophical fiction, but it's not a novel (Q8261) but a short story (Q49084). So we have to create a "philosophical short story" item, ok? And then we also have to create "cyberpunk novelette", "mystery novella", "science fiction short story", "distopian novelette", etc, etc. We have now at least M x N "genres" from the combination of (fantasy, mistery, dystopia, ...) with (novel, novella, novelette, short story). It's possible to do this? Yes. Is it appropriate? It doesn't sound as a good ontology (to me at least), it does sound like we are trying to blend two classification criteria into one. --JavierCantero (talk) 10:53, 4 March 2019 (UTC)
novel (Q8261) can't be a genre: genre is about the content and not about the format. In reality, books can be described by several parameters:
  • genre: classification of the content of a book (science-fiction, fantasy, biography, ...)
  • form: classification of the text format (novel, short text, roman,...)
  • support: classification according to support structure of the text (scroll, codex, tablet, hardcover, papercover...)
  • material: classification according to the material (papyrus, parchment, paper, vellum...)
  • writing type: manuscrit, printed,
So we can have a science-fiction novel printed on a papyrus scroll, an erotic roman hand written on a parchment codex. we definitively need 5 properties to describe correctly a book. Snipre (talk) 20:11, 4 March 2019 (UTC)
In practice, only the first two are used to describe the work; the latter three describe an edition or manifestation only. A science-fiction novel will be a science-fiction novel regardless of what it is written upon or the writing type used to encode the text. Only the form and genre will be invariant among all editions, and therefore edition independent. --EncycloPetey (talk) 21:39, 4 March 2019 (UTC)
novel (Q8261) shouldn't be used as a genre, but the example value for genre (P136) in the project page says otherwise. And it seems that at least the OP also thinks that way. --JavierCantero (talk) 23:07, 4 March 2019 (UTC)
The "OP"? --EncycloPetey (talk) 23:42, 4 March 2019 (UTC)
The example mentioned is The Hours (Q2610868), which is currently identified as an instance of written work (Q47461344) change made Nov 2018, and has four different values for genre (P136): parallel novel (Q6619804), feminist novel (Q26987767), LGBT (Q17884), novel (Q8261). The last (novel) was added when this merge was done in Dec 2017. --EncycloPetey (talk) 23:49, 4 March 2019 (UTC)
(OP = "Original Post", commonly used to refer to the comment that starts a discussion thread) --JavierCantero (talk) 11:41, 5 March 2019 (UTC)
I’d take an opposite direction because forms and genre, in my humble opinion, can be totally mixed. For example « comic strip » is something caracterized as a specific form and usually a humor genre, but it’s definitely something on its own. I’d definitely use instance of (P31) to characterize xkcd as a comic strip for example, this emcompass both some kind of genre and a kind of form. This can coexist with other properties but in the end the generic classification properties are really useful to model these « blurry » situation which are, in my opinion, more like the norm than the exception. And everybody knows what a comic-strip is, so it’s useful. I’d use metaclassification to classify items such as « comic-strip », for example
< comic-strip > instance of (P31)   < form >
< comic-strip > instance of (P31)   < genre >
, and benefit the flexibility of the generic classification properties while fully maintaining precision. Which is not easy to do as these objectives may seem opposite.
It would also be possible to use constructions such as
< comic-strip > has quality (P1552)   < statements of instances in qualifiers (Q47524457)     >
form search < comic >
genre (P136)   < humor >
or stuffs like that. author  TomT0m / talk page 11:30, 14 August 2019 (UTC)
@TomT0m: Your example is a particular one and I would prefer to start to build a model based on the general case. Do we agree that a text can be classified by several characteristics, at least by genre, but other exists ? If yes, then instead of focusing on particular cases, can we define the different characteristics of a text and do we agree to create a property for each of them ? That's the basics. Snipre (talk) 11:40, 14 August 2019 (UTC)
I don’t think that’s really a fruitful approach, as this problematics is transversal to artworks in general, (forms and genre at least), so before focusing on what is specific to text it’s useful to ask ourselves « how do we classify artworks ? » (this is where the flexibility of the generic properties allow to easily capture common type of art defined by a variety of criteria that nevertheless have a name). When these broad classes are defined we can focus on what’s missing and which properties are used to define the classes (the length of a text …) . But takes items like Burlesque poetry (Q3401086). Clearly, an artwork of that type is a poem of a certain genre, we can superclass it with both. If we say that it’s an instance of Burlesque poetry (Q3401086) we already said a lot at a cheap cost. author  TomT0m / talk page 11:56, 14 August 2019 (UTC)
@TomT0m: The problem of that kind of classification is the lack of systematic: do we have an item for all types of poetry ? Do we want to create similar items for book, movie, theatre, TV serie,... ? Again, if we want to be efficient and thinking to data extraction by machine, we should be more programming oriented. Snipre (talk) 13:05, 14 August 2019 (UTC)
@Snipre: We don’t have to create all those items, that’s the beauty of the stuff. It’s enough to create two « instance of » statements to obtain exactly the same result than two statement « form + genre ». Search for all burlesque poetry ? query ?poem wdt:instance of/wdt:subclass of* <burlesque> ; ?poem wdt:instance of/wdt:subclass of* <poem>. You’ll also find the instances of « burlesque poetry ». author  TomT0m / talk page 13:23, 14 August 2019 (UTC)
@TomT0m:, of course we can put all properties into some P31 or P279, but should we?.. --Infovarius (talk) 10:14, 15 August 2019 (UTC)
@infovarius: We can't, for a start :) Datatype properties can't naturally, for example, date of birth and so on. Properties like parenthood and so on will never fit neatly either. But here, I have the feeling, backed up by a really quick google search (a quote of the page, There are a number of traditional classifications of the arts, for instance in terms of their media (stone, words, sounds, paint, etc.), their species (sculpture, literature, music, drama, ballet, etc.), or their styles or contents (tragedy, comedy, surrealism, impressionism, etc.). The ontology of works of art does not map neatly on to these classifications, however." I did not read the book) that the artwork classification is something that actually needs flexibility and is transversal to a lot of criteria. It's really a classification matter. A genre like romantic comedy (Q860626) clearly defines a subtype of film.
The genre (P136)   property should nevertheless be useful, even if we chose to not use it on artwork themselves, for example to link a music band to the kind of music it creates, for example. This avoids a total parallel explicit classification of artists and artworks. author  TomT0m / talk page 13:55, 15 August 2019 (UTC)
EDIT : the english article also says romantic comedy can also be a play. author  TomT0m / talk page 13:59, 15 August 2019 (UTC)

Invitation to join Linked Data for Libraries Wikidata Affinity Group First Meeting 2019-04-23Edit

I'm a new Wikimedian in Residence as part of the Linked Data for Production project. One of the goals of the project is understanding how libraries can contribute to and leverage Wikidata as a platform for publishing, linking, and enriching library linked data. A number of institutions that are part of the grant are working on projects involving Wikidata and we decided to start an interest group with biweekly meetings to discuss various aspects of Wikidata in support of the projects. Possible topics include Wikidata best practices, documentation, communication channels, policies, and tools.

At each meeting, myself or a guest will present some relevant material related to the topic and we’ll discuss any issues members have encountered as well as helpful resources. At the first meeting on April 23rd, we’ll talk about the purpose and goals of the group as well as the Wikidata related projects that are part of the grant.

The Affinity Group is open to anyone interested. The call details and communication channels are below.

First call details:

  • April 23, 2019 9am PST / 12noon EST / 5pm GMT / 6pm CET


Chicagohil (talk) 21:43, 22 April 2019 (UTC)

@Chicagohil: What we need from professionals is a classification system for books, if possible with a list of advantages or disadvantages of the system. The current system presented on the project page is not a global concept but the aggregation of solutions to different problems. What is missing is the relations between the different levels of the system: most of the time WD contributors focus on one item (work, edition, exemplar, manuscript,...) but never try to organize the data distribution between the different levels to avoid duplication of data or dicrepancies. In my opinion we should not have several tables, one for each level, but an unique table providing the properties to use to describe one level and the ay the data can be retrieved from the different levels. Snipre (talk) 23:36, 22 April 2019 (UTC)

Scored book reviewsEdit

Hi. I'm the Wikipedia Visiting Scholar at Northeastern University in the Women Writers Project. I'm interested in modelling pre-XX-c written works by women (novels, poems, essays, etc.), to include the reviews these works received, and whether the reviews were Positive, Neutral, or Negative. I appreciate any feedback on how to go about this. Thanks. --Rosiestep (talk) 20:42, 24 April 2019 (UTC)

Hi Rosie, I don't think there is a property for book reviews. Look at the review Der Kaiser ging ... (Q19157726) by Carl von Ossietzky. For the link to the book he reviews I've used main subject (P921). --Kolja21 (talk) 23:39, 24 April 2019 (UTC)
We have described by source (P1343), which can be used to identify the periodical or newspaper that included a review, and then qualify that with statement is subject of (P805) to add a data item containing the full bibliographic information for the particular review. --EncycloPetey (talk) 15:38, 25 April 2019 (UTC)
Sounds interesting. Can you give an example? What irritates me: statement is subject of (P805) is marked as "qualifier only". --Kolja21 (talk) 16:08, 25 April 2019 (UTC)
I've mostly seen this applied to people, such as Sophocles (Q7235). Look for the described by source (P1343) section. What happens is the primary value identifies the periodical / work in which the description (review) was printed, and the statement is subject of (P805) is used as a qualifier. The statement is subject of (P805) link then points to a data item for the article / review where all the publication details would be placed so that it can be cited.
So, if you had a review published in The Times (Q50008), then described by source (P1343) would have a value of The Times (Q50008). You would create a separate data item for the specific review article, and add it as a qualifier value using statement is subject of (P805). --EncycloPetey (talk) 20:20, 25 April 2019 (UTC)
Ok. Let's do it the same way as in the case of biographical articles. I've created an example:
--Kolja21 (talk) 22:09, 25 April 2019 (UTC)
Thanks for the quick response. This would work for how to cite the review. Part B of my conundrum is that I want to "score" the review, e.g. that it was Positive, Neutral, or Negative. Could I do that (how to deal with the issue of bias?), and if it is possible, how? Adding Maxlath (talkcontribslogs) to the conversation per suggestion by Will (Wiki Ed) (talkcontribslogs) who is helping me with the brainstorming. --Rosiestep (talk) 00:22, 26 April 2019 (UTC)
hi! for the link between a review item and a work, in absence of a dedicated "review of" property, I guess main subject (P921) is the way to go: it's already in use here and there for reviews. As for the score, we might lack an adapted property: we already got review score (P444), but it seems that it is used on the reviewed works to indicate a score and then add the review source as a qualifier with review score by (P447). -- Maxlath (talk) 08:29, 26 April 2019 (UTC)
@Kolja21: You can't use instance of (P31) book (Q571), because "book" / "Buch" is a nonspecific label. It could refer to a work, a specific physical copy, or anything in between. Use literary work (Q7725634) or one of its subclasses. --EncycloPetey (talk) 01:00, 26 April 2019 (UTC)
@Maxlath:, @Rosiestep: Is there a way to capture the sentiment of a review if it's not numerically-based? A review inherently contains a judgement on a work, but without a numerical evaluation system, I can't think of a non-subjective way to evaluate the conclusion of a review. This project sounds so compelling, but I don't want it to fall into original research. I would be in favor of creating a "review of" property! Will (Wiki Ed) (talk) 17:56, 29 April 2019 (UTC)
+1. I would support a "review of" property. --Kolja21 (talk) 18:01, 29 April 2019 (UTC)
I’d support this too. There are more reviews wth the subject book as “main subject” than the query above captures - some are P31=“scholarly article” with genre=book review. - PKM (talk) 01:47, 30 April 2019 (UTC)
Hi everyone - @Rosiestep: just proposed the "review of" property. Feel free to make a comment here on the property proposal page. Will (Wiki Ed) (talk) 22:04, 2 May 2019 (UTC)
Thanks, everyone, for your comments here and if you choose to make them on the proposed "review of" property. If all of this goes forward, it'll be a pretty big project for me to undertake. BTW, does anyone know if/how the Women Writers in Review API can be transformed into Wikidata? --Rosiestep (talk) 22:58, 2 May 2019 (UTC)

Key wordsEdit

Can I use main subject (P921) for key words? Key words are few words, which characterize the content of a book or an article (e.g. Jaromír Jágr - interview - hockey - NHL). Juandev (talk) 07:14, 25 April 2019 (UTC)

Imho yes. --Kolja21 (talk) 15:33, 25 April 2019 (UTC)


Do we have any property, which would represent this? rubric (Q1335351) For example in the newspapers, some articles are under a special name, called sometimes rubric.--Juandev (talk) 19:21, 25 April 2019 (UTC)

Not sure what you're seeking to represent. I've never seen a newspaper that printed a section in red ink. Normally, I see this only in printed copies of the New Testament. --EncycloPetey (talk) 20:16, 25 April 2019 (UTC)

So, lets not talk abour the rubric. Lets talk about something, I dont know, how it is officially called in English. And lets go into the example: the magazine is called Forbes, the XY is called Tech - the article is called "New Tesla is coming". I can set published in (P1433) = Forbes, but how can I indicate "New Tesla is coming" article is a part of XY Tech?--Juandev (talk) 11:10, 26 April 2019 (UTC)

We might create a Wikidata item for “XY Tech” with <instance of>column (Q267628), and then use <published in> Forbes, <part of> “XY Tech”. I’m not sure about <part of> for an article in a recurring column. What do others think? Do we need a new property for this? That might be the cleanest solution. - PKM (talk) 04:30, 27 April 2019 (UTC)

The problem is, we in Czech use for this the term rubric, but there is no Czech description for rubric (Q1335351) and if I look to w:en:rubric it does not use that sence either, but Czech w:cs:rubrika does: and it says rubric is a section in the magazine or newspaper. So I wonder, weather the closest way of the Czech "rubrika" is "section" in English.

So looking for properties which include the term section, I came to section, verse, paragraph, or clause (P958), which may stay for that.

E.g. "New Tesla is coming"

Could it work like that? Juandev (talk) 08:48, 27 April 2019 (UTC)

Have you asked at Wikidata:WikiProject Periodicals? This seems like a question better suited to the works they are working with than it does with books. --EncycloPetey (talk) 17:55, 27 April 2019 (UTC)

Oh, thx, I havent been aware of this project. --Juandev (talk) 20:29, 27 April 2019 (UTC)

How does Has Part interact with the work/edition distinction?Edit

The project page mentions has part (P527), but completely fails to clarify whether this property is supposed to be used on the work item or the edition item. How do I connect the various preprinted monographs of Histoire des Plantes (Q5898798) to it (e.g. Histoire des plantes. Monographie des Renonculacées (Q51488450), which is the first chapter in volume 1 of that work)?

Am I going to have to make a work/version separation for each of these preprint (which, I would like to emphasize, do not otherwise have other versions independent of the greater work)? I would honeslty find that preporsterous and give up ever continuing my work with Taxonomic literature : a selective guide to botanical publications and collections with dates, commentaries and types (Q56649865)-indexed material. Circeus (talk) 06:44, 29 April 2019 (UTC)

Modeling the two editions of Taxonomic literature (Q56683530) here is an interesting case. But I don't think this enhancement for TL2 is correct. --Succu (talk) 19:00, 29 April 2019 (UTC)
I was actually referring to my going through the works in it to add Taxonomic Literature 2 number (P5878) and general enhancement and fixes. Even if one chooses to treat the TL-2 supplement as a separate work (I personally firmly believe both options are defensible, but obviously leans toward treating them as not separate), modelling them is nowhere as complex as Histoire des Plantes (Q5898798), where the work has these monographs (prepublished, but reproducing the larger work's pagination) and a volumation (Not to mention an english translation—The natural history of plants (Q51508335)—whose volumation is entirely different!). Circeus (talk) 19:18, 29 April 2019 (UTC)
BHL has only a subset of the 13 volumns: A temporary solution… --Succu (talk)
Beg your pardon...
Mind you, that doesn't answer my question about how I'm supposed to properly interconnect the ca. 50 monograph preprints, all of which have items on Wikidata (primarily because they are also found on BHL via Biblioteca Digital Real Jardin Botanico). Circeus (talk) 20:35, 29 April 2019 (UTC)
Am I'm right you want to model this TL2 entry? --Succu (talk) 21:03, 29 April 2019 (UTC)
What's the relationship between Histoire des plantes (Q51398585) and Histoire des Plantes (Q5898798)? --Succu (talk) 21:32, 29 April 2019 (UTC)
Homonymous book by Louis Figuier (TL-2 number 34.454) with no connection aside from sharing the same title and illustrator. Circeus (talk) 06:48, 30 April 2019 (UTC)
I used “has part” on the edition, not the work, with Berg Encyclopedia of World Dress and Fashion (Q55816150). - PKM (talk) 02:00, 30 April 2019 (UTC)

More broadly: should multivolume work always have volumes as separate part?Edit

It seems that the main reason we see multivolume work with separate volume items is 99% of the time that these volumes were indexed separately in BHL. And by this I mean most such instances are bot-imports for items that were later combined under a single BHL bibliography id or are separate solely because they are external links (e.g. the various volumes of Dictionnaire de Botanique (Q5805676) which BHL does not host would be under a single BHL bibbliography ID if it did). A related side effects is duplicates caused by the Biblioteca Real that have otherwise no business existing such as Astragalogia, nempe astragali, biserrulae et oxytropidis :nec non phacae, colutae et lessertiae historia iconibus illustrata (Q51444464) and Astragalogia (Q51444463), indubitably two copies of the same edition of the same book, but merging them would cause issues with values of BHL bibliography ID (P4327).

In general, it seems to me that volumation is a bibliographic detail of the relevant edition that pretty much only becomes relevant when the item is used as a reference. In practice, there is no difference between using a volume that is a separate item or a version/edition/translation item + volume (P478). Indeed, we do that for periodicals, and why wouldn't we? We wouldn't consider it logical to have separate items for volumes of a periodical. When we do have them, it is for the same reason we do volumes of a multivolume work: they are bot-generated.

Really, the only reason we don't do this is that there no string-data version of applies to part (P518). With an "applies to volume" property (heck, series ordinal (P1545) could handle it if it didn't clash occasionally or need to handle named instead of numbered volumes), the only property that IMO genuinely causes issue for Taxonomic literature : a selective guide to botanical publications and collections with dates, commentaries and types (Q56649865) (i.e. ISBN-10 (P957)) could be neatly treated under a single item and eliminate the need for volume items entirely (this could cover all other properties that vary across the work just the same). Circeus (talk) 12:41, 30 April 2019 (UTC)

@Circeus: If you look at Wikidata:WikiProject_BHL/Statistics:Titles#Titles_--_IDs, you can see we have 58,938 Internet Archive IDs for only 53,989 works. In most cases that already exactly corresponds to what you're describing, a single item for a multivolume work edition, with multiple Internet Archive IDs, a different one for each volume. So in very many cases, including BHL works, we already do pull all the volumes together under a single item, despite there being different links to sites to read them.
That's also what I am doing for books from the British Library: See Wikidata:WikiProject_BL19C/Statistics#Titles_--_statements and its different item and statement counts for full work available at (P953).
I don't see a need for a new "applies to volume" property -- The existing volume (P478) can and indeed already is fulfilling this role when used as a qualifier. (And is string-valued, so can deal with non-numerical parts).
In fact here is a query counting how many times volume (P478) is being used as a qualifier, and on what properties, showing heavy use on Internet Archive ID (P724), full work available at (P953), publication date (P577), scanned file on Wikimedia Commons (P996), Google Books ID (P675) to distinguish different values for different volumes. Jheald (talk) 14:23, 30 April 2019 (UTC)
Part of my thought was predicated on the presumption that volume (P478) asked for a numeric value. I'm glad to be wrong in that. I will have to start merging items, though in some cases it gets really hairy (I've stumbled across one particular multivolume work with the same volume having 3 different Internet Archive scan, and even if BHL merges the 4 bibliographies, this duplicate scans remain a likely constraint violation). Circeus (talk) 14:42, 30 April 2019 (UTC)
@Circeus: I don't think volume items have to be merged into the item for the edition, if it is more convenient to treat them separately. In some cases, also, it may be more appropriate to treat the overall entity as a series of creative works (Q7725310) -- often the line can be a bit grey. The important thing, I think, is that in the converse direction there is definitely no requirement to split a multi-volume book into separate items for each volume. Jheald (talk) 14:52, 30 April 2019 (UTC)
I prefer to treat volumes as separate items when each volume has its own subtitle and when each volume has a different editor or author. - PKM (talk) 01:59, 8 May 2019 (UTC)
Also for many dictionaries I've dealt with so far the volumes have different publication date (P577). I prefer separate items as well, but don't always create them tbh because it's more work. --Marsupium (talk) 00:19, 11 May 2019 (UTC)

Connecting Wikisource related pages on Commons to WikidataEdit

Cross posting with Wikidata talk:Wikisource:

Commons has 779 thousand pages calling Book infobox template, mostly used by files used by Wikisource projects. We have over 2 thousand templates in c:Category:Book templates, which are mostly used for books that store each page in a separate file and great many PDF and DjVu files storing multiple pages. Very few of those books, are connected to Wikidata in any way: few sitelinks from Wikidata book items to Commons categories and very few Book templates with "wikidata" parameters linking them to Wikidata. Lately, I was working on rewriting Book template to use Lua code c:Module:Artwork, already used by Artwork and Photograph templates. The new code will be able to utilize data from Wikidata if "wikidata" parameter is provided to the template. I am not done testing it yet, but the new version can be accessed through Book/sandbox if anybody wants to try it. Also it would be great if there was some way to add "wikidata" parameters to Book templates and individual book files, as most wikisource entries are already connected. --Jarekt (talk) 20:28, 6 May 2019 (UTC)

@Jarekt: Naming your lua box Book is perhaps not the best idea: since the beginning of WD we are struggling with that term which mixes 3 concepts: work, edition and exemplar. I assume that in more cases, these boxes refer to editions and some to particular exemplars. It can be a good idea to separate these 2 cases using different boxes. Snipre (talk) 21:26, 6 May 2019 (UTC)
Snipre, I am not creating any new names. Book was created over a decade ago, and I am updating it so if connected to wikidata item it can use metadata stored there. If it is not connected (great majority at this point) than the template will work the same way as the original. --Jarekt (talk) 02:19, 7 May 2019 (UTC)
The problem is that the template "Book" might be used on Commons in a category for a WORK, or in a category for an EDITION, or in a category for an EXEMPLAR. Sometimes the category on Commons mixes two or three of these in a single category. Until Commons disentangles these three concepts from "Book", there is little that Wikidata can do. --EncycloPetey (talk) 00:17, 8 May 2019 (UTC)
I would not expect Commons users to understand the distinctions wikidata makes between works, editions, and exemplars.
@Jarekt: this looks like a rich and overlooked source. I’ll take a look at the sandbox. - PKM (talk) 01:37, 8 May 2019 (UTC)
Book is used to describe physical scans and they all have (or should have) edition numbers etc., so majority should be linked to EDITION items. Some may be unique manuscripts, and those should be linked to items for tat unique book (EXEMPLAR?). Categories for books on Commons are often underdeveloped, bordering on nonexisting, so I would not be using then to guide you, and they also can be easily changed. --Jarekt (talk) 02:23, 8 May 2019 (UTC)
@Jarekt: I understood your point, but even with an unique infobox, we can generate different looks depending on the information entered in the infobox. This could be a way to distinguish the infobox in function of the topic but using the same template. Snipre (talk) 09:35, 8 May 2019 (UTC)
The Book/sandbox already displays instance of (P31) property. I can highlight differences between work, edition and exemplar type items, or just group them to separate categories so it is easier to inspect them. I am doing something similar for artworks as I try to detect cases when people linked artworks to items for authors or subjects. --Jarekt (talk) 12:39, 8 May 2019 (UTC)
+1 for getting them into dedicated maintenance categories. Here, we have the same problem as for art prints and a similar problem to that with groups or series of artworks. Institution/collection data e.g. should in most cases only be in exemplar items.
It could be useful to put the most special or lowest level Wikidata item available as the |wikidata= parameter value on Commons, fetch information not in that item from higher items which can be an edition and a work item. If Commons holds information on a "book" in a lower level than the Wikidata item for the lowest level new items for lower levels should be created if we consider them to be notable enough. Otherwise that information should live on Commons. --Marsupium (talk) 00:46, 11 May 2019 (UTC)

New IDs mostly about Italian authorsEdit

Hi y'all. We have discussed with User:Epìdosis about some new IDs for book authors availabe on the publisher sites, mostly Italian. He made this accurate list:

I prefer to ask you first and not the Italy project in this case. What do you think? Also, is anyone interested in some semi-automated import? That's not really my cup of tea, so far I mostly help with manual updates and uploads during literacy events.--Alexmar983 (talk) 08:59, 9 May 2019 (UTC)

Just a little addition: one already exists, Adelphi author ID (P5859), and I have completely matched it. --Epìdosis 09:02, 9 May 2019 (UTC)
Good.--Alexmar983 (talk) 09:54, 9 May 2019 (UTC)
FYI if there is no opposition unless I have some doubts while scrolling their website, I will propose them one by one in alphabethical order.--Alexmar983 (talk) 09:55, 9 May 2019 (UTC)
@Alexmar983: What is the interest of adding so many new ids ? Can't we cover these authors with more general IDs ? My problem with your proposition is the fact that authors are not strongly connected to publishers. Publisher information are more related to editions and we can in any case establish the link between publishers and author through the editions items. I am not strongly opposed but I find these new properties useless. Snipre (talk) 14:44, 9 May 2019 (UTC)
I concur with Snipre: What is to be gained from these IDs? Do they add any value to Wikidata? --EncycloPetey (talk) 14:56, 9 May 2019 (UTC)
All these IDs contain (with few exceptions) some biographical information about the author (date of birth, but tipically also something else, e.g. the academic position or the alma mater, which are usually absent in more general IDs) and can also be useful for notability. --Epìdosis 17:16, 9 May 2019 (UTC)
(conflicted)They add the same value of any other ID. Acutally even more because they contain small biogrpahies so they can be used as effective sources for specific information. These are the main editors in italy, they are very accurate, reliable and they cover very well almost all the authors when combined. I am not understanding the part of the connection to publishers, but if there is a guideline that states a specific threshold for quality please let me know. So far, they look to me IDs like the others.--Alexmar983 (talk) 17:19, 9 May 2019 (UTC)
Not every ID is of equal value. Library databases are usually NPOV, presenting facts. The "biographies" that I've looked at from these Italian publishers look to be mostly promotional, and very POV. The purpose of these biographies is not to present facts, but to sell books. --EncycloPetey (talk) 17:55, 9 May 2019 (UTC)
They are not promotional. We are both expert users and we checked before proposing them, we did not notice any POV (not even very POV). Show an example please. Also, please show a guidiline according to which I can calibrate the different values of these IDs. As far as i can see they are reliable descriptions produced by established publishers, and they can be use as source... even in itwikipedia, one of the most strict regarding notability and quality source, they are considered reliable.--Alexmar983 (talk) 18:07, 9 May 2019 (UTC)
@Alexmar983, Epìdosis: The quality of the data is very different:
one example: no information
one example: no information
If I recognize that some information can be helpful, it is far away from more general database and perhaps less stable as commercial sites. Again I am not strongly oppose to the creation of new properties but if you really want to get some support better indicate the advantages of the related databases. For me the data found in these databases is too variable in term of quality (no systematic, raw text,...).
But finally you don't answer my first question: aren't all these authors already present in large databases which are authority in the field of litterature ? You can start the property proposals but don't be surprise if the support is low. Snipre (talk) 20:57, 9 May 2019 (UTC)
Snipre actually I reply at a certain point asking to show me a guideline that states how to calibrate the different values of IDs here. In my mind, this includes also to show me how guidline defines how superposition is a important aspect for an ID and how you would define it. Having a superposition with previous databases is not a problem for a new database, considering also there is no way in many cases to calculate it before importing it nd they often evolve (but there are tools we use to evaluate after the import and is sometimes even 90%-95%, and I don't recall any suggestion for removal in those cases). it's "emotional" more than factual. I could understand for very small sets that it's not worth the effort if they are mostly included in a big one, but these are quite big. How can you evaluate as critical something that you cannot objectively estimate? The point in my experience from a practical point of view is not if two databases are superposing (good database always superimpose on the long term, that's in a way a proof of their quality because the converge and expand) but if they are independent. Everything on scopus is basically on google scholar, to cite one example. So I don't expect the support to be low because of such aspect, many other users will understand this is not defined and could be applied to everything. If not, this is not a problem of the databases but the fact that there is a lack of a general perspective. That's why I use the verb "calibrate" and ask for a guideline. if I had proposed them one by one (so what occurs with many other properties in other fields), it should have been fine. I see them all together and I see no difference with many other groups of IDs when you group together, there is no difference in the fact that they come from two people or from random users over two years. That's why I used the verb "calibrate". we really need a zero of the scale here.
Your examples show empty data for very famous authors, we did not request these databases for such profiles but for the less common authors, relevant people whose information are however more scattered on the internet, a case where is very crucial to have clear verified information so we can reference other key metadata of their item in an elegant way. We never even opened these hgher profiles because that's not the goal in ou workflow. You can left those unimported and the database still will fulfill its goal. BTW how much time did it take to you to find those? We can still skip Bompiani.--Alexmar983 (talk) 21:13, 9 May 2019 (UTC)

BTW, IMHO the best is probably the Mondadori ID. It contains more than 2000 summaries, I have not found one yet and with missing text and they contain useful information for referencing.--Alexmar983 (talk) 23:23, 9 May 2019 (UTC)

@Alexmar983: You ask for guidelines but why do we use a process like the property proposal if we have guidelines ? If the creation of a property was just a question of filling some criteria, then no need of the current process of presentation and evaluation.
Your attitude indicates a lack of understanding about what happens here in WD: we can access to hunderds of data sources, but the goal is not to connect everything together but to share knowledge. So for this purpose, it is correct to focus first on the main data sources.
If you want to be successful in your property proposal, you have to have a better selling spirit than what you show until now. I asked about the advantages of your databases, you mentioned data about biography, I just checked 6-8 names in one database and I found 2 completely empty so I assume 20% of useless entries. Ok, please show me I am wrong: execute a kind of query on your databases to show how much entries are empty, or provide other facts like most of the authors in those databases are not present in others databases, give number, type of data, structure, authority of the database,... I am honest: your databases are not sexy for a datascraper like me. If you don't like my opinion, just go away to find another contributor who will buy your poor show. Or directly go tho property proposal and start the process, but at the end, don't come back and complain about poor favorable support: we have other things to do than performing a deep analysis for potential interest on each proposal. You do the proposal, do your job until the end. Snipre (talk) 23:49, 9 May 2019 (UTC)
(confl.)Snipre I understand wikidata they are aspects of wikidata which you are not interested. BTW whatever you think about me, fine. If you would like to change opinion, feel free to contact me. Just one thing: I am not here to sell anything because this is precisely the social dynamics that produce poor databases and poor knowledge of their dynamics, very fragile working environment and disfunctional communities and I want nothing to do with that. I prefer to be disliked or misunderstaood than encouraging them at any level. Wikidata does not stop at getting one thing you want done, that's a very poor vision and I am glad i don't have it, it's a good sign I get this much more than you give me credit. --Alexmar983 (talk) 01:01, 10 May 2019 (UTC)
I had a similar experience as Snipre when I selected several random links at Rizzoli (the only publisher I've heard of). I found two biographies that were empty, only one with dates, and a couple of errors (such as the same book listed under two different authors). The overall impression is that their data is poor. I also question the long-term stability of such data. --EncycloPetey (talk) 00:29, 10 May 2019 (UTC)
if you have time, please cite a "promotional, and very POV" one. that sentence was very strong, it really made me curious. About the rest, as I said myself some are empty, and I pointed out that in such database they are those of very important writers, not the ones of the "less important" writers, the ones we need in the workflow to create more robust items. Some items on wikidata are already linked to databases that contains less information for one entry than another and this was never an issue per se. We can stretch an aspect that we globally ingore in another case, like the superposition cited above, but in the end the question is if they are reliable (they are, they are empty not wrong), their presence increases the quality of the data. You can simply give the precedence to the ones that have no empty descriptions so far 8like Mondadori) and wait for the others more years, and you can still get a good improvement of enough items of writers for the moment. Improvement that we don't get with other databases. VIAF ID are very minimal, they are the only ones we can get, while the BNCF IDs (the National Libraries) are far from complete, without the presence of the main private publishers it's complicated to cover Italian writers.--Alexmar983 (talk) 01:15, 10 May 2019 (UTC)

contemporary constraintEdit

Please comment at Property_talk:P50#contemporary_constraint. This affects many, many editions of books. --EncycloPetey (talk) 03:03, 18 May 2019 (UTC)

Work vs editionEdit

Please help me to understand. If an original work (item A) can have different translations (say, items B/C) then we can consider A as a piece of information (sujet, author, date of creation) independent of language, can't we? Original publication of the work (first, in a language of creation) should have its own item which would contain language of work or name (P407). So I conclude that A should not have language of work or name (P407) and title (P1476). So for example in The Family of the Vourdalak (Q1212326) we should extract all notions about French in a separate item shouldn't we? --Infovarius (talk) 08:08, 3 July 2019 (UTC)

@Infovarius: Your model could work if you are able to track all editions/translations in order to find the first original edition.
To be able to know in which language the first edition (or event the first draft) of a work was written, you need to find the corresponding edition item. How do you want to do that ?
The edition number only allows you to determine the serie of editions by the same publisher. If several publishers in the original language print a work, then you will have several edition number = 1. Same for translation, for each translation and each different publisher publishing it, there is a first edition. So as you have several edition number =1 for the same work you are not able to identify the original edition by that way. The only way is to use the publication date. But then you need to be sure that all editions and especially the original edition has its item. For some reason, a contributor can only create an item about the work and not the corresponding first edition item. In that case how can you apply your model ?
Just an example: for reference reason, I want to add an item about an edition of English work translated in French: I create the item for the translated edition and another one for the work. I don't need the original edition in the original language so I won't spend time to look for the information and for the creation of the corresponding item. By doing that, your model will assume that the language of the mentioned work is French and not English because the only existing edition present in WD is a translated edition. Snipre (talk) 00:14, 4 July 2019 (UTC)

How to model manuscripts, books and editionsEdit

Hi everyone,

I am working in the item Le Canarien: crónicas francesas de la conquista de Canarias (Q65600504). It is a work (printed book) in which its two authors translated, analyzed and commented the original manuscript, Le Canarien (Q1478385). The first time I thought in how to work with these items and how to model them was: the manuscript, which has a book in which it was translated and this book has an edition, each one with its own Wikidata item. However, I a bit confused. I read about the manuscript properties but I admit you it didn't clarify me a lot.

I still have the next doubt: should I create an item for the book and for the edition? Or, should the book being considered itself as a edition of the manuscript? I am going to leave the items without edit them until I received an answer of you, to not work in vain nor mess up a lot the data.

Thanks in advance for your attention!

Regards, Ivanhercaz (Talk) 00:34, 17 July 2019 (UTC)

@Ivanhercaz: You need an item for the work, one item for the printed edition and one item for the manuscript
Le Canarien: crónicas francesas de la conquista de Canarias (Q65600504) is the printed edition of the work defined by Le Canarien (Q1478385)
An additional item is necessary to described one of the two manuscripts. If you create that new item, you have to add the following properties : instance of manuscript and exemplar of Le Canarien (Q1478385).
Simple advice: never use the term book when describing your problem in WD. Book can be the work, the edition of the exemplar depending on the point of view. Snipre (talk) 12:41, 17 July 2019 (UTC)
To avoid mistake I created two items, one for each existing manuscript: codex Montruffet (Q65617317) and codex Egerton 2709 (Q65617336). Snipre (talk) 13:01, 17 July 2019 (UTC)
@Snipre: Thank you very much for the explanation! And for the creation of the items too. I am going to make my own scheme to keep this in mind for the next time in which I need to address a similar situation. Regards, Ivanhercaz (Talk) 16:47, 19 July 2019 (UTC)

Tool for adding works/versions from OCLC/Google BooksEdit

Is there any tool/script to easily create works/versions from an OCLC/Google Books link? This would help a lot with the tedious process of adding items for references. Thanks, Calliopejen1 (talk) 20:02, 17 July 2019 (UTC)

@Calliopejen1: Look at User:MichaelSchoenitzer/CiteTool.js or citoid. Snipre (talk) 05:15, 18 July 2019 (UTC)
@Calliopejen1: CiteTool.js will create a fully-populated reference when you use the OCLC or Google books link as the "reference URL". It does not (as far as I know) actually create items for the work or edition - but I have faith that at some point in the future a bot will be developed that will turn these references into items.
  • There is an active project to implement Citoid for Wikidata. If you're interested in following the development effort, here's the Phabricator link. I believe this will handle references/citations; I don't know that it will create items for books/editions.
  • If you already use Zotero to keep track of your references, then you might also look at Wikidata:Zotero. It creates QuickStatements input to create an edition-level item. It's frustrating to me in a number of ways. It uses P31=Q571 ('book', the old recommendation, rather than 'version/edition'), and it doesn't look anything up, so you don't get the QIDs for the author (if they exist), publisher, place of publication, distribution format, etc. I seem to recall you have to change "english:" to "en:" as well.
  • After experimenting with extremely complex spreadsheets to create work/edition pairs, I have settled on the following process as easier:
    • Create the "work" item using the Cradle book (work) form (yes, you still have to copy/paste a lot of stuff)
    • Duplicate the work item to make the edition, using the "Duplicate this item" tool (script added to your common.js - see User:Magnus_Manske/duplicate_item.js). Add a description, change the P31 to "version/edition", remove the main subject, add publisher, place of publication, etc., and link the work and edition to each other. - PKM (talk) 20:55, 18 July 2019 (UTC)
@PKM, Snipre: Thanks for all this. A bummer that it's such a complicated process! I guess an opportunity for some volunteer coder later on... Calliopejen1 (talk) 21:38, 18 July 2019 (UTC)

Idea of cleanupEdit


We decided not to use book (Q571) a long time ago but there still is a lot of item using it (68238 right now according to this query Shouldn't we replace this value by written work (Q47461344)? Maybe not in all items (we may need to do some double-checking before) but at least most of them I guess.

Viswaprabha (talk)
Maximilianklein (talk)
Jane023 (talk) 08:21, 30 May 2013 (UTC)
Alexander Doria (talk)
Ruud 23:15, 24 June 2013 (UTC)
Jayanta Nath
Yann (talk)
John Vandenberg (talk) 09:14, 30 November 2013 (UTC)
Danmichaelo (talk) 19:30, 16 February 2014 (UTC)
Ravi (talk)
Mvolz (talk) 08:21, 20 July 2014 (UTC)
Hsarrazin (talk) 07:56, 9 August 2014 (UTC)
PKM (talk) 19:58, 10 October 2014 (UTC)
Revi 16:54, 29 November 2014 (UTC)
Giftzwerg 88 (talk) 23:36, 1 January 2015 (UTC)
Almondega (talk) 00:17, 5 August 2015 (UTC)
Jura to help sort out issues with other projects
Skim (talk) 13:52, 24 June 2016 (UTC)
Marchitelli (talk) 12:29, 5 August 2016 (UTC)
BrillLyle (talk) 15:33, 26 August 2016 (UTC)
Alexmar983 (talk) 23:53, 28 August 2016 (UTC)
Finn Årup Nielsen (fnielsen) (talk) 10:44, 29 August 2016 (UTC)
Chiara (talk) 14:15, 29 August 2016 (UTC)
Thibaut120094 (talk) 20:31, 14 September 2016 (UTC)
Ivanhercaz | Discusión   15:30, 31 October 2016 (UTC)
YULdigitalpreservation (talk) 17:35, 10 November 2016 (UTC)
PatHadley (talk) 21:51, 15 December 2016 (UTC)
Erica (ohmyerica) (talk) 19:26, 1 January 2017 (UTC)
Mauricio V. Genta (talk) 05:38, 12 March 2017 (UTC)
Sam Wilson 09:24, 24 May 2017 (UTC)
Sic19 (talk) 22:25, 12 July 2017 (UTC)
MartinPoulter (talk) 09:21, 20 July 2017 (UTC)
ThelmadatterThelmadatter (talk) 01:11, 13 September 2017 (UTC)
Zeroth (talk) 15:01, 16 September 2017 (UTC)
Beat Estermann (talk) 20:07, 12 November 2017 (UTC)
Shilonite - specialize in cataloging Jewish & Hebrew books
Elena moz
Oa01 (talk) 10:52, 3 February 2018 (UTC)
Maria zaos (talk) 11:39, 25 March 2018 (UTC)
Wikidelo (talk) 13:07, 15 April 2018 (UTC)
Mfchris84 (talk) 10:08, 27 April 2018 (UTC)
Mlemusrojas (talk) 3:36, 30 April 2018 (UTC)
salgo60 Salgo60 (talk) 12:42, 8 May 2018 (UTC)
Dick Bos (talk) 14:35, 16 May 2018 (UTC)
Marco Chemello (BEIC) (talk) 07:26, 30 May 2018 (UTC)
 徵國單  (討論 🀄) (方孔錢 💴) 14:35, 20 July 2018 (UTC)
Alicia Fagerving (WMSE)
Louize5 (talk) 20:05, 11 September 2018 (UTC)
Viztor (talk) 05:48, 6 November 2018 (UTC)
RaymondYee (talk) 21:12, 29 November 2018 (UTC)
Merrilee (talk) 22:14, 29 November 2018 (UTC)
Kcoyle (talk) 22:17, 29 November 2018 (UTC)
JohnMarkOckerbloom (talk) 22:58, 29 November 2018 (UTC)
Tris T7 TT me
Helmoony (talk) 19:49, 8 December 2018 (UTC)
Shooke (talk) 19:17, 12 January 2019 (UTC)
DarwIn (talk) 14:58, 14 January 2019 (UTC)
I am Davidzdh. 16:08, 18 February 2019 (UTC)
Juandev (talk) 10:03, 27 February 2019 (UTC)
Buccalon (talk) 15:51, 27 March 2019 (UTC)
MJLTalk 16:48, 8 April 2019 (UTC)
Rosiestep (talk) 20:26, 24 April 2019 (UTC)
Dcflyer (talk) 12:23, 7 May 2019 (UTC)
Susanna Giaccai (talk) 05:56, 29 July 2019 (UTC)
Asaf Bartov (talk) 19:03, 31 July 2019 (UTC)
Msuicat (talk) 17:58, 6 August 2019 (UTC)
SilentSpike (talk) 15:27, 12 August 2019 (UTC)
TheFireBender (talk) 12:40, 20 August 2019 (UTC)
  Notified participants of WikiProject Books

What do you think? Is it a good idea?

Cheers, VIGNERON (talk) 09:58, 1 August 2019 (UTC)

I would support that (with some temporary qualifier for future checking). Book is "false" in any case and written work would be mostly correct.
Perhaps we could also check manually in the first place the book published after the author's death (which are more likely to be about a specific edition).
Alexander Doria (talk) 10:35, 1 August 2019 (UTC)
I would support a cleanup to remove book (Q571), but making them all written work (Q47461344) provides no useful information, and could easily be wrong. We need to know first of all whether it is a data item for a work or an edition/translation. Second, we need to know what sort of "book" it is: if it is a novel (Q8261) or a scholarly work (Q55915575) or something else. There are already many editors here who think that written work (Q47461344) is the correct value over all others, even at the expense of clarity or specificity. We should not promote that idea by a blanket change. Surely our tools are better than that by now. --EncycloPetey (talk) 15:12, 1 August 2019 (UTC)
@EncycloPetey: true, how do you suggest to proceed? (I have several idea but I'd love to hear other point of view). Cheers, VIGNERON (talk) 16:06, 2 August 2019 (UTC)
Any of the items tagged with a value for translator (P655) or editor (P98) or publisher (P123) is a candidate for version, edition, or translation (Q3331189). I would start with those, and then recount the remaining items to see what progress was made. --EncycloPetey (talk) 16:19, 2 August 2019 (UTC)
A combinaison of instance of book (Q571) + one of the dedicated properties of edition has to lead to the instance of written work (Q47461344) definition. Not sure that property translator (P655) is the best one to identify version, edition, or translation (Q3331189): some works are mixing different languages. The most important properties to identify recent editions are edition number (P393), place of publication (P291), publisher (P123) or publication date (P577) in my opinion. Snipre (talk) 22:39, 5 August 2019 (UTC)
publication date (P577) isn't a dedicated edition property; it is used on works as well as editions. It is used to indicate the date of first publication of a work. I'd also point out that I've come across more than a few works which had edition data included on them (e.g. ISBN) when that data was imported from a Wikipedia page about the work. --EncycloPetey (talk) 23:34, 5 August 2019 (UTC)
@EncycloPetey: According to data model defined on Wikidata:WikiProject_Books, publication date (P577) is an edition property. For me this is the only truth: the data model has to be respected unless it explicitely mention some exception. So the question is not to know how people are using the propeties in a wrong way, the question is to define if publication date (P577) should be an edition property only or should be extended to work. Once this done then we will have to clean the items according to data model. Snipre (talk) 05:55, 6 August 2019 (UTC)
And which should be a date for a work? inception (P571)? --Infovarius (talk) 10:55, 7 August 2019 (UTC)
@Infovarius: Can a date represent the writing of a work ? But yes, inception (P571) is a better property for work (this is the way mentioned in the data model) but I would be really happy if someone can explain the use of that property in this scenario: is the date the date of the beginning of the writing or the end of it ? An author can start to write in a period of his life and then stop a moment to finish later, how can we model that ? Again trying to represent the writing process with one date is a huge simplification. Snipre (talk) 13:21, 7 August 2019 (UTC)
The problem with inception (P571) is that it might refer to the date an author began writing a work, rather than the date of first publication. As Snipre has pointed out, inception (P571) is not very clear what it refers to. It is really intended to items that have a clear beginning (and ending) date, such as the existence of a company or nation. --EncycloPetey (talk) 16:27, 7 August 2019 (UTC)
@EncycloPetey: For me work item should not have any date unless a clear source mentions the writing period of a work. Instead of starting to put edition data in work item, the correct way is to create the related edition item and to add the information at the correct place. I don't understand why the publication date has to be mentioned in the work item. If you want to have that information just do the job correctly: create the corresponding edition item. Snipre (talk) 20:21, 7 August 2019 (UTC)
@Alexander Doria, EncycloPetey, Snipre, Infovarius: this discussion is very interresting but it's going sideways. So if I understand correctly the collective point of view, for items that might be about editions, you prefer to keep book (Q571), ok, no problem. Can I at least do the replacement book (Q571) -> written work (Q47461344) on the 22167 items that are most likely not editions (by removing all the items with any of these properties: translator (P655), editor (P98), publisher (P123), illustrator (P110), author of foreword (P2679), author of afterword (P2680), publication date (P577), place of publication (P291), ISBN-10 (P957), ISBN-13 (P212)), and I probably won't touch the others since it's too much of a mess (a lot of them seems to be merge of several editions/works/items/whatever :/ ). Cdlt, VIGNERON (talk) 14:53, 7 August 2019 (UTC)
However if the work is a novel (Q8261), then that value should be used instead of written work (Q47461344). We've had this discussion several times now, and have repeatedly come to that conclusion. written work (Q47461344) is only the most general possible value, and if a more precise value exists, we should use it. --EncycloPetey (talk) 15:43, 7 August 2019 (UTC)
Another suggestion: If book (Q571) is not the only value for instance of (P31) on an item, then book (Q571) can simply be removed, rather than replaced. I've poked around and found a few cases where there were multiple values present. --EncycloPetey (talk) 19:48, 7 August 2019 (UTC)
@EncycloPetey: No, we never agree that a work can be a instance of everything: a work can be an instance of a subclass of written work. Novel is not a subclass of written work but an instance of literary form. So instances of novel can't be a work. Snipre (talk) 20:14, 7 August 2019 (UTC)
@Snipre:: novel (Q8261) used to be a subclass of literary work (Q7725634). There is no separate property for literary form approved for use by this community. The form is the value for "instance of". And we have agreed as a group (several times, including one instance still visible above) that instance of (P31) should be novel (Q8261) for novels, because this aligns with the FaBio tree at Wikidata:WikiProject Books/Works. --EncycloPetey (talk) 20:55, 7 August 2019 (UTC)
@VIGNERON: You can do the inverse: if an item with instance of book contains 3 or more properties related to edition class, then we can define it as instance of edition. Snipre (talk) 20:17, 7 August 2019 (UTC)
@EncycloPetey: isn't written work (Q47461344)novel (Q8261) a value for genre (P136) and not instance of (P31)? (it's how it's used 90 % of the time). That said, the remark is interresting and I checked: there is 122 items with both book (Q571) and novel (Q8261) as value for instance of (P31), then I guess we could remove the book (Q571), replace it by written work (Q47461344) and move written work (Q47461344)novel (Q8261) in genre (P136)). For the other cases of instance of (P31) with book (Q571) and something else, there is 3208 items (again quite low) and most of the time, the second value is wrong:
@Snipre: I thought about it but I guess I can't because the inverse of "not once this property" is "any number of value for this property" so if there is multiple values, then it's not *one* edition, it's multiple editions (which is a whole different problem that can't be treated automatically - because sometimes one edition has actually several values -, or maybe it's possible but I don't see how, I looked at the data but it seems to be quite a mess). Bottomline: I'm just aiming at the easy low hanging fruit there. Cheers, VIGNERON (talk) 21:02, 7 August 2019 (UTC)
No, "written work" is not a genre. If it is being used that way, then I suspect someone ran a bot replacement incorrectly. --EncycloPetey (talk) 21:05, 7 August 2019 (UTC)
Obviously bad copy-paste, corrected, VIGNERON (talk) 06:31, 8 August 2019 (UTC)
No, novel is not a genre. People have been putting that in because it was in our data model, but we have repeatedly agreed that novel is not a genre. There is a discussion further up this page where we agreed so. We keep having this discussion, but each time we have it, some people seem to have forgotten that we decided novel was a literary form (like poem, play, or scholarly article) rather than a genre (like Gothic literature, Western literature, historical fiction). Novel is a property of the length of a work of fiction, and not a property of its style or content. Genre describes style and content, not length. It is ridiculous to say that War and Peace (Q161531), Gulliver's Travels (Q181488), and The Shining (Q470937) are all in the same genre. They are all novels (long prose works), but they are in very different genres. --14:10, 8 August 2019 (UTC)
@VIGNERON: I agree with EncycloPetey: if novel is not a genre, how do you define classification based on content (SF, erotic, historical,...) ? We need 2 different properties to describe a text according to its content or its form. Snipre (talk) 10:04, 14 August 2019 (UTC)
short story collection (Q1279564) is also often used with genre, even though it violates a constraint. Likewise, short story (Q49084), which has been declared to be a genre so doesn't violate the constraint. Ghouston (talk) 01:45, 15 August 2019 (UTC)

RfC about model for document descriptionEdit

Dear all,

I started a RfC to improve our model for document description. As I am not all-knowing, I did a proposition of model and I expect some modifications before we can launch a decision phase. The principle of that 2 phases RfC is to avoid to start the decision before having input from a large number of contributors mentioning particular cases which can change the original proposition. This is always frustrating to give its opinion about a proposition which changes several times between the start and the end of the decision phase.

Please have a look at Wikidata:Requests for comment/Improved model for document description. Snipre (talk) 13:16, 14 August 2019 (UTC)

@VIGNERON, EncycloPetey, Alexander Doria, Andreasmperu, Pasleim, TomT0m: @Infovarius, Freddy eduardo, Aubrey, Micru, Tpt, Kolja21: Snipre (talk) 13:19, 14 August 2019 (UTC) @Hsarrazin, PKM, Giftzwerg 88, Jura1, Beat Estermann, Jc3s5h: Snipre (talk) 13:22, 14 August 2019 (UTC)

linking book review item to book author item and literary work itemEdit


How should the review of her book item be linked to her item and to the book item? (Not sure which properties to use). thx --Tagishsimon (talk) 21:45, 19 August 2019 (UTC)

@Tagishsimon: Have a look at review of (P6977). No need to linked the review to the author: this done by the links between the review/work and work/author. Why to add a third link review/author ? Snipre (talk) 08:22, 20 August 2019 (UTC)
Excellent, Snipre; thank you. --Tagishsimon (talk) 15:29, 20 August 2019 (UTC)

Many bad Cewbot editdsEdit

It looks as though @Cewbot: is adding lots and lots of bad data (e.g. [1]) to numerous data items.

There are two problems: (1) no book has 0±0 pages, as that is nonsense. (2) all the data about page numbers, illustrators, etc. are being added to data items for works rather than specific editions. --EncycloPetey (talk) 02:07, 8 September 2019 (UTC)

Labels for edition items, use of parenthesesEdit

In Project chat recently, I noticed a comment that we shouldn't use parentheses in labels for items. I looked at the Help:Label page and sure enough, in a section titled Disambiguation information belongs in the description, it does appear to discourage the use of parenthetical information to disambiguate in the label.

I have been routinely adding parentheticals such as (1st edition) to the labels for edition items and find them helpful. And many examples on the WikiProject Books page do as well. I'm not sure what to make of this. How else would we distinguish editions from works in the label? Comments? --Lrobare (talk) 21:19, 12 September 2019 (UTC)

I don't distinguish works from editions in the label; I do that in the description. - PKM (talk) 23:15, 12 September 2019 (UTC)
I personally add the edition number in parentheses for book edition. Just type CRC Handbook of Chemistry and Physics in the search engine: without the edition number in the label you will have 7 times the same label. Same when you will select a value when creating/modifying a statement. I think in case of edition, this information is important especially if the item can reused several times like it is the case for book in references. Snipre (talk) 10:10, 13 September 2019 (UTC)
The label should name the book; the description should give the edition particulars. Both fields show up in a search. @Snipre:, the example you give is a god reason not to use parentheses. The book title is so long that the parenthetical information is off the edge of the search window. --EncycloPetey (talk) 17:28, 13 September 2019 (UTC)
@EncycloPetey: I don't know the resolution of your screen but in my case I am able to select the good edition item directly from the search window. The lable is a wikidata field used to identify the item in the wikidata environment. If you want to use the title in any kind of external application, you should use the appropriate property title (P1476). Why do we create that property if the label and the value of property title (P1476) are exactly the same ? Snipre (talk) 19:27, 13 September 2019 (UTC)
Because labels are meant to be read together with descriptions. --- Jura 19:34, 13 September 2019 (UTC)
In German I use a full stop as a delimiter, see eg. Taxonomic literature : a selective guide to botanical publications and collections with dates, commentaries and types (Q56649865). --Succu (talk) 19:47, 13 September 2019 (UTC)
We don't use parentheses to distinguish songs of the same title, or films of the same title, or TV episodes of the same title. Search for "Tobacco Road" as an example. It's helpful to enable the "Descriptions" gadget in the your preferences so that descriptions appear on hover. - PKM (talk) 20:14, 13 September 2019 (UTC)
@Snipre: "Why do we create that property if the label and the value of property title (P1476) are exactly the same?" It will not always be the same. The label and title will probably be the same in the language of publication, but may be different in other language labels. Also, some editors use the library record form of the title, which drops initial articles from the title, such as "the", "a", "le", "una", or "el". In these situations the label and property value will not match. --EncycloPetey (talk) 01:02, 14 September 2019 (UTC)
@EncycloPetey: So if label can be translated and be different from the official title of a the book, why can't we modify the label to distinguish the item from other items ? Just take as example Gone with the Wind (Q2870): why do we accept the tanslation of the label ? The official title in the original langauge is Gone with the Wind, so this should be the same for all languages. If we accept that the label is translated for the work item in order to facilitate the item identification for every contributor, why can we add the edition number in the label ? Snipre (talk) 21:31, 16 September 2019 (UTC)
Why not? Because Wikidata norm disfavor doing so. Why use parentheses when the description exists for precisely that purpose? Why not just use the description, the way it was intended, instead of stuffing everything into a label? --EncycloPetey (talk) 01:14, 17 September 2019 (UTC)

Work with one editionEdit

Perhaps a very stupid question..... What do I do with a written work, that has only one edition? Do I have to create two wikidata-items? And what are the naming conventions for those two items? (see e.g. Q21962241) --Dick Bos (talk) 17:50, 2 October 2019 (UTC)

@Dick Bos: Can you ensure that no new edition will be edited in the future ? I think no, so two items is recommended. For the name, both items can have the same label. For edition there is a long unresolved discussion if it is a good practice to add the edition number in the label of edition item. Ex.: blablabla (1st ed.). And in the description, use work or edition and not book. You are welcome. Snipre (talk) 11:47, 3 October 2019 (UTC)
Return to the project page "WikiProject Books".