Shortcut: WD:PP/WORK
Wikidata:Property proposal/Creative work
Property proposal: | Generic | Authority control | Person | Organization |
Creative work | Place | Sports | Sister projects | |
Transportation | Natural science | Computing | Lexeme |
See also[edit]
- Wikidata:Property proposal/Pending – properties which have been approved but which are on hold waiting for the appropriate datatype to be made available
- Wikidata:Properties for deletion – proposals for the deletion of properties
- Wikidata:External identifiers – statements to add when creating properties for external IDs
- Wikidata:Lexicographical data – information and discussion about lexicographic data on Wikidata
This page is for the proposal of new properties.
Before proposing a property
- Search if the property already exists.
- Search if the property has already been proposed.
- Check if you can give a similar label and definition as an existing Wikipedia infobox parameter, or if it can be matched to an infobox, to or from which data can be transferred automatically.
- Select the right datatype for the property.
- Read Wikidata:Creating a property proposal for guidelines you should follow when proposing new property.
- Start writing the documentation based on the preload form below by editing the two templates at the top of the page to add proposal details.
Creating the property
- Once consensus is reached, change status=ready on the template, to attract the attention of a property creator.
- Creation can be done 1 week after the creation of the proposal, by a property creator or an administrator.
- See property creation policy.
On this page, old discussions are archived. An overview of all archives can be found at this page's archive index. The current archive is located at 2024/06. |
Cultural heritage[edit]
- See also: Wikidata:WikiProject Cultural heritage, Wikidata:WikiProject Intangible Cultural Heritage
- Other related projects: Category:Cultural heritage WikiProjects
National Historical Museums of Sweden object ID[edit]
Description | authority identification for an object in the collections of the National Historical Museums of Sweden |
---|---|
Data type | External identifier |
Allowed values | [0-9A-Z]{8}-[0-9A-Z]{4}-[0-9A-Z]{4}-[0-9A-Z]{4}-[0-9A-Z]{12} |
Example 1 | Streiff (Q10681657) → https://samlingar.shm.se/object/A4B754D2-5CB6-4FA1-997A-970250E32044 |
Example 2 | Mosjömadonnan (Q10589526) → https://samlingar.shm.se/object/7C505995-EBF5-4106-BBEE-17F52BB3EA83 |
Example 3 | Elizabeth Reliquary (Q26253636) → https://samlingar.shm.se/object/8BA2743C-5065-438B-9FAA-D854606DB716 |
Source | https://samlingar.shm.se |
Planned use | Matching and creating items in the collection that are depicted on Wikimedia Commons |
Number of IDs in source | 1 300 000 |
Expected completeness | no label (Q21873886 (always incomplete)) |
Formatter URL | https://samlingar.shm.se/object/$1 |
See also | Nationalmuseum Sweden artwork ID (P2539) |
Single-value constraint | yes |
Distinct-values constraint | yes |
Motivation[edit]
Needed to be able to matching and creating items on Wikidata that are objects in the collection of NHM and that are depicted in images on Wikimedia Commons, for example. / LinneaKarlberg (talk) 12:58, 7 April 2022 (UTC)
Discussion[edit]
- Support Azad Karimi (talk) 13:56, 7 April 2022 (UTC)
- Support LinneaKarlberg (talk) 13:05, 7 April 2022 (UTC)
- Support Eva L Vedin (talk) 13:08, 7 April 2022 (UTC)
- Support Elinor Rajka (talk) 19:13, 7 April 2022 (UTC)
- Support Azad Karimi (talk) 13:56, 7 April 2022 (UTC)
- Comment @LinneaKarlberg:, @Eva L Vedin:, @Elinor Rajka:, @Azad Karimi: coordinating support votes with ones colleagues is not helpful, the property proposal process is in place for a reason. Abbe98 (talk) 22:34, 7 April 2022 (UTC)
- Sorry, we did not know. LinneaKarlberg (talk) 07:19, 8 April 2022 (UTC)
- Comment Considering that National Historical Museums of Sweden ID (P9495) exists and that other properties from SHM are likely to be proposed in the future(places, events, heritage sites, ect) maybe there should only be one property? As far as I'm aware the UUIDs are unique across the various types and even if that wouldn't be the case one could include the type prefix in the id. Abbe98 (talk) 22:40, 7 April 2022 (UTC)
- @Abbe98: Sure, that would probably work. Do you have an example of another external identifier that includes several different types so I can check how it works? Is it possible then to change the name and details of P9495? LinneaKarlberg (talk) 07:22, 8 April 2022 (UTC)
- Europeana entity (P7704) would be one example. I would imagine migrating/generalizing National Historical Museums of Sweden ID (P9495) by: 1. updating the formatter URL 2. adding the agent prefix to existing values 3. updating the label/description of the property Abbe98 (talk) 10:08, 8 April 2022 (UTC)
- @Abbe98: Sure, that would probably work. Do you have an example of another external identifier that includes several different types so I can check how it works? Is it possible then to change the name and details of P9495? LinneaKarlberg (talk) 07:22, 8 April 2022 (UTC)
- Oppose Per the discussion above, I would suggest generalizing National Historical Museums of Sweden ID (P9495) rather than creating a new property for each type. I cave created a section on the discussion page. Abbe98 (talk) 10:20, 8 April 2022 (UTC)
- Hello Abbe98 , It would then be necessary to differentiate "agents" from "object". How would you like to do? (incorporate it into the identifier as a general property? or use an external URL formatter?) We can also consider that each property will be dedicated to the type (less errors with dedicated constraints). It would be necessary to recontact those who have already voted, as well as the voters of the other property, to find out if your idea appeals to them, but with more information. I don't see a URL leading directly to the correct page without using the type (with only the UUID). Example:
type:UUID
. Cordially. —Eihel (talk) 03:47, 13 April 2022 (UTC)- Hi! I would imagine we would use one of the seven possible prefixes like agent/<UUID> and object/<UUID>. We could also use a generic resolver but there isn't an official one so I think such a solution is less optimal. Abbe98 (talk) 06:48, 13 April 2022 (UTC)
- @Abbe98: @Eihel: @LinneaKarlberg: We just had a discussion about this with the Wikidata team at the National Historical Museums of Sweden. Our conclusion is that this property should not be created, and Abbe98's solution (using prefixes) is better. This will include us (WMSE is supporting the museum in their Wikidata work) generalizing National Historical Museums of Sweden ID (P9495) and removing
/person/
from the formatter URL and then adding the person prefix to all the existing uses of the property. --Alicia Fagerving (WMSE) (talk) 12:10, 21 April 2022 (UTC)- @Alicia Fagerving (WMSE) I have pinged all the people who voted on National Historical Museums of Sweden ID (P9495). I think we should leave it over the weekend at least but then if there are no one oposing this I can migrate it early next week. Abbe98 (talk) 12:32, 21 April 2022 (UTC)
- We at NHM are all on board with this approach instead of several Properties. LinneaKarlberg (talk) 08:09, 29 April 2022 (UTC)
- Sounds like an excellent idea. Many thanks Abbe98 . /André Costa (WMSE) (talk) 08:51, 24 May 2022 (UTC)
- Thanks everyone, I've started re-defining National Historical Museums of Sweden ID (P9495) and will migrate the existing items using it. --Alicia Fagerving (WMSE) (talk) 12:19, 9 June 2022 (UTC)
- Sounds like an excellent idea. Many thanks Abbe98 . /André Costa (WMSE) (talk) 08:51, 24 May 2022 (UTC)
- We at NHM are all on board with this approach instead of several Properties. LinneaKarlberg (talk) 08:09, 29 April 2022 (UTC)
- @Alicia Fagerving (WMSE) I have pinged all the people who voted on National Historical Museums of Sweden ID (P9495). I think we should leave it over the weekend at least but then if there are no one oposing this I can migrate it early next week. Abbe98 (talk) 12:32, 21 April 2022 (UTC)
- @Abbe98: @Eihel: @LinneaKarlberg: We just had a discussion about this with the Wikidata team at the National Historical Museums of Sweden. Our conclusion is that this property should not be created, and Abbe98's solution (using prefixes) is better. This will include us (WMSE is supporting the museum in their Wikidata work) generalizing National Historical Museums of Sweden ID (P9495) and removing
- Hi! I would imagine we would use one of the seven possible prefixes like agent/<UUID> and object/<UUID>. We could also use a generic resolver but there isn't an official one so I think such a solution is less optimal. Abbe98 (talk) 06:48, 13 April 2022 (UTC)
- Hello Abbe98 , It would then be necessary to differentiate "agents" from "object". How would you like to do? (incorporate it into the identifier as a general property? or use an external URL formatter?) We can also consider that each property will be dedicated to the type (less errors with dedicated constraints). It would be necessary to recontact those who have already voted, as well as the voters of the other property, to find out if your idea appeals to them, but with more information. I don't see a URL leading directly to the correct page without using the type (with only the UUID). Example:
National Archives of Sweden persistent identifier[edit]
Description | persistent identifier for objects in the National Archives of Sweden main archival database |
---|---|
Represents | National Archives of Sweden (Q1724971) |
Data type | External identifier |
Domain | archival resource (Q106815942), document (Q49848), work (Q386724) |
Allowed values | Base62-encoded UUID |
Example 1 | No 2. Elbing. (Q111517198) → eYHMeAFOm4sNVmxKK3M5L2 |
Example 2 | No 3. Elbing (Q111517379) → 0zDW3BS0Gw9Haap2yUVspE |
Example 3 | No 4. Danzigk wir es Eltere und newer werck (Q111519390) → zmQwWNi2ag9DQGJxnSVmD0 |
Implied notability | Wikidata property for an identifier that does not imply notability (Q62589320) |
Formatter URL | https://sok.riksarkivet.se/arkiv/$1 |
See also | Swedish National Archive reference code (P5324) |
Applicable "stated in"-value | National Archives of Sweden (Q117288060) |
Single-value constraint | yes |
Distinct-values constraint | yes |
Motivation[edit]
Wikidata-objekt med denna egenskapen kan också ha Nationell Arkivdatabas Referenskod (P5324), men den persistenta identifieraren är enklare att använda för att skapa webbsides-URLer och länkad data-URIer. Nils Weinander (Riksarkivet Sverige) (talk) 13:28, 28 April 2022 (UTC)
Discussion[edit]
- Comment Hi - could you fix your examples to look more like other property proposals (should look like: item → id) ? Also it would be useful to have formatter URL and some of the other template parameters filled out if possible. ArthurPSmith (talk) 14:21, 29 April 2022 (UTC)
- Thanks for the feedback! This is my first property proposal so I am very unsure of how to do things. I have reformatted the examples, added URL format and a see also reference. Nils Weinander (Riksarkivet Sverige) (talk) 08:22, 2 May 2022 (UTC)
- Support Ok, looks good to me now! ArthurPSmith (talk) 15:48, 9 May 2022 (UTC)
- Support Jneubert (talk) 05:53, 10 May 2022 (UTC)
- Comment are the above examples also the canonical URIs? Considering that the RA has quite a lot of identifiers, could there be a less generic name/description? "primary database" doesn't say much to the average user. Abbe98 (talk) 21:18, 11 May 2022 (UTC)
- Support, Notified participants of WikiProject Sweden —MasterRus21thCentury (talk) 06:36, 21 March 2023 (UTC)
It has been created as Swedish National Archive agent ID (P9713) se discussion - Salgo60 (talk) 07:43, 21 March 2023 (UTC)
- Not the same as I understand. This proposal is for objects in archives (maybe even archives or series, though I struggle to come up with a case where they would have a wikidata item). The property you link is for an agent (Swedish: arkivbildare). Belteshassar (talk) 09:15, 21 March 2023 (UTC)
- @Belteshassar, Nils Weinander (Riksarkivet Sverige), Abbe98: Dont we make it more complex than needed. Formatter url is the same
https://sok.riksarkivet.se/agent/$1
- My suggestion change the name on Swedish National Archive agent ID (P9713) to be both... I have used (maybe wrongly) both for the "person agent" and the "archive agent"
- 1) List examples nota bene August Strindberg seems to have more person identifiers at the National Archive looks like something that needs to be cleaned at "the National Archive"...
- Having 2 different properties is like if someone should connect with Wikidata and add new properties for every type of instance instance of (P31) Wikidata has... ?
- Also Swedish National Archive reference code (P5324) is used for both persons and archives
- - Salgo60 (talk) 20:35, 24 March 2023 (UTC)
- Comment, I think this would be useful, perhaps also on commons. I’m not sure how many entries in NAD reference individual works, as I understand the purpose of the proposal, and to what degree those works are notable for Wikidata. Perhaps the creator of the proposal could enlighten me. Belteshassar (talk) 09:23, 21 March 2023 (UTC)
- pushed the question also to github.com/Riksarkivet/dataplattform - Salgo60 (talk) 13:24, 27 March 2023 (UTC)
- Comment read the thoughts over at the National Archive - Salgo60 (talk) 03:10, 28 March 2023 (UTC)
- Comment Writing as the original author of this propopsal, I would like to put this on hold for the moment. I realize that this should probably be the RDF URI rather than just the PID. I have to think this over and if I do end up with wanting the RDF URI, there are issues to clear with the format of this. - Nils Weinander (Riksarkivet Sverige) (talk) 11:26, 28 Mars 2023 (UTC)
- FYI: Nils is working at the Swedish National Archives with this - Salgo60 (talk) 17:17, 28 March 2023 (UTC)
writing technique[edit]
Description | technique used for writing on stone, paper or other support |
---|---|
Data type | Item |
Example 1 | EDR 092763 (Q124815019) -> chiselling (Q125418433) |
Example 2 | Alexamenos graffito (Q577890) -> scratching (Q125653002) |
Example 3 | Saint Clement and Sisinnius inscription (Q15157527) -> painted writing (Q125653482) |
See also | fabrication method (P2079) |
Motivation[edit]
Notified participants of WikiProject Epigraphy As in the case of height of letters (P12549), indicating the writing technique (Q125400578) is a useful part of the description of an inscription (e.g. this detail is present in the entries of Epigraphic Database Roma (Q124541686)). --Epìdosis 17:20, 27 April 2024 (UTC)
Discussion[edit]
- Should we limit the type of techniques we could specify? On EDR looking over, I've seen these: scalpro, caelo and signaculo Men (talk) 18:33, 27 April 2024 (UTC)
- I think that all entities having instance of (P31)writing technique (Q125400578) are valid values for this property. EDR recognizes 18 possible values, listed in the manual at page 15. Epìdosis 23:10, 27 April 2024 (UTC)
- Comment Looking for "technique" returned fabrication method (P2079) − can you briefly explain why this would not be a good fit? Jean-Fred (talk) 19:06, 28 April 2024 (UTC)
- @Jean-Frédéric: firstly thanks for pointing to fabrication method (P2079), I hadn't noticed it; effectively writing technique (Q125400578) wouldn't fit bad in it; I'm now uncertain if we effectively need this new property, although I can still see some potential advantages: a new property "writing technique", which would be a subproperty of "fabrication method", would apply more specifically to the field of epigraphy, and potentially an item regarding an inscription could have both a value of "fabrication method" for processes related to its fabrication as object and a value of "writing technique" for processes related specifically to how it has been inscribed (anyway, these two values could also go, with no particular concern, both in "fabrication method"). I leave the proposal open to collect other opinions if we need a new property or if using P2079 is just fine. --Epìdosis 08:48, 29 April 2024 (UTC)
Wikidata:Property proposal/Fondazione Torino Musei
Cinematography[edit]
- See also: Wikidata:WikiProject Movies
- Other relevant projects: Category:Movie WikiProjects
Television[edit]
- See also: Wikidata:WikiProject Movies
showrunner[edit]
Description | person who is responsible for the day-to-day operation of a television show |
---|---|
Represents | showrunner (Q1440873) |
Data type | Item |
Template parameter |
|
Domain | work (Q386724) |
Allowed values | television program (Q15416), television series (Q5398426), television series season (Q3464665) |
Example 1 | The Walking Dead, season 1 (Q136546)→Frank Darabont (Q295445) |
Example 2 | The Walking Dead, season 2 (Q181631)→Glen Mazzara (Q1530813) |
Example 3 | The Office, season 1 (Q3465812)→Greg Daniels (Q1544904) |
See also | executive producer (P1431) |
Wikidata project | WikiProject Film (Q8485793) |
Subproperty of | executive producer (P1431) |
Motivation[edit]
On English Wikipedia, showrunners were added as a new param to TV infoboxes last month, and this property is now slowly migrating to other interlanguage Wikipedia infoboxes. On wikidata, it used to be an alias for , but I think it would be useful to separate it for synchronization with infoboxes (since executive producers are there, too). Generally speaking, the showrunner is more of a top-level executive producer who has the most control over the current season, while other executive producers have less control over creative stuff and on-set production, but deal with administrative, financial, or other responsibilities. The actual episode credits usually list the showrunners as executive producers, but sources often state who the showrunner is at the time. Individual seasons are always the responsibility of the showrunners, who may change from season to season, while the list of executive producers is most often supplemented as the series progresses by former showrunners (who may no longer be involved in production). So showrunners usually specified in the infobox with a listing for every season (see The Walking Dead (TV series) or The Simpsons). Also, some executive producers may never be showrunners for any season of the show. Solidest (talk) 18:14, 28 May 2024 (UTC)
Discussion[edit]
Notified participants of WikiProject Authority control Regards, ZI Jony (Talk) 18:14, 30 May 2024 (UTC)
Notified participants of WikiProject Movies Regards, ZI Jony (Talk) 18:14, 30 May 2024 (UTC)
- Support Back ache (talk) 09:33, 31 May 2024 (UTC)
Anime and manga[edit]
- See also: Wikidata:WikiProject Anime and Manga
Music[edit]
- See also: Wikidata:WikiProject Music
- Other relevant projects: Category:Music WikiProjects
Yandex.Music track ID[edit]
Description | Yandex.Music track ID |
---|---|
Data type | External identifier |
Domain | audio track (Q7302866) |
Example 1 | The Knot (Q109795369) -> 3639885/track/30124805 |
Example 2 | The bandits (Q113149889) -> 3639147/track/30168054 |
Example 3 | The Time Will Come (Progress Studies Humans' Behavior) (Q106098098) -> 25575448/track/113143569 |
Motivation[edit]
For Yandex.Music we already have label, genre, artist, album - lets add track. Vitaly Zdanevich (talk) 17:58, 10 May 2024 (UTC)
Discussion[edit]
- Support Tracks are an important musical release component, therefore if Yandex is already offering property IDs for the above, adding this new one makes sense. Youyouca (talk) 13:04, 1 June 2024 (UTC)
- Not done, duplicate of Yandex Music release ID (P2819), use Yandex Music release ID (P2819) with qualifier.
- But description says "identifier for an album on Yandex Music" - album, not track Vitaly Zdanevich (talk) 01:32, 3 June 2024 (UTC)
Video game[edit]
- See also: Wikidata:WikiProject Video games
- Other relevant projects: Category:Video game WikiProjects
pacing[edit]
Description | video game mechanic based on the rhythm of the player's actions |
---|---|
Data type | Item |
Example 1 | Civilization: Call to Power (Q1027136)→turn-based (Q74023227) |
Example 2 | Madden NFL 24 (Q119238637)→real-time (Q74023731) |
Example 3 | Fallout 76 (Q54497595)→persistent world (Q736958) |
Motivation[edit]
The video games have different types of rhythm mechanic. They can be divided into three or even four categories: turn-based, real-time, persistent (and even medidative or zen, when the goal of the video game is to relax the player).
Nevertheless, there is not a real specific property for this. That's why I suggest this one.
Nota: in French, we could translate it by "rythme narratif", but if you have a better suggestion, please let me know. :)
Notified participants of WikiProject Video games
YotaMoteuchi (talk) 01:21, 19 April 2024 (UTC)
Discussion[edit]
- Comment I don't think we should put 'rhythm' in the English label (maybe in the aliases, however) because rhythm game (Q2632782) has stronger associations with that word in the context of video games. timekeeping in games (Q4421045) seems to be the main topic but that doesn't lend itself to a property label... Here's a perhaps-relevant Listeria list: WD:WikiProject Video games/Statistics/game mechanic Arlo Barnes (talk) 01:59, 19 April 2024 (UTC)
- In English, the label should be 'pacing' which is used very often in other sites or databases. YotaMoteuchi (talk) 17:18, 19 April 2024 (UTC)
- 'Pacing' sounds fine to me. Arlo Barnes (talk) 13:51, 26 April 2024 (UTC)
- Comment Wouldn't it be better to use game mechanics (P4151) here? Regards Kirilloparma (talk) 02:41, 19 April 2024 (UTC)
- I wouldn't recommend game mechanics (P4151) here. Indeed, if you refer to the discussion of the property proposal Wikidata:Property proposal/Système de jeu, you will see that it has been proposed for role games and gamebooks. That's why I suggest this 'Pacing' property. YotaMoteuchi (talk) 17:18, 19 April 2024 (UTC)
- game mechanics (P4151) is used for video games as well. For instance, you may find it used for open world games. Regards Kirilloparma (talk) 20:25, 19 April 2024 (UTC)
- I see that game mechanics (P4151) is now used for video games, which detracts from the origin of the property. I think we're using a polysemantic word for a lot of unrelated things. Wouldn't using a more specific property be more appropriate? YotaMoteuchi (talk) 07:18, 20 April 2024 (UTC)
- @Kirilloparma: would you like to give your opinion based on the response? Regards, ZI Jony (Talk) 06:42, 26 April 2024 (UTC)
- @Kirilloparma:, would you like to give your final opinion based on the response? Regards, ZI Jony (Talk) 12:44, 22 May 2024 (UTC)
- @YotaMoteuchi: Well, I'm not exactly saying that we don't need a specific property. It's just that if you look at the
{{Games properties}}
template in the "All Games" category, you can see that there are some properties related to games, board games and video games that are reciprocally used and that's why we don't have for example a separate property called "video game mechanics" because we already have a semantically correct game mechanics (P4151) property. Regards Kirilloparma (talk) 02:05, 29 May 2024 (UTC)- I understand that point of view. On another hand, some properties are quite similar (on another subect, for example, based on (P144) and inspired by (P941)) and it's not very easy to know if we need a more specific property in some cases.
- Here, as I said Property:P4151 is a little mishmash, that's why I suggested this property. YotaMoteuchi (talk) 12:07, 29 May 2024 (UTC)
- @Kirilloparma:, shall we proceed? Or do you have any objections? Regards, ZI Jony (Talk) 19:03, 29 May 2024 (UTC)
- @YotaMoteuchi: Well, I'm not exactly saying that we don't need a specific property. It's just that if you look at the
- @Kirilloparma:, would you like to give your final opinion based on the response? Regards, ZI Jony (Talk) 12:44, 22 May 2024 (UTC)
- @Kirilloparma: would you like to give your opinion based on the response? Regards, ZI Jony (Talk) 06:42, 26 April 2024 (UTC)
- I see that game mechanics (P4151) is now used for video games, which detracts from the origin of the property. I think we're using a polysemantic word for a lot of unrelated things. Wouldn't using a more specific property be more appropriate? YotaMoteuchi (talk) 07:18, 20 April 2024 (UTC)
- Support with label/description that clearly differentiates it from similar properties. Arlo Barnes (talk) 13:51, 26 April 2024 (UTC)
Weak opposeThis can often be inferred from the genre. If applicable, genre (P136)turn-based strategy video game (Q2176159) or genre (P136)real-time strategy (Q208189) should be used instead. Use game mechanics (P4151)persistent world (Q736958) for consistency with game mechanics (P4151)open world (Q867123). Dexxor (talk) 06:21, 19 April 2024 (UTC)
- Here too, game mechanics (P4151) shouldn't be used as I said before. Regarding the way it can be inferred from the genre, sometimes, a same game can refer to two types of 'pacing'. FF12 have a "real-time" pacing when you are walking over the world and a "turn-based" when you fight agains monsters. So, a genre is not always a good way to infer the 'pacing'. YotaMoteuchi (talk) 17:18, 19 April 2024 (UTC)
- @Dexxor:, any changes in your opinion based on the response? Regards, ZI Jony (Talk) 12:45, 22 May 2024 (UTC)
- @Kirilloparma, Dexxor: pining for attention. Regards, ZI Jony (Talk) 07:24, 28 May 2024 (UTC)
- @ZI Jony: I change my !vote to Weak support because pcgamingwiki.com also has a pacing property. Dexxor (talk) 11:57, 28 May 2024 (UTC)
- @Kirilloparma, Dexxor: pining for attention. Regards, ZI Jony (Talk) 07:24, 28 May 2024 (UTC)
- @Dexxor:, any changes in your opinion based on the response? Regards, ZI Jony (Talk) 12:45, 22 May 2024 (UTC)
- Here too, game mechanics (P4151) shouldn't be used as I said before. Regarding the way it can be inferred from the genre, sometimes, a same game can refer to two types of 'pacing'. FF12 have a "real-time" pacing when you are walking over the world and a "turn-based" when you fight agains monsters. So, a genre is not always a good way to infer the 'pacing'. YotaMoteuchi (talk) 17:18, 19 April 2024 (UTC)
- Weak support Seems reasonable to have a more specific term for the pacing of video games. –MrBenjo (talk) 07:38, 24 April 2024 (UTC)
- Wait / Oppose I actually agree we need something like that (I have long been thinking of something along these lines), but I think the proposal is under-developed. For the video game part of things, I would us to have a clearer picture of acceptable values (are the 3 in examples the only ones? Would Active Time Battle (Q1796885) for example be acceptable?), have mappings to other ontologies (does the Video Game Metadata Schema (Q61572854) have something like that?) and databases (what do Moby, IGDB, Glitchwave do here?). Does the future property also make sense for eg board games? The proposal is called “rythme narratif” in French, does it mean we need to involve Wikiproject Narration? Also, I don’t think property proposals are the best place to hold such discussions, and that we really should talk about such things beforehand. This is expected to be a major data modelling addition for a domain with close to 100K items, and it would go ahead with a bare 3 "weak support"? I think we need more work and more consensus here. Jean-Fred (talk) 06:04, 31 May 2024 (UTC)
- (Also, for clarity: I would be more than happy to help with that work (research and consensus-building) ; but the timing of that proposal did not work great for me this time. I don’t blame ZI Jony for trying to move things forwards (indeed, without you, the proposal would have died down!) but I think the shorter lifecycle of property proposals can be at odds with the necessary research/discussion time) Jean-Fred (talk) 06:14, 31 May 2024 (UTC)
- Hello @Jean-Frédéric. Just for answering you regarding some points.
- I didn't found any pacing property on Video Game Metadata Schema (Q61572854). I can tell the same for IGDB or Glitchwave.
- Anyway, for Mobygames (and to tell the truth, it's this website who inspired this property here), we can found this category with the following genres: Meditative / Zen, Persistent, Real-time and Turn-based.
- This category can be also found on PCGamingWiki which is adding the Continuous turn-based genre.
- Checking some other websites, I found also that we could add a sub-genre of "real-time"; it could be "real-time with pause", but I guess it's the case for any "real-time" game (or 99% of these games) which should use a pause key or anthing like that.
- For the board games, yes, I would suggest a "turn-based" value.
- Regarding the French proposal, I tried to translate it and only found the expression "rythme narratif". I know that it's not the best translation but I couldn't find any French expression around the websites which could describe this property. Do you have another suggestion?
- YotaMoteuchi (talk) 22:43, 1 June 2024 (UTC)
- (Also, for clarity: I would be more than happy to help with that work (research and consensus-building) ; but the timing of that proposal did not work great for me this time. I don’t blame ZI Jony for trying to move things forwards (indeed, without you, the proposal would have died down!) but I think the shorter lifecycle of property proposals can be at odds with the necessary research/discussion time) Jean-Fred (talk) 06:14, 31 May 2024 (UTC)
Literature[edit]
- See also: Wikidata:WikiProject Books
- Other relevant projects: Category:Book WikiProjects
Korrespondenzen der Frühromantik[edit]
person ID[edit]
Description | Korrespondenzen der Frühromantik person ID |
---|---|
Represents | Korrespondenzen der Frühromantik (Q125973359) |
Data type | External identifier |
Domain | human (Q5) |
Allowed values | \d* |
Example 1 | Johann Wolfgang von Goethe (Q5879) → 137 |
Example 2 | Meta Forkel-Liebeskind (Q1416394) → 1834 |
Example 3 | Sophie Mereau (Q66313) → 4290 |
Number of IDs in source | 1804 |
Expected completeness | eventually complete (Q21873974) |
Formatter URL | https://briefe-der-romantik.de/letters/search?query=index_personen_11.ID:($1) |
Applicable "stated in"-value | Korrespondenzen der Frühromantik (Q125973359) |
Single-value constraint | yes |
Distinct-values constraint | yes |
organization ID[edit]
Description | Korrespondenzen der Frühromantik organization ID |
---|---|
Represents | Korrespondenzen der Frühromantik (Q125973359) |
Data type | External identifier |
Domain | type of organisation (Q17197366) |
Allowed values | \d* |
Example 1 | Charité (Q162684) → 10342 |
Example 2 | University of Göttingen (Q152838) → 6154 |
Example 3 | Leipzig Book Fair (Q571730) → 6043 |
Number of IDs in source | 102 |
Expected completeness | eventually complete (Q21873974) |
Formatter URL | https://briefe-der-romantik.de/letters/search?query=index_koerperschaften_15.ID:($1) |
Applicable "stated in"-value | Korrespondenzen der Frühromantik (Q125973359) |
Single-value constraint | yes |
Distinct-values constraint | yes |
place ID[edit]
Description | Korrespondenzen der Frühromantik place ID |
---|---|
Represents | Korrespondenzen der Frühromantik (Q125973359) |
Data type | External identifier |
Domain | administrative territorial entity type (Q15617994) |
Allowed values | \d* |
Example 1 | Berlin (Q64) → 15 |
Example 2 | Vienna (Q1741) → 16 |
Example 3 | Zürich (Q72) → 227 |
Number of IDs in source | 305 |
Expected completeness | eventually complete (Q21873974) |
Formatter URL | https://briefe-der-romantik.de/letters/search?query=index_orte_10.ID:($1) |
Applicable "stated in"-value | Korrespondenzen der Frühromantik (Q125973359) |
Single-value constraint | yes |
Distinct-values constraint | yes |
work ID[edit]
Description | Korrespondenzen der Frühromantik work ID |
---|---|
Represents | Korrespondenzen der Frühromantik (Q125973359) |
Data type | External identifier |
Domain | intellectual work (Q15621286) |
Allowed values | \d* |
Example 1 | Q110190088 → 8512 |
Example 2 | Panegyricus (Q3893205) → 2742 |
Number of IDs in source | 1811 |
Expected completeness | eventually complete (Q21873974) |
Formatter URL | https://briefe-der-romantik.de/letters/search?query=index_werke_12.ID:($1) |
Applicable "stated in"-value | Korrespondenzen der Frühromantik (Q125973359) |
Single-value constraint | yes |
Distinct-values constraint | yes |
periodical ID[edit]
Description | Korrespondenzen der Frühromantik periodical ID |
---|---|
Represents | Korrespondenzen der Frühromantik (Q125973359) |
Data type | External identifier |
Domain | periodical (Q1002697) |
Allowed values | \d* |
Example 1 | Propyläen (Q2113178) → 2954 |
Example 2 | The Madras Courier (Q7749355) → 2696 |
Example 3 | Kritisches Journal der Philosophie (Q3199839) → 1537 |
Number of IDs in source | 124 |
Expected completeness | eventually complete (Q21873974) |
Formatter URL | https://briefe-der-romantik.de/letters/search?query=index_periodika_13.ID:($1) |
Applicable "stated in"-value | Korrespondenzen der Frühromantik (Q125973359) |
Single-value constraint | yes |
Distinct-values constraint | yes |
Motivation[edit]
Korrespondenzen der Frühromantik (Q125973359) is an academic project funded by the German Research Foundation (Q707283). It offers a letters edition with focus on the German early Romanticist movement. The creation of these five properties would facilitate a further development of items related to this topic. Since all, or at least most, entries in those five registers achieve WD:N #2 notability, these properties would also facilitate notability consideration by admins and other users alike.
Note: I responded to this topic by email and offered to create this property proposal. I have not received any compensation, monetary or otherwise, and I’m not affiliated with the project. --Emu (talk) 22:02, 18 May 2024 (UTC)
Discussion[edit]
Notified participants of WikiProject Germany Regards, ZI Jony (Talk) 19:47, 20 May 2024 (UTC)
- I don't think we need a place ID, but the rest looks good. Bigbossfarin (talk) 07:13, 21 May 2024 (UTC)
- Oppose Organizations, places and periodicals seem to be each <=305 records, I wouldn't say that justifies properties for them, rather a case for described at URL (P973). However, I support properties for person ID and work ID. Best, --Marsupium (talk) 09:54, 22 May 2024 (UTC)
- @Emu, Bigbossfarin, Marsupium: Done as Korrespondenzen der Frühromantik person ID (P12780) and Korrespondenzen der Frühromantik work ID (P12781). Regards, ZI Jony (Talk) 07:24, 2 June 2024 (UTC)
Video[edit]
Image[edit]
- See also: Wikidata:WikiProject Visual arts
Podcast[edit]
- See also: Wikidata:WikiProject Podcasts
Theatre[edit]
Fiction[edit]
- See also: Wikidata:WikiProject Fictional universes, Wikidata:WikiProject Narration
- For projects about specific universes, see: Category:Fiction WikiProjects
is part of canon[edit]
Description | canon status for this creative work, episode or fictional entity in it's respective narrative universe |
---|---|
Represents | canon (Q53815) |
Data type | Item |
Domain | creative work (Q17537576) |
Allowed values | instances of canon (Q53815) |
Example 1 | Radioactive Man (Q1953829)→The Simpsons canon (Q124206593) |
Example 2 | Treehouse of Horror VII (Q1087745)→unknown (not part of any known canon) |
Example 3 | Star Wars: Episode IV – A New Hope (Q17738)→Star Wars canon (Q3648466) |
Example 4 | Star Wars: Rebel Assault (Q55259)→Star Wars Legends (Q3551295) (canon should probably have its own item) |
Expected completeness | always incomplete (Q21873886) |
Distinct-values constraint | no |
Motivation[edit]
This proposal is an alternative proposal for Wikidata:Property proposal/Canonicity.
- This is a subproperty of part of (P361).
- The subject of this property must be a work (Q386724).
- The object of this property must be a canon (Q53815)
- The property may be used in reference statements, if the object of the reference has no wikidata item. For instance if it is merely a url.
The truthfullness of statements should be evaluated using references. Conflicting statements of non-work entities should be ranked with
- preferred
- reason for preferred rank (P7452) → at least one source is considered canonical (Q106831793) (example)
- depricated
- reason for deprecated rank (P2241) → source is not considered canonical (Q124173200) (example)
Non-conflicting, statements should not be qualified with any canonicity evaluations. Instead a reference statement with stated in (P248) should be present. The object of stated in (P248) should itself have a is part of canon statement. This way a user can query which statements are relevant for a particular canon.
A statement without a reference statement should not be considered canonical – Shisma (talk) 09:16, 8 January 2024 (UTC)
Discussion[edit]
- Notified participants of WikiProject Narration Notified participants of WikiProject Fictional universes –Shisma (talk) 11:43, 8 January 2024 (UTC)
Comment Why are we not allowed to use this on fictional entities?--Trade (talk) 02:08, 9 January 2024 (UTC)
- you could qualify almost every statement of a fictional entity with with whether it is canon or not but that would be:
- a lot of work
- a lot of redundancy
- because the question can be answerd purely on the fact if the information is taken from a work that is part of the body of a canon or if it isn't. thats why I propose only qualify conflicting statements with existing properties. It is a common misconception that an information or statement can be canon. A canon is a collection of works – Shisma (talk) 08:10, 9 January 2024 (UTC)
- I literally said nothing about statements Trade (talk) 14:50, 9 January 2024 (UTC)
- I don't understand. do you have an example? – Shisma (talk) 15:42, 9 January 2024 (UTC)
- ah, you mean like a character? – Shisma (talk) 15:55, 9 January 2024 (UTC)
- Yeah Trade (talk) 16:09, 9 January 2024 (UTC)
- so you mean statements like:
- Professor Moriarty (Q283111)is part of canoncanon of Sherlock Holmes (Q2316684)
- I think it would be more correct and straightforward forward to say:
- Professor Moriarty (Q283111)present in work (P1441)The Final Problem (Q228119) + The Final Problem (Q228119)is part of canoncanon of Sherlock Holmes (Q2316684)
- But I'd be fine with the former too. Other opinions? – Shisma (talk) 16:39, 9 January 2024 (UTC)
- Yeah Trade (talk) 16:09, 9 January 2024 (UTC)
- ah, you mean like a character? – Shisma (talk) 15:55, 9 January 2024 (UTC)
- I don't understand. do you have an example? – Shisma (talk) 15:42, 9 January 2024 (UTC)
- I literally said nothing about statements Trade (talk) 14:50, 9 January 2024 (UTC)
- Support, an important property for fiction.--Arbnos (talk) 14:00, 11 January 2024 (UTC)
- Support I have a slight preference for this one. But Trade's proposal has the advantage that it is possible to make it explicit that something is not part of a certain canon (using canon status:non-canon, restricted to the canon using applies to work (P10663), for instance). With this property we can only express that something is not part of a certain canon if we are complete with respect to that canon. We can use <no value> if there is really no canon this work belongs to, but couldn't there be a Simpsons-Sherlock-Holmes-Crossover that is considered part of the Simpsons canon but not part of the Sherlock Holmes canon? (I could not think of a real example and I'm not sure if this is a likely scenario). How would we express this? - Valentina.Anitnelav (talk) 12:47, 13 January 2024 (UTC)
- I suppose proving that something is not part of any canon is like proving that something doesn't exist. Maybe it is part of my headcanon that I published on my entirely irrelevant weblog in the late 90s. There would also be an infinite number of works that are not part of a canon. For instance: every Episode of the Simpsons is not in the Sherlock Holmes Canon. I'd say we can add unknown if we don't have a complete catalog of canon items. – Shisma (talk) 16:59, 13 January 2024 (UTC)
- In general you're right. I was just thinking of cases where one would expect that a work is part of a canon but it is not. E.g. for every episode of The Simpsons (Q886) it may be expected that it is part of The Simpsons canon (or I would expect that), but Treehouse of Horror II (Q2376730) is not. It is somehow more interesting that an episode of The Simpsons (Q886) is not part of The Simpsons canon than that it is part of the canon. It is somehow similar to does not have part (P3113) - Valentina.Anitnelav (talk) 08:03, 19 January 2024 (UTC)
- Valentina.Anitnelav: you mean like not found in (P9660) (opposite of described by source (P1343))? – Shisma (talk) 13:00, 19 January 2024 (UTC)
- Yes, or like this (depending on how you think of the relationship between a canon and its "parts"). On the other hand I think my Simpsons-Holmes-expample (where we could not use <no value>) would be very, very rare. Probably we can just forget about it. - Valentina.Anitnelav (talk) 15:34, 19 January 2024 (UTC)
- No, lets keep in mind that is not part of canon could be useful in the future for edge cases – Shisma (talk) 16:13, 19 January 2024 (UTC)
- Yes, or like this (depending on how you think of the relationship between a canon and its "parts"). On the other hand I think my Simpsons-Holmes-expample (where we could not use <no value>) would be very, very rare. Probably we can just forget about it. - Valentina.Anitnelav (talk) 15:34, 19 January 2024 (UTC)
- Valentina.Anitnelav: you mean like not found in (P9660) (opposite of described by source (P1343))? – Shisma (talk) 13:00, 19 January 2024 (UTC)
- In general you're right. I was just thinking of cases where one would expect that a work is part of a canon but it is not. E.g. for every episode of The Simpsons (Q886) it may be expected that it is part of The Simpsons canon (or I would expect that), but Treehouse of Horror II (Q2376730) is not. It is somehow more interesting that an episode of The Simpsons (Q886) is not part of The Simpsons canon than that it is part of the canon. It is somehow similar to does not have part (P3113) - Valentina.Anitnelav (talk) 08:03, 19 January 2024 (UTC)
- I suppose proving that something is not part of any canon is like proving that something doesn't exist. Maybe it is part of my headcanon that I published on my entirely irrelevant weblog in the late 90s. There would also be an infinite number of works that are not part of a canon. For instance: every Episode of the Simpsons is not in the Sherlock Holmes Canon. I'd say we can add unknown if we don't have a complete catalog of canon items. – Shisma (talk) 16:59, 13 January 2024 (UTC)
- Weak support - Weak support. Preferring Trade's proposal. My focus (admittedly I've been on a bit of a wiki-break lately due to IRL priorities) around here has been with works such as the Touhou Project, where canonicity can be fuzzy at times, thanks to the series mostly being the work of just one developer. The first five games in the series were made for the Japanese PC-98 computer in the late '90s. After the PC-98 was discontinued around the turn of the millennium, the series "started over" with 2002's Touhou Koumakyou: the Embodiment of Scarlet Devil, featuring Reimu and Marisa (the deuteragonists) but none of the other characters from the PC-98 games. Only two PC-98 characters (Yuuka Kazami and Alice Margatroid) have ever reappeared in a later Windows game, with both having been redesigned to some degree. When asked about the PC-98 games' canonicity, ZUN (the sole creator) has stated multiple times that (paraphrased) "PC-98 canon applies as long as Windows canon doesn't conflict with it." However ZUN doesn't always section everything off, and the fans are left with "Is this still canon or is this decanonized?" type-of-questions. (For example, Yuuka Kazami had a big mansion-esque building in Touhou 4 (a PC-98 game). She (eventually) reappeared in Touhou 9 (a Windows game)... just in a big flower field, with no sign of a mansion. Did it get removed (decanonized) and replaced with the flower field? Did we just not see it in Touhou 9? Who knows! So would "stuff" (I use the term loosely) discarded in such a manner - never outright stated to have been decanonized, but partially overwritten and otherwise not brought up again - be considered part of a "canon of X" item, or do they not? Or would they be part of a separate "canon of X (old)" item? -- Kurzov (talk) 17:28, 16 January 2024 (UTC)
- I don't know any particulars of this franchise. But here's my interpretation and how I suppose the proposed property would apply: There is apperently a work that "is part of a canon" and another work that is "(only partially) part of a canon". Sorry for repeating myself: this property is only concerned with works, not anyone's interpretation of what can be seen in them. In short, i'd model this with the qualifier: nature of statement (P5102) partially (Q100349848) –Shisma (talk) 19:18, 16 January 2024 (UTC)
- We could probably use an item named "loose canon" for this. Trade (talk) 02:41, 28 March 2024 (UTC)
- I don't know any particulars of this franchise. But here's my interpretation and how I suppose the proposed property would apply: There is apperently a work that "is part of a canon" and another work that is "(only partially) part of a canon". Sorry for repeating myself: this property is only concerned with works, not anyone's interpretation of what can be seen in them. In short, i'd model this with the qualifier: nature of statement (P5102) partially (Q100349848) –Shisma (talk) 19:18, 16 January 2024 (UTC)
last appearance[edit]
Description | last work featuring a fictional character or item |
---|---|
Represents | last appearance (Q125686982) |
Data type | Item |
Example 1 | Mary Camden (Q125682212)→…And Thank You (Q114523400) |
Example 2 | Dane Vogel (Q56613123)→Saints Row: Gat out of Hell (Q17911588) |
Example 3 | Victor Vance (Q2469911)→Grand Theft Auto: Vice City (Q94671) |
Example 4 | Troy McClure (Q1504550)→Bart the Mother (Q2617345) |
Example 5 | Mermaid Man (Q93186548)→Patrick-Man! (Q29566244) |
Example 6 | Leonard Burton (Q107024611)→The Hundred Year Play (Q109677017) |
Example 7 | Bulldog (Q60649159)→Saints Row IV (Q13060351) |
Wikidata project | WikiProject Video games (Q8485882) |
Motivation[edit]
This seemed needed--Trade (talk) 04:10, 29 April 2024 (UTC)
- Notified participants of WikiProject Narration Notified participants of WikiProject Fictional universes--Trade (talk) 04:13, 29 April 2024 (UTC)
- Notified participants of WikiProject Video games--Trade (talk) 04:14, 29 April 2024 (UTC)
Discussion[edit]
- Support some implementation of this but we should consider how to minimise data staleness if a new addition to a franchise is released (perhaps unexpectedly). This isn't a problem with first appearance (P4584). Arlo Barnes (talk) 05:33, 29 April 2024 (UTC)
- number of episodes (P1113) would be a better example Trade (talk) 20:43, 29 April 2024 (UTC)
- Question I think this is doable in a different way, by present in work (P1441) we get an appearance on works, by publication date (P577) we get the publication date of the work. We can always sort by publication date to get the last appearance, doable in sparql and in lua both. If the point is to mark that it is known that it won't appear again (or is now forgotten) why not adding a qualifier ⟨ The Adventures of Tintin (Q744536) ⟩ present in work (P1441) ⟨ Tintin and the Picaros (Q612595) ⟩or something like that
followed by (P156) ⟨ no value Help ⟩- What would be the issue with that ? Too complicated ? Do not cover all cases ? author TomT0m / talk page 09:43, 30 April 2024 (UTC)
- The only way we would be able to infer this would be if the vast majority of items about works and episodic works had a complete dataset. And you would still all of said items that a character have appeared in to be linked to them or vice versa which is even more rare Trade (talk) 23:43, 30 April 2024 (UTC)
- Oppose Using P1441 with qualifiers as TomT0m said should be enough. --Tinker Bell ★ ♥ 16:15, 30 April 2024 (UTC)
- There isn't much of a benefit unless one consider the existence of new non-identifier properties to be actively harmful to the project. --Trade (talk) 00:06, 1 May 2024 (UTC)
- Support This property is widely used in infoboxes of fictional characters on many wikipedias (enwiki, a couple on ruwiki). It will be difficult if not impossible to output the value of P1441 with the latest date to this param. Also, TV series characters often have a last episode listed, and there is no practice on WD to list dozens/hundreds of episodes in the character's P1441. Solidest (talk) 03:58, 8 May 2024 (UTC)
- I would even say that P1441 itself needs to be redesigned. Filling in all kinds of media, individual works, episodes of works, series of works of one media, series of works of cross-media (franchise) - this is all bad practice, because of which there are now difficulties with tuning infoboxes. Solidest (talk) 04:02, 8 May 2024 (UTC)
- The problem is not on the data model, but in the infoboxes. We shouldn't model the data considering only Wikipedia usecases, Wikidata does not exist only to fullfill Wikipedia infoboxes and tables. The real problem is that now there isn't a way to make SPARQL queries from Lua templates for query data that has complex relationships. Changing the data model will not fix that. There is no problem on the way P1441 is used, because all of these uses express the same relationship, and SPARQL can be used to get further data, based in whether the predicate is a franchise, collection or a single creative work. --Tinker Bell ★ ♥ 23:42, 8 May 2024 (UTC)
- @Tinker Bell: So you're suggesting that it's correct and optimal to list thousands of episodes in which fictional characters participated, so that only one of them has the qualifier “last”? That seems like the wrong model and the wrong method for wikidata to me. It would be also strange to specify a TV series, franchise, series of works, individual episodes at the same time, and if you add the tags first and last appearance, it would be a complete mess. And if we specify characters in the items of distinct episodes and then make a query in such a way as to find the most recent release date, then again how to be and how to universalize if a character appears in several series, movies or franchises? The P1551 solution seems completely non-optimal and unstable for such cases. I don't think it would be possible to make a universal query in SPARQL that would work for every character for all kinds of media and works. There will be nuances everywhere, and each sphere will need different queries, also possibly ignoring unrelated or unofficial appearances. Or appearances in an advertisements that are likely not needed in the character's item, but may be filled in the item of such advertisement, etc. And by contrast, specifying such data in a specific property is the optimal solution to maintain data where the character last appeared. What you are proposing has serious problems in the data modeling, that in an attempt to simplify and not add specific property - it turns out to be impossible to make a unified approach for extracting this data from WD. This is a data modeling problem, not an infobox problem. Solidest (talk) 02:27, 1 June 2024 (UTC)
- Could you elaborate? I am confused what the issue you are referring to is Trade (talk) 22:43, 10 May 2024 (UTC)
- @Trade: This is probably a problem only for infoboxes, regarding the intersection of data on large series/franchises and nested individual works. The header of character infoboxes indicates that this is a character from X series or X franchise - and it's a specific parameter connected to P1551 - "series" or "franchise". For example Eric Cartman (Q47352) is from South Park (Q54622175) (franchise), or since there is no article on franchise on Russian wikipedia, therefore the series is listed there. P1551 suggests that it covers anything where the character appeared - franchise, TV series, films, video games, and Tinker Bell also suggests adding 300+ episodes of the TV series, and probably seasons of the TV series? In this form, the property on wikipedia cannot be used with auto-displaying such data in the infobox, and the data itself seems visually cluttered in items imo. Although it would probably be possible to retrieve all fictional characters that have what is p31=series/franchise in P1551 via SPARQL query. So it's probably a problem of infoboxes (but maybe also a schema problem for fictional characters data). By the way, there is also media franchise (P8345) and it's not clear how to use it with characters either. It seems like they just don't have it filled in right now. Solidest (talk) 02:43, 1 June 2024 (UTC)
- @TomT0m: would you like to give your opinion? @Tinker Bell: any changes in your opinion? Regards, ZI Jony (Talk) 03:53, 27 May 2024 (UTC)
- @ZI Jony: I mantain my opinion. @Trade: I'm saying that, if we have already an x property, it's redundant to have also an last x property. I also see that a lot of support for these proposals come from people that just want to show that info in Wikipedia infoboxes, but then, the real problem is not the lack of properties, but the Wikibase Client extension inability to let template creators to make SPARQL queries to get the result and filter, not only by the last appearance, but also the first appearance, or also last appearance in x country television. --Tinker Bell ★ ♥ 04:25, 27 May 2024 (UTC)
- The problem is not on the data model, but in the infoboxes. We shouldn't model the data considering only Wikipedia usecases, Wikidata does not exist only to fullfill Wikipedia infoboxes and tables. The real problem is that now there isn't a way to make SPARQL queries from Lua templates for query data that has complex relationships. Changing the data model will not fix that. There is no problem on the way P1441 is used, because all of these uses express the same relationship, and SPARQL can be used to get further data, based in whether the predicate is a franchise, collection or a single creative work. --Tinker Bell ★ ♥ 23:42, 8 May 2024 (UTC)
- I would even say that P1441 itself needs to be redesigned. Filling in all kinds of media, individual works, episodes of works, series of works of one media, series of works of cross-media (franchise) - this is all bad practice, because of which there are now difficulties with tuning infoboxes. Solidest (talk) 04:02, 8 May 2024 (UTC)
- Support adding some form of this, whether it be through a new property or otherwise -Kurzov (talk) 13:37, 13 May 2024 (UTC)
- Support good point.--Frettie (talk) 22:49, 14 May 2024 (UTC)
- Comment I boldly modified the infobox to change the data type to Item. Looking at the examples, this is clearly what Trade wanted. —Tacsipacsi (talk) 18:28, 26 May 2024 (UTC)
Creative work[edit]
- See also: Wikidata:WikiProject Infoboxes/works
- Software products and brands, see: Wikidata:WikiProject Infoboxes/terms
- Books, see: Wikidata:WikiProject Books
promodj.com album ID[edit]
Description | Album page on promodj.com - this is a popular website, started in 2005. |
---|---|
Data type | External identifier |
Example 1 | Earth's Attraction (Q106247051) -> complexnumbers/groups/700597 |
Example 2 | The Morning of the New Millennium (Q106199063) -> complexnumbers/groups/700625 |
Example 3 | MISSING |
Formatter URL | https://promodj.com/$1 |
Motivation[edit]
We already have PromoDj ID - but only for person, this proposal is for album, after I will create a new proposal - for track. Vitaly Zdanevich (talk) 20:38, 11 May 2024 (UTC)