User talk:AdamSeattle

From Wikidata
Jump to navigation Jump to search

Logo of Wikidata Welcome to Wikidata, UWashCataloging!

Wikidata is a free knowledge base that you can edit! It can be read and edited by humans and machines alike and you can go to any item page now and add to this ever-growing database!

Need some help getting started? Here are some pages you can familiarize yourself with:

  • Introduction – An introduction to the project.
  • Wikidata tours – Interactive tutorials to show you how Wikidata works.
  • Community portal – The portal for community members.
  • User options – including the 'Babel' extension, to set your language preferences.
  • Contents – The main help page for editing and using the site.
  • Project chat – Discussions about the project.
  • Tools – A collection of user-developed tools to allow for easier completion of some tasks.

Please remember to sign your messages on talk pages by typing four tildes (~~~~); this will automatically insert your username and the date.

If you have any questions, don't hesitate to ask on Project chat. If you want to try out editing, you can use the sandbox to try. Once again, welcome, and I hope you quickly feel comfortable here, and become an active editor for Wikidata.

Best regards!

evs 💬 03:40, 13 July 2018 (UTC)[reply]

OLAC Video Game Genre Vocabulary (Q60440967)

[edit]

Hello!

Thank you for your changes on OLAC Video Game Genre Vocabulary (Q60440967).

I noticed you had added -instance of (P31)thesaurus (Q17152639).

Since thesaurus (Q17152639)subclass of (P279)controlled vocabulary (Q1469824), I had then removed -instance of (P31)controlled vocabulary (Q1469824): it would not be necessary to have both values as instance of (P31) − this is implicit per the subclass of (P279) relationship.

Unless is it wrong to have thesaurus (Q17152639)subclass of (P279)controlled vocabulary (Q1469824)?

Cheers, Jean-Fred (talk) 09:29, 16 June 2020 (UTC)[reply]

Q207761

[edit]

Hi! Please note that Q-items on Wikidata are about concepts, not words. Hence different items should be created for different concepts denoted by the same word. Data about words can be entered as Wikidata:Lexicographical data in "Lexeme" namespace instead. 2001:7D0:81F7:B580:D996:CF7C:6B2B:63C0 08:06, 22 September 2020 (UTC)[reply]

Also, please don't mix ethnic group and nationality (or sum of all residents of a country). E.g. Estonians (Q173302) (ethnic group) and citizens (or residents) of Estonia are entirely different groups of people. If in some relation it becomes useful, and it isn't enough to say that e.g. an individual is a citizen of Estonia or alike, then rather separate item should be created for Estonians or residents or citizens of Estonia, too. 2001:7D0:81F7:B580:F519:F3B5:A49:8293 09:46, 16 November 2020 (UTC)[reply]

orientalist (Q1731155)

[edit]

Hello, please do not merge into the newest item. Thanks. Ayack (talk) 08:27, 10 October 2020 (UTC)[reply]

Wood chemistry

[edit]

Hello, you asked me of me removing YSO ID from the item wood chemistry (Q25451366). I am one of the maintainers of YSO at National Library of Finland. YSO is a trilingual vocabulary (Finnish, Swedish, English). wood chemistry (Q25451366) is/was an item with no links to Wikipedia. On the other hand, there were two items, Q31886986 (Swedish: träkemi) and Q99196245 (Finnish: puukemia), with identical meanings that both had one Wikipedia article link to Swedish Träkemi and Finnish Puukemia respectively. As you say, "wood chemistry" is indeed "puukemia" in Finnish. On the other hand, in Swedish "wood chemistry" is called "träkemi". Thus there were separate items in all these three languages (English, Finnish, Swedish) when there should have been only one. I merged all the three items into one and linked YSO with the remaining item. I've been instructed by Wikimedia Finland that a) it is safest to link to the remaining item and not the one(s) that have been merged with it and b) it is best to keep the oldest item while merging. I followed these instructions. Tpalonen (talk) 11:20, 2 December 2020 (UTC)[reply]

  • Thank you for your reply! And thank you for bringing up the lowercase issue. It is indeed quite common for the Finnish labels in Wikidata to have an upper case initial. My theory for this is that many of them may have been generated from the Finnish Wikipedia article topic. Tpalonen (talk) 12:00, 2 December 2020 (UTC)[reply]

Adding YSO ID's to items

[edit]

Hello, I'm an information specialist working at National Library of Finland's Finto service where we are linking General Finnish Ontology (YSO) concepts to Wikidata items at the moment. As you may know, YSO is an indexing tool used widely in the Finnish library sector as well as in museums, archives, public administration and media. I noticed that you have added YSO id's to Wikidata items. While we appreciate your kindess, we would also like to remind that YSO concepts are maintained by a team of information specialists and are a result of careful concept analysis. Each concept has a specific meaning, indicated foremost by its Finnish and Swedish preferred terms and its broader concepts in the ontology hierarchy, but also, in practical terms, by its use in indexing of Finnish non-fiction literature and other domains. Any links made should be in accordance with the precise meaning of the concept. Therefore, while we are happy to receive help, we also express that anybody who's willing to help us in linking YSO concepts to Wikidata should have excellent skills in Finnish and Swedish and should follow the guidelines given by National Library of Finland (for example, see our guidelines for linking YSO to LCSH in the link, all of these won't apply to Wikidata, however, as we are only using SKOS:closeMatch with Wikidata as opposed to closeMatch/narrowMatch/broadMatch in the case of LCSH: https://www.kiwi.fi/display/Finto/YSOn+LCSH-linkitysten+linjaukset). For example, online translation tools such as Google Translate are not a good enough source for judging the equivalence of a Wikipedia item and a YSO concept. If you are interested in helping us more, please contact us. See our contact info here: https://www.kansalliskirjasto.fi/en/services/system-platform-services/finto Thank you! Tpalonen (talk) 11:38, 2 December 2020 (UTC)[reply]

Label and case

[edit]

Hi,

Unlike Wikipedia articles title, the label on Wikidata is not a title ; that's why the case is different (and that's why I changed ~5000 labels today, like I do every months for years now). See Help:Label#Capitalization for more details.

Cheers, VIGNERON (talk) 19:48, 31 October 2020 (UTC)[reply]

Filiberto Barajas-López (Q101012047)

[edit]

Thanks for adding Library of Congress authority ID (P244) ! Did this exist at the time I created the item? I must have forgotten to look... Riesengrey (talk) 23:04, 12 November 2020 (UTC)[reply]

nature conservation

[edit]

You moved many articles from conservation (Q628403) to nature conservation (Q20113959). I do not understand what the difference of the subject of these items is and what your criteria for having articles liked one or the other item is. Could you explain this? --GPSLeo (talk) 12:34, 13 January 2021 (UTC)[reply]

Conservation is a broader concept than Nature conservation. Conservation includes energy resources, mineral resources, agriculture, water resources, etc. The links I moved are for nature conservation specifically (https://en.wikipedia.org/wiki/Nature_conservation), which should be linked to the Wikidata item for nature conservation, not the more general item on conservation. I left the Wikipedia links that are broader on the item for conservation. See also https://en.wikipedia.org/wiki/Conservation, which discusses the differences of types of conservation. UWashPrincipalCataloger (talk) 18:32, 13 January 2021 (UTC)[reply]
I understand the difference but then I do not see the difference to environmental protection (Q832237). Another problem conservation (Q628403) has the statement instance of (P31) branch of biology (Q28598684) with the new definition this statement would be false. But I also think things you wrote as included in Conservation but not in nature conservation are included in nature conservation. The enwiki has "enhancing ecosystem services" as part of nature conservation and the definition in dewiki has, based on the German law, the protection of artificial landscapes like agricultural landscapes as part of nature conservation. --GPSLeo (talk) 19:27, 13 January 2021 (UTC)[reply]
As I understand it, environmental protection (Q832237) would cover things like air and water quality, soil pollution, protection from hazardous wastes, etc., none of which would be considered part of nature conservation. I fixed the relationship problem that you mentioned. I'm also fixing labels so that they are on the right item. And I'm adding more identifiers to the nature conservation and related items. UWashPrincipalCataloger (talk) 20:22, 13 January 2021 (UTC)[reply]

Two VIAF

[edit]

Hi Adam. The script for adding identifiers works pretty cool. Thanks for suggesting that. It saves a lot of time. I wanted to ask you one question. What should we do if the person has two different VIAF pages ? --Gazal world (talk) 18:10, 15 January 2021 (UTC)[reply]

Hi, the best thing to do is to report the duplicates to OCLC. There's "feedback" link on each VIAF page that you can use. You can also put both IDs into the item for now. --Adam UWashPrincipalCataloger (talk) 18:24, 15 January 2021 (UTC)[reply]

Ok. Got it. I will do as you suggested. One more question ? How to add identifiers for books? For example this book. --Gazal world (talk) 14:10, 16 January 2021 (UTC)[reply]
See https://www.wikidata.org/wiki/Wikidata:WikiProject_Books. The type of identifiers you can add depends on what the item represents. There should be one item for the work, and then separate items for any editions of the work. ISBNs can only go on edition items. The WikiProject Books page explains everything. Lord and Peasant in Russia: From the Ninth to the Nineteenth Century (Q104844726) appears to represent the work, since it is the only item for this work. On this record you can add the properties for work found at https://www.wikidata.org/wiki/Wikidata:WikiProject_Books#Work_item_properties. Then you can create separate items for specific editions of the work by following https://www.wikidata.org/wiki/Wikidata:WikiProject_Books#Edition_item_properties. Here's an example that I did recently: Tacoma Stories (Q104593306) and Tacoma Stories (First edition) (Q104594562). UWashPrincipalCataloger (talk) 23:52, 16 January 2021 (UTC)[reply]

Your modification

[edit]

Hello UWashPrincipalCataloger, Your modification doesn't suit a property. Cordially. —Eihel (talk) 07:12, 29 January 2021 (UTC)[reply]

wrong LCCN entries

[edit]

Hi, since you are a professional librarian from the US, I though I might ask you: Is there any way to have faulty LCCN entries (like conflations) corrected? I know nobody who managed to contact the LC in any way … --Emu (talk) 11:12, 2 February 2021 (UTC)[reply]

Hi Emu, probably the simplest way would be to contact LC at coop@loc.gov to report a problem with an LCCN that represents more than one person. Or contact a NACO library from the directory at https://www.loc.gov/aba/pcc/naco/contact.html. UWashPrincipalCataloger (talk) 18:52, 2 February 2021 (UTC)[reply]

Your edit at RfD

[edit]

Hi, you removed Deletion requests with your recent edit at WD:RfD. If that happened on purpose, can you provide an explanation; If it didn't happen on purpose, can you please undo it and make sure that it doesn't happen again? Thank you -- Dr.üsenfieber (talk) 12:17, 16 February 2021 (UTC)[reply]

I did not intentionally remove any requests, and I am baffled about this. The only thing that I did on this page yesterday was to add a vote to keep Q54800218. I am unclear what exactly needs to be undone. UWashPrincipalCataloger (talk) 17:11, 16 February 2021 (UTC)[reply]

url farm on Q102047184

[edit]

Hi UWashPrincipalCataloger,

Somehow your approach on Q102047184 seems to go in the opposite way this is generally done: rather than determine the topic of an article and create an item for it, you added a set of identifier urls on the item of the topic. Besides, it isn't consistent with the purpose of described at URL (P973). Maybe you want to seek input on project chat on how to model this in general. --- Jura 00:21, 17 February 2021 (UTC)[reply]

I think you are misinterpreting the purpose of described at URL (P973). It is used to point to web sources that are about the item, not to the full text of the article that is represented by the item. described at URL (P973) is a subject link to sources on the web that describe the concept in the item. For an article item, the full text of the article isn't about the article, it is the article. I will follow up on project chat. UWashPrincipalCataloger (talk) 00:26, 17 February 2021 (UTC)[reply]

  • Two of the articles didn't have "main subject" link to the topic, I added it. @UWashPrincipalCataloger: I think @Jura1: is right: there are millions of articles that have "main subject" links to topics. The topics don't have links "described by source" to all those articles because there could be hundreds of thousands of articles about the same topic.
    I can't say that these are the best 4 articles, but I don't see anything in the property that requires this. I interpret the property as being used to link to items for useful sources that describe the topic. UWashPrincipalCataloger (talk) 20:37, 7 December 2021 (UTC)[reply]

Problematic property creation

[edit]

Hi UWashPrincipalCataloger,

If you create properties, please create them as proposed. DO NOT substantially alter them as done at [1]. If you think the proposal needs to be improved before creation, please participate in the discussion instead. "Polishing" them is fine (see Wikidata:Property_creators#Create_the_property). --- Jura 09:20, 28 February 2021 (UTC)[reply]

@Jura1: noted, thanks. UWashPrincipalCataloger (talk) 19:59, 28 February 2021 (UTC)[reply]

Unreferenced claim

[edit]

Hi UWashPrincipalCataloger

At [2], you added a claim about ethnic groups to Wikidata. Can you add a reference to this? You might want to have a look at w:Demographics_of_Zambia#Ethnic_groups.

On a related matter, please note that ethnic group (P172) has specific referencing requirements. --- Jura 07:13, 9 March 2021 (UTC)[reply]

  • Hi Jura1, ethnic group (Q41710) is defined as "socially defined category of people who identify with each other", and the Wikipedia article says it is a "grouping of people who identify with each other on the basis of shared attributes that distinguish them from other groups such as a common set of traditions, ancestry, language, history, society, culture, nation, religion, or social treatment within their residing area. Ethnicity is sometimes used interchangeably with the term nation ...", so on the basis of being a socially defined category based on being a nation, it seems that calling Zambians an ethnic group is acceptable. Nearly every item for the people of a country have a statement that they are an instance of an ethnic group. I've added a few sources that I hope are acceptable. In particular, the first, http://www.zambiapretoria.net/demography/, says: "Culture Name: Zambian."

UWashPrincipalCataloger (talk) 07:45, 9 March 2021 (UTC)[reply]

    • Well, all claims about ethnic groups should have such references. Ideally these meet the requirements of ethnic group (P172). The demographics article about the country seems to have a different view. If one uses two terms interchangeably, it's unclear why one would add claims with items for each as statements. --- Jura 08:00, 9 March 2021 (UTC)[reply]

Christine K Luscombe (Q45766736)

[edit]

Hi Adam, you have reverted my Edit on Christine K Luscombe (Q45766736). Here is the reference for "Country of Citizenship" [3] - so I would suggest to take both USA/JPN ?! In Germany you become a citizenship at birth for the corresponding country - is this other in the US ? Best regards, --Erfurth (talk) 09:46, 10 March 2021 (UTC)[reply]

@Erfurth: Japan has a rather strict ius sanguinis, so her birth in Kobe does not imply Japanese citizenship. As she wasn’t born in the US, her being an American citizen isn’t so sure either (but may very well be the case). Just leave it empty until proper references can be found. --Emu (talk) 10:12, 10 March 2021 (UTC)[reply]
@Erfurth, Emu: Agreeing with Emu, this is why I didn't include country of citizenship, because while it is likely she is an American citizen now, I didn't have any definitive information. I don't know if Japan requires someone to give up citizenship when they become citizens of another country, as some countries do. UWashPrincipalCataloger (talk) 17:40, 10 March 2021 (UTC)[reply]

ethnic group (Q41710)

[edit]

Hi, I have problem with your changes in Czechs (Q170217). After your changes there are 10 links to Czech Republic (Q213). But this object isn't related to the Czech Republic (See cs.wikipedia article or some links in encyclopedias). This is related to nation for long time in history. Same for Slovaks (Q171336). I don't understand sense of Czechoslovaks (Q100146275). There is Czechoslovakians (Q91075059), which was (1920-1948) real nation/nationality used in Czechoslovakia. After 1948 there were nationalities like Czechs (Q170217), Slovaks (Q171336) and others. Could you describe, what do you do? Skim (talk) 17:02, 10 March 2021 (UTC)[reply]

@UWashPrincipalCataloger: Ok, Czechs (Q105969758) and Czechs (Q170217) are somehow ok. I can't tell if Czechs (Q105969758) makes sense. I improved Czechoslovakians (Q91075059) for inception (P571) and dissolved, abolished or demolished date (P576) as official dates of this nation in Czechoslovakia (Q33946). I think, that's ok now. I will ping my community. Skim (talk) 06:29, 13 April 2021 (UTC)[reply]

Gymnocarpium ×brittonianum (Q17046489)

[edit]

I reverted your edits. --Succu (talk) 20:38, 10 April 2021 (UTC)[reply]

Amalia Rosenblüth (Rosenblueth)

[edit]

Hello, @Goesseln: wrote a new article (w:de:Amalia Rosenblüth) about Amalia Rosenblüth (Q101112434). She worked as a librarian at UWash and died in 1979 in Seattle. Do you have any idea how to find her exact death date online? Thanks a lot! --Emu (talk)

✓ Done I found her under her pseudonym! Sorry to bother you … --Emu (talk) 12:49, 12 April 2021 (UTC)[reply]
@Goesseln, Emu: I'm afraid you've confused two different universities. Her item says she worked at Washington University, which is a private university in Saint Louis, Missouri. It's often confused with the University of Washington, which is a state university in Seattle. UWashPrincipalCataloger (talk) 17:38, 12 April 2021 (UTC)[reply]
@Goesseln, Emu: After reading her Wikipedia article, it seems that it's her item that has the wrong information. I've changed the information so that it is correct. UWashPrincipalCataloger (talk) 17:40, 12 April 2021 (UTC)[reply]
Yes, indeed, sorry – American universities and their names are often confusing for me. Thanks for correcting the item! --Emu (talk) 20:11, 12 April 2021 (UTC)[reply]

May I borrow your time?

[edit]

One of my colleagues at English Wikisource put this local question Wikidata talk:WikiProject Periodicals#Properties for periodicals tiers: work/series/volume/issue/article and we would appreciate a professional PoV. We WSers are very good at transcribing old texts and getting better at presenting for the modern age. Cataloguing (and probably categorising) and the dark arts around the right meta data for the right place are less our skill set, so polite though firm commentary is always our wont. <shrug with rueful smile>  — billinghurst sDrewth 23:49, 14 April 2021 (UTC)[reply]

I'd be happy to try to help, but I am not a serials cataloger and haven't cataloged them for a very long time. There are some serials catalogers in the PCC Wikidata Pilot Project though (https://www.wikidata.org/wiki/Wikidata:WikiProject_PCC_Wikidata_Pilot), and you might get better information and guidance from one of them. If you'd like to compose an email to the pilot project participants, I could send it out for you on our discussion list and ask serials catalogers to contact you. UWashPrincipalCataloger (talk) 00:51, 15 April 2021 (UTC)[reply]

Our Campaigns race ID (P9446) not working properly

[edit]

Thanks for creating Our Campaigns race ID (P9446) - at least on my end, the identifiers aren't linked - you can't click them to go to the source website. I tried fixing this but I have no idea what the problem is, can you take a look? tysm! Elli (talk) 09:08, 16 April 2021 (UTC)[reply]

Ah, thanks for your help! Was very confused. Elli (talk) 17:55, 17 April 2021 (UTC)[reply]
@Elli: They are working now. UWashPrincipalCataloger (talk) 19:54, 17 April 2021 (UTC)[reply]

Q60723717

[edit]

Hi! I noticed that you added statements related to reality TV shows that are singing competitions to Q60723717, but this is a more generic item for singing competitions on TV and off of it. Could you please create a separate item for the TV-related ones? Thanks :) -Yupik (talk) 07:51, 23 April 2021 (UTC)[reply]

Hi, Yupik, I have created singing talent show (Q106603795) and revised some items and added it as a genre to a number of additional items. Hope this helps! UWashPrincipalCataloger (talk) 19:04, 23 April 2021 (UTC)[reply]

That's great, thanks! -Yupik (talk) 22:09, 23 April 2021 (UTC)[reply]

Archdiocese of Liverpool

[edit]

Thanks for sorting this out. My first proposal! It seems to connect now. Rodhullandemu (talk) 20:15, 27 April 2021 (UTC)[reply]

The first one is always the most difficult! On to the next! :) UWashPrincipalCataloger (talk) 20:24, 27 April 2021 (UTC)[reply]

Q9824248 vs Q99705827

[edit]

Could You please clear the relationship between Molecular Engineering & Sciences Building and Nano Engineering and Sciences Building before reverting my changes. Are these identical buildings (duplicate, with just different names?), different sections of one building or two different separate units? It is not optimal that there is now a link from Nano Engineering and Sciences Building to an archINFORM entry, which links back to Molecular Engineering & Sciences Building ! --Arch2all (talk) 08:20, 21 June 2021 (UTC)[reply]

Hello @Arch2all:. First, you reverted the items that I created, which I believe were correctly established. Your reversions indicated that you did not understand the nature of these two entities, so instead of reverting them, it would have been better to initiate this discussion first. These are two separately named buildings that were built in two phases. You can see them on a map and with description at https://www.washington.edu/maps/#!/mol and https://www.washington.edu/maps/#!/nan. The buildings are adjacent to each other. They were funded as one project with two phases of construction to build two separate buildings. Molecular Engineering & Sciences opened in 2012 and the second phase was completed with the opening of Nano Engineering and Sciences in 2017. Additional description can be seen at https://www.moles.washington.edu/facilities/building-2/ and https://www.engr.washington.edu/about/bldgs/nanoresearch. The archINFORM and PCAD entries describe the entire project which was called Molecular Engineering Buildings Phases I and II. Note the plural term "Buildings". Phase I resulted in Molecular Engineering & Sciences Building (Q98242488) while phase II resulted in Nano Engineering and Sciences Building (Q99705827). While this may be a bit unusual case, the archINFORM and PCAD identifiers identify what are ultimately two different buildings, and as such, the identifiers are appropriate on both Wikidata items. These are not identical buildings, and they are not different sections of one building. UWashPrincipalCataloger (talk) 17:50, 21 June 2021 (UTC)[reply]

GRY-Online vs Gry-Online

[edit]

Hmmm that is strange. I thought labels on wikidata should reflect rather names used by connected Wikipedia articles (see pl:Gry-Online and en:Gry-Online - only first letter is capitalized). Additionally, in Polish language capitalizing all letters of name, which is not an acronym is just typographically incorrect (I don't know if it's the same in English, though). Thanks. Sir Lothar (talk) 18:18, 9 August 2021 (UTC)[reply]

In most cataloging rules, which is what I am most familiar with, a basic principle is to record information like titles in the form that a resource represents itself. Here is the Statement of International Cataloguing Principles. These statements are the relevant ones:

2.3. Representation. Descriptions and controlled forms of names should be based on the way an entity describes itself.
2.4. Accuracy. The entity described should be faithfully portrayed.

I am fairly certain that labels on Wikidata do not have to match what is in Wikipedia. See https://www.wikidata.org/wiki/Help:Label: "There is no requirement that an item's label be the same as the page name on its corresponding Wikimedia site. In fact there are several cases, discussed below, in which it is actually desirable for the Wikidata label to be different from the Wikimedia page title."

--UWashPrincipalCataloger (talk) 18:28, 9 August 2021 (UTC)[reply]

I see. Thanks for clarifying this issue. I suppose I should change Polish label back to GRY-Online too? Sir Lothar (talk) 18:36, 9 August 2021 (UTC)[reply]
Yes, I would. :) UWashPrincipalCataloger (talk) 19:39, 9 August 2021 (UTC)[reply]

Open questions

[edit]

Hi UWashPrincipalCataloger

Can you see that the missing samples issue per Wikidata:Property_proposal/setlist#Discussion are addressed? In the future, please ensure this is addressed before creating properties. Thanks. --- Jura 07:49, 14 August 2021 (UTC)[reply]

slender-billed prion?

[edit]

Do you read sometimes realated sources? --Succu (talk) 21:23, 16 September 2021 (UTC)[reply]

You can find numerous sources that capitalize the letters in various ways. The form of the label should not be based on one form of capitalization. Most of the sources for "Slender-billed Prion" are just the same publication in different versions. In English, common names of animals are not considered proper nouns (unless they have a geographic or person's name in them) and therefore are not capitalized in normal writing. I added additional capitalization forms and sources for them in taxon common name. The best label is uncapitalized. UWashPrincipalCataloger (talk) 22:12, 16 September 2021 (UTC)[reply]
This is your POV! There is no consensus for this here. --Succu (talk) 04:38, 17 September 2021 (UTC)[reply]

The standard guide for English writing is The Chicago Manual of Style, which says:

For the correct capitalization and spelling of common names of plants and animals, consult a dictionary or the authoritative guides to nomenclature, the ICN and the ICZN, mentioned in 8.119. In general, Chicago recommends capitalizing only proper nouns and adjectives, as in the following examples, which conform to Merriam-Webster's Collegiate Dictionary:

   Dutchman's-breeches

   jack-in-the-pulpit

   mayapple

   Cooper's hawk

   rhesus monkey

   Rocky Mountain sheep

The National Geographic Style Manual lists some common names (e.g., honeybee, tsessebe, Harris's hawk) and does not capitalize anything but proper nouns. See also: https://www.dailywritingtips.com/when-to-capitalize-animal-and-plant-names/, https://projects.ncsu.edu/cals/course/zo150/mozley/nomencla.html, https://mostlybirds.wordpress.com/2015/12/09/should-common-names-of-species-be-capitalized/, and https://grammar.yourdictionary.com/capitalization/capitalization-of-animal-names.html, among many others.

Also for virus names, see this, from the International Committee on Taxonomy of Viruses (ICTV): "The first letters of words in a virus name, including the first word, should only begin with a capital when these words are proper nouns (including host genus names but not virus genus names) or start a sentence. Single letters in virus names, including alphanumerical strain designations, may be capitalized. ... Examples: 

   Isolates of dengue virus 2 were obtained ....

   Detection of West Nile virus in human serum ....

   Salmonella phage SE1 was isolated ....

   Sida ciliaris golden mosaic virus (SCGMV) causes ....

   Aphids transmit potato virus Y (PVY)

--UWashPrincipalCataloger (talk) 05:22, 17 September 2021 (UTC)[reply]

The Codes do not govern common names. At least two major sources (IUCN and IOC) do not follow your POV. --Succu (talk) 09:13, 17 September 2021 (UTC)[reply]

Thanks

[edit]
The Wikidata Barnstar
Thank you for your work improving properties from all around the planet. 99of9 (talk) 04:36, 17 September 2021 (UTC)[reply]

Thank you!! UWashPrincipalCataloger (talk) 05:52, 17 September 2021 (UTC)[reply]

University of Alaska Anchorage (Q1285252)

[edit]

The problem with using 'parent organization' in this context is that the term (as defined on WD) has a very specific meaning. It's 'inverse item label' is "has subsidiary", with the inverse property has subsidiary (P355). The Parent organization/subsidiary relationship is supposed to imply ownership of another organization that is 'completely separate', such as one company buying another. That kind of relationship doesn't generally apply to state university systems... the actual organization is typically (and seems to be the case in Alaska) a "Board of Regents" that is legally given 'governing authority' over the various universities, which do not themselves have a separate legal identity.... they are instead constituent parts of 'the system' governed over by the Regents.

The role played by the Board of Regents is far more significant with regards to the universities than simply 'owning' them... a Board of Regents, as a body corporate, does not in fact actually 'own' the universities (they are state property) but instead governs them according to the authority delegated by state law. State universities typically have their own police departments, that enforce not only state and local laws, but the regulations 'enacted' by the Board of Regents, with the force of law (as an example of how the situation is different).

The whole situation is altogether a different relationship than what is intended/implied by "parent organization" and "subsidiary". In a parent/subsidiary relationship, the control exerted by the 'parent' is not through direct governance, but instead through the shareholder's ability to appoint the management of the 'subsidiary' organization.... they remain, conceptually, 'separate things'. Jarnsax (talk) 15:01, 21 September 2021 (UTC)[reply]

Essentially, in a parent/subsidiary relationship, the parent is (talking legalistically here) a "member of the corporation" of the subsidiary, with rights defined by the articles of incorporation of the subsidiary, and controls the subsidiary through possessing the majority of member votes. Jarnsax (talk) 15:07, 21 September 2021 (UTC)[reply]

Very proud of you!

[edit]

10000th property created, I knew you had potential as a property creator. You own this symbolic threshold!--Alexmar983 (talk) 02:20, 17 October 2021 (UTC)[reply]

That's very kind of you! Thanks very much. UWashPrincipalCataloger (talk) 03:20, 17 October 2021 (UTC)[reply]

pulication date / inception on "Last Days" (Q44370964)

[edit]

May I ask why you removed "publication date" on Q44370964 and replaced it with "inception"? My understanding has always been that they refer to two different things with written works, namely when they were published and when they were written. Is it because part of the work had been published pror to 2009? But simply removing the property seems a suboptimal solution in that case.--Pfadintegral (talk) 06:15, 23 November 2021 (UTC)[reply]

Inception (date of creation) is used on items for works, whereas publication date is used on items for specific editions. Items are not supposed to combine both work and edition. The model that is supposed to be followed is at https://www.wikidata.org/wiki/Wikidata:WikiProject_Books. UWashPrincipalCataloger (talk) 18:20, 23 November 2021 (UTC)[reply]

I understand the need to separate works and editions. But if you restrict "publication date" to editions, how would you deal with cases like Q48229 where "inception" (when it was written) and "publication date" (when it was first published) have two different values? Do you think the date of first publication should simply not be stored on work items? --Pfadintegral (talk) 06:44, 25 November 2021 (UTC)[reply]

Yes, my understanding is that "publication date", even first publication date, is not supposed to be recorded on items for works, which also aren't supposed to have "publisher", "place of publication", "number of pages", "ISBN-13" and "ISBN-10" and other properties related to specific manifestations. Work itself is an abstract concept, so only "inception" (date of creation) should be given. Of course in many cases, the date of creation is inferred from the date of first publication. For Lost in America (Q48229), only the date the work was created should be there. There should be a separate item for the first edition published in 1927. Here's an example: work - Golden Boy (Q17105820), first publication - Golden Boy (2013 British edition) (Q109690729). UWashPrincipalCataloger (talk) 07:31, 25 November 2021 (UTC)[reply]

PCC: BIBCO, CONSER, NACO, SACO

[edit]

Could you please:

  • Edit the NACO/SACO data to be consistent with each other, eg:
    • the pref label should be "NACO"?
    • I think "part of" is enough, there should be no "subsidiary / parent org" because the subprograms are not orgs
  • Add BIBCO and CONSER
  • Add "participant" lists. I added such list to PCC, but actually that's the list for NACO (taken from the VIAF home page). If different subsets of libraries participate in the different subprograms, I'll need to fix that

Cheers! --Vladimir Alexiev (talk) 07:59, 8 December 2021 (UTC)[reply]

Yes, there are different participants in each of the programs. Some libraries participate in all four, but many are just NACO or SACO libraries. To be in BIBCO and CONSER, they have to be NACO participants. I can work on the BIBCO and CONSER items. UWashPrincipalCataloger (talk) 08:19, 8 December 2021 (UTC)[reply]

Q110271724 and Q6649

[edit]

Hi! I saw that you edited the page about "lesbianism" and added some to the "lesbian" page (which was created today), but since all these pages are talking about the same subject I don't see why separate them. That's why I propose that there is a fusion of the two so that the interwiki pages are not in different places just by name or that the interwiki pages are totally separated from Q6649 so that there is no confusion. --N4CH77 (talk) 23:36, 26 December 2021 (UTC)[reply]

studied in (P2579)

[edit]

Hi @UWashPrincipalCataloger:, why did you add student (Q48282) to the constraints of studied in (P2579) back in February ? Isn't practiced by (P3095) more appropriate for students ? For example, physics (Q413) practiced by (P3095) physicist (Q169470), why not the same for students ? I think that we are mixing very different entities if we use studied in (P2579) for both the discipline (activity) and the students (humans). Thank you for your help. CaLéValab (talk) 12:12, 27 December 2021 (UTC)[reply]

Merchandise Giveaway Nomination – Successful

[edit]
A Wikimedia t-shirt!
A Wikimedia t-shirt!

Hey UWashPrincipalCataloger,

You have been successfully nominated to receive a free t-shirt from the Wikimedia Foundation through our Merchandise Giveaway program. Congratulations and thank you for your hard work! Please email us at merchandise@wikimedia.org and we will send you full details on how to accept your free shirt. Thanks!

On behalf of the Merchandise Giveaway program,

-- janbery (talk) 22:30, 26 January 2022 (UTC)[reply]

New External Identifier property P10312

[edit]

Hi,UWashPrincipalCataloger. Thanks for creating this new identifier.

Since you did so, eleven hours have passed and still it appears that links created using the identifier (the three examples given as justification) while set up still are not clickable. Similarly a Quickstatements batch I have of 4200 updates to use the identifier fails on every one.

I just wondered if this time passing (until the identifier can be used) is normal or not - or whether I or someone else needs to do something to finish the process.

Thanks again.

Watty62 (talk) 19:12, 31 January 2022 (UTC)[reply]

The links are live now. UWashPrincipalCataloger (talk) 15:59, 1 February 2022 (UTC)[reply]

Authority control properties

[edit]

Hi, @UWashPrincipalCataloger. I have exchanged the position of LDT @ Library Name Authority ID (P10489) and NCL ID (P1048) in {{Authority control properties}}. They have two different UID. The IDs in P10489 are the same with CYT in Virtual International Authority File (Q54919). Kethyga (talk) 06:58, 14 March 2022 (UTC)[reply]

DACS IDs

[edit]

I've just tweeted DACS to see if they might have be able to give us a list giving their new IDs matched to their old IDs [4]. I'm guessing probably not, but no harm in asking.

In the meantime, can I suggest that when there has been a total change in IDs like this, it might be worth suggesting a new property, eg DACS ID (2022), to keep the new IDs completely separate from the old ones; and to redirect the old ones to point to something like [5] for Andy Warhol, by changing the URL formatter to https://web.archive.org/web/20210630075411/https://www.dacs.org.uk/licensing-works/artist-search/artist-details?ArtistId=$1.

(We had to do something similar for the Royal Academy identifiers a couple of years back).

That way the old IDs won't get muddled with the new IDs; and people will still be able to see what the information DACS used to give about them, at least as it was in 2021, for artists when we only have the old IDs.

Cheers, Jheald (talk) 18:45, 15 March 2022 (UTC)[reply]

Thanks for the suggestion and the tip. I think this might be the first time I've noticed this kind of change and didn't necessarily know how to deal with it in the best way. The tip about using the Internet archive address to replace the former URL is very cool. I'll revise the existing property with the redirect URL you suggest. UWashPrincipalCataloger (talk) 19:55, 15 March 2022 (UTC)[reply]
New proposal at https://www.wikidata.org/wiki/Wikidata:Property_proposal/Person#DACS_ID_(2022). UWashPrincipalCataloger (talk) 20:13, 15 March 2022 (UTC)[reply]
Thanks, I think that does make sense. The only exception would be if they did give us a list with the entire old ID -> new ID mapping, so that we could update all the values overnight, in one go (deprecating the old ones). So I am curious as to whether they will get back to me. But even then it might be cleaner just to have the new property.
That's a heroic set of translations of 'former', btw! Jheald (talk) 21:36, 15 March 2022 (UTC)[reply]
Thank you Google Translate! ;-) UWashPrincipalCataloger (talk) 02:07, 16 March 2022 (UTC)[reply]
Their comms person has now pinged my email on to three people on their tech team, so fingers still crossed for a translation table. Jheald (talk) 17:53, 17 March 2022 (UTC)[reply]

Juniperus communis, etc.

[edit]

FYI: I've removed a whole lot of vernacular names that are only relevant to one or another particular subspecies, not to the species as a whole; please do not re-add them there, as it is misleading to suggest they apply to the whole species. Also please be careful about adding huge numbers of obscure and rarely-used vernacular names, as it just clutters up the VN listing at Commons and elsewhere; particularly not ones that are no more than typographical errors such as ommissions of hyphens due to sloppy editorial work at the references cited. Thanks! - MPF (talk) 16:06, 25 March 2022 (UTC)[reply]

Indiana State Historical Marker Program

[edit]

I made some adjustments to Indiana State Historical Marker Program ID (P9546) to model the related concept more clearly as you may have seen my changes to the property examples, adding constraints, and moving of IDs. I also created the second proposal for the numberic ID as it is critical to include to keep data linked long term if the URL changes as it is the most stable identification of the marker. See the new proposal - Indiana State Historical Marker Program numeric ID. I'm not sure the the Indiana State Historical Marker Program (Q106571962) "program" is the correct statement for what the marker IDs stated in or represent as much as the website or database of that program. Wolfgang8741 (talk) 17:21, 31 March 2022 (UTC)[reply]

I created Indiana Historical Markers (Q111442916) for the website, and replaced applicable 'stated in' value (P9073) with it instead of the Program. UWashPrincipalCataloger (talk) 17:50, 31 March 2022 (UTC)[reply]

Help with properties

[edit]

Hello! Would you help me fill in the properties All.Rugby club ID (P10590), traveloka restaurant ID (P10591), maPZS trails/locations ID (P10592) and Kinowiki ID (P10593)? MasterRus21thCentury (talk) 05:22, 9 April 2022 (UTC)[reply]

Angiosperms (Q25314)

[edit]

You removed taxon name (P225) for Angiosperms (Q25314) probably because that item is clade, but anyway, if you delete taxon name you have to add clade name or some other property name. Currently the item is taxonomically broken. --Termininja (talk) 14:58, 5 May 2022 (UTC)[reply]

I added it back in. UWashPrincipalCataloger (talk) 15:07, 5 May 2022 (UTC)[reply]

Awesome work on creation of Reflora ID (P10701)

[edit]

This was magnificent work! https://www.wikidata.org/wiki/Property:P10701 is super complete, a work of art really. Congratulations and thank you for your contribution! Best, TiagoLubiana (talk) 19:24, 17 May 2022 (UTC)[reply]

Thank you so much! Means a lot to me to do a good job on these properties. UWashPrincipalCataloger (talk) 00:18, 18 May 2022 (UTC)[reply]

Star Trek novel (Q72996181) as a genre

[edit]

Hi,

What I meant was just, that we now have a single item treating it as a genre: 

SELECT ?item ?itemLabel WHERE {
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
  ?item wdt:P136 wd:Q72996181.
}
Try it!

and 991 item treating it as a class: 

SELECT ?item ?itemLabel WHERE {
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
  ?item wdt:P31 wd:Q72996181.
}
Try it!

😅

I have no strong opinion one way or the other, I just think it should be consistent. And by extension this also applies on Star Trek video game (Q78444225) 

SELECT ?item ?itemLabel WHERE {
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
  ?item wdt:P31 wd:Q78444225.
}
Try it!

also on Star Trek episode (Q61220733) 

SELECT ?item ?itemLabel WHERE {
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
  ?item wdt:P31 wd:Q61220733.
}
Try it!

and on Star Trek comic (Q3496994) 

SELECT ?item ?itemLabel WHERE {
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
  ?item wdt:P31 wd:Q3496994.
}
Try it!

Should those all be genres? --Shisma (talk)

Re:

[edit]

As "Indio" in Spanish refers to Native Americans, "Hindú" is used for Indian citizens, while Hindu (the religion believers) is rendered in Spanish as "hinduista". The original Spanish Wikipedia article talks about Indian citizens and their descendants outside India and not about the religious community --Bankster (talk) 07:22, 12 July 2022 (UTC) I know this can arise confusion for speakers of other languages like English and French which do not have this ambiguous meaning on "Indian" and similar equivalents. I offer you my apologies for that matter. --Bankster (talk) 07:24, 12 July 2022 (UTC)[reply]

subclass/instance of OECD countries

[edit]

Hi. I just noticed this edit (and a series like it): https://www.wikidata.org/w/index.php?title=Q30&curid=126&diff=1701320212&oldid=1698468645 . I think it should be an instance not a subclass. A subclass would imply that anything that is an instance of the USA is an OECD country. But there's nothing that's an instance of the USA. Let me know if I've misunderstood. --99of9 (talk) 03:51, 11 August 2022 (UTC)[reply]

Oh, hmm, I've thought about this more, and I see you have a point. It still comes across weirdly to me, but maybe I just need to reflect on it more. --99of9 (talk) 04:03, 11 August 2022 (UTC)[reply]

It seems to me it's just an unnecessary duplication of member of (P463) Organization for Economic Cooperation and Development (Q41550).--Jklamo (talk) 09:13, 11 August 2022 (UTC)[reply]

I think subclass is the right property. The 38 countries of the OECD are in the class OECD countries. Most vocabularies treat the class OECD countries as a geographic entity, so I think it is correct to say that the U.S. geographic region is a subclass of the OECD countries region. UWashPrincipalCataloger (talk) 19:12, 11 August 2022 (UTC)[reply]
99of9 is right: for Q30 to be a subclass it needs to be a class by itself. But is Q30 a class? --Infovarius (talk) 16:32, 7 February 2023 (UTC)[reply]

Thanks for adding new property

[edit]

Hi Adam, thanks for creating new props. Could you create https://www.wikidata.org/wiki/Wikidata:Property_proposal/travelweekly_hotel_ID if you're free. Germartin1 (talk) 07:05, 22 November 2022 (UTC)[reply]

Alternate Form

[edit]

Hello! I saw you've been replacing some forms with a spelling variant of alternative form (Q59342809). Is this because they share the same grammatical features? -wd-Ryan (Talk/Edits) 17:10, 5 January 2023 (UTC)[reply]

e.g https://www.wikidata.org/w/index.php?title=Lexeme:L940625&diff=1803442375&oldid=1803441946 -wd-Ryan (Talk/Edits) 17:10, 5 January 2023 (UTC)[reply]
This is how I have understood these differences should be indicated based on discussions/feedback on the Telegram chat list for lexemes. UWashPrincipalCataloger (talk) 20:20, 5 January 2023 (UTC)[reply]
That makes sense. I'll also follow that rule. -wd-Ryan (Talk/Edits) 21:08, 5 January 2023 (UTC)[reply]
Was just made aware of this property for forms, in case you didn't know: alternative form (P8530). -wd-Ryan (Talk/Edits) 21:31, 21 January 2023 (UTC)[reply]
Thanks, I didn't know about it either. AdamSeattle (talk) 22:09, 21 January 2023 (UTC)[reply]

P11485

[edit]

Infopédia entry (P11485) values are not being shown as links, but just as plain text. Enaldodiscussão 16:38, 9 January 2023 (UTC)[reply]

Yes, that is normal. It takes up to 24 hours for the links to work. Try purging the lexemes now. AdamSeattle (talk) 16:52, 9 January 2023 (UTC)[reply]

PCP reference number (P381)

[edit]

Hello The number scheme for PCP reference number (P381) has changed to 5-digit with leading zeros , regardless the number e.g. 13 becomes 00013 288 becomes 00288 or 9876 becomes 09876. - Source: https://www.babs.admin.ch/en/aufgabenbabs/kgs/inventar.html
As I don't know how to adapt the property, I kindly as you if you might have time and will to adapt?
Best regards, AnBuKu (talk) 15:14, 24 January 2023 (UTC)[reply]

Anyhow, I keep adding the zeros, as you told me it works fine.
Best regards AnBuKu (talk) 22:58, 24 January 2023 (UTC)[reply]
The links do not work any more with leading 0's. https://heritage.toolforge.org/api/api.php?action=search&format=html&srcountry=ch&srid=133 brings up a web page but https://heritage.toolforge.org/api/api.php?action=search&format=html&srcountry=ch&srid=00133 does not. I suggest leaving the identifiers as they were, without leading zeros. Adding the zeros apparently breaks the links. You'll have to go back and change all of the items that you edited. AdamSeattle (talk) 03:24, 25 January 2023 (UTC)[reply]
Thank's so far Adam. I'll try o find the coder who developed heritage.toolforge.org/api/api.php? as he/she might have an idea how to adapt the tool. AnBuKu (talk) 03:42, 25 January 2023 (UTC)[reply]
FYI: Have asked @M2k~dewiki https://www.wikidata.org/wiki/Topic:Xbcy58fywxh6shvz if he has some solution. cheers, AnBuKu (talk) 13:18, 25 January 2023 (UTC)[reply]
It works! thx a lot for your support! AnBuKu (talk) 00:26, 31 January 2023 (UTC)[reply]

Help needed

[edit]

Hi @AdamSeattle, I notice that you created this property Rekhta author ID (P9459) some two years ago. I notice a problem and it forces to write labels. I'm copying that whole, Entities with statements for Rekhta author ID should also have a label at least in any of the following languages:

  • Hindi
  • Punjabi
  • Western Punjabi

I believe that Urdu language should be included, and if an item has a label in Urdu language, the warning must not be popping up. Much of the works on Rekhta happen to be in Urdu instead of these three languages and this forceful entry of labels in these three languages is problematic. I don't have much knowledge about how these things work and I look forward to your insightful and friendly help. Best, ─ The Aafī (talk) 18:12, 26 February 2023 (UTC)[reply]

Hi @TheAafi, I think that someone else added these label constraints after I created the property. However, if you look at the label constraints at the bottom of the property, Urdu is mandatory (code ur), and the other languages are suggested but not mandatory {codes hi, pa, pnb). It seems as if you didn't notice the row above what you quoted: "Label required in languages: ur: Entities using this property should have labels in one of the following languages: ur". So, what you are asking for is already there. Urdu labels are required. AdamSeattle (talk) 23:37, 26 February 2023 (UTC)[reply]

Thanks @AdamSeattle. As I already said, I do not have enough knowledge about these things. Could you please check Ijteba Nadwi (Q105487770) and tell me why it adds up the error button and asks to include label in any of the three languages that I quoted above. IMO, an item with a label in Urdu mustn't be getting such warnings. ─ The Aafī (talk) 03:35, 27 February 2023 (UTC)[reply]
OK, I see what you are asking now. This is a suggestion constraint. It is a suggestion that there should be labels in those language, but it is not a mandatory constraint. You can just ignore it. AdamSeattle (talk) 03:53, 27 February 2023 (UTC)[reply]

The Order of annotator (P11105) in element page

[edit]

The order of annotator (P11105) property in element page comes at last before references. But it must be order after author (P50) and editor (P98). حبيشان (talk) 02:35, 27 February 2023 (UTC)[reply]

I'm not sure that I understand what you are asking, but I don't know how to revise the order of properties on items. AdamSeattle (talk) 03:00, 27 February 2023 (UTC)[reply]

sign your property proposals!

[edit]

Hi Adam - you have created a number of new proposals that are missing your signature - therefore they don't show who the proposer is, or when exactly the proposal was made. Example is Wikidata:Property proposal/Wise Music Classical composer ID. Thanks. ArthurPSmith (talk) 16:59, 2 March 2023 (UTC)[reply]

P10832

[edit]

Hi Adam, WorldCat Entities ID (P10832) has only 855 entities, the database is much larger (Press release: OCLC releases more than 150 million WorldCat Entities as the foundation of a linked data infrastructure). What's the procedure to increase the number of these entities in Wikidata? Grimes2 (talk) 11:40, 19 March 2023 (UTC)[reply]

Could we internationalize patent agent (Q106385760) ?

[edit]

Patent agents exist in many countries and I am marking some people as having that occupation. Is there a reason to use the US definition that they passed a particular exam, or could I take that US-specific bit out of the description in patent agent (Q106385760))? I ask you as the creator of the item. -- econterms (talk) 23:34, 4 April 2023 (UTC)[reply]

Hyphens and en dashes

[edit]

You reverted my edit in Q45682. Which English language sources are you referring to? I found quite easily several sources for en dashes to be used to mark ranges: en:WP:DASH, [6], [7], [8] and [9]. Best regards, ––Apalsola t • c 19:18, 4 June 2023 (UTC)[reply]

Plate as a property

[edit]

Hello, some time ago I think you added plate (Q108607888). As on the (second, Die Säugthiere) taxon name reference on Simia mona (Q122294837), the plate (XV) is relevant (and dated for citation purposes as per here) and has the binomial, unlike the related text. Do you think there is a need for a related property, so that, rather than use, which we may not be able to do here, plate (Q108607888) as a qualifier of the constraint-violating page(s) (P304)=>Tab. XV, we can simply add Property:Plate=>XV. "Plate" could then display as 図版 or equivalent per the language selector, while "Tab." might be a little less clear even to some English speakers. Thank you, Maculosae tegmine lyncis (talk) 21:19, 7 September 2023 (UTC)[reply]

I think you could certainly make a proposal for a property for plate number as an equivalent to page(s) (P304). The only other way that I think to use property page(s) (P304) is to give the value "no value" and then add a qualifier object stated in reference as (P5997) with a value like "plate XV". AdamSeattle (talk) 00:30, 9 September 2023 (UTC)[reply]
Wikidata:Property proposal/Plate (perhaps a little rough around the edges, it is my first, but...), thank you, Maculosae tegmine lyncis (talk) 06:55, 9 September 2023 (UTC)[reply]
I've cleaned up the proposal a bit and fixed the first example to show what you need to show, and I've added a second example. You'll want to add a third example too patterned on the others. AdamSeattle (talk) 21:50, 9 September 2023 (UTC)[reply]
Thank you very much, I have done so, Maculosae tegmine lyncis (talk) 22:47, 9 September 2023 (UTC)[reply]

"For the year" as a property

[edit]

Hello again, before I start another property proposal, as for Novi Commentarii Academiae Scientiarum Imperialis Petropolitanae (Q6046009) here, the title page distinguishes publication date (P577), volume (P478), and {{pro anno}}. For, eg, Vulpes japonica (Q40719908), as in the references to the taxon name, though the PZS volume for the taxon publication says "1868" [10] [11], this page range was, according to Q54800901, actually published in 1869. For the bibliographic reference we need Gray, 1868, for the taxon-related citation Gray, 1869. MSW3 here distinguishes between bibliographic reference ({{pro anno}}) and actual publication date for Assam macaque (Q738925) (gbif) Do you have any related thoughts/suggestions at this stage? Thank you, Maculosae tegmine lyncis (talk) 07:06, 11 September 2023 (UTC)[reply]

  • I would say what you have is a "chronological designation" associated with the volume, which is different from the date of publication. In serials cataloging, we have a specific MARC 21 field for numbering of serials, which contains both the numeric designation (volume, number, issue, etc.) and chronological designation (year, or month and year, or day, month and year, etc.). So perhaps your proposal could be for "serial chronological designation"? You can see examples of how we record this for serials in our catalog records at https://www.loc.gov/marc/bibliographic/bd362.html. For example: Vol. 1, no. 1 (Apr. 1981)- . The instructions there say "The date may consist of the year, month, or day; month or season and year; or year alone, depending upon the frequency of publication and the usage of the publisher." These are the properties used by our cataloging rules, RDA: http://rdaregistry.info/Elements/m/P30149 and http://rdaregistry.info/Elements/m/P30150. So I think something like "chronological designation" or "serial chronological designation" could be what you are looking for, as separate from "publication date". AdamSeattle (talk) 20:59, 11 September 2023 (UTC)[reply]
Thank you, also for the MARC 21 link; have drafted Wikidata:Property proposal/chronological designation, Maculosae tegmine lyncis (talk) 11:08, 12 September 2023 (UTC)[reply]

Call for participation in a task-based online experiment

[edit]

Dear AdamSeattle,

I hope you are doing well,

I am Kholoud, a researcher at King's College London, and I am working on a project as part of my PhD research, in which I have developed a personalised recommender model that suggests Wikidata items for the editors based on their past edits. I am collaborating on this project with Elena Simperl and Miaojing Shi.

I am inviting you to a task-based study that will ask you to provide your judgments about the relevance of the items suggested by our model based on your previous edits.

Participation is completely voluntary, and your cooperation will enable us to evaluate the accuracy of the recommender system in suggesting relevant items to you. We will analyse the results anonymised, and they will be published in a research venue.

The experiment should take no more than 15 minutes, and it will be held next week.

If you agree to participate in this study, please either contact me at kholoud.alghamdi@kcl.ac.uk or use this form https://docs.google.com/forms/d/e/1FAIpQLSfA1wfdBfCRlcG3WhDyc-V8lzgPNx3fDFCNXkyn4CSwahXZ_A/viewform?usp=sf_link

Then, I will contact you with the link to start the study.

For more information about my project, please read this post: https://www.wikidata.org/wiki/User:Kholoudsaa

In case you have further questions or require more information, don't hesitate to contact me through my mentioned email.

Thank you for considering taking part in this research.

Regards Kholoudsaa (talk) 22:02, 9 October 2023 (UTC)[reply]

Lost email

[edit]

Hi Adam - I had a notification of an email from you but I can't find it anywhere. Not sure what happened; probably best to use talk pages like this for wiki-specific communications? ArthurPSmith (talk) 13:58, 17 October 2023 (UTC)[reply]

I had emailed you this: I believe that these two proposals ought to be marked as ready to create. Could you mark them?: https://www.wikidata.org/wiki/Wikidata:Property_proposal/Natural_science#Flora_of_New_Jersey_Project_atlas_ID and https://www.wikidata.org/wiki/Wikidata:Property_proposal/Natural_science#FloraVeg.EU_taxon_ID AdamSeattle (talk) 17:36, 17 October 2023 (UTC)[reply]

Property

[edit]

Hi Adam, can I ask you to create Wikidata:Property proposal/Propylaeum-VITAE id? I would do it myself but I'm not allowed to. If you're unsure about the details, I can iron them out later. Thanks, Jonathan Groß (talk) 09:44, 23 November 2023 (UTC)[reply]

Hi I can work on it this weekend. AdamSeattle (talk) 19:42, 24 November 2023 (UTC)[reply]

Thanks! No need to put in so much effort, just press the button "Create" so nobody can complain about foul play, then I can iron out all the kinks on my own. Cheers, Jonathan Groß (talk) 21:06, 24 November 2023 (UTC)[reply]

Journal of Ornithology/Journal für Ornithologie (Q473337 and Q21386253)

[edit]

Hi! I see you recently merged Q21386253 into Q473337. Unfortunately, I'm not sure if this was correct for Wikidata; as far as I've been hearing, the precedent is to have separate items for the old title and new title of a journal, since they also have different identifiers (for instance different ISSNs and ISSN-Ls). See for instance discussion at Wikidata talk:WikiProject Periodicals#Journal name changes. Monster Iestyn (talk) 19:12, 6 January 2024 (UTC)[reply]

The consensus on that talk page appears to me to be to have separate items when a title change causes a change in ISSN. This is how libraries catalog serials. It also is important to be able to cite a journal article with the correct title of the journal that it appeared it. Otherwise it does not make sense to me to say an article was published in a title that doesn't actually correspond to that volume and issue. We wouldn't accept a bibliography that gave the wrong title for the journal an article was published in. In cataloging standards, a major title change means you have a new work, and a new work should have its own Wikidata item in my opinion. AdamSeattle (talk) 21:56, 6 January 2024 (UTC)[reply]
Yeah, and what I'm saying is that's what happened for Journal für Ornithologie and Journal of Ornithology: the former title (used from 1853 to 2003) has ISSNs 0021-8375 (print) and 1439-0361 (online), and the current title (2004 onwards) has ISSNs 2193-7192 (print) and 2193-7206 (online). Monster Iestyn (talk) 23:43, 6 January 2024 (UTC)[reply]
Oh, that was clearly a mistake, and oddly not what I recall doing. I'll undo the merge, as I agree that there should be separate items. AdamSeattle (talk) 01:20, 7 January 2024 (UTC)[reply]
Thanks, though there are still the article items linking to the redirect Q21386253 rather than the new item Q124161355 you just created. They need to be linked to that instead. Monster Iestyn (talk) 03:34, 7 January 2024 (UTC)[reply]
I'm working on them. AdamSeattle (talk) 03:48, 7 January 2024 (UTC)[reply]

subclass of taxon

[edit]

please don't just remove information. I think we should establish (potentially a lot of) specialized new properties for plant taxons and eventually move that information there.

But for now, why do you think this information is better held as instance of (P31) instead of subclass of (P279)? A species is a group of related plant individuals, isn't it?.. Cartoffel (talk) 12:31, 21 February 2024 (UTC)[reply]

Subclasses have not been used for taxa and it seems incorrect to me to state that a species is a subclass of a habit type any more than it correct to say it is a subclass of deciduous or evergreen plants or blue-flowered plants. I think these kinds of life history, habit, morphology, etc. information should have separate properties for sure. Were you planning to put these subclasses somewhere else once new properties for them were approved? AdamSeattle (talk) 16:08, 21 February 2024 (UTC)[reply]

Why has my ip address been blocked?

[edit]

@Jasper Deng: I am accused of vandalism and my ip address blocked until December 2024, but I do not know what vandalism I've supposedly done. I certainly have never intentionally vandalized anything in WD, and I believe that I am a trusted editor and property creator. Would you please consider unblocking me? Occasionally I neglect to log in before editing something, but that is extremely rare. AdamSeattle (talk) 02:38, 3 May 2024 (UTC)[reply]

Jasper has not logged in for 2 weeks. Consider posting to Wikidata:Administrators' noticeboard. Yes I confirm you are trusted with 300k edits over 7 years and participation in wiki community conversation. I do not see your block but I support you getting access that you need. Bluerasberry (talk) 19:40, 3 May 2024 (UTC)[reply]
I have granted you IP block exemption for a year. I cannot of course comment on the actual IP block for your privacy. You should be able to edit normally as long as you are logged in.--Jasper Deng (talk) 10:24, 8 May 2024 (UTC)[reply]
Thank you. AdamSeattle (talk) 22:51, 8 May 2024 (UTC)[reply]

Dowry in Islam

[edit]

Hi AdamSeattle. I discovered this morning that all my additions in the mahr (Q902443) page (Dowry in Islam) have been canceled. In particular, these authority links have been targeted:

  1. LCAuth: https://id.loc.gov/authorities/sh2022006551
  2. LCAuth: https://id.loc.gov/authorities/sh85039242
  3. LCClass: https://id.loc.gov/authorities/classification/BP190.5.D69
  4. FAST: https://id.worldcat.org/fast/2060623
  5. FAST: https://id.worldcat.org/fast/897273
  6. IdRef: https://www.idref.fr/17523244X
  7. BnF: https://catalogue.bnf.fr/ark:/12148/cb16729423j
  8. BNE: https://datos.bne.es/resource/XX547746

All the beautiful and patient work that I have brought to this page has been canceled. I am afraid that all the other pages that I have improved and enriched will suffer the same fate. SOS! Soufiyouns (talk) 06:28, 4 July 2024 (UTC)[reply]

I don't see any deletions of properties in the history of this item. But you should be very careful when adding subject authority links to LCSH or FAST or other vocabularies that what you are linking to is an exact match for the concept represented in the item. Dowry--Religious aspects--Islam is not the same exact thing as mahr. I also see that you are adding dictionary properties to items, when most of these properties are restricted to use in lexemes. It is not appropriate to add them to items if the property was only established for lexemes. AdamSeattle (talk) 19:33, 4 July 2024 (UTC)[reply]
@AdamSeattle: Thank you very much for your comments and guidance. Soufiyouns (talk) 06:24, 5 July 2024 (UTC)[reply]

Indexer Property Proposal

[edit]

Hi @AdamSeattle,

Kindly requesting your input as  Support or  Oppose for the following property proposal for 'indexer' at https://www.wikidata.org/wiki/Wikidata:Property_proposal/indexer

Thanks for your support for inker (P10836) as well. Wallacegromit1 (talk) 11:25, 5 July 2024 (UTC)[reply]

P31 on Lexemes

[edit]

Hi,

I notice that you are adding unusual values as instance of (P31) on Lexemes, for instance food name (Q116447555). I'm not sure what is the supposed benefit ; you added manually Q116447555 on 34 lexemes but this simple query https://w.wiki/B9k4 already gives automatically 8714 lexemes.

Cheers, VIGNERON (talk) 17:26, 10 September 2024 (UTC)[reply]

Naturbasen species ID

[edit]

The regular expression for Naturbasen species ID is causing many errors on taxon pages because it doesn't appear to actually encapsulate how the identifiers for Naturbasen are formatted. Could you please have a look at it and revise it so that it actually captures all of the forms of the identifiers. David Newton (talk) 19:02, 5 October 2024 (UTC)[reply]

Can you give me some examples of the identifiers that don't work? AdamSeattle (talk) 19:07, 5 October 2024 (UTC)[reply]

organization and corporate body

[edit]

You added organization as a subclass of corporate body, which is defined as something composed of persons. Are you sure that all instances of organization fit this definition? Peter F. Patel-Schneider (talk) 08:17, 8 November 2024 (UTC)[reply]

Organization is a type of corporate body in all cataloging rules. Yes an organization is composed of persons, but is not a person. I've made revisions to corporate body as well to make it clear that all organizations fit the definition. AdamSeattle (talk) 18:02, 8 November 2024 (UTC)[reply]

Retrieved from "https://www.wikidata.org/w/index.php?title=User_talk:AdamSeattle&oldid=2271999163"