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/12. |
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)
- 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)
ID Centre d'Etudes Picasso
[edit]Description | identifier of a resource of the Picasso Museum |
---|---|
Represents | Musée Picasso (Q743206) |
Data type | External identifier |
Example 1 | Paul en Arlequin (Q3898246)→c160000000000554 |
Example 2 | Jaime Sabartés (Q130752354)→c160000000018448 |
Example 3 | La berceuse (Q124703839)→c160000000001183 |
Number of IDs in source | 54387 in november 2024 |
Formatter URL | https://cep.museepicassoparis.fr/ark:/43781/$1 |
Motivation
[edit]The Musée Picasso (Q743206) has a new website for its collections and all documents (photographs, archives, books...) : https://cep.museepicassoparis.fr/decouvrir-le-cep . It's a unique website with ark URLs. The main website museepicassoparis.fr links only to this new website where ressources are linked and wil be maintained in a sustainable manner. According to this discussion instead of changing the current property Musée Picasso artwork ID (P6358), which is linked with M&M, it is proposed to create a new one.
Notified participants of WikiProject Visual arts,@Thierry Caro, Nomen ad hoc, PKM, Marianne Casamance, ديفيد عادل وهبة خليل 2, Gamaliel: participants to the previous property proposal. Best regards Shonagon (talk) 20:06, 1 November 2024 (UTC)
Discussion
[edit]- Support PKM (talk) 08:24, 2 November 2024 (UTC)
- Support Interesting to know about the issue with the old property. I guess going forward it will be useful to have both if the former one is for objects on show or something. Looks useful. Jane023 (talk) 08:43, 2 November 2024 (UTC)
- Support Creating a new property for the CEP id seems to be the best solution, although we are not really talking about a new id here. The ids of the objects that are part of the museum’s collections (subject to inventory) are generated by the museum’s collections management software. They do not depend on the website. Example:
- https://www.navigart.fr/picassoparis/artwork/160000000000554
- https://cep.museepicassoparis.fr/ark:/43781/c160000000000554
- The only difference here is the prefix “c” (for “collection” I guess) in the CEP record. This difference is due to the fact that this new website aggregates contents that come from different sources:
- the publication tool of the museum’s collections management software (Gcoll, Navigart): ids with prefix “c” like the one in the example above.
- the documentation, audiovisual and archive database (Ligeo): ids with prefix “aligeo-” (example)
- the library records that seem to be attributed a RBMN id: ids with prefix “b” (example)
- (maybe there are other cases I missed)
- So, it would seem to me that the old id is still THE id for objects subject to inventory and should not be deprecated. At the same time, creating the new property, as suggested, would allow Wikidata to link to the corresponding CEP record, as well as to create new Wikidata items for objects not subject to inventory (documentation, private archives etc.), whose records are being published for the first time. I am not sure whether this CEP id should be considered as an object id or more likely as a record id.
- Ebakogianni (talk) 17:55, 2 November 2024 (UTC)
- Ebakogianni As you point, the ID is indeed the same for artworks of the collection; only the root URL is changing. That's why, there was hesitation to propose a new property. But as you explain, the old database retains its value, including structured value and Mix'n'match as bridge to wikidata. The new database has a larger scope, is promoted by the museum that undertakes to maintain URLs with the use of ark. Best regards Shonagon (talk) 14:51, 3 November 2024 (UTC)
Collectie Nederland ID
[edit]Description | aggregation identifier in the Collectie Nederland database |
---|---|
Data type | External identifier |
Example 1 | Girl with a Pearl Earring (Q185372)→mauritshuis/670 |
Example 2 | The Night Watch (Q219831)→amsterdam-museum/SA-7392 |
Example 3 | The Night Watch (Q219831)→rijksmuseum/oai-rijksmuseum.nl-SK-C-5 |
Example 4 | At Eternity's Gate (Q500554)→kroller-muller/44553 |
Formatter URL | https://data.collectienederland.nl/resource/aggregation/$1 |
Motivation
[edit]Collectie Nederland is an aggregator with over 6 million objects in it including at least 30.000 paintings. We probably have most of them, but probably still quite a few missing paintings and a good way to check coverage for the Netherlands. Multichill (talk) 16:33, 8 December 2024 (UTC)
Notified participants of WikiProject Visual arts
Discussion
[edit]- Support Looks useful! I also just recently discovered this website. Jane023 (talk) 19:01, 8 December 2024 (UTC)
- Support This has come up on DifoolBot's list of unrecognized URLs as we have over 22,000 items with collectienederland.nl URLs in the references. There seems to be two URL formats:
https://data.collectienederland.nl/page/aggregation/$1
andhttps://www.collectienederland.nl/page/aggregation/$1
which give exactly same looking pages. You can also replace "page" with "resource" and it redirects you to the right page. Samoasambia ✎ 16:43, 9 December 2024 (UTC)
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
Danbooru tag
[edit]Description | tag for an item on Danbooru |
---|---|
Represents | Danbooru (Q64514853) |
Data type | External identifier |
Example 1 | Flandre Scarlet (Q41561041)→flandre_scarlet |
Example 2 | Nessa (Q116707789)→nessa_(pokemon) |
Example 3 | Rem (Q28859527)→rem_(re:zero) |
Example 4 | My Hero Academia (Q104918088)→boku_no_hero_academia |
Example 5 | Zenless Zone Zero (Q111983519)→zenless_zone_zero |
Example 6 | Kill la Kill (Q13637192)→kill_la_kill |
Example 7 | skirt (Q2160801)→skirt |
Example 8 | nagamaki (Q1304426)→nagamaki |
Example 9 | ponytail (Q653122)→ponytail |
Source | https://safebooru.donmai.us/tags |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://safebooru.donmai.us/wiki_pages/$1 |
URL match pattern | ^https:\/\/(?:safebooru|danbooru)\.donmai\.us\/wiki_pages\/([a-z0-9_!"#$%&'()+.\/:;<=>?@\[\\\]^`{|}~-]+)
|
See also | Archive of Our Own tag (P8419) |
Wikidata project | WikiProject Anime and manga (Q7098843) |
Motivation
[edit]Danbooru is an imageboard for anime/manga-style art, it has a very extensive tagging system along with a wiki that describes many of the tags.
Tags can be categorised as general, character, copyright, artist or meta. I have only provided examples for character, copyright and general - though it should be possible to match artists with pixiv user ID (P5435). The wiki articles are usually short, reasonably well-written and often provide useful external links related to the topic.
Note that the true domain for the website is danbooru.donmai.us, and the safebooru.donmai.us (official SFW mirror) domain is just being used to prevent accidentally exposing people to NSFW content - I'm not sure which formatter URL would be best for the property.
--Lewis Hulbert (talk) 14:08, 18 October 2024 (UTC)
Discussion
[edit]- Notified participants of WikiProject Anime and Manga. --Lewis Hulbert (talk) 14:10, 18 October 2024 (UTC)
- Support Useful property for sure due to the large amount of image data provided and its applicability to characters and media franchises. IntensionalLogican (talk) 04:03, 20 October 2024 (UTC)
- Support Linking to the SFW version by default would be preferable. Jotamide (talk) 21:58, 30 October 2024 (UTC)
AniSearch character ID
[edit]Description | identifier for a character in AniSearch database |
---|---|
Represents | AniSearch (Q55517348) |
Data type | External identifier |
Domain | Q95074 |
Allowed values | [1-9]\d* |
Example 1 | Noriko Takaya (Q124629290)AniSearch character ID is3506 |
Example 2 | Nadia la Arwall (Q101342467)AniSearch character ID is49348 |
Example 3 | Rei Ayanami (Q1140524)AniSearch character ID is1 |
Source | https://www.anisearch.com/ |
External links | Use 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]. |
Planned use | Identifying characters with corresponding character IDs on AniSearch. |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://www.anisearch.com/character/$1 |
Robot and gadget jobs | Yes |
See also | AniDB character ID (P5648), AnimeClick character ID (P5847), MyAnimeList character ID (P4085) |
Motivation
[edit](Add your motivation for this property here and your signature) – The preceding unsigned comment was added by Z. Patterson (talk • contribs) at 02:35, December 3, 2024 (UTC).
Discussion
[edit]Notified participants of WikiProject Anime and Manga
- @Z. Patterson: please fill out the template more completely and add a motivation section for this. ArthurPSmith (talk) 19:09, 3 December 2024 (UTC)
Support. As one of the leading anime and manga databases, this property is intended to be comprehensive in its field. --Wiccio (talk) 07:22, 6 December 2024 (UTC)
Music
[edit]- See also: Wikidata:WikiProject Music
- Other relevant projects: Category:Music WikiProjects
Zvuk album ID
[edit]Description | identifier for an album or single on Zvuk |
---|---|
Represents | Zvuk (Q105047698) |
Data type | External identifier |
Domain | musical release (Q2031291), release group (Q108346082) |
Example 1 | L'Emprise (Q114656238)→33387960 |
Example 2 | In the Zone (Q27166)→3322072 |
Example 3 | Akustichesky Albom (Q4060256)→8125614 |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://zvuk.com/release/$1 |
See also | Zvuk artist ID (P10524) |
Wikidata project | Zvuk (Q105047698) |
Motivation
[edit]Уже существует свойство для страниц исполнителей, но пока нет свойства для самих альбомов.
Discussion
[edit]- It also covers singles, so it rather should named "Zvuk release ID". Solidest (talk) 03:50, 28 November 2024 (UTC)
DNCI label ID
[edit]Description | ID used on DNCI website to define a music label |
---|---|
Data type | External identifier |
Domain | Q18127 |
Example 1 | Fantasy (Q3739374) → 376 |
Example 2 | Odeon (Q706013) → 23 |
Example 3 | Q3637713 → 730 |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | http://discografia.dds.it/scheda_etichette1.php?ida=$1 |
See also | National Discography of Italian Song artist/group ID (P2510), National Discography of Italian Song work ID (P4027) |
Wikidata project | WikiProject Music (Q5830855) |
Motivation
[edit]There are properties to link to DNCI database for releases and for artists but not for labels. --★ → Airon 90 19:14, 7 December 2024 (UTC)
Notified participants of WikiProject Italy
Discussion
[edit]- Support. --Wiccio (talk) 11:07, 8 December 2024 (UTC)
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
Game Jolt username
[edit]Description | username on Game Jolt |
---|---|
Represents | Game Jolt (Q28444637) |
Data type | External identifier |
Domain | human (Q5), group of humans (Q16334295), video game developer (Q210167), video game publisher (Q1137109) |
Allowed values | ^[\w-]+$ |
Example 1 | NomnomNami (Q92000350)→Nomnom-Nami |
Example 2 | Angela He (Q107359444)→Zephy0 |
Example 3 | Studio Peaches (Q130478353)→studiopeaches |
Example 4 | Pirate Software (Q113101662)→PirateSoftware |
Example 5 | Killmonday Games HB (Q24080817)→Killmondaygames |
Expected completeness | always incomplete (Q21873886) |
Implied notability | Wikidata property for an identifier that does not imply notability (Q62589320) |
Formatter URL | https://gamejolt.com/@$1 |
URL match pattern | ^https?:\/\/(?:www\.)?gamejolt\.com\/@([\w-]+)
|
See also | Game Jolt game ID (P12072), itch.io developer profile (P8176) |
Single-value constraint | yes |
Distinct-values constraint | yes |
Wikidata project | WikiProject Video games (Q8485882) |
Motivation
[edit]Game Jolt is a platform for indie games, we already have Game Jolt game ID (P12072) and this property can be used to identify developers/publishers/etc. of those games.
--Lewis Hulbert (talk) 12:13, 30 October 2024 (UTC)
Discussion
[edit]- Notified participants of WikiProject Video games. --Lewis Hulbert (talk) 12:16, 30 October 2024 (UTC)
- Support Matthias M. (talk) 12:42, 30 October 2024 (UTC)
- Support -wd-Ryan (Talk/Edits) 15:41, 30 October 2024 (UTC)
- Support ~ RampantSpirit (talk) 18:52, 30 October 2024 (UTC)
- Support ―Applsdev (talk) (contribs) 08:16, 5 November 2024 (UTC)
Battle.net game ID
[edit]Description | identifier of this game on Battle.net |
---|---|
Represents | Battle.net (Q725130) |
Data type | External identifier |
Domain | video game (Q7889) |
Example 1 | Overwatch (Q18515944)→overwatch (end time - October 4, 2022) |
Example 2 | Overwatch 2 (Q73163646)→overwatch (start time - October 4, 2022) |
Example 3 | Call of Duty®: Modern Warfare® III - Tracer Pack: Ghost Punk Pro Pack (Q131406347)→call-of-duty-modern-warfare-iii-wz-ghost-punk-pro-pack |
Example 4 | Crash Bandicoot 4: It's About Time (Q96574138)→crash-bandicoot-4 |
Example 5 | World of Warcraft®: Free Trial (Q131406401)→world-of-warcraft-free-trial |
Source | https://eu.shop.battle.net/en-us |
Formatter URL | https://eu.shop.battle.net/en-gb/product/$1 |
See also | EA games ID (P8261), Ubisoft Store game ID (P8268) |
Wikidata project | WikiProject Video games (Q8485882) |
Motivation
[edit]Discussion
[edit]- Support I guess the number of games is stretched thin, but "see also" justifies it. If we already have EA and Ubisoft exclusive shops, then there is no real argument against Blizzard. Matthias M. (talk) 14:37, 8 December 2024 (UTC)
- I can create more items if you want Trade (talk) 16:09, 8 December 2024 (UTC)
- Support Nothing to add. --CommanderKefir (talk) 22:24, 8 December 2024 (UTC)
- I can create more items if you want Trade (talk) 16:09, 8 December 2024 (UTC)
Literature
[edit]- See also: Wikidata:WikiProject Books
- Other relevant projects: Category:Book WikiProjects
Innovating Knowledge manuscript ID
[edit]Description | identifier of a manuscript in the Innovating Knowledge database |
---|---|
Data type | External identifier |
Domain | item |
Allowed values | M plus 4 digits (regex: ^M\d{4}$ ) |
Example 1 | St Dunstan's Classbook (Q55287054) → M0445 |
Example 2 | Paris, Bibliothèque nationale de France, Latin 1008 (Q125135736) → M0238 |
Example 3 | Tripartite Psalter (Q62053634) → M0233 |
Source | https://zenodo.org/records/13827506 |
Number of IDs in source | 507 |
Expected completeness | eventually complete (Q21873974) |
Implied notability | Wikidata property for an identifier that suggests notability (Q62589316) |
Formatter URL | https://db.innovatingknowledge.nl/#detail/$1 |
Applicable "stated in"-value | Innovating Knowledge (Q130602682) |
Single-value constraint | yes |
Distinct-values constraint | yes |
Motivation
[edit]Innovating Knowledge (https://db.innovatingknowledge.nl/) is a database about the manuscripts of Isidore of Seville's Etymologiae. In September 2024 they released their data under CC BY 4.0 (https://zenodo.org/records/13827506). This database holds a lot of original information and would be very useful to have as a reference on Wikidata.
Notified participants of WikiProject Manuscripts Jonathan Groß (talk) 14:50, 27 October 2024 (UTC)
Discussion
[edit]- Support! --Epìdosis 15:06, 27 October 2024 (UTC)
- Support --Marsupium (talk) 18:08, 27 October 2024 (UTC)
- Support Angayubagia (talk) 01:32, 28 October 2024 (UTC)
- @Jonathan Groß, Epìdosis, Marsupium, Angayubagia: Done: Innovating Knowledge manuscript ID (P13100). --Lewis Hulbert (talk) 15:06, 28 October 2024 (UTC)
- I was going to add my support with a question, but the proposal is already closed. @Lewis Hulbert: I feel that barely 24 hours is a bit short for the community to meaningfully review a property proposal. Please consider extending it for other cases. —-Jahl de Vautban (talk) 08:03, 29 October 2024 (UTC)
- @Lewis Hulbert: previous ping likely didn’t work. —-Jahl de Vautban (talk) 08:05, 29 October 2024 (UTC)
- @Jahl de Vautban: The proposal was created on the 21st of October so it was open 7 days before creation. But, in hindsight, I probably would have left it a little longer if I had noticed the ping and support votes were all in the past 24 hours. --Lewis Hulbert (talk) 11:56, 29 October 2024 (UTC)
- @Lewis Hulbert: my bad you’re right, I only considered on the ping without checking the history. —-Jahl de Vautban (talk) Jahl de Vautban (talk) 12:05, 29 October 2024 (UTC)
- @Lewis Hulbert, Jahl de Vautban: My bad! I created this proposal on 21 October but it took a few days to get the details right. I only transcluded it on 27 October, which I thought should have been regarded as the beginning of the evaluation period. Anyway, many thanks to all involved! Jonathan Groß (talk) 11:09, 20 November 2024 (UTC)
- @Jahl de Vautban: The proposal was created on the 21st of October so it was open 7 days before creation. But, in hindsight, I probably would have left it a little longer if I had noticed the ping and support votes were all in the past 24 hours. --Lewis Hulbert (talk) 11:56, 29 October 2024 (UTC)
Scientific literature
[edit]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
health/hit points
[edit]Description | health or armor points of this video game, board game or role-playing game character |
---|---|
Represents | health (Q668136) |
Data type | Quantity |
Example 1 | Adam Warlock (Q130232493) > 250 |
Example 2 | Infested Girl (Q130232401) > 16 |
Example 3 | Mercy (Q28592386) > 225 |
Example 4 | Sniper (Q128164668) > 90 |
Example 5 | Sniper (Q128164668) > 50 (applies to part > armor (Q130232601)) |
Example 6 | Claude Speed (Q2721597) > 10 |
Example 7 | Claude (Q14805400) > 100 |
Example 8 | Zoey (Q65924442) > 100 |
Example 9 | Creeper (Q13164404) > 20 (applies to work (P10663) > Minecraft (Q49740)) |
Example 10 | Cacodemon (Q108324133) > 400 (applies to work (P10663) > Doom (Q189784)) |
Wikidata project | WikiProject Video games (Q8485882) |
Motivation
[edit]We have no way of modeling this so a property is needed
- Notified participants of WikiProject Fictional universes--Trade (talk) 21:52, 3 September 2024 (UTC)
- Notified participants of WikiProject Video games--Trade (talk) 21:52, 3 September 2024 (UTC)
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)
- 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)
- @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)
- 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)
- 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)
- 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. ChristianKl ❪✉❫ 19:35, 22 September 2024 (UTC)
- @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)
- 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)
- 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)
- Comment This could be used on all items of Minecraft mobs. -wd-Ryan (Talk/Edits) 22:02, 3 September 2024 (UTC)
- 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)
- How about we just widen the scope to include board and role-playing games? Trade (talk) 22:50, 3 September 2024 (UTC)
- @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)
- 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)
- 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)
- 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)
- 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)
- That's something along the lines I meant. EdoAug (talk) 17:25, 4 September 2024 (UTC)
- @EdoAug, @Lewis Hulbert, @Matthias M., @Wd-Ryan, would you like to give your opinions? Regards, ZI Jony (Talk) 19:21, 16 September 2024 (UTC)
- 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)
- @EdoAug, @Lewis Hulbert, @Matthias M., @Wd-Ryan, would you like to give your opinions? Regards, ZI Jony (Talk) 19:21, 16 September 2024 (UTC)
- That's something along the lines I meant. EdoAug (talk) 17:25, 4 September 2024 (UTC)
- 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)
- 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)
- 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)
- @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)
- How about we just widen the scope to include board and role-playing games? Trade (talk) 22:50, 3 September 2024 (UTC)
- 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)
- 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)
- 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)
- 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)
- 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)
- "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)
- 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)
- 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)
- 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)
- 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)
- 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)
- "not meaningful to non-players" is not a good reason against. -- Jerimee (talk) 23:47, 3 October 2024 (UTC)
- 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)
- 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)
- Support (without comment) Jerimee (talk) 23:47, 3 October 2024 (UTC)
- 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)
- As long as the properties are broad enough to be able to be applied to a wide range of fiction items i don't think it's an issue. As it is, hitpoints is a fairly generic statistic that exists in virtually all games featuring combat Trade (talk) 06:46, 23 November 2024 (UTC)
- Comment How would this work for characters with variable health points? For example, Nick Valentine (Q107028136) of Fallout 4 has health points which are dependent on player level. His HP is calculated as follows: 225 + (([Player Level] - 10) × 5). 1857a (talk) 23:59, 29 October 2024 (UTC)
- I would just stick with the base HP. People can read the fandom page themselves if they want to calculate something more specific Trade (talk) 06:47, 23 November 2024 (UTC)
game damage
[edit]Motivation
[edit]We have no way of modeling this so a property is needed
- Notified participants of WikiProject Fictional universes--Trade (talk) 21:52, 3 September 2024 (UTC)
- Notified participants of WikiProject Video games --Trade (talk) 22:18, 3 September 2024 (UTC)
Discussion
[edit]- Comment Where did you source those example values from? Matthias M. (talk) 10:21, 4 September 2024 (UTC)
- @Trade:, could you please clarify the comment? Regards, ZI Jony (Talk) 19:22, 16 September 2024 (UTC)
- If Matthias wish to rally against the use of Fandom as a reference this is not the appropriate place to do so. --Trade (talk) 11:40, 18 September 2024 (UTC)
- Trade, I am sorry to say that I personally did not expect such a reply especially from you. It's simple, if you have any source then YES (with reference), else NO! Matthias M., any comment based on the response? Regards, ZI Jony (Talk) 03:00, 21 September 2024 (UTC)
- Using Fandom article ID (P6262) would be a valid reference. Having none is unacceptable though. Matthias M. (talk) 09:42, 21 September 2024 (UTC)
- We already had users adressing this exact thing in the above proposal. I'll rather we just move the discussion somewhere else instead of going through it in every single proposal ad infinitum Trade (talk) 18:28, 21 September 2024 (UTC)
- Trade, I am sorry to say that I personally did not expect such a reply especially from you. It's simple, if you have any source then YES (with reference), else NO! Matthias M., any comment based on the response? Regards, ZI Jony (Talk) 03:00, 21 September 2024 (UTC)
- If Matthias wish to rally against the use of Fandom as a reference this is not the appropriate place to do so. --Trade (talk) 11:40, 18 September 2024 (UTC)
- @Trade:, could you please clarify the comment? Regards, ZI Jony (Talk) 19:22, 16 September 2024 (UTC)
- Comment needs to be broadened to all games, both board games and role-playing ones. I don't think it can be used for real weapons though, or any other physical object, as its very much a gaming concept. Vicarage (talk) 17:50, 7 October 2024 (UTC)
- Comment The name of the property should be something related to a game like "game damage", or similar, to reduce the number of times the property will be used in the wrong way. Ainali (talk) 18:15, 7 October 2024 (UTC)
- +1 PKM (talk) 21:53, 21 October 2024 (UTC)
- Done. Are you willing to cast a vote now? Trade (talk) 23:33, 2 November 2024 (UTC)
- +1 PKM (talk) 21:53, 21 October 2024 (UTC)
Creative work
[edit]ISLRN
[edit]Description | International Standard Language Resource Number |
---|---|
Represents | ISLRN (Q30592540) |
Data type | External identifier |
Allowed values | \d{3}-\d{3}-\d{3}-\d{3}-\d |
Example 1 | TIMIT (Q7670405) => 664-033-662-630-6 |
Example 2 | Chinese Proposition Bank 1.0 (Q125926939) => 731-738-468-307-2 |
Example 3 | The AQUAINT Corpus of English News Text (Q124812853) => 153-002-267-999-9 |
Formatter URL | https://www.islrn.org/resources/$1/ |
Motivation
[edit]Persistent Unique Identifier for Language Resources.--GZWDer (talk) 12:03, 12 November 2024 (UTC)
Discussion
[edit]- See also: Wikidata:WikiProject Infoboxes/works
- Software products and brands, see: Wikidata:WikiProject Infoboxes/terms
study or design for this work
[edit]Motivation
[edit]This property, inverse of study or design for (P6606) will makes it possible to identify this studies or design in the finished work item. It was already suggested but not proposed. It was said that based on (P144) could be used but this use has several issues :
- based on (P144) has already an inverse property derivative work (P4969),
- based on (P144) has a to much scope, which does not allow easy queries and infobox uses,
- based on (P144) should requires the use of a qualifier to identify, that is not done an probably will not be,
- cannot apply to depicts (P180) with study qualification.
With a specific property, as sketches are often about part of an artwork, we could precise the study or design at the depicts (P180) level, what we cannot do properly at present. For the above example, in the painting item Apollo in the Forge of Vulcan (Q247282) there is a claim depicts (P180) : Apollon (Q37340) which could be qualified to the preparation work : Study for the head of Apollo (Q4473883).
The creation of this property would involve work on the p144 already filled in, in which I would be happy to participate.
Discussion
[edit]Notified participants of WikiProject Visual arts
- Support Shonagon (talk) 11:54, 11 November 2024 (UTC)
- Support --BeatrixBelibaste (talk) 12:50, 11 November 2024 (UTC)
- Comment If you still need a qualifier anyway, then I don't see the difference with based on (P144)/derivative work (P4969). I guess I would approve a "related work" property that leaves the whole time issue (what came first?) neutral. In your example, it's not clear from the creation dates in both paintings that one head of Apollo is a study or inspired by the other painting, because the inception dates are so far apart. I do find it frustrating that it's so hard to model the statements to form the relationships. You can use the qualifier applies to part (P518) to specify which part of the painting is meant. I think it is perfectly valid to use based on (P144) multiple times for group portraits. You can use qualifiers to pin it down. For large paintings, multiple studies were made. I guess I don't think derivative work (P4969) is too precise, though it's mostly used on close copies. When it comes to partial copies I think it's OK to keep using it. Things get tricky when the same portraits are used over and over again but in different contexts, such as in the multiple versions of paintings of the protestant reformers such as The Protestant Reformers (Q43463266). Many of these were based on prints. Jane023 (talk) 14:02, 11 November 2024 (UTC)
- Thanks for you reply. In this example, the information state that this a study. Ther eare many others example where there is a preparative work: Diana begs Jupiter not to subject her to the hymen (Q29840528) has for study Q27831918 ; Ophelia (Q21191005) has Study for Ophelia (Q21192341). Of course for several portraits, or others artworks linked (for example The siesta (after Millet) (Q11826275) based on (P144) Noonday Rest (Q19696670), based on (P144) is valid and more the property tyo use. For a qualification with based on (P144) on depicts (P180) we can not use qualifications like to specify that it a study, because we can not qualify a qualification. That was I was pointing on the depicts (P180) : Apollon (Q37340) example. A specific property would resolve this issue and not being too tricky as you said. The need to link a specific depicts (P180) explicitly to a study lead to this proposal. Best regards. Shonagon (talk) 14:38, 11 November 2024 (UTC)
- Jane023 More examples are added to more explain the need with depicts (P180) statements and to show the potentiality with the proposed property. Best regards Shonagon (talk) 18:45, 11 November 2024 (UTC)
- Support OK I see what you mean about not being able to qualify a qualifier. For queries it could be useful to handle such partial studies this way. I will support this now. Jane023 (talk) 15:58, 12 November 2024 (UTC)
- Support (Note i generally like inverse properties.)- PKM (talk) 23:43, 11 November 2024 (UTC)
- Comment The suggested label is "study or design" or "has study or design" I guess. Certainly a useful property, it's just that I am not sure if we should mix the type of relationship between two works with the type of work. Ideally I would prefer a label with a broader scope, for example "preparatory work", in order to express the relationship, and let the instance of (P31) statement of the related work specify whether this is a drawing, a model, a manuscript, a musical score or any other kind of work that was a step in the creative process of the related finished work. Note: My original intention when I started writing this comment was to support the proposal. I have a visual arts museum background and, in this perspective, "study or design" makes perfect sense. But when I think about it in the context of Wikidata as a whole, I find it difficult to decide. Ebakogianni (talk) 21:49, 13 November 2024 (UTC)
- Hello @Ebakogianni Indeed the scope should be broad to "preparatory work". This is a question of label because for the French label, it is proposed as you say "étude ou travail préparatoire". The concept is the same and that could improved by English speakers. In practice with the property, we could link easily a lot from artworks or details to studies, where Wikidata has a great potential. Best regards Shonagon (talk) 18:39, 16 November 2024 (UTC)
- Support Hi @Shonagon. Thanks for your reply. Indeed, the french label is more accurate and applicable to creative works that do not necessarily belong to the visual arts. Ebakogianni (talk) 19:58, 16 November 2024 (UTC)
- Hello @Ebakogianni Indeed the scope should be broad to "preparatory work". This is a question of label because for the French label, it is proposed as you say "étude ou travail préparatoire". The concept is the same and that could improved by English speakers. In practice with the property, we could link easily a lot from artworks or details to studies, where Wikidata has a great potential. Best regards Shonagon (talk) 18:39, 16 November 2024 (UTC)
thesis submitted for
[edit]Description | academic degree for which a thesis or dissertation is submitted |
---|---|
Data type | Item |
Domain | item, thesis (Q1266946) |
Allowed values | academic degree (Q189533) |
Example 1 | A Survey of Radial Velocities in the Zodiacal Dust Cloud (Q28971627)→Doctor of Philosophy (Q752297) |
Example 2 | L'Église et les clercs face aux béguines et aux béghards du Rhin supérieur du XIVe siècle au XVe siècle (Q43257720)→doctorate in History (Q27639256) |
Example 3 | On stochastic processes (Q113686414)→Doctor of Science (Q2248352) |
Example 4 | French Books in Early Australian Public and Private Collections (Q116950303)→Master of Arts (Q2091008) |
Example 5 | Flight Speeds and Energetics of Seven Bird Species (Q76550143)→Master of Science (Q950900) |
Example 6 | Some aspects of early castle building in Scotland (Q105097652)→Master of Philosophy (Q1527520) |
See also | thesis submitted to (P4101), academic degree (P512), grants (P5460) |
Motivation
[edit]Academic thesis is written and submitted to obtain an academic degree, but the property describing this relationship is lacking. Some people try to represent this relationship (see [1]) using academic degree (P512), main subject (P921), or even instance of (P31):
- academic degree (P512): this describes academic degree that the person holds, and expanding the domain to thesis is bad idea in my opinion.
- main subject (P921): degree is a goal or purpose, not a topic or subject of thesis.
- instance of (P31): thesis itself is not a degree.
Another way is using a subclass of thesis (Q1266946) for each kind of academic degree (Q189533) (see [2]); however, there is no way connecting such subclass and degree item. So it is desirable to create a new property. --Mzaki (talk) 05:14, 17 November 2024 (UTC)
Notified participants of WikiProject Higher education
Discussion
[edit]- Comment Another way to link this is via the item for the thesis writer, where you could have a educated at (P69) statement qualified by academic degree (P512) and academic thesis (P1026). Here's a query with examples of this. Some of the results seem odd, presumably errors in data entry somewhere. But I'm not sure a new property is necessary here since it's already being done another way? ArthurPSmith (talk) 14:55, 19 November 2024 (UTC)
- When we describe someone's thesis, there are at least 3 elements: human (Q5) instance, thesis (Q1266946) instance, and academic degree (Q189533) subclass. We could have the following relationships, and I propose the last one:
- human (Q5)academic thesis (P1026)thesis (Q1266946) (possibly 1:n), and, in reverse, thesis (Q1266946)author (P50)human (Q5) (ideally 1:1 but might be 1:n)
- human (Q5)academic degree (P512)academic degree (Q189533) (possibly 1:n)
- thesis (Q1266946)→academic degree (Q189533) (ideally 1:1 but might be 1:n)
- The relationship 3 is an intrinsic property of thesis (Q1266946), independent of the fact that the author holds the degree. Imagine that a submitted but failed thesis (I think failed thesis usually does not satisfy WD:N criteria, but there could be exceptional cases).
- From a practical viewpoint, WikiData data model for the relationships 1 & 2 is not firmly established. One can describe it, as shown by @ArthurPSmith, in human (Q5)educated at (P69)higher education institution (Q38723)
academic degree (P512)academic degree (Q189533) academic thesis (P1026)thesis (Q1266946), which works well for course-based degree. But sometimes there are degrees granted to non-student who submits a thesis (frequent in Japan, for example). In such cases, we can describe it human (Q5)academic degree (P512)academic degree (Q189533) academic thesis (P1026)thesis (Q1266946) conferred by (P1027)higher education institution (Q38723). Also one can describe these as direct relationships like human (Q5)academic degree (P512)academic degree (Q189533) & human (Q5)academic thesis (P1026)thesis (Q1266946). So inferring the relationship 3 from 1 & 2 is not a trivial task, especially for person holds multiple degrees. On the contrary, introducing a new property for the relationship 3 is quite straightforward, since it is an intrinsic property of thesis (Q1266946).
- When we describe someone's thesis, there are at least 3 elements: human (Q5) instance, thesis (Q1266946) instance, and academic degree (Q189533) subclass. We could have the following relationships, and I propose the last one:
- Mzaki (talk) 01:34, 20 November 2024 (UTC)
Comment We created an application profile for our theses and dissertations: https://www.wikidata.org/wiki/Wikidata:WikiProject_PCC_Wikidata_Pilot/University_of_Washington/Application_Profiles/Dissertations_and_Theses. We use instance of (P31) = written work (Q47461344) (or other appropriate class such as sheet music sheet music (Q187947)), and either doctoral thesis (Q187685) or master's thesis (Q1907875). However, this doesn't specify the specific degree such as Ph.D., Ed.D., D.Mus., etc. The specific degree is given in the graduate student's item who wrote the thesis. AdamSeattle (talk) 14:16, 26 November 2024 (UTC)
- Do you mean a thesis is not bound to specific degree at the time of submission in your system, and the committee or the institution decide which degree should be granted to the thesis author, so students cannot expect either Ph.D or D.Mus would be granted before the decision? In my country, almost all thesis is submitted for obtaining specific degree, since there are different standards for granting different degree and students write their thesis to satisfy the standard for specific degree, that means a thesis is bound to specific degree at the time of submission. That's why I need new wikidata property for describing such intrinsic property of thesis (Q1266946), as I explained above. Mzaki (talk) 15:24, 26 November 2024 (UTC)
- No, I didn't mean that. The thesis is certainly submitted for a particular degree, known in advance. What I meant was that we associate the degree with the person in their item and in the thesis item we can only state that it is an instance of a master's thesis or doctoral thesis. I agree that there is no current way to say which specific degree a thesis was submitted for (M.A., M.S., Ph.D., Ed.D., etc.). If accepted your proposal would provide the means to do that, although perhaps it's a bit redundant with the information in the person item. But if your proposal is approved, we would probably add it to our application profile to use in our thesis items. AdamSeattle (talk) 17:28, 26 November 2024 (UTC)
- Thank you for clarification. As for the redundancy, I think we have to tolerate it, because the relationships among human (Q5), thesis (Q1266946), academic degree (Q189533), and higher education institution (Q38723) is not so simple as we instantly imagine. There are thesis-based and non-thesis-based degrees. Both students and non-students are granted thesis-based degrees. There are accepted and failed theses. We need a set of properties sufficient to capture these diverse relationships, which may seem redundant in simpler cases. Mzaki (talk) 01:45, 27 November 2024 (UTC)
- Another comment for the redundancy. We already have thesis (Q1266946)thesis submitted to (P4101)higher education institution (Q38723), although this relationship could, possibly, be inferred via the person item using educated at (P69) or conferred by (P1027) for simpler cases. But this is not an easy task, as similar in the case of thesis (Q1266946)→academic degree (Q189533). My proposal is in line with the introduction of thesis submitted to (P4101), and I think the redundancy claimed is an acceptable price to pay for the practical benefits, as in the case of thesis submitted to (P4101). Mzaki (talk) 02:23, 27 November 2024 (UTC)
- No, I didn't mean that. The thesis is certainly submitted for a particular degree, known in advance. What I meant was that we associate the degree with the person in their item and in the thesis item we can only state that it is an instance of a master's thesis or doctoral thesis. I agree that there is no current way to say which specific degree a thesis was submitted for (M.A., M.S., Ph.D., Ed.D., etc.). If accepted your proposal would provide the means to do that, although perhaps it's a bit redundant with the information in the person item. But if your proposal is approved, we would probably add it to our application profile to use in our thesis items. AdamSeattle (talk) 17:28, 26 November 2024 (UTC)
- Support Ok I think these are good arguments in favor, this can't hurt. ArthurPSmith (talk) 18:53, 27 November 2024 (UTC)
role named as
[edit]Motivation
[edit]As you might be aware almost all works have different ways of naming the roles of it's contributors in the credits even if the role means the same. Other works have roles that are so specific that they have no items on Wikidata.
Having this property would allow us to show how the roles of subjects were described in the individual works, both as a way to provide additional context but also to allow us to show the roles even when no appropriate item exists and to make it easier to find said subjects in the credits--Trade (talk) 07:05, 23 November 2024 (UTC)
Discussion
[edit]- Thought you might be interested @Moebeus:--Trade (talk) 16:36, 23 November 2024 (UTC)
- It is indeed interesting. My immediate thought: this would be
meaninglessvery confusing unless it's specifically tied to an edition of a work, right? Moebeus (talk) 18:07, 23 November 2024 (UTC)- I haven't encountered this issue so far. Either way we should always go with whichever release is the original/official Trade (talk) 18:42, 23 November 2024 (UTC)
- It is indeed interesting. My immediate thought: this would be
- If we already do this for movie cast roles I guess it's only logical to do an extension into video games too. It will lead to more text in how roles appear in video games. Can help us make roles better, so this data may help us editors more than it might help others(which is not a bad thing, life can be very difficult for editors like us who are expected to be either experts or know a thing or two). I find subject named as being very useful when naming video games on Wikidata because we see identifiers like Steam, how they name a game and then on igdb it may appear differently, especially if the main language isn't English. That helps in creating "Also named as" where people may search for something but it may turn up 0 results, which can be very frustrating so knowing what names roles have, we can better know how to name a role.
- Support Don't see an issue, as long as they include structured data as well. More information is good. -wd-Ryan (Talk/Edits) 18:37, 6 December 2024 (UTC)