Shortcut: WD:PP/WORK

Wikidata:Property proposal/Creative work

From Wikidata
Jump to navigation Jump to search


Property proposal: Generic Authority control Person Organization
Creative work Place Sports Sister projects
Transportation Natural science Computing Lexeme

See also

[edit]

This page is for the proposal of new properties.

Before proposing a property

  1. Search if the property already exists.
  2. Search if the property has already been proposed.
  3. 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.
  4. Select the right datatype for the property.
  5. Read Wikidata:Creating a property proposal for guidelines you should follow when proposing new property.
  6. 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

  1. Once consensus is reached, change status=ready on the template, to attract the attention of a property creator.
  2. Creation can be done 1 week after the creation of the proposal, by a property creator or an administrator.
  3. See property creation policy.


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]
   On hold
Descriptionauthority identification for an object in the collections of the National Historical Museums of Sweden
Data typeExternal identifier
Allowed values[0-9A-Z]{8}-[0-9A-Z]{4}-[0-9A-Z]{4}-[0-9A-Z]{4}-[0-9A-Z]{12}
Example 1Streiff (Q10681657)https://samlingar.shm.se/object/A4B754D2-5CB6-4FA1-997A-970250E32044
Example 2Mosjömadonnan (Q10589526)https://samlingar.shm.se/object/7C505995-EBF5-4106-BBEE-17F52BB3EA83
Example 3Elizabeth Reliquary (Q26253636)https://samlingar.shm.se/object/8BA2743C-5065-438B-9FAA-D854606DB716
Sourcehttps://samlingar.shm.se
Planned useMatching and creating items in the collection that are depicted on Wikimedia Commons
Number of IDs in source1 300 000
Expected completenessno label (Q21873886 (always incomplete))
Formatter URLhttps://samlingar.shm.se/object/$1
See alsoNationalmuseum Sweden artwork ID (P2539)
Single-value constraintyes
Distinct-values constraintyes

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)[reply]

Discussion

[edit]
 Support Azad Karimi (talk) 13:56, 7 April 2022 (UTC)[reply]
 Support LinneaKarlberg (talk) 13:05, 7 April 2022 (UTC)[reply]
 Support Eva L Vedin (talk) 13:08, 7 April 2022 (UTC)[reply]
 Support Elinor Rajka (talk) 19:13, 7 April 2022 (UTC)[reply]
 Support Azad Karimi (talk) 13:56, 7 April 2022 (UTC)[reply]
 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)[reply]
Sorry, we did not know. LinneaKarlberg (talk) 07:19, 8 April 2022 (UTC)[reply]
 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)[reply]
@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)[reply]
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)[reply]
 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)[reply]
Hello Abbe98 Hello, 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)[reply]
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)[reply]
@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)[reply]
@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)[reply]
We at NHM are all on board with this approach instead of several Properties. LinneaKarlberg (talk) 08:09, 29 April 2022 (UTC)[reply]
Sounds like an excellent idea. Many thanks Abbe98 . /André Costa (WMSE) (talk) 08:51, 24 May 2022 (UTC)[reply]
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)[reply]

National Archives of Sweden persistent identifier

[edit]
   On hold
Descriptionpersistent identifier for objects in the National Archives of Sweden main archival database
RepresentsNational Archives of Sweden (Q1724971)
Data typeExternal identifier
Domainarchival resource (Q106815942), document (Q49848), work (Q386724)
Allowed valuesBase62-encoded UUID
Example 1No 2. Elbing. (Q111517198)eYHMeAFOm4sNVmxKK3M5L2
Example 2No 3. Elbing (Q111517379)0zDW3BS0Gw9Haap2yUVspE
Example 3No 4. Danzigk wir es Eltere und newer werck (Q111519390)zmQwWNi2ag9DQGJxnSVmD0
Implied notabilityWikidata property for an identifier that does not imply notability (Q62589320)
Formatter URLhttps://sok.riksarkivet.se/arkiv/$1
See alsoSwedish National Archive reference code (P5324)
Applicable "stated in"-valueNational Archives of Sweden (Q117288060)
Single-value constraintyes
Distinct-values constraintyes

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)[reply]

Discussion

[edit]

It has been created as Swedish National Archive agent ID (P9713) se discussion - Salgo60 (talk) 07:43, 21 March 2023 (UTC)[reply]

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)[reply]
@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... ?
- Salgo60 (talk) 20:35, 24 March 2023 (UTC)[reply]
Looks like Nils left Riksarkivet and the whole thing died. I tried to ask about Riksarkivets terms but get odd answers see issue #22 - Salgo60 (talk) 10:53, 11 June 2024 (UTC)[reply]

Cinematography

[edit]
See also: Wikidata:WikiProject Movies
Other relevant projects: Category:Movie WikiProjects

Television

[edit]
See also: Wikidata:WikiProject Movies

Anime and manga

[edit]
See also: Wikidata:WikiProject Anime and Manga

Music

[edit]
See also: Wikidata:WikiProject Music
Other relevant projects: Category:Music WikiProjects

Spirit of Metal band ID

[edit]
   Under discussion
Descriptionidentifier of a metal band the Spirit of Metal database
Representsmusical group (Q215380)
Data typeExternal identifier
DomainSpirit of Metal (Q2311104)
Example 1Babymetal (Q11190781)Baby_Metal
Example 2Lordi (Q23471)Lordi
Example 3Metallica (Q15920)Metallica
Example 4Yōsei Teikoku (Q247634)Yousei_Teikoku
External linksUse in sister projects: [ar][de][en][es][fr][he][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd][en.wikt][fr.wikt].
Number of IDs in source118193
Expected completenesseventually complete (Q21873974)
Formatter URLhttps://www.spirit-of-metal.com/en/band/$1

Motivation

[edit]

Discussion

[edit]

Rate Your Music track ID

[edit]
   Under discussion
Descriptionidentifier of a music or audio track in the RateYourMusic database
Representsaudio track (Q7302866)
Data typeExternal identifier
DomainRate Your Music (Q1145963)
Example 1Gangnam Style (강남스타일) (Q130464715)강남스타일-gangnam-style
Example 2Despacito (Q130464775)luis-fonsi/despacito
Example 3We Are the World (USA for Africa) (Q130464784)usa-for-africa/we-are-the-world
Example 4My Heart Will Go On (Q105838473)celine-dion/my-heart-will-go-on-love-theme-from-titanic
External linksUse in sister projects: [ar][de][en][es][fr][he][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd][en.wikt][fr.wikt].
Number of IDs in sourceUnknown
Expected completenesseventually complete (Q21873974)
Formatter URLhttps://rateyourmusic.com/song/$1
See alsoRate Your Music work ID (P11665), Rate Your Music release ID (P8392)

Motivation

[edit]

Discussion

[edit]

Board game

[edit]
See also: Wikidata:WikiProject Board Games

Video game

[edit]
See also: Wikidata:WikiProject Video games
Other relevant projects: Category:Video game WikiProjects

Push Square series ID

[edit]
   Under discussion
Descriptionidentifier of a video game series in the Push Square database
Data typeExternal identifier
DomainPush Square (Q108733456)
Example 1Saints Row (Q683841)saints-row
Example 2Assassin's Creed (Q420292)assassin%27s-creed
Example 3Overwatch (Q73398918)overwatch
External linksUse in sister projects: [ar][de][en][es][fr][he][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd][en.wikt][fr.wikt].
Number of IDs in sourceUnknown
Expected completenessalways incomplete (Q21873886)
Formatter URLhttps://www.pushsquare.com/games/browse?title=series%3A$1

Motivation

[edit]

Discussion

[edit]

VG247 series ID

[edit]
   Under discussion
Descriptionidentifier of a video game series in the VG247 database
Data typeExternal identifier
DomainVG247 (Q4052505)
Example 1Silent Hill (Q236821)silent-hill
Example 2Battlefield (Q474587)battlefield
Example 3Grand Theft Auto (Q132730)grand-theft-auto
External linksUse in sister projects: [ar][de][en][es][fr][he][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd][en.wikt][fr.wikt].
Number of IDs in sourceUnknown
Expected completenessalways incomplete (Q21873886)
Formatter URLhttps://www.vg247.com/video-game-franchises/$1

Motivation

[edit]

Discussion

[edit]

Literature

[edit]
See also: Wikidata:WikiProject Books
Other relevant projects: Category:Book WikiProjects

‎TEES ID

[edit]
   Under discussion
DescriptionDictionary of Turkish literature works
RepresentsQ119505599
Data typeExternal identifier
Example 1Q2876569ask-i-memnu-halit-ziya-usakligil
Example 2Q30686608kral-in-sozlugu-rasulid-hexaglot
Example 3Q1753178kutadgu-bilig
Example 4Q6065643ma-rifetname
Sourcetees.yesevi.edu.tr
External linksUse in sister projects: [ar][de][en][es][fr][he][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd][en.wikt][fr.wikt].
Number of IDs in source8.085
Formatter URLhttps://tees.yesevi.edu.tr/madde-detay/$1
See alsoTEİS ID

Motivation

[edit]

An encyclopedia about Turkish literary works. All of the items were written by academics. --Devrim ilhan (talk) 17:09, 10 October 2024 (UTC)[reply]

Discussion

[edit]

Scientific literature

[edit]

Video

[edit]

Image

[edit]
See also: Wikidata:WikiProject Visual arts

Podcast

[edit]
See also: Wikidata:WikiProject Podcasts

Theatre

[edit]
See also: Wikidata:WikiProject Performing arts, Wikidata:WikiProject Theatre

Fiction

[edit]
See also: Wikidata:WikiProject Fictional universes, Wikidata:WikiProject Narration
For projects about specific universes, see: Category:Fiction WikiProjects

health/hit points

[edit]
   Under discussion
Descriptionhealth or armor points of this video game, board game or role-playing game character
Representshealth (Q668136)
Data typeQuantity
Example 1Adam Warlock (Q130232493) > 250
Example 2Infested Girl (Q130232401) > 16
Example 3Mercy (Q28592386) > 225
Example 4Sniper (Q128164668) > 90
Example 5Sniper (Q128164668) > 50 (applies to part > armor (Q130232601))
Example 6Claude Speed (Q2721597) > 10
Example 7Claude (Q14805400) > 100
Example 8Zoey (Q65924442) > 100
Example 9Creeper (Q13164404) > 20 (applies to work (P10663) > Minecraft (Q49740))
Example 10Cacodemon (Q108324133) > 400 (applies to work (P10663) > Doom (Q189784))
Wikidata projectWikiProject Video games (Q8485882)

Motivation

[edit]

We have no way of modeling this so a property is needed

Discussion

[edit]
  •  Comment is this really within Wikidata:Scope? You can only look this up from the game data which makes this original research. Also how do you compare this across games? 100 hitpoints might be a lot for one game and not so much for a game where the weapons kill you at first shot. Matthias M. (talk) 21:58, 3 September 2024 (UTC)[reply]
    It can also be referenced from wikis about the game. Original research isn't the only option. -wd-Ryan (Talk/Edits) 22:01, 3 September 2024 (UTC)[reply]
    @Wd-Ryan: Are you referring to Fandom/Wikia wikis and other player-maintained wikis? These are considered unreliable (due to it being user-generated content) on many other Wikimedia projects. Is this "allowed for" on Wikidata? EdoAug (talk) 22:48, 3 September 2024 (UTC)[reply]
    I'm not sure if it makes the statement ineligible for inclusion altogether, but most identifiers can be entered as a reference. These websites, however, do not make the subject of the item notable. Either way, it isn't accurate to say health points wouldn't be found in any other external resource. For example, this random news article I quickly found references hitpoints (Not that this specific one is applicable).
    I'd also be fine with having this data in an existing property if there's a good one. -wd-Ryan (Talk/Edits) 23:11, 3 September 2024 (UTC)[reply]
    If someone for whatever reason wishes to ban Fandom as a source then this is not the right place to discuss it anyways Trade (talk) 22:30, 5 September 2024 (UTC)[reply]
    Wikidata has no general policy that declares player-maintained wikis to be unreliable. In practice it depends on the individual source. When it comes to information about these statistics I would expect those Wikis to be very reliable. ChristianKl19:35, 22 September 2024 (UTC)[reply]
    Naturally in some games 100 hitpoints will be a lot and in others very little. This is an issue of scaling and balancing and not something that affects the truthness of the statement Trade (talk) 22:41, 3 September 2024 (UTC)[reply]
  •  Comment This could be used on all items of Minecraft mobs. -wd-Ryan (Talk/Edits) 22:02, 3 September 2024 (UTC)[reply]
  •  Comment What about using properties such as has characteristic (P1552) (or something similar) and quantity (P1114) for the plethora of (video, board, role-playing) game attributes? A similar property is personality trait of fictional character (P9652). EdoAug (talk) 22:34, 3 September 2024 (UTC)[reply]
    How about we just widen the scope to include board and role-playing games? Trade (talk) 22:50, 3 September 2024 (UTC)[reply]
    @Trade: I'm referring to other types of attributes, such as strength, charisma, armour, running speed, mana, agility, dexterity, and the many other traits that characters may have in video games (but also other types of games), as well as health (and damage). Instead of creating bespoke properties for these, why not just have one for "gameplay trait of fictional character or item", or just use one of the aforementioned properties (and qualifier)? EdoAug (talk) 22:58, 3 September 2024 (UTC)[reply]
    Mechanics such as hit points and damage are largely universal across game genres and (arguable) inherent to most of them. Being able to spend skill points across multiple attributes for your characters is not Trade (talk) 23:17, 3 September 2024 (UTC)[reply]
    Not all usage of other attributes include spending skill points. Health and damage are not static numbers, either – many non-player characters in RPG video games have an ever-changing array of numbers, such as Jaina Proudmoore (Q819585), whose health is different in various expansions of World of Warcraft, as well as spin-off games such as Heroes of the Storm and Hearthstone, where her damage and mana (resource) is also relevant.
    I am simply offering an alternative way of portraying these numbers in a way that may include a wider spectrum of similar traits. I don't really think specific properties are necessary, but I'm not too opposed to them either. I think it would be better to have a more open-ended property that would accommodate for multiple types of statistics (including health and damage... and mana, agility, running speed, level, et cetera). EdoAug (talk) 23:28, 3 September 2024 (UTC)[reply]
    I agree we need a property with a wider scope, there's going to be plenty of stats that only apply to items from specific games so a general purpose property in the same area as has characteristic (P1552) would likely work best. Taking Pokémon items as an example (I believe we have over 1000 of those at this point) it would be advantageous to be able to provide their base statistics: HP, Attack, Defense, Special Attack, Special Defense and Speed. Since these stats are quite relevant to gameplay it should be easy to find sources without having to resort to fan wikis. --Lewis Hulbert (talk) 02:22, 4 September 2024 (UTC)[reply]
    I agree with you, Lewis. Some kind of "has statistic" property with a number data type and units for each statistic type. (health point, attack point, etc.) -wd-Ryan (Talk/Edits) 17:15, 4 September 2024 (UTC)[reply]
    That's something along the lines I meant. EdoAug (talk) 17:25, 4 September 2024 (UTC)[reply]
    @EdoAug, @Lewis Hulbert, @Matthias M., @Wd-Ryan, would you like to give your opinions? Regards, ZI Jony (Talk) 19:21, 16 September 2024 (UTC)[reply]
    We need some kind of scope for that type of property to work. Otherwise it just becomes an unworkable mess Trade (talk) 14:49, 18 September 2024 (UTC)[reply]
  •  Oppose This type of data belongs in a specific fan wiki. The numbers aren't meaningful to non-players. Dexxor (talk) 00:02, 4 September 2024 (UTC)[reply]
    Wikidata is contributed by people active in different topics and have very different goals of contribution, so "not meaningful to non-players" is not a good reason against it. However we does have a Wikia equalvent of Wikidata (Wikibase Cloud), so I have no position for or against the property.--GZWDer (talk) 11:20, 4 September 2024 (UTC)[reply]
    The values are only comparable within other actors of the same game so a per game https://wikiba.se/ is the only option that makes sense to me. I am biased because I think this is the equivalent of en:WP:GAMECRUFT and I am not at all interested in these values as well. Matthias M. (talk) 19:28, 16 September 2024 (UTC)[reply]
    There are plenty of property proposals that doesnt interest me. Doesnt mean that it somehow doesnt belong on Wikidata Trade (talk) 11:39, 18 September 2024 (UTC)[reply]
    Actually, this whole proposal process is mostly not about validity, but if people find it interesting. You can also get rejected when nobody replies. Also note that I did not vote against your proposal even though I raised concerns. On Wikipedia this kind of content would be removed and Fandom wiki (Q106513246) took over the niche. Maybe this wants to live in a Wikidata instanced hosted by Fandom, Inc. (Q20466202) instead? I am not sure where to draw the line and if this has been discussed already. I think even video game character classes like Sniper (Q128164668) and Sniper (Q56363410) are a bit of a stretch of what I assume this website is about. Matthias M. (talk) 09:54, 21 September 2024 (UTC)[reply]
    "Actually, this whole proposal process is mostly not about validity, but if people find it interesting." Dunno. If i were to oppose any identifiers for scholarly papers with the reasoning that the subject bored me i can imagine it would get some push back
    Either way i think it would be beneficial for both of us if we had something like Wikidata:Arguments to avoid in property proposals Trade (talk) 18:20, 21 September 2024 (UTC)[reply]
    The thing with these numbers is that they are not comparable across game franchises. I can't imagine a situation where you would want to query for them on Wikidata instead of processing a table of health values collected by fans of the game, especially considering it's unrealistic to create items for every game entity that has health points. While there's nothing wrong with this property per se, we also need to take into account whether it's useful (external identifiers are often useful because they help with disambiguation and data reconciliation). Dexxor (talk) 21:51, 21 September 2024 (UTC)[reply]
    I cant imagine a situation where someone would want to compare health points across completely different games in the first place. If one wishes to query this property, limiting the results to characters from specific works or franchises shouldn't be too hard Trade (talk) 16:43, 24 September 2024 (UTC)[reply]
    "not meaningful to non-players" is not a good reason against. -- Jerimee (talk) 23:47, 3 October 2024 (UTC)[reply]
  •  Support (without comment) Jerimee (talk) 23:47, 3 October 2024 (UTC)[reply]
  •  Comment So far, fictional objects have been primarily modeled based on lore/story information, like we would describe/model a real object. So the focus was mostly on the fiction aspect, not the specific technical implementations in games or other works. But health points, damage, mana, strength, dexterity or number of weapon slots are purely gameplay-specfic technical details that developers apply to game characters for gameplay and balancing-related reasons and don't necessatily correlate with their lore-version. Adding properties like this and the other proposals could IMO shift the focus of the items to the rather specific, purely technical details of individual implementations. --2A02:810B:581:C300:6C68:1127:8BA5:DCF9 17:26, 8 October 2024 (UTC)[reply]

damage

[edit]

Motivation

[edit]

We have no way of modeling this so a property is needed

Discussion

[edit]

identifiant d'un document audiovisuel dans le catalogue de l'Inathèque (fr) – (Please translate this into English.)

[edit]
   Ready Create
Descriptionidentifiant d'un document audiovisuel dans le catalogue de l'Inathèque (dépôt légal de l'audiovisuel public) (fr) – (Please translate this into English.)
RepresentsInathèque(3149791)
Data typeExternal identifier
Domainémission(11578774)
Example 1Aqui sian bèn du 13 juin 2021(130363491)RD_13123012.001
Example 2Vaqui(130343801)RE_RAC03025398
Example 3Vaqui du 7 avril 1984(130394405)RE_RAC86000042
Formatter URLhttps://catalogue.ina.fr/doc/TV-RADIO/$1
See alsoidentifiant de vidéo Ina(P3194), identifiant France Télévisions d'une émission(P13024), Radio France program ID(P13026)
VIGNERON
Ayack
Ash Crow
Tubezlob
PAC2
Thierry Caro
Pymouss
Alphos
GAllegre
Jean-Frédéric
Manu1400
Marianne Casamance
Nattes à chat
Pierre André
Bouzinac
Jsamwrites
Baidax
LearnKnowGive1
Mathieu Kappler
Daieuxetdailleurs
Archives nationales DJI
Jmax
LearnKnowGive1
Koxinga
Maxime
Framawiki
Legonin

Notified participants of WikiProject France. Maxime 07:31, 2 October 2024 (UTC)[reply]

  •  Support. If the identifier could indeed be interesting, I would not encourage the creation of all Wikidata elements per episode which would be excessive and would not moreover meet the structural need. — Baidax 💬 07:43, 2 October 2024 (UTC)[reply]
    Bonjour Baidax. Nous sommes déjà d'accord sur le fait qu'une telle propriété serait utile pour mieux référencer et décrire tous les programmes de l'audiovisuel public français. Concernant les émissions/épisodes, cela me semble mériter la discussion. En tout cas, je crois savoir que Deansfa (avec d'autres) en a créé un certain nombre, et cela me semble utile et nullement excessif. Après tout, je crois que Wikidata ambitionne de proposer une somme du savoir humain. Bien à toustes, Maxime 08:02, 2 October 2024 (UTC)[reply]
  •  Support. --Deansfa (talk) 19:08, 3 October 2024 (UTC)[reply]

Creative work

[edit]
See also: Wikidata:WikiProject Infoboxes/works
Software products and brands, see: Wikidata:WikiProject Infoboxes/terms

‎bais

[edit]
   Under discussion
DescriptionIndicates a specific form of bias present in a media source, organization, or document, such as false balance, slant, or omission, affecting the representation of information.
Representsbias (Q742736)
Data typeItem
Example 1Daily Mail (Q210534)biassensationalism (Q427532)
Example 2CNN (Q48340)biasselection bias (Q284172)
Example 3Cass Review (Q125456040)biascisnormativity (Q123689471)
Example 4Breitbart News (Q4960434)biaspopulism (Q180490)
Example 5Fox News (Q186068)biaspopulism (Q180490)
Planned useWithin the next month, this property will be applied to media outlets such as the BBC, allowing for the identification and categorization of specific biases in their reporting. This will provide a structured way to track biases across different media sources and enhance the analysis of how such biases influence the public narrative on various issues.
Robot and gadget jobsBots or gadgets could assist by automatically tagging media sources or documents with the appropriate bias label based on predefined criteria. For example, this property could be used by platforms like Ground News or other media bias tracking websites to collect and categorize bias data consistently. Automated tools could also cross-check this property with other related data fields (e.g., political leaning, funding sources) to ensure consistency and accuracy in bias identification across Wikidata entries.

Motivation

[edit]

This property aims to standardize the identification of various forms of bias in media, organizations, and documents. By labeling specific biases such as sensationalism, false balance, or selection bias, it enables greater transparency and more precise data analysis. Researchers, fact-checkers, and policymakers will benefit from a clearer understanding of how biases impact the representation of information. This tool is essential for improving the quality of public discourse, ensuring accountability, and promoting accuracy in media and organizational outputs.

Discussion

[edit]