Wikidata:Property proposal/Creative work


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

See alsoEdit

This page is for the proposal of new properties.

Before proposing a property

  1. Check if the property already exists by looking at Wikidata:List of properties (research on manual list) and Special:ListProperties.
  2. Check if the property was previously proposed or is on the pending list.
  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. Start writing the documentation based on the preload form below and add it in the appropriate section.
Caveat
Do not use the Visual editor, because it will mess up the content of your request (the order of the template parameters will be shuffled and paragraphs are concatenated as one long string of text).

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 proposal, by a property creator or an administrator.
  3. 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 2022/05.

CinematographyEdit

Afisha.ru movie IDEdit

   Ready Create
Descriptionидентификатор фильма на Афиша.ру (ru) – (Please translate this into English.)
RepresentsAfisha (Q4072772)
Data typeExternal identifier
Template parameterTemplate:Afisha ru (Q22840986)
Domainaudiovisual work (Q2431196), film (Q11424), television series (Q5398426), animated film (Q202866), animated series (Q581714), animated feature film (Q29168811), television program (Q15416)
Allowed units[0-9]/+
Example 1Game of Thrones (Q23572)259078
Example 2The Simpsons (Q886)259079
Example 3The Avengers (Q182218)205920
Sourcehttps://afisha.ru
External linksUse in sister projects: [ar][de][en][es][fr][he][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd].
Planned usefor usage in stated in (P248) and for Template:Authority control (Q3907614)
Number of IDs in source75912
Expected completenesseventually complete (Q21873974)
Formatter URLhttps://www.afisha.ru/movie/$1
Robot and gadget jobsMix'x'match
See alsoKinopoisk film ID (P2603)
Applicable "stated in"-valueAfisha (Q4072772)
Single-value constraintyes
Distinct-values constraintyes
Wikidata projectRussia, Movies

MotivationEdit

Afisha.ru was since in April 1999. Initially, it was published as a magazine about cultural events in the largest cities of Russia. It is one of the few publications in the country that has successfully switched to the Internet - since 2015, the publication of the magazine of the same name has been discontinued. The cinema database includes over 70,000 films where users can post their reviews. MasterRus21thCentury (talk) 16:35, 6 May 2022 (UTC)

DiscussionEdit

  •   Support --Trade (talk) 22:32, 7 May 2022 (UTC)
  •   Support - Kareyac (talk) 15:25, 10 May 2022 (UTC)

Rusakters.ru IDEdit

   Ready Create
Descriptionidentifier on the website Российские и советские актёры
Representsrusakters.ru (Q55121940)
Data typeExternal identifier
Template parameterTemplate:Rusakters.ru (Q22863849)
Domainhuman (Q5)
Allowed units[a-z]+
Example 1Nikita Yefremov (Q4177512)efremov-nikita
Example 2Alexander Belyavsky (Q2067930)belyavskiy-aleksandr
Example 3Tatiana Doronina (Q4166919)doronina-tatyana
Sourcehttps://rusakters.ru
External linksUse in sister projects: [ar][de][en][es][fr][he][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd].
Planned usefor usage in stated in (P248) and for Template:Authority control (Q3907614)
Number of IDs in source2296
Expected completenesseventually complete (Q21873974)
Formatter URLhttps://rusakters.ru/$1.html
Robot and gadget jobsMix'x'match
See alsoKinopoisk person ID (P2604)
Applicable "stated in"-valuerusakters.ru (Q55121940)
Single-value constraintyes
Distinct-values constraintyes
Wikidata projectRussia, Russia

MotivationEdit

One of the few well-known sites about famous actors of Russian and Soviet cinema. Being launched in 2008, it absorbed about 2.3 thousand biographical information, which is significantly less than its counterparts - Kinopoisk, Film.ru and others. MasterRus21thCentury (talk) 18:43, 6 May 2022 (UTC)

DiscussionEdit

  •   Support --Trade (talk) 22:32, 7 May 2022 (UTC)
  •   Support - Kareyac (talk) 15:26, 10 May 2022 (UTC)

Kinokolo.ua film IDEdit

   Ready Create
Descriptionидентификатор фильма на kinokolo.ua (ru) – (Please translate this into English.)
Representsno label (Q12071403)
Data typeExternal identifier
Template parameterTemplate:Kinokolo.ua title (Q26191199)
Domainfilm (Q11424)
Allowed units[0-9]+
Example 1Shadows of Forgotten Ancestors (Q1409627)1282
Example 2Lone Wolf (Q2904496)376
Example 3Zakhar Berkut (Q4188524)520
Sourcehttps://kinokolo.ua
External linksUse in sister projects: [ar][de][en][es][fr][he][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd].
Planned usefor usage in stated in (P248) and for Template:Authority control (Q3907614)
Number of IDs in sourceunknown
Expected completenesseventually complete (Q21873974)
Formatter URLhttp://www.kinokolo.ua/cyclopedia/film.php/$1
Robot and gadget jobsMix'x'match
See alsoKino-teatr.ua film ID (P5311)
Applicable "stated in"-valueno label (Q12071403)
Single-value constraintyes
Distinct-values constraintyes
Wikidata projectUkraine, Movies

MotivationEdit

Kinokolo is the first portal about Ukrainian cinema. Being founded in 2002, it collected information about Soviet films shot at Ukrainian film studios (named after Dovzhenko, Odessa Film Studio, etc.), as well as biographies of leading directors and actors. MasterRus21thCentury (talk) 05:36, 8 May 2022 (UTC)

DiscussionEdit

  •   Support --Trade (talk) 00:45, 12 May 2022 (UTC)

Kinokolo.ua person IDEdit

   Ready Create
Descriptionидентификатор человека на kinokolo.ua (ru) – (Please translate this into English.)
Representsno label (Q12071403)
Data typeExternal identifier
Template parameterQ26191200
Domainhuman (Q5)
Allowed units[0-9]+
Example 1Alexander Dovzhenko (Q55198)327
Example 2Ivan Mykolaichuk (Q2454822)371
Example 3Viktor Politov (Q4370160)133
Sourcehttps://kinokolo.ua
External linksUse in sister projects: [ar][de][en][es][fr][he][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd].
Planned usefor usage in stated in (P248) and for Template:Authority control (Q3907614)
Number of IDs in sourceunknown
Expected completenesseventually complete (Q21873974)
Formatter URLhttp://www.kinokolo.ua/cyclopedia/person.php/$1
Robot and gadget jobsMix'x'match
See alsoKino-teatr.ua person ID (P5312)
Applicable "stated in"-valueno label (Q12071403)
Single-value constraintyes
Distinct-values constraintyes
Wikidata projectUkraine, Movies

MotivationEdit

Kinokolo is the first portal about Ukrainian cinema. Being founded in 2002, it collected information about Soviet films shot at Ukrainian film studios (named after Dovzhenko, Odessa Film Studio, etc.), as well as biographies of leading directors and actors. —MasterRus21thCentury (talk) 05:50, 8 May 2022 (UTC)

DiscussionEdit

  •   Support --Trade (talk) 00:45, 12 May 2022 (UTC)

Kino.mail.ru film IDEdit

   Under discussion
Descriptionидентификатор фильма на Кино Mail.Ru (ru) – (Please translate this into English.)
Representsno label (Q16534697)
Data typeExternal identifier
Domainfilm (Q11424)
Example 1The Green Mile (Q208263)624334_zelenaja_milja
Example 2The Diamond Arm (Q1999930)623580_brilliantovaja_ruka
Example 3Moscow Does Not Believe in Tears (Q53105)517557_moskva_slezam_ne_verit/
Sourcehttps://kino.mail.ru
External linksUse in sister projects: [ar][de][en][es][fr][he][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd].
Planned usefor usage in stated in (P248) and for Template:Authority control (Q3907614)
Number of IDs in sourceunknown
Expected completenessalways incomplete (Q21873886)
Formatter URLhttps://kino.mail.ru/cinema/movies/$1
Robot and gadget jobsMix'x'match
See alsoKinopoisk film ID (P2603), Kinomania.ru film ID (P10164), kino-teatr.ru film ID (P10269), Film.ru film ID (P10303)
Applicable "stated in"-valueno label (Q16534697)
Single-value constraintyes
Distinct-values constraintyes
Wikidata projectRussia, Movies

MotivationEdit

Cinema Mail.Ru is one of the oldest portals of Runet about cinema. It was launched in August 2000 as Afisha Mail.Ru and was positioned as a portal about urban entertainment. In 2016, the portal received its current name and is entirely focused on cinema. Through the site you can buy tickets to cinemas in the largest cities of Russia. MasterRus21thCentury (talk) 06:24, 18 May 2022 (UTC)

DiscussionEdit

Kino.mail.ru series IDEdit

   Under discussion
Descriptionидентификатор сериала на Кино Mail.Ru (ru) – (Please translate this into English.)
Representsno label (Q16534697)
Data typeExternal identifier
Domaintelevision serial (Q7724161)
Example 1The Meeting Place Cannot Be Changed (Q2370768)769211_mesto_vstrechi_izmenit_nelzya
Example 2MISSING
Example 3MISSING
Sourcehttps://kino.mail.ru
External linksUse in sister projects: [ar][de][en][es][fr][he][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd].
Planned usefor usage in stated in (P248) and for Template:Authority control (Q3907614)
Number of IDs in sourceunknown
Expected completenessalways incomplete (Q21873886)
Formatter URLhttps://kino.mail.ru/series_$1
Robot and gadget jobsMix'x'match
See alsoKinopoisk film ID (P2603), Kinomania.ru film ID (P10164), kino-teatr.ru film ID (P10269), Film.ru film ID (P10303)
Applicable "stated in"-valueno label (Q16534697)
Single-value constraintyes
Distinct-values constraintyes
Wikidata projectRussia, Movies

MotivationEdit

Cinema Mail.Ru is one of the oldest portals of Runet about cinema. It was launched in August 2000 as Afisha Mail.Ru and was positioned as a portal about urban entertainment. In 2016, the portal received its current name and is entirely focused on cinema. Through the site you can buy tickets to cinemas in the largest cities of Russia. MasterRus21thCentury (talk) 06:24, 18 May 2022 (UTC)

DiscussionEdit

Kino.mail.ru person IDEdit

   Under discussion
Descriptionидентификатор персоналии на Кино Mail.Ru (ru) – (Please translate this into English.)
Representsno label (Q16534697)
Data typeExternal identifier
Domainhuman (Q5)
Example 1Leonardo DiCaprio (Q38111)445477_leonardo_dicaprio
Example 2MISSING
Example 3MISSING
Sourcehttps://kino.mail.ru
External linksUse in sister projects: [ar][de][en][es][fr][he][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd].
Planned usefor usage in stated in (P248) and for Template:Authority control (Q3907614)
Number of IDs in sourceunknown
Expected completenessalways incomplete (Q21873886)
Formatter URLhttps://kino.mail.ru/person/$1
Robot and gadget jobsMix'x'match
See alsoKinopoisk person ID (P2604)
Applicable "stated in"-valueno label (Q16534697)
Single-value constraintyes
Distinct-values constraintyes
Wikidata projectRussia, Movies

MotivationEdit

Cinema Mail.Ru is one of the oldest portals of Runet about cinema. It was launched in August 2000 as Afisha Mail.Ru and was positioned as a portal about urban entertainment. In 2016, the portal received its current name and is entirely focused on cinema. Through the site you can buy tickets to cinemas in the largest cities of Russia. —MasterRus21thCentury (talk) 06:35, 18 May 2022 (UTC)

DiscussionEdit

TelevisionEdit

BritBox IDEdit

   Under discussion
DescriptionIdentifier for programs and series on the BritBox video on demand streaming service
RepresentsBritBox (Q30681965)
Data typeExternal identifier
Domainfilm (Q11424), television program (Q15416), television series (Q5398426), etc
Allowed values(series|programme)/[0-9]+
Example 1Thunderbirds: The Anniversary Episodes (Q110896417) → programme/51229
Example 2Gavin & Stacey (Q3395368) → programme/36843
Example 3Coronation Street (Q945030) → programme/48423
Example 4Belgravia (Q65120601) → series/49784
Example 5Spooks, season 4 (Q7579110) → series/36897
Sourcehttps://watch.britbox.co.uk/
Planned useadding IDs for British TV shows
Number of IDs in sourcethousands to tens of thousands; see https://www.justwatch.com/us/provider/britbox which says "144+ movies and 311+ TV shows in its library", where typically TV shows have tens to hundreds of individual episodes
Expected completenessalways incomplete (Q21873886)
Formatter URLhttps://www.britbox.co.uk/$1
See alsoBBC programme ID (P827), Netflix ID (P1874), Amazon.com Prime Video ID (P8055)
Distinct-values constraintyes

MotivationEdit

BritBox (Q30681965) (en:BritBox) is a major British TV streaming service run as a joint venture by the BBC and ITV, with a huge library of TV shows made by all the major British terrestrial broadcasters. IDs for this are thus useful to Wikidata in the same way as IDs for programs and series on other major streaming services such as Netflix. The Anome (talk) 09:55, 12 February 2022 (UTC)

DiscussionEdit

Peacock IDEdit

   Under discussion
RepresentsPeacock TV Q67765302
Data typeExternal identifier
Domainproperty, items include Q104590890, Q85799839, Q107272564, Q107862864
Example 1The Amber Ruffin Show (Q104590890) the-amber-ruffin-show
Example 2Joe Exotic (Q107862864) joe-vs-carole
Example 3Psych 3: This Is Gus (Q109649196) psych-3-this-is-gus
External linksUse in sister projects: [ar][de][en][es][fr][he][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd].
Planned useChange https://en.wikipedia.org/wiki/Template:Peacock_title to pull from this Wikidata item in a similar way to other templates on en Wikipedia, for external links sections only
Number of IDs in sourcethere's https://www.peacocktv.com/stream-movies and https://www.peacocktv.com/stream-tv available before the ID, can change by identifying whether it's a movie or TV series in other identifer
Expected completenessno label (Q21873974 (eventually complete))
Formatter URL<https://www.peacocktv.com/stream-moves/$1 and https://www.peacocktv.com/stream-seriies/$1 available, can change by identifying whether it's a movie or TV series in other identifer – WRONG FORMAT
Robot and gadget jobsCould check the Wikipedia template for IDs entered there to bring here

MotivationEdit

Same as other external link categories on Wikipedia, ensure Wikipedia is up to date for links Indagate (talk) 20:57, 16 April 2022 (UTC)

DiscussionEdit

I see some issues here. I assume the-amber-ruffin-show is from https://www.peacocktv.com/stream-tv/the-amber-ruffin-show. When logged in to Peacock, that URL redirects to https://www.peacocktv.com/watch/asset/tv/the-amber-ruffin-show/7069386783458050112. The second URL is included in the javascript of the first page. tv/the-amber-ruffin-show/7069386783458050112 is probably a more stable identifier, except that if you're not logged in, you're redirected to a login page.

Aside from all that, Peacock could change the slugs they use in their URLs, breaking the identifiers. HBO Max sort of did, and broke a lot of identifiers in HBO Max ID (P8298). Trivialist (talk) 22:43, 17 April 2022 (UTC)

  •   Support, an important property for television.--Arbnos (talk) 00:05, 24 April 2022 (UTC)
  •   Support, I don't see why not, given we have similar properties for Netflix, Hulu, Disney+, etc. AntisocialRyan (Talk) 00:50, 5 May 2022 (UTC)

WhoSampled television IDEdit

   Ready Create
Descriptionidentifier for an television series or episode on WhoSampled.com
RepresentsWhoSampled (Q7997133)
Data typeExternal identifier
Domaintelevision series (Q5398426), television series episode (Q21191270)
Example 1The Simpsons (Q886)The-Simpsons
Example 2Futurama (Q73622)Futurama
Example 3Family Guy (Q5930)Family-Guy
Example 4Fox News (Q186068)Fox-News
SourceWhoSampled (Q7997133)
External linksUse in sister projects: [ar][de][en][es][fr][he][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd].
Number of IDs in sourceUnknown
Expected completenessalways incomplete (Q21873886)
Formatter URLhttps://www.whosampled.com/tv/$1/

MotivationEdit

WhoSampled is a very comprehensive database that not only categorizes music but also television shows and movies. --Trade (talk) 23:02, 24 April 2022 (UTC)

  •   Support If this helps with identifying samples I'm for it. Moebeus (talk) 22:37, 7 May 2022 (UTC)

DiscussionEdit

Anime and mangaEdit

MusicEdit

audio containsEdit

MotivationEdit

We do not have a property to state audio recording(s) an audio recording contains. This property can be used to:

  • Relate music video sound recordings with their original sound recordings as both each have their own ISRC (P1243).
  • Audio tracks that remix/mashup songs to specify what songs are being remixed in one audio track.
  • Podcasts, videos, or other media that feature audio in them.

This will be a subproperty of has part or parts (P527). We should have a separate property instead of using has part or parts (P527) because has part or parts (P527) could mean the part of a podcast (intro, meet our featured guest, etc.) or a section of a song (intro, bridge, chorus, etc.).

Lectrician1 (talk) 00:20, 8 February 2022 (UTC)

DiscussionEdit

  Comment The proposal needs more discussion and an important topic definitely, so thanks! Seems we need to see what we already have first, and then go from there. So, looks like we already have some related properties: samples from work (P5707) and remix of (P9810) but unsure of applicability in all use cases here. Maybe you could dive into their previous proposals and Discussion pages and research some if you haven't already. Then come back here. Recording is different from Song, certainly. --Thadguidry (talk) 17:15, 14 February 2022 (UTC)

  CommentYes, per Thadguidry's point that recording and song are different I think this property has potential to be more broadly applicable. Allowed values could be expanded to any item which is an instance of a subclass of audio content (Q108676767); for example an audio recording could contain a interview audio recording (Q108679208) or a Wilhelm scream (Q1141711). --Middle river exports (talk) 20:58, 8 May 2022 (UTC)

Video gameEdit

LiteratureEdit

National Union Catalog IDEdit

   Ready Create
DescriptionThe identifier for this work in the The National Union Catalog, Pre-1956 Imprints: a Cumulative Author List Representing Library of Congress Printed Cards and Titles Reported By Other American Libraries (Q107434107)
Data typeExternal identifier
Domainitems of type version, edition, or translation (Q3331189)
Allowed valuesregex: N[A-Z]? \d{7}(\.\d+)?
Example 1Robert Carter: His Life and Work (Q106913633) -> NC 0506050: qualifiers:
Example 2In Memoriam: Faded and Other Poems (Q106914750): NJ 00717622
Example 3Authoritative Christianity, First Council of Nicaea, vol. 1 (1891) (Q106917163): NC 0407550
Planned useadding NUC authority control to editions
Number of IDs in sourcethe number of items in the NUC (hundreds of thousands)
Expected completenessalways incomplete (Q21873886) (as new volumes being published)
Distinct-values constraintyes
Wikidata projectWikiProject Books (Q8487081)

MotivationEdit

The NUC is a huge catalogue of all works catalogued by a group of libraries in the US, including the Library of Congress. Of particular interest are the 754 volumes of the Pre-1956 Imprints, which are, for many works, the only place they are catalogued. Inductiveload (talk) 20:45, 19 September 2021 (UTC)

  • It's described at en:National Union Catalog.
    • Many entries do not have an 'identification'. These entries all represent "alternate entries", in library-speak....redirects. There is little point to trying to enter those on WD, in my opinion.
    • The catalog was compiled from copies of catalog cards submitted by hundreds of US research libraries, starting in the 1950s, of (what was intended to be) every title they held which was not already represented by a Library of Congress printed card. This was added to the works that already had cards (meaning, works that have an LCCN and are held by the Library of Congress).
    • This means, specifically, that the NUC was intended to include every US publication that does not have an LCCN (as well as those that do), and many of the libraries that contributed to the NUC are not contributors to WorldCat..... there are a massive number of works in the NUC that have probably never been electronically cataloged, and are not in the Library of Congress.
    • The LoC almost never obtained copies of later editions unless there was a new copyright claim registered, which is why many such editions do not have LCCNs.
    • The 'human brains' that created this were far better than the OCLC algorithm at merging duplicates, as well.
    • When you find references in LCCN or LoC authorities records to 'the old catalog'.... this is it. Much of the catalog of the Library of Congress that you find online, for older works, was a transcription from the printed card (often with info left out)... these are replaced as the LoC re-catalogs the actual books, and will probably take decades. This is where you look for complete bibliographic information... the entries are 'photostatic' copies of the submitted library catalog cards, cataloged by actual professional librarians from books they were actually holding, in the original binding (so, correct pagination).
    • Additionally, the NUC itself also gives abbreviations for what libraries submitted information on each book, which is probably the most valuable bit of information... these libraries mainly still hold the same works. This allows you to search for digitized versions at those libraries based on the actual cataloged search terms, instead of whatever Google or the Internet Archive mangled it into.
    • This is also the information one would need to possibly use interlibrary loan to obtain a copy.
  • TLDR; referring to the actual Mansell catalog is how you resolve the not-uncommon problem of either zero or way too many, and not matched, entries for a pre-1956 book in WorldCat, or obtain realistically accurate 'lists' of multiple editions of the same book. This is the pre-digital WorldCat actual people spent decades on. Jarnsax (talk) 21:43, 19 September 2021 (UTC)

DiscussionEdit

  •   Support ofc. Jarnsax (talk) 23:18, 19 September 2021 (UTC)
    • The exact construction of the identifier is the letter N, followed by the first letter of the "main entry" name (the card title) or null if it is a symbol, then a space, then a seven digit 'sequential but not consecutive' number, with inserted entries given the same identifier as the previous entry, with the addition of an unpadded sequential number after a decimal point. Jarnsax (talk) 23:29, 19 September 2021 (UTC)
  •   Comment if it's an identifier, why would it need volume and page numbers as qualifiers? --- Jura 05:57, 20 September 2021 (UTC)
  • Because there is no online portal for the NUC, just a huge pile of page scans, so actually finding an item in the thousands of volumes of the NUC is a bit of a mission if you have the number but don't know exactly where it is. The IDs are sequential, but you still need locate the volume and then scrub though that volume to find it. But, if you've just looked up an item and found it, adding the volume/number is easy, because you have the page in front of you. For example, example 1 above has a page scan at https://babel.hathitrust.org/cgi/pt?id=mdp.39015082906424&view=1up&seq=480.
  • Probably would be better if there was an item for the volume, then it could be published in (P1433) → the volume item (which would then link to Hathi, the IA, Commons, etc), but it'll still need a page(s) (P304) and perhaps even column (P3903). Inductiveload (talk) 10:21, 20 September 2021 (UTC)
  • I see. Eventually I suppose the statements could provide a guess in which volume/page to find a new value. --- Jura 10:56, 20 September 2021 (UTC)
  • With enough items, you could certainly book-end a range of pages that a given ID would land in, though it would be a lot of items before it would land you right on the page reliably, since there are something like 500k pages in the catalog, and, AFAIK no machine-readable way to ingest the data. Inductiveload (talk) 13:00, 20 September 2021 (UTC)
  • FWIW, since the scans are on Hathi, it's possible to permalink to the scan of a specific page (using a handle url). It's down near the bottom of the left menu on Hathi. Jarnsax (talk) 16:06, 20 September 2021 (UTC)

Proza.ru author IDEdit

   Ready Create
Descriptionидентификатор писателя на Прозе.ру (ru) – (Please translate this into English.)
Representsproza.ru (Q4380129)
Data typeExternal identifier
Domainhuman (Q5)
Allowed units[a-z]+
Example 1Victor Kimovich Gubarew (Q4151278)drake
Example 2Sergeĭ Aksënenko (Q4059982)ksemich
Example 3Anna Grachevskaya (Q56191949)anisyamed
Sourcehttps://proza.ru
External linksUse in sister projects: [ar][de][en][es][fr][he][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd].
Planned usefor usage in stated in (P248) and for Template:Authority control (Q3907614)
Number of IDs in sourceunknown
Expected completenesseventually complete (Q21873974)
Formatter URLhttps://proza.ru/avtor/$1
Robot and gadget jobsYes, it would be great to have a separate mix'n'match catalog.
See alsoLib.ru author ID (P10362)
Wikidata projectRussia

MotivationEdit

Proza.ru, along with Stihi.ru, is one of the most popular literary sites in Russia: since 2000, more than 20 million works have been published on the site and over half a million authors have been registered on it. The purpose of the portal is to realize the potential of novice writers and help them find readers. MasterRus21thCentury (talk) 06:18, 12 March 2022 (UTC)

DiscussionEdit

Stihi.ru author IDEdit

   Under discussion
Descriptionидентификатор писателя на Стихах.ру (ru) – (Please translate this into English.)
Representsstihi.ru (Q4442644)
Data typeExternal identifier
Domainhuman (Q5)
Allowed units[a-z]+
Example 1Nataliya Terekhova (Q4455712)guitaristka
Example 2Igor Talkov-younger (Q4450675)mirimirim
Example 3Aleksandr Basov (Q3609544)av30168
Sourcehttps://stihi.ru
External linksUse in sister projects: [ar][de][en][es][fr][he][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd].
Planned usefor usage in stated in (P248) and for Template:Authority control (Q3907614)
Number of IDs in sourceunknown
Expected completenesseventually complete (Q21873974)
Formatter URLhttps://stihi.ru/avtor/$1
Robot and gadget jobsYes, it would be great to have a separate mix'n'match catalog.
See alsoLib.ru author ID (P10362), Wikidata:Property proposal/Proza.ru author ID
Wikidata projectRussia

MotivationEdit

The site Stihi.ru appeared in 2000 at the same time as Proza.ru. Currently, in the ratings of Rambler and Mail.ru, it ranks first in the rating of literary sites, and the popularity of the resource, according to an article from the Literary Gazette, is due to the absence of restrictions on the publication of works. By the site's 20th anniversary in 2020, 60 million works have been published and more than a million authors have registered. MasterRus21thCentury (talk) 07:17, 12 March 2022 (UTC)

DiscussionEdit

VideoEdit

ImageEdit

onscreen participantEdit

   Ready Create
Descriptionan agent taking an active role as a participant onscreen in a nonfiction moving image work
Representsonscreen participant (Q104879379)
Data typeItem
Domainmoving image (Q10301427), non-fiction film (Q24960157), factual television (Q5428822)
Allowed valuesQ number
Example 1RBG (Q54829190) has onscreen participant Ruth Bader Ginsburg (Q11116)
Example 2RBG (Q54829190) has onscreen participant Nina Totenberg (Q7038136)
Example 3Shadow Girl (Q26911180) has onscreen participant Maria Teresa Larrain (Q26911182)
Example 4Burroughs: The Movie (Q16249038) has onscreen participant Allen Ginsberg (Q6711)
Example 5The Great Math Mystery (Q56604860) has onscreen participant Mario Livio (Q1898912)
Example 6Chasing the Moon (Q85751667) has onscreen participant Buzz Aldrin (Q2252)
Example 7Chasing the Moon (Q85751667) has onscreen participant Michael Collins (Q104859)
Example 8Tiger King: Murder, Mayhem and Madness (Q88306935) has onscreen participant Carole Baskin (Q88495947)
Example 9Tiger King: Murder, Mayhem and Madness (Q88306935) has onscreen participant Joe Exotic (Q83688347)
Example 10Grey Gardens (Q2104352) has onscreen participant Edith Bouvier Beale (Q535330)
Example 11Grey Gardens (Q2104352) has onscreen participant Edith Ewing Bouvier Beale (Q5338542)
Example 12Shut Up & Sing (Q2905624) has onscreen participant The Chicks (Q142636)
Example 13The Last Dance (Q85807688) has onscreen participant Chicago Bulls (Q128109)
Planned useWill add property to nonfiction moving image works as they are encountered; or will change existing property cast member (P161) used on many records to the onscreen participant property, because these people are not actors in a film or television program
Expected completenessalways incomplete (Q21873886)
See alsocast member (P161), contributor to the creative work or subject (P767), participant (P710), talk show guest (P5030)

MotivationEdit

This proposal originated in a discussion on the Wikidata Telegram channel. There isn't an ideal property to indicate the onscreen participants in a nonfiction film or television program. These are not cast member, as they are not actors in a fictional work. Typically they are interviewees or commenters in documentaries and other nonfiction films and television programs. Having the specific property "onscreen participant" would enable an exact explanation of their role in relation to a moving image work. This property exists in RDA: see "has onscreen participant agent" (http://rdaregistry.info/Elements/e/P20279) and its subelements "has onscreen participant person" (http://rdaregistry.info/Elements/e/P20363), "has onscreen participant collective agent" (http://rdaregistry.info/Elements/e/P20422), "has onscreen participant corporate body" (http://rdaregistry.info/Elements/e/P20481), and "has onscreen participant family" (http://rdaregistry.info/Elements/e/P20540). UWashPrincipalCataloger (talk) 05:46, 18 January 2021 (UTC)

DiscussionEdit

ValterVB LydiaPintscher Ermanon Cbrown1023 Discoveranjali Mushroom Queryzo Danrok Rogi Mbch331 Jura Jobu0101 putnik ohmyerica AmaryllisGardener FShbib Andreasmperu Li Song Tiot Harshrathod50 U+1F350 Bodhisattwa Shisma Wolverène Tris T7 Antoine2711 Hrk6626 TheFireBender V!v£ l@ Rosière WatchMeWiki! CptViraj ʂɤɲ Trivialist 2le2im-bdc Sotiale Wallacegromit1, mostly focus on media historiography and works from the Global South Floyd-out M2k~dewiki Rockpeterson Mathieu Kappler Sidohayder Spinster Gnoeee Ranjithsiji Ontogon   Notified participants of WikiProject Movies --- Jura 19:38, 18 January 2021 (UTC)

  •   Support This will be a useful property. --Crystal Clements, University of Washington Libraries (talk) 16:51, 20 January 2021 (UTC)
  •   Support This seems like it would be useful for differentiating people in news reports, video footage, etc. from actors playing a part. 21:51, 21 January 2021 (UTC)
  •   Support--2le2im-bdc (talk) 13:30, 23 January 2021 (UTC)
  •   Oppose I don't really see how we could do the proposed "sorting" efficiently and avoid having to re-do it frequently. Currently, these people are already identified as participants with P161 (not as actors) and generally referenced with various sources that also do not differentiate as above. Already the difference between cast and "voice actor" is sometimes hard to maintain. --- Jura 09:04, 25 January 2021 (UTC)
    • In almost all of the items that I have looked at, these people are identified as "cast member". "Participant" is too broad and could mean anyone participating in the creation of a film, not just those appearing on camera. UWashPrincipalCataloger (talk) 00:53, 27 January 2021 (UTC)
      • Yes, participant with P161. --- Jura 23:02, 28 January 2021 (UTC)
  •   Comment I've thought about a property like this for quite a while. For documentary films, interviews and other non-fictional content, cast member (P161) doesn't seem ideal. Using character role (P453) themselves (Q18086706) kind of works, but doesn't quite convey that the person isn't playing some kind of role. Using a different property could do that.
    On the other hand pretty much all film/tv databases out there don't make any such distinctions and just list all such on-screen participants as cast members. Which makes importing or comparing data more difficult if our data is split among several properties. But having more granularity in our data isn't necessarily a bad thing, we are already doing that with properties like presenter (P371), voice actor (P725) or talk show guest (P5030).
    Although I think instead of creating a new property, we could also repurpose/expand talk show guest (P5030) instead to not include just talk show guests but all kinds of on-screen participants. --Kam Solusar (talk) 22:32, 28 January 2021 (UTC)
    • If we change this, I think either way, it would be good to see a plan how to implement this fairly large change, before creating the property. @UWashPrincipalCataloger, Moebeus, 2le2im-bdc, Clements.UWLib, Rockpeterson: @Emwille: what do you think? what's your plan? @Kam Solusar: --- Jura 10:44, 2 February 2021 (UTC)
    • @Kam Solusar: Re:repurposing talk show guest (P5030): one issue is that talk show guest (P5030) is currently used for guests which are *not* "on-screen", because it’s media without a screen (podcasts and radio shows). Jean-Fred (talk) 14:13, 2 February 2021 (UTC)
    • Talk show guest and onscreen participant are very different things. As has been pointed out, talk show guests are not necessarily on screen in a visual resource, they can be guests on radio shows and podcasts. UWashPrincipalCataloger (talk) 19:09, 2 February 2021 (UTC)
    • Jura makes a good point about maintaining differences and dealing with onscreen participants already identified as cast members. This seems to be an issue that will come up whenever we need more specific properties for roles people play in a creative work. How are these more granular new properties usually dealt with in Wikidata? I don't see how adding "participant" with P161 would sidestep that issue, exactly. "Participant" doesn't add a meaningful distinction because it's so broad, but there would still be maintenance. I don't think repurposing talk show guest (P5030) would be ideal either, because talk show guests are often, as Jean-Fred points out, not on-screen. --Crystal Clements, University of Washington Libraries (talk) 16:49, 3 February 2021 (UTC)
  • I do agree with Jura as it will be a hard and jumbled task to differentiate people as actors and on screen participant and there is no valid source to confirm if he/she is of either category . If we find out a proper method of sorting then this property would be really helpful for proposing a detailed database of the documentary/shows . Rockpeterson (talk) 09:07, 4 February 2021 (UTC)
Wouldn't it still be better to input new items with a much more correct property that editors could use instead of cramming people into "cast member"? Why perpetuate this problem, even if it is not immediately possible to correct already existing items? Editors could correct records as they encounter them or need to edit them further. I agree that it might be hard to identify all the statements that need to be corrected, but "cast member" is simply wrong, and that is what is being used primarily now. Perhaps it is possible to gather all nonfiction moving image works that have a cast member property and work on cleaning them up. UWashPrincipalCataloger (talk) 19:31, 4 February 2021 (UTC)
Yes its a great idea @UWashPrincipalCataloger: , it will be more efficient and helpful if we make a project to gather all nonfiction moving image works sort them in years(period) and work on them in a group so that the task will be completed faster . If you agree I am ready to work Rockpeterson (talk) 06:35, 5 February 2021 (UTC)
I would be willing to work on this, and I think some of our media catalogers would also. UWashPrincipalCataloger (talk) 15:51, 5 February 2021 (UTC)
  • Maybe you could start out with the currently existing model and once you have a clear view on how it could be implemented, come back to this proposal. --- Jura 12:21, 8 February 2021 (UTC)
  • I don't think it's a good idea to have two approaches for the same information nor creating a new one without a clear view on how to implement it. There is nothing inherently wrong with the current approach. It may be that some interpret existing statements incorrectly, but that is essentially their problem. As mentioned, participants are added with the property cast member (P161) and qualified if wanted. We need to make sure an approach can be implemented on the practical level in Wikidata.
    The project has already suffered much in the field of books from people coming here trying to spell out the theoretical ideal approach and, 8 years down the road, WikiProject Books still in an non-ideal shape. Let's make sure we don't undo WikiProject Movies in the same way. --- Jura 13:17, 5 February 2021 (UTC)
    • But @Jura1:, cast members are actors in a fictional work. The cast member property is defined as pertaining to actors. Onscreen participants are not actors. Using the cast member property is not correct for these kinds of participants in nonfictional works who appear as themselves and are not acting. UWashPrincipalCataloger (talk) 18:12, 8 February 2021 (UTC)
      • I understand that this is your point of view. It just not current modeling practice, not here and not at even larger projects we rely on. --- Jura 14:46, 28 February 2021 (UTC)
        • It should be current modeling practice. I'd be willing to help with a sorting project for implementation if that helps. Cast members and onscreen participants are not the same thing. Wikipedia defines cast members as actors. --Crystal Clements, University of Washington Libraries (talk) 00:09, 26 March 2021 (UTC)
        • This is not Telegram or Wikipedia. You might want to read what I and others wrote about that above. What's needed is a sustainable plan. --- Jura 04:32, 27 August 2021 (UTC)
  •   Support It seems to me that this property would help us streamline current modelling practices in this area (<cast member><role><themselves> vs. <participant><has role><xy>. --Beat Estermann (talk) 14:37, 28 February 2021 (UTC)
  •   Support Pteropotamus (talk) 10:11, 1 March 2021 (UTC)
  •   Support --Jala360 13:50, 2 March 2021 (UTC)
  •   Support Not sure what the disagreement is. If cast member is not appropriate we need a term that IS appropriate, and this one seems like it would nicely cover many current problems. -- Categerhart (talk) 00:25, 26 March 2021 (UTC)
    • A property for this is already available and used in line with similar properties we are mapping from other leading databases in the field. If you need to query the label, you can add aliases to the existing property. Apparently, some UWashington staff members disagree with the current approach, but still haven't presented a viable way to implement another approach. Maybe, there is just a confusion between Wikidata property, Wikidata label and "term". --- Jura 14:35, 26 March 2021 (UTC)
      • It would not be appropriate to add "onscreen participant" as an alias of "cast member". They have very different semantics. See below for a possible viable way to implement separate properties for participants in non-fiction works versus cast members in fictional works. UWashPrincipalCataloger (talk) 00:53, 3 April 2021 (UTC)
        • Well, it's the current approach. I understand that you disagree with this. I suppose you are aware of the problems of Wikidata:WikiProject Books. It's advised by 100+ specialists on how to implement it in Wikidata, but 8 years down the line, it still hasn't happened and WMF now considers another project to handle this instead. Maybe you can help them sort it out? In any case, we don't want WikiProject Books problems to proliferate into Movies, don't we? --- Jura 11:54, 5 April 2021 (UTC)
  •   Comment I'd like to propose a way to take on implementation if this proposal is approved. It would address statements already in existence for "cast members" in non-fiction films and television. I used a set of queries for works with the targeted genres and sub-genres (query results for non-fiction films, factual television, reality television, and game shows) to accumulate all the statements we would like to change into an OpenRefine project and posted a copy in a Google spreadsheet here. There are a little over 35,000 statements. I propose that a group of volunteers such as myself, Categerhart, UWashPrincipalCataloger, and Rockpeterson review the proposed changes, in consultation with WikiProject Movies, then make the changes in OpenRefine/QuickStatements after submitting them for bot review (this is enough to require bot review, right?). As for maintaining the distinctions between cast members and onscreen participants during large data imports from databases which do not make the same distinction, I would be willing to help brainstorm implementation ideas to make the distinction during the import process. I don't know who is doing most of that already. Maybe folks involved with WikiProject Movies? What do you think Jura? --Crystal Clements, University of Washington Libraries (talk) 00:21, 3 April 2021 (UTC)
    • Thanks. That is a start.
      If it goes beyond of what's in the queries, can you store the lists somewhere onsite (or on WMF site)? e.g. Wikidata:Sandbox/1. Contributors should be able to edit without having to use offsite resources.
      I think there are three or four distinct issues to address:
      (1) how to deal with existing statements: sorting as you suggest can address this. How does it go beyond checking genre?
      (2) how to deal with new statements going forward
      (3) how to ensure people can easily add incremental contributions
      (4) how bulk imports or reference additions by bot should work going forward (as most other databases just use one property "cast"). --- Jura 11:54, 5 April 2021 (UTC)
  •   Support What is the hold up on this one? I have a ton of imagineNative shorts coming up that would be in dire need of this property. -Yupik (talk) 01:12, 25 August 2021 (UTC)
  •   Comment can we see a plan how to implement and maintain this? As it's not compatible with Wikidata's current approach (and that of a series of references frequently quoted), an outline would help. If, in the meantime, the proposer/supporters haven't been active or are no longer active in Wikidata, maybe we should close this as stale. --- Jura 17:31, 25 August 2021 (UTC)
  • @UWashPrincipalCataloger, Moebeus, Jean-Frédéric, Rockpeterson, 2le2im-bdc: @Clements.UWLib, Kam Solusar, Yupik, Beat Estermann, Pteropotamus: @Jala360, Categerhart: I'd marked this as ready but Jura continues to oppose, and suggests you may be "no longer active in Wikidata". Jura did raise 4 "issues" just above, so it would probably be helpful if you directly address them. Thanks. ArthurPSmith (talk) 17:47, 26 August 2021 (UTC)
    Just for the record: I still edit from time to time :) Moebeus (talk) 17:52, 26 August 2021 (UTC)
    • How would you address the above? Given that I had to clean up something else the proposer (or their associated project) added to Wikidata, I would be more comfortable if other participants of WikiProject Movies would come up with a plan. --- Jura 18:56, 26 August 2021 (UTC)

    I also edit routinely, and although I don't have the expertise to address Jura concerns about batch loading, I continue to think we need this new property regardless of whether others out there do not use it. As Crystal says, there are ways around that which could be used to fix mistakes periodically. I would be willing to do clean-up as needed as well.Categerhart (talk) 18:16, 26 August 2021 (UTC)
    • Frankly, I don't think I have seen you and some other participants in this discussion around WikiProject movies. In the meantime, you can use P161. --- Jura 18:56, 26 August 2021 (UTC)
    • I edit all the time, albeit it less right now since I have relatives visiting. The suggestion that we don't is frankly weird. Like Categerhart, I don't batch upload, so I can't address that concern. P161 does not reflect what is needed in spite of the persistent insistence it be used in this property's place. -Yupik (talk) 21:23, 26 August 2021 (UTC)
    • You are correct, I'm am mainly active in the Telegram music group, but just because I haven't become active in the media group does not make my opinion any less worthwhile. There are many similarities between music and media and if a similar problem came up in the music group, where a term was incorrectly being used because of bad batch loading, us music folks would figure out how to fix it, not just ignore it and let the data continue to be incorrect, or not useful. Using a term like participant seems to not give us the granularity that we need. It would be like using performer instead of pianist, or singer. I still support this proposal. None of Jura's arguments negate the fact that there is a constituency that needs this term.Categerhart (talk) 22:25, 26 August 2021 (UTC)
      • P161 is the current way of modeling it at Wikidata (see the comment by a highly active contributor to Movies on Wikidata above). If you prefer not to tackle the open questions, maybe other users can. --- Jura 04:32, 27 August 2021 (UTC)

  • @Clements.UWLib: has offered a means to clean up existing items and our group at the University of Washington is willing to tackle this. We are daily editors of Wikidata and some of us are film and video catalogers. Once the property has been created we will plan a remediation project and will involve participants of Wikiproject Movies if there are some there willing to participate. UWashPrincipalCataloger (talk) 01:02, 27 August 2021 (UTC)
    • Maybe it's easier to outline the plan and address the questions on separate page if you prefer not to do it here. If you need a property to simulate your approach, you can use Sandbox-Item (P369). We need to avoid a repeat of "Haligonians" (see Wikidata talk:WikiProject PCC Wikidata Pilot) where it was left to others to clean up. --- Jura 04:32, 27 August 2021 (UTC)
  •   SupportMasterRus21thCentury (talk) 18:42, 2 January 2022 (UTC)

reprinted inEdit

   Under discussion
Descriptionlarger work in which a shorter work has been reprinted or anthologised
Data typeItem
Domainwritten works
Allowed valuesitems representing written works
Example 1Expedition to Belsen (Q108307261)Belsen: medical aspects of a World War II concentration camp. Paper 1. (Q53956727)
Example 2[Item representing Rebel, H., 1907. "
Lepidopteren aus Sudarabien und von der Insel Sokótra
"] → [Item representing volume containing Rebel, H., 1931. "
Zoologische Ergebnisse der Expedition der Kaiserlichen Akademie der Wissenschaften nach Südarabien und Sokótra im Jahre 1898/99.
"] (see discussion at species:Wikispecies:Village Pump#Rebel, 1907
Example 3The Bicentennial Man (Q468132)The Bicentennial Man and Other Stories (Q2398251)
See alsocites work (P2860), quotes work (P6166)
Wikidata projectWikiCite

MotivationEdit

So far as I can tell we have no adequate method of modelling this relationship. Neither full work available at URL (P953) (as currently used on the first example) nor has part or parts (P527) seem adequate. Objects could be qualified with object has role (P3831), with values representing "original text", "revised version", "corrected version", "abridged version", etc., as needed. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:53, 28 August 2021 (UTC)

DiscussionEdit

  •   Support - This is a common and important relationship to represent for articles, short stories, etc. It could help connect items in anthologies to their first publication. Examples for different situations would be useful. For instance, make clear whether/how it should also be used for long items (monographs/books) that are printed multiple times. Jodi.a.schneider (talk) 15:29, 28 August 2021 (UTC)
  •   Support John Samuel (talk) 17:51, 28 August 2021 (UTC)
  •   Comment Why won’t published in (P1433) work for this? - PKM (talk) 03:02, 30 August 2021 (UTC)
  •   Comment Would this also apply for facsimile? I would prefer not to limit this property to printed material only. -- JakobVoss (talk) 11:57, 30 August 2021 (UTC)
  •   Oppose In my opionion published in (P1433) cover this perfectly. /ℇsquilo 15:30, 31 August 2021 (UTC)

BIU Santé image bank IDEdit

   Under discussion
Descriptionidentifier for an image on the Bibliothèque interuniversitaire de santé image bank
RepresentsImage bank (Q107463432)
Data typeExternal identifier
Domainitem
Allowed values[a-zA-Z0-9_-]
Example 1Q108915125CIPC0020
Example 2MISSING
Example 3MISSING
Sourcehttps://www.biusante.parisdescartes.fr/histoire/images/index.php
External linksUse in sister projects: [ar][de][en][es][fr][he][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd].
Planned useThe BIU Santé would like to add to Wikimedia Commons about 3000 images from our image bank. The aim is to create a wikidata identifier for each image, which will allow us to manage the metadata related to the images
Number of IDs in source18000
Formatter URLhttps://www.biusante.parisdescartes.fr/histmed/image?$1
See alsoBIU Santé person ID (P5375)

MotivationEdit

BIU Santé - Solenne Coutagne 09:34, 27 May 2021 (UTC) This new Wikidata property will make it possible to improve the quality of the metadata of the images of the BIU Santé uploaded on Wikimedia Commons, by linking them to people, places, events, discoveries...

Two more motivations : This would also be a new Wikidata property related to medicine (Q19887775) which would allow a better coverage of the history of medicine (Q380274) and to facilitate the reuse of the images from the Image bank (Q107463432) added to Commons. BIU Santé - Olivier Ghuzel (talk) 13:26, 9 July 2021 (UTC)

DiscussionEdit

  •   Support, an important property for Wikidata.--Arbnos (talk) 15:32, 31 May 2021 (UTC)
  •   Oppose what is currently proposed. This is an image id, so it should definitely not be used on human (Q5) or organization (Q43229) items.
Regarding the aim of adding metadata to images, this is obviously useful, but we already have BIU Santé person ID (P5375) for people and your images are internally indexed on it. So I guess you have a basis at least for your metadata on people, but we don't want those 123 image ids added to Louis Pasteur (Q529).--Nono314 (talk) 09:01, 4 June 2021 (UTC)
@BIU Santé - Solenne Coutagne: By the way, is there a reason those metadata are not available in your online pages (ie no link back from image to bio, only the other way round)? I remember when I tried a few years ago to add images from BIU Santé, but it happened to be extremely tedious...--Nono314 (talk) 10:12, 4 June 2021 (UTC)
@Nono314:You are right, our examples are badly chosen and do not describe exactly what this property will be used for: linking an image identifier from our image bank to the wikidata record of this image.
We don’t want to link image IDs with human or organization items. We plan to create new items representing images, for which we will specify the subject. It could be a person, a building, a place, an event or any other relevant subject... (our image bank doesn’t only contain portraits). It’s not the image ID that would be connected with a person (or any other subject), but the person ID that may be specified at the image level thanks to the « depicts » property (depicts (P180)).
For the second point, we know the problem between the biography database and the image bank. It will be resolved soon. BIU Santé - Solenne Coutagne (talk) 14:53, 25 June 2021 (UTC)

  Comment @BIU Santé - Solenne Coutagne, BIU Santé - Olivier Ghuzel, Arbnos, Nono314: I created a new item Q108915125 and put it here as an example (and masked the other old examples), what do you think? @Olivier/Solenne: could you use OpenRefine to create some other items? (following the model of my example, which might not be perfect). If not, an other "simplier" way to go is to not create item for each document on Wikidata and just use this property directly on Commons, then the example would be Commons:Special:EntityData/M60226381CIPB1478. Both ways could work, tell us what you prefer ;) Cheers, VIGNERON (talk) 14:15, 17 October 2021 (UTC)

PodcastEdit

TheatreEdit

Creative workEdit

See also: Wikidata:WikiProject Infoboxes/works
Software products and brands, see: Wikidata:WikiProject Infoboxes/terms
Books, see: Wikidata:WikiProject Books

+

entries with this initial start at qualifier valueEdit

   Ready Create
Descriptioninitial letter or character of entries found at pages starting with qualifier value in this book with alphabetically ordered entries. Use applicable qualifier such as "page(s)" (P304), "file page" (P7668), "column" (P3903), "folio(s)" (P7416). If needed, "volume" (P478).
Data typeItem
Domaindictionaries and other works ordered by alphabet
Allowed valuesletter (Q9788), items for letters, possibly numbers, and a qualifier, e.g., page(s) (P304), file page (P7668), column (P3903), folio(s) (P7416). volume (P478)
Example 1Słownik „Dux-Liliput“ angielsko-polski (Q108959596)A (Q9659), qualified with page(s) (P304) = 5 [1]
Example 2Słownik „Dux-Liliput“ angielsko-polski (Q108959596)B (Q9705), qualified with page(s) (P304) = 53 [2]
Example 3Słownik „Dux-Liliput“ angielsko-polski (Q108959596)C (Q9820), qualified with page(s) (P304) = 83 [3]
Example 4File:Stanisław Goldman - Słownik Dux-Liliput.djvuA (Q9659), qualified with file page (P7668) = 9 [4]

MotivationEdit

(Add your motivation for this property here.) --- Jura 18:06, 6 December 2021 (UTC)

DiscussionEdit

  •   Comment I could see a point to having a single-valued property that gives the page number of the start of an index, but having one value per letter? That seems excessive and unnecessary. ArthurPSmith (talk) 19:30, 7 December 2021 (UTC)
    The sample one doesn't have an alphabetical index (and other similar ones where this property applies might not have that either).
    In the paper version one just has to guess where the page is. It's generally feasible as one knows the size of the book. This is somewhat problematic once it's digitized. Possibly the reason why Wikisource created one in it's pages about the sample above.
    @ArthurPSmith Maybe I misunderstood your suggestion. Can you do a sample? --- Jura 21:36, 7 December 2021 (UTC)
    • Oh, I see you're trying to apply this to a dictionary or other work where most of the work is in some sort of alphabetical order? When I saw "alphabetical index" I thought you were referring to the location of the index in any work (many nonfiction books have an index section at the end). What I had in mind was "Nonfiction work" "alphabetical index starts on page" "355" or something like that. I think your label is at least confusing for this purpose; it also still seems of limited usefulness. ArthurPSmith (talk) 21:43, 7 December 2021 (UTC)
      The one you had in mind can be added with front and back matter (P8570).
      Apparently, contributors at Wikisource find it's needed, otherwise they wouldn't create it there.
      I agree that label isn't that great, but I couldn't come up with a better one. I suppose we can update the label if we find a better one. --- Jura 21:49, 7 December 2021 (UTC)
  •   Comment following the comment by Arthur, I changed the label, maybe "entries with this initial start at qualifier value" is better than "alphabetical index". Where applicable, volume (P478) should be included as qualifier. --- Jura 09:11, 8 December 2021 (UTC)
  •   Support it can be useful to enrich items of alphabetically-ordered works. --Epìdosis 14:15, 9 January 2022 (UTC)

Category for work of subjectEdit

MotivationEdit

We have quite a few properties for "Category for ..." and this one seems to be missing — Martin (MSGJ · talk) 20:33, 14 December 2021 (UTC)

DiscussionEdit

  •   Comment maybe related category (P7084) can do? The link between a work and subject can take various forms. --- Jura 12:56, 21 December 2021 (UTC)
    I would support Jua1 here. The property you want can already be implemented by means of the property related category (P7084) --Gymnicus (talk) 17:50, 27 December 2021 (UTC)
    "Related category" seems a bit vague. How is it related?? — Martin (MSGJ · talk) 21:37, 15 January 2022 (UTC)
  •   Comment we have some very specific properties like category of people buried here (P1791). On the other hand "category for someone's work" seems quite broad and applicable to many topics — Martin (MSGJ · talk) 13:17, 27 January 2022 (UTC)
    • Wouldn't it be unpredictable what it would hold? Thus the suggestion to use related category (P7084) with its qualifier approach. --- Jura 16:26, 27 January 2022 (UTC)
  •   Oppose more category properties. Also two out of three examples failed Wikidata:Notability so I deleted them. Multichill (talk) 15:59, 1 May 2022 (UTC)

"beforehand owned by" & "afterwards owned by"Edit

beforehand owned byEdit

   Under discussion
Descriptionperson or institution that owned the subject just before stated event. Aliases: acquired from, bought from, purchased from, seller
Representsproprietor (Q16869121)
Data typeItem
Template parameterc:template:Template:ProvenanceEvent "oldowner"
Domainitems work of art (Q838948)
Allowed valuesperson (Q215627), organization (Q43229)
Example 1At Girl with a Pearl Earring (Q185372):
significant event
  purchasing
point in time 1881
beforehand owned by Arnoldus Andries des Tombe
0 references
add reference


add value
Example 2At The Bohemian (Q1000128):
Example 3At The meeting of Jacob and Rachel (Q53673495):
Planned useLook through items which use of (P642) qualifier of significant event (P793) to see if we can fix some of the ambiguous statements by replacing of (P642) with the new properties. I would also rewrite c:Module:Wikidata art's "get_object_history" function used by c:Template:Artwork.
See alsoowned by (P127), significant event (P793), of (P642) (might get depreciated)
Distinct-values constraintno
Wikidata projectWikiProject Painting (Q14942930)
Proposed byJarekt (talk) 03:54, 14 February 2022 (UTC)

afterwards owned byEdit

   Under discussion
Descriptionperson or institution that owned the subject after stated event. Aliases: acquired by, bought by, purchased by, buyer
Representsproprietor (Q16869121)
Data typeItem
Template parameterc:template:Template:ProvenanceEvent "newowner"
Domainitems work of art (Q838948)
Allowed valuesperson (Q215627), organization (Q43229)
Example 1At Mona Lisa (Q12418):
significant event
  acquisition
point in time 1519
afterward owned by Francis I of France
0 references
add reference


add value
Example 2At The Bohemian (Q1000128):
Example 3At Bridge in winter (Q79041853):
Planned useLook through items which use of (P642) qualifier of significant event (P793) to see if we can fix some of the ambiguous statements by replacing of (P642) with the new properties. I would also rewrite c:Module:Wikidata art's "get_object_history" function used by c:Template:Artwork.
See alsoowned by (P127), significant event (P793), of (P642) (might get depreciated)
Distinct-values constraintno
Wikidata projectWikiProject Painting (Q14942930)
Proposed byJarekt (talk) 03:54, 14 February 2022 (UTC)

MotivationEdit

When describing provenance of artworks one of the most useful properties on Wikidata is significant event (P793), while on Commons we model it with c:Template:ProvenanceEvent template. One challenge with P793 property is that different types of events require different set of qualifiers to fully describe the event. Some events can be well modeled with the existing properties (like bequest (Q211557) or art theft (Q1756454)), however the most often used group of events which describe some form of change of ownership (for example change of ownership (Q14903979), significant event (P793), sales (Q194189), auction (Q177923), purchasing (Q1369832), trade (Q601401), etc.) do not have usable properties for describing old and new owners. As a result, many artworks are missing this most basic information about the event, or items use badly fitting existing properties resulting in unclear statements open to interpretations.

Some examples of such confusing or statements:

At Mona Lisa (Q12418)
significant event
  acquisition
point in time 1519
of Francis I of France
0 references
add reference


add value

where "of (P642)" property is used to specify either seller or the buyer. In above case it is a buyer, but at almost identical statement for The meeting of Jacob and Rachel (Q53673495) it is a buyer. I am not sure of other languages but in English it seems like we are talking about "acquisition" "of" that person.

At Girl with a Pearl Earring (Q185372)
significant event
  purchasing
point in time 1881
owned by Arnoldus Andries des Tombe
price 2 Dutch guilder
0 references
add reference


add value

where owned by (P127) property is used to specify the owner either before or after the transaction, but it is not clear which one.

So the motivation for those properties is to

  • be able to accurately models statements like "Acquisition method: purchased from Thomas Agnew and Sons Ltd, 1937"[5], which is currently not possible
  • to fix previously added ambiguous statements
  • to provide better mapping between Wikidata's data model and the way we model the same data since 2009 using c:Template:ProvenanceEvent on Commons and allow better use of Wikidata resources by c:Module:Artwork and other projects
--Jarekt (talk) 05:22, 14 February 2022 (UTC)

DiscussionEdit

  •   Support A question might be: how much of this is redundant to owned by (P127), or could be done via that property. But I think these two new properties would be much neater, notably for modelling 'provenance events' where we have a particular pattern of data.
    Yes, a "beforehand owner" should also be indicated by owned by (P127) + end time (P582) + end cause (P1534), and some people won't like that redundancy. But IMO, when we have data about a particular sale event, it is useful to be able to pull that together on a single statement, together perhaps with additional information like venue or auctioneer. Yes, perhaps one might be able to infer from "X owned the portrait until ..." + "Y owned the portrait from ...", that X had sold it to Y. But that might be an inference that might be wrong, because the actual chain might have been, X sold it to dealer A, who sold it at auction to dealer B, who sold it privately to Y.
    So having the information of the actual transfer in a single significant event (P793) statement is useful, I think, and does seem more secure and a more sure way of modelling things, than trying to draw inferences from owned by (P127) statements even when apparently successive. I therefore support these two properties, as together creating a useful neat and tidy model for such transaction events. Jheald (talk) 16:00, 14 February 2022 (UTC)
    • Agree to this whole analysis that it can create some redundancy, but is still useful. --Marsupium (talk) 08:42, 7 May 2022 (UTC)
  •   Comment Provenance is complicated so thanks for adding these proposals and spelling out issues with Commons templates that I heavily use but which are still a mystery to me. I suspect this conversation can better be had over at Wikidata:WikiProject Provenance, which I set up to gather such questions and answers. Despite the desire to place provenance events in a distinct timeline, I doubt it’s always possible to do with “before & after” context in a verifiable way that would make such properties useful. In the end we would like to use dates as much as possible but for inheritance chains it would be nice to be able to do those “by inheritance” handoffs semi-automatically. Jane023 (talk) 15:50, 15 February 2022 (UTC)
Jane023, Thanks for alerting me about Wikidata:WikiProject Provenance. I did a lot of digging about current providence modeling, but never run into it. --Jarekt (talk) 02:58, 20 February 2022 (UTC)
  • I had to dig a bit to find Wikidata_talk:WikiProject_sum_of_all_paintings/Archive/2020#Refining_provenance_events, nothing really happened so thanks for bringing this up again. This is a more generic problem. We have events that involve multiple actors, one persons sells and the other buys. That's both the same event. This proposal seems to be too limited in scope. Probably needs more refinement. Maybe we can have a look how this gets modeled in other place? So   Oppose for now to prevent premature creation. Multichill (talk) 21:05, 16 February 2022 (UTC)
    • Multichill, I am fine with refinement if there are some other ideas. Those 2 properties were based on how we were modeling it on Commons for the last decade, but I am open to alternative proposals. One think I would like to avoid is postponing this discussion for next number of years, because people are trying to model it now and the results are incomprehensible . A lot of provenance data you can find for artworks is an array of ownerships punctuated by change of ownership events. So we can model it either by owned by (P127) with the 2 book-end events or by significant event (P793) with before and after owners. I doubt you can find other approaches, but I am OK with wider discussion on how to model this (perhaps at Wikidata:WikiProject Provenance), before we proceed. --Jarekt (talk) 02:58, 20 February 2022 (UTC)
        Comment Multichill, Jarekt: To "Maybe we can have a look how this gets modeled in other place?" (repeating myself from here where Jarekt considere these properties in 2018 already): "They would be similar to CIDOC-CRM's P22 transferred title to (acquired title through) and P23 transferred title from (surrendered title through)".
      I think this is a good proposal, I think I want support it, but want to have a look into the CIDOC-CRM solution another time and read the full discussion here before. Are there more specific, good reasons against the properties, also considering the "postponing this discussion for next number of years"?? Best, --Marsupium (talk) 07:56, 30 April 2022 (UTC)
  •   Comment same as Jane023 and Multichill. Additional to Jane023 there are not only heritage chains but also sales-chains and combined chains by sales, heritage, gift and bequest. So we have to model credit line. And we have Wikidata_talk:WikiProject sum of all paintings/Archive/2021#Provenance, continued. There is also a need to express on loan; --Oursana (talk) 12:19, 18 February 2022 (UTC)

@Jarekt, Jheald, Jura1, Jane023, Multichill: I just want to give you an example with gift, which in my opinion works fine with owned by (P127) and gift: Statue of Venus (Q98784999). "previous owner" / "subsequent owner" can also be expressed by date and series ordinal (P1545). In my example I would rather delete significant event (P793)--Oursana (talk) 19:19, 12 March 2022 (UTC)

  • One of the main points was to reduce the use of "of" in significant event. In this case Oursana you have used significant event to show that Louis XV gave it as a gift in 1750. I added this the same way I have been doing for bequests, with donated by (P1028) with qualifier point in time (P585). To indicate reception, I added the qualifier start time (P580) to the relevant collection (P195) statement. It's still missing a location (P276) statement. Just saying "we need to model the credit line" is much more complex than adding a 'credit line' property or making a 'credit line' significant event. Jane023 (talk) 10:03, 13 March 2022 (UTC)
    • Please see also my changes to the example item The Bohemian (Q1000128). Jane023 (talk) 10:03, 13 March 2022 (UTC)
      • @Jane023: Have to admit, I can't see a Bouguereau now without thinking of this sequence in a documentary a few years back by David Hockney: [6]  :-)
As to the edits, yes you can now sort-of work out what happened (or at least you can as a human), by spotting that the start of the time in the collection at Minneapolis matches the time of the donation; but I do think that the "subsequent owner" property proposed here would a valuable addition, to make the chain a lot more concrete, without needing to use a certain amount of inference to 'join the dots'.
Good move to try to get rid of of (P642) though, it's a menace. Jheald (talk) 19:56, 14 March 2022 (UTC)
Thanks for that clip! Bouguereau annoys me personally for a multitude of reasons, but this wasn't one of them until now. Thanks for the approval and my intention was to show how modelling provenance can never be done in one property, but it touches virtually all properties we currently use for paintings (including at times, dimensions and painting surface). In this case, I also changed the significant event itself, from the general sales (Q194189) to art auction (Q74570489), because the qualifier lot number (P4775) was used. I have been using this combo for works that have sold for high prices, such as this one. That said, in my opinion the other more significant part of this event in this particular case is deaccessioning (Q25339601) which I added under has cause (P828). The reason I set up the WikiProject Provenance was to centralize decisions on this. As far as I can tell reading through this proposal, the before and after are just for use in modelling significant events for artworks? I assume because we haven't decided what types of Qids can be the object of the before & after? I would like to draw a line in the sand as far as types of entities that can be collections or owners, but have been unsuccessful thus far in ordering my thoughts on this. I am unwilling to touch P127 on the Mona Lisa, but I disagree with stuffing whole countries in there. To sum up my objection to this specific proposal: There are more ways to get rid of "of" by getting rid of the significant event using other properties. Jane023 (talk) 11:43, 15 March 2022 (UTC)
  •   Support, an important property for culture.--Arbnos (talk) 15:15, 23 April 2022 (UTC)
  •   Comment Jarekt, would you be okay with replacing anonymous (Q4233718) ("term used to describe the unknown creator of a work") in the examples with "some value"? Thanks, --Marsupium (talk) 08:42, 7 May 2022 (UTC)
  •   Support per all above, modelling for this is needed, the proposed properties solve at least part of the problems, I don't see huge issues with this proposal, no good alternatives shown, proposed modelling is in line with CIDOC-CRM. --Marsupium (talk) 08:42, 7 May 2022 (UTC)

Culture.ru institutes IDEdit

   Under discussion
Descriptionidentifier of a cultural institution on the portal Culture.ru
RepresentsCulture.ru (Q62561023)
Data typeExternal identifier
Domainculture of Russia (Q1976715)
Example 1Bolshoi Theatre (Q138908)10218
Example 2Hermitage Museum (Q132783)1485
Example 3Russian State Library (Q1048694)15458
Example 4Cathedral of Christ the Saviour (Q194474)7808
Example 5Russian Institute of Theatre Arts (Q2177054)35014
Example 6Yasnaya Polyana (Q749556)14699
Sourcehttps://culture.ru
External linksUse in sister projects: [ar][de][en][es][fr][he][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd].
Planned usefor usage in stated in (P248) and for Template:Authority control (Q3907614)
Number of IDs in sourceunknown
Expected completenesseventually complete (Q21873974)
Formatter URLhttps://www.culture.ru/institutes/$1
Robot and gadget jobsYes, it would be great to have a separate mix'n'match catalog.
See alsoCulture.ru person ID (P10417)
Wikidata projectRussia

MotivationEdit

Culture.ru is the largest site dedicated to Russian culture and the culture of the peoples of Russia. Started in 2013 under the auspices of the Ministry of Culture of Russia, it has become one of the most popular sites on theater, cinema, literature, architecture, etc. MasterRus21thCentury (talk) 19:34, 11 March 2022 (UTC)

DiscussionEdit

colocated withEdit

MotivationEdit

Conference Entries such as https://www.wikidata.org/wiki/Q105979018 should IMHO be avoided. This entry IMHO denotes three different events that are colocated with each other. They happen at the same date and location but are different events with different proceedings and so on.

Workshops are often colocated with conferences, sometimes conferences are colocated with each other. Being able to show these relations will make curating scientifc events easier.

WolfgangFahl (talk) 15:14, 12 March 2022 (UTC)

DiscussionEdit

  •   Comment This does seem to be a reasonable proposal for a relationship we don't currently have. However, can you create suitable examples from existing Wikidata items to clarify exactly how you plan for this proposed property to work? ArthurPSmith (talk) 18:24, 14 March 2022 (UTC)
  •   Comment The example in the motivation would have to be split into three different events. http://ceur-ws.org/Vol-139/ shows the proceedings of a workshop that if it should be entered into wikidata would have it's own entry while the conference it is colocated with https://mobiquitous.eai-conferences.org/2021/ would be another entry linked by the proposed property. In my database at https://conferencecorpus.bitplan.com/ there are 66 examples that have "colocated" even in the title and would need splitting and linking via the property. https://dblp.org/db/conf/etaps/index.html shows the colocation of a whole series of workshops with the ETAPS Event series.

query

SELECT source,coalesce(year, '') year,title
FROM event where title like "%colocated%"
order by year,source


result

source year title
tibkat 1998 24th European Conference on Optical Communication, September 20 - 24, 1998, Madrid, Spain, [colocated with: 4th European Exhibition on Optical Communication], EEOC '98 / ECOC '98. [Organized by Telefónica...] ; Vol. 1: Regular and invited papers
tibkat 1998 24th European Conference on Optical Communication, September 20 - 24, 1998, Madrid, Spain, [colocated with: 4th European Exhibition on Optical Communication], EEOC '98 / ECOC '98. [Organized by Telefónica...] ; Vol. 2: Tutorials and symposium papers; Symposium on Extended Wavelength and Second Window Optical Amplifiers
tibkat 1998 24th European Conference on Optical Communication, September 20 - 24, 1998, Madrid, Spain, [colocated with: 4th European Exhibition on Optical Communication], EEOC '98 / ECOC '98. [Organized by Telefónica...] ; Vol. 3: Postdeadline papers
crossref 2004 Proceedings of the 7th International Workshop on the Web and Databases colocated with ACM SIGMOD/PODS 2004 - WebDB '04
dblp 2004 Proceedings of the Seventh International Workshop on the Web and Databases, WebDB 2004, June 17-18, 2004, Maison de la Chimie, Paris, France, Colocated with ACM SIGMOD/PODS 2004
dblp 2005 P2PKM '05, Peer-to-Peer Knowledge Management, Proceedings of the Second Workshop on Peer-to-Peer Knowledge Management, July 17, 2005, UCSD, La Jolla, San Diego, California, USA - Colocated with The Second Annual International Conference on Mobile and Ubiquitous Systems: Networking and Services (MobiQuitous 2005)
dblp 2007 Anticipatory Behavior in Adaptive Learning Systems, From Brains to Individual and Social Behavior [the book is a result from the third workshop on anticipatory behavior in adaptive learning systems, ABiALS 2006, Rome, Italy, September 30, 2006, colocated with SAB 2006]
dblp 2007 Proceedings of the 1st International Workshop on Ambient Information Systems, Colocated at Pervasive 2007, Toronto, Canada, May 13, 2007
dblp 2007 Proceedings of the 2nd International Workshop on Case Based Reasoning and Context-Awareness Colocated with the 7th International Conference on Case Based Reasoning (ICCBR), Belfast, Northern Ireland, August 15, 2007
dblp 2007 PLAN-X 2007, Programming Language Technologies for XML, An ACM SIGPLAN Workshop colocated with POPL 2007, Nice, France, January 20, 2007
tibkat 2007 Scheduling and planning applications : selected papers from the Spark Workshop series ; [papers presented in this volume have been selected from the International Scheduling and Planning Applications WoRKshop (SPARK) series, colocated with the International Conference on Automated Planning and Scheduling (ICAPS) ... This special issue gathers selected contributions from 2007 to 2008 editions]
tibkat 2007 5th International Conference on Natural Language Processing (ICON-2007) : January 4 - 6, 2007 ; [colocated with IJCAI-07]
tibkat 2007 Special issue on pulsed power science and technology : [... 16th IEEE International Pulsed Power Conference held in Albuquerque, NM, in 2007 ; this conference was combined with the 34th IEEE International Conference on Plasma Science (ICOPS) ; in addition, a joint plenary session was held with the colocated 22nd IEEE Symposium on Fusion Engineering]
tibkat 2007 2007 IEEE Symposium on Computers and Communications : [ISCC 2007]; Santiago [i.e. Aveiro], Portugal, 1 - 4 July 2007; [colocated with the Second Workshop on MultiMedia Applications over Wireless Networks, MediaWin 2007] / [sponsored by: IEEE Communications Society; IEEE Computer Society...] ; Vol. 1
tibkat 2007 2007 IEEE Symposium on Computers and Communications : [ISCC 2007]; Santiago [i.e. Aveiro], Portugal, 1 - 4 July 2007; [colocated with the Second Workshop on MultiMedia Applications over Wireless Networks, MediaWin 2007] / [sponsored by: IEEE Communications Society; IEEE Computer Society...] ; Vol. 2
tibkat 2007 2007 IEEE Symposium on Computers and Communications : [ISCC 2007]; Santiago [i.e. Aveiro], Portugal, 1 - 4 July 2007; [colocated with the Second Workshop on MultiMedia Applications over Wireless Networks, MediaWin 2007] / [sponsored by: IEEE Communications Society; IEEE Computer Society...] ; Vol. 3
tibkat 2007 12th IEEE Symposium on Computers and Communications, 2007 : ISCC 2007 ; 1 - 4 July 2007, Aveiro, Portugal ; [colocated with the] Second Workshop on MultiMedia Applications over Wireless Networks, MediaWin 2007
CEUR-WS 2008 Proceedings of Workshops colocated with the MobIS-2008 conference: EPK-2008, KobAS-2008 and ModKollGP-2008,Saarbrücken, Germany, November 27-28, 2008.Submitted by: Thorsten Dollmann, Peter Loos
dblp 2008 Proceedings of the Workshops colocated with the MobIS2008 Conference: Including EPK2008, KobAS2008 and ModKollGP2008, Saarbrücken, Germany, November 27-28, 2008
dblp 2008 PLAN-X 2008, Programming Language Technologies for XML, An ACM SIGPLAN Workshop colocated with POPL 2008, San Francisco, California, USA, January 9, 2008
tibkat 2010 14th Conference on Computational Natural Language Learning 2010 : (CoNLL 2010); colocated with ACL 2010; Uppsala, Sweden, 15 - 16 July 2010 / [organized by SIGNLL, the ACL Special Interest Group on Natural Language Learning]
tibkat 2010 14th Conference on Computational Natural Language Learning 2010 : (CoNLL 2010); colocated with ACL 2010; Uppsala, Sweden, 15 - 16 July 2010 / [organized by SIGNLL, the ACL Special Interest Group on Natural Language Learning]: Shared task
tibkat 2011 Special issue: agent-based simulations, adaptive algorithms, ICCS 2011 Workshop : [... is devoted to the papers presented during "Agent Based Simulations, Adaptive Algorithms and Solvers" Workshop colocated with the Eleventh International Conference on Computational Sciences, held in Singapore (June 1 - 3, 2011)
dblp 2012 Coalgebraic Methods in Computer Science - 11th International Workshop, CMCS 2012, Colocated with ETAPS 2012, Tallinn, Estonia, March 31 - April 1, 2012, Revised Selected Papers
dblp 2012 1st International Workshop on Cloud Intelligence (colocated with VLDB 2012), Cloud-I '12, Istanbul, Turkey, August 31, 2012
tibkat 2012 Coalgebraic methods in computer science : 11th international workshop, CMCS 2012, colocated with ETAPS 2012, Tallin, Estonia, March 31 - April 1, 2012 ; revised selected papers
tibkat 2012 Intelligent narrative technologies : papers from the 2012 AIIDE workshop ; [held October 8 - 9, 2012 at Stanford University, Stanford, California, USA ; colocated with the 8th AAAI Conference on Artificial Intelligence and Interactive Digital Entertainment (AIIDE'12)]
CEUR-WS 2013 Proceedings of the Educators' Symposium (EduSymp 2013) colocated with MODELS 2013,Miami, USA, September 30th, 2013.Submitted by: Perdita Stevens
dblp 2013 2nd International Workshop on Cloud Intelligence (colocated with VLDB 2013), Cloud-I '13, Riva del Garda, Trento, Italy, August 26, 2013
dblp 2013 Grid and Pervasive Computing - 8th International Conference, GPC 2013 and Colocated Workshops, Seoul, Korea, May 9-11, 2013. Proceedings
tibkat 2013 2013 9th International Conference on Network and Service Management (CNSM 2013) [and its three colocated workshops 8th International Workshop on Internet Charging and QoS Technologies (ICQT), 7th International DMTF Academic Alliance Workshop on Systems and Virtualization Management (SVM), Workshop on Social-aware Economic Traffic Management for Overlay and Cloud Applications (SETM)] : Zürich, Switzerland, 14 - 18 October 2013
tibkat 2013 2013 9th International Conference on Network and Service Management (CNSM) and its three colocated workshops 8th International Workshop on Internet Charging and QoS Technologies (ICQT), 7th International DMTF Academic Alliance Workshop on Systems and Virtualization Management (SVM), Workshop on Social-aware Economic Traffic Management for Overlay and Cloud Applications (SETM) : Zürich, Switzerland, 14 - 18 October 2013
tibkat 2013 2013 17th International Conference on Information Visualisation (IV 2013) : London, United Kingdom, 16 - 18 July 2013 ; [including papers of colocated conferences]
wikicfp 2013 SDAIN 2013 : 2nd International Workshop on Semantic and Dynamic Analysis of Information Networks - SDAIN 2013 colocated with ASONAM 2013
dblp 2014 Coalgebraic Methods in Computer Science - 12th IFIP WG 1.3 International Workshop, CMCS 2014, Colocated with ETAPS 2014, Grenoble, France, April 5-6, 2014, Revised Selected Papers
tibkat 2014 Coalgebraic methods in computer science : 12th IFIP WG 1.3 international workshop, CMCS 2014, colocated with ETAPS 2014, Grenoble, France, April 5 - 6, 2014 ; revised selected papers
tibkat 2015 2015 Workshop on Socio-Technical Aspects in Security and Trust (STAST 2015) : Verona, Italy, 13 July 2015 : [colocated with 28th IEEE Computer Security Foundations Symposium (CSF)]
tibkat 2015 2015 Workshop on Socio-Technical Aspects in Security and Trust (STAST) : 13 July 2015, Verona, Italy : colocated with 28th IEEE Computer Security Foundations Symposium (CSF)
dblp 2016 Coalgebraic Methods in Computer Science - 13th IFIP WG 1.3 International Workshop, CMCS 2016, Colocated with ETAPS 2016, Eindhoven, The Netherlands, April 2-3, 2016, Revised Selected Papers
dblp 2016 Proceedings of the First Conference on Machine Translation, WMT 2016, colocated with ACL 2016, August 11-12, Berlin, Germany
tibkat 2016 Coalgebraic methods in computer science : 13th IFIP WG 1.3 international workshop, CMCS 2016, colocated with ETAPS 2016, Eindhoven, The Netherlands, April 2-3, 2016 : revised selected papers
dblp 2018 Coalgebraic Methods in Computer Science - 14th IFIP WG 1.3 International Workshop, CMCS 2018, Colocated with ETAPS 2018, Thessaloniki, Greece, April 14-15, 2018, Revised Selected Papers
dblp 2018 PROOFS 2018, 7th International Workshop on Security Proofs for Embedded Systems, colocated with CHES 2018, Amsterdam, The Netherlands, September 13, 2018
tibkat 2018 Coalgebraic methods in computer science : 14th IFIP WG 1.3 International Workshop, CMCS 2018, colocated with ETAPS 2018, Thessaloniki, Greece, April 14–15, 2018 : revised selected papers
wikicfp 2018 BigCyber 2018 : Workshop on Big Data for CyberSecurity (Colocated with IEEE BigData 2018)
wikicfp 2018 DSHCM 2018 : The 2nd International Workshop on Data Science for Human Capital Management (colocated with ECML-PKDD'18)
CEUR-WS 2019 Proceedings of the First Workshop on Intelligent Textbooks (iTextbooks 2019), colocated with AIED 2019,Chicago, IL, USA, June 25, 2019.Submitted by: Sergey Sosnovsky
dblp 2019 Proceedings of 8th International Workshop on Security Proofs for Embedded Systems, PROOFS 2019, colocated with CHES 2018, Atlanta, GA, USA, August 24, 2019
CEUR-WS 2020 Proceedings of the PrivateNLP 2020: Workshop on Privacy in Natural Language Processing- Colocated with WSDM 2020, Houston, USA, Feb 7, 2020.Submitted by: Sepideh Ghanavati
dblp 2020 Joint Proceedings of Workshops AI4LEGAL2020, NLIWOD, PROFILES 2020, QuWeDa 2020 and SEMIFORM2020 Colocated with the 19th International Semantic Web Conference (ISWC 2020), Virtual Conference, November, 2020.
dblp 2020 Coalgebraic Methods in Computer Science - 15th IFIP WG 1.3 International Workshop, CMCS 2020, Colocated with ETAPS 2020, Dublin, Ireland, April 25-26, 2020, Proceedings
dblp 2020 GPGPU@PPoPP '20: 13th Annual Workshop on General Purpose Processing using Graphics Processing Unit colocated with 25th ACM SIGPLAN Symposium on Principles and Practice of Parallel Programming, San Diego, California, USA, February 23, 2020
dblp 2020 PMAM@PPoPP '20: Eleventh International Workshop on Programming Models and Applications for Multicores and Manycores colocated with the 25th ACM SIGPLAN Symposium on Principles and Practice of Parallel Programming, San Diego, California, USA, February 22, 2020
dblp 2020 Proceedings of the PrivateNLP 2020: Workshop on Privacy in Natural Language Processing - Colocated with WSDM 2020, Houston, USA, Feb 7, 2020.
tibkat 2020 Coalgebraic methods in computer science : 15th IFIP WG 1.3 international workshop, CMCS 2020, colocated with ETAPS 2020, Dublin, Ireland, April 25-26, 2020 : proceedings
tibkat 2020 ASLD 2020 - advances in semantics and linked data: joint workshop proceedings from ISWC 2020 : joint proceedings of workshops AI4LEGAL2020, NLIWOD, PROFILES 2020, QuWeDa 2020 and SEMIFORM2020 : colocated with the 19th International Semantic Web Conference (ISWC 2020) : virtual conference, November, 2020
tibkat 2020 PrivateNLP 2020: Workshop on Privacy in Natural Language Processing : proceedings of the PrivateNLP 2020: Workshop on Privacy in Natural Language Processing - colocated with WSDM 2020 : Houston, USA, Feb 7, 2020
wikicfp 2020 DSRE 2020 : Data Science for Retail and E-commerce workshop (colocated with SIAM SDM 20)
wikicfp 2020 KGEcom 2020 : Knowledge Graphs and E-commerce workshop, colocated with ACM KDD'2020
wikicfp 2020 NLPaSE 2020 : 1st Workshop on Natural Language Processing Advancements for Software Engineering (NLPaSE) Colocated with 27th APSEC 2020
tibkat FOOL VII : [Seventh International Workshop on Foundations of Object-Oriented Languages, held on January 22, 2000, colocated with the ACM Symposium on Principles of Programming Languages in Boston, Massachusetts, USA]
tibkat Final program and proceedings - DPP 2005, International Conference on Digital Production Printing and Industrial Applications : May 9 - 13, 2005, Amsterdam, the Netherlands ; colocated with GRAFIVAK
tibkat Emerging web services technology, volume III : [proceedings of the 3rd Workshop on Emerging Web Services Technology 2008 (WEWST '08), which was colocated with the 6th European Conference on Web Services (ECOWS '08) and took place in November 2008 in Dublin, Ireland]
tibkat Emerging Web Services Technology Volume III : [this third volume on Emerging Web Services Technologies follows the current research activities in the areas of Web Services and Service Oriented Architectures. It includes the proceedings of the 3rd Workshop on Emerging Web Services Technology 2008 (WEWST'08), which was colocated with the 6th European Conference on Web Services (ECOWS'08) and took place in November 2008 in Dublin, Ireland. In addition, this volume features three papers from the ECOWS'08 business track.]
tibkat BioNLP shared task 2013 : Sofia, Bulgaria, 9 August 2013 ; [presented at the ACL/HLT BioNLP-ST Workshop colocated with the BioNLP Workshop]
tibkat Proceedings of the 7th International Workshop on the Web and Databases colocated with ACM SIGMODPODS 2004

--WolfgangFahl (talk) 09:40, 29 March 2022 (UTC)

smb.museum-digital IDEdit

   Under discussion
Data typeExternal identifier
Domainartificial physical object (Q8205328)
Allowed values\d+
Example 1Bust of Willibald Imhoff (Q96315806)140048
Example 2MISSING
Example 3MISSING
Sourcehttps://smb.museum-digital.de
Number of IDs in source232422, https://smb.museum-digital.de/objects
Formatter URLhttp://smb.museum-digital.de/object/$1
See alsoP9957; P8923; Q1360745

MotivationEdit

very helpful to use identifier instead of complete url Oursana (talk) 23:37, 10 April 2022 (UTC)

DiscussionEdit

"SMB" see Berlin State Museums (Q700216)--Oursana (talk) 21:31, 6 May 2022 (UTC)
if you click top left of https://smb.museum-digital.de you get the complete range of md=museum digital concerning German museum https://www.museum-digital.de https://www.museum-digital.de/?lang=en https://nat.museum-digital.de/?navlang=en. We could rather create more properties.--Oursana (talk) 21:38, 6 May 2022 (UTC)

Fiction (in-universe perspective)Edit

Fiction (out-of-universe perspective)Edit

Fictional characterEdit