User talk:DPLA bot/Archive 2

From Wikimedia Commons, the free media repository
Jump to navigation Jump to search
File:(Memorial Day preparations, HUD headquarters-) Prisoners of War-Missing in Action (POW-MIA) Table - DPLA - 924defd47092f9762c7f91741efcb9de.jpg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.

If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues.

Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Corqe (talk) 15:13, 28 October 2022 (UTC)

File:Bye Bye Birdie musical poster, 1975 production, Colfax, Washington - DPLA - d9aed71d7f8156904475ea5bb24498dc.jpg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.

If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues.

Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

(Oinkers42) (talk) 02:37, 29 October 2022 (UTC)

File:PTC 220 MHz Radio- Union Pacific Locomotive 5802 GE C44-9-AC-CTE Locomotive Noise Test Battery Report, June 2012 - DPLA - a614136d0d964d8a2e28c68e2cc5075e.pdf has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.

If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues.

Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

ShakespeareFan00 (talk) 21:42, 7 November 2022 (UTC)

Some files are missing useful detailed information located at the linked source.

File:YB 19-50 - DPLA - 57943694cd25c64a4730e7a1a4bfb2fe.jpg

This file and many other similar files are missing most of the useful detailed information that exists at the file's linked "source."

Can this bot add this detailed source information to these files to help with file categorization and possible future renaming? Thanks, -- Ooligan (talk) 08:21, 10 November 2022 (UTC)

Can you clarify what specifically you think is missing? The bot adds all data fields from the DPLA record. The file you linked has a bad identifier (I have been in the middle of fixing a number of these), but for example File:I. Fiske Musical Wind Instruments - DPLA - 70619e3134eda73c3fc872360ae26b17 (page 1).jpg comes from [1]. There may be more data at the original source that DPLA aggregates from, but we'd have no way of adding it by bot, since they can be in any format, and we would not know what to map where. Dominic (talk) 15:57, 10 November 2022 (UTC)

Filemoving

Hi, if you move files, please leave a redirect. The File:Mosque of Muhammad Ali, Saladin Citadel of Cairo - DPLA - ffe03811ff8007689a2120ffd9455a30.jpg is in use[2]. Thank you 2003:DE:720:1612:FDFD:4C52:1F18:FB25 07:27, 12 November 2022 (UTC)

Also File:Man with donkey or ass - DPLA - cbf3631f85ff921e1a18ac05159b81d3.jpg and File:Virgin Mary's Tree in Cairo - DPLA - ebc3d51ae3347f37fc967f61d5ccf11e.jpg and File:Great Sphinx of Giza in 3-4 profile - DPLA - 2f93834815e9214e85554294c5ae2f10.jpg. They are also in use. The rules for file movers provide for redirects. •2003:DE:720:1612:FDFD:4C52:1F18:FB25 07:36, 12 November 2022 (UTC)
Hi, I know you are an administrator. But since you still don't follow the rules and don't leave a redirect when moving files, I'll report you for vandalism •2003:DE:720:1683:FDFD:4C52:1F18:FB25 06:53, 13 November 2022 (UTC)
These have all been corrected. Dominic (talk) 14:42, 15 November 2022 (UTC)
File:(Views of) Chinatown area, Washington, D.C. - DPLA - f8e216be6ce00167b17d8500a237fc1c.jpg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.

If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues.

Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

A1Cafel (talk) 08:56, 27 December 2022 (UTC)

Notification about possible deletion

Some contents have been listed at Commons:Deletion requests so that the community can discuss whether they should be kept or not. We would appreciate it if you could go to voice your opinion about this at their entry.

If you created these pages, please note that the fact that they have been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with them, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues.

Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Affected:

And also:

Yours sincerely, Huntster (t @ c) 03:04, 31 December 2022 (UTC)

(Oinkers42) (talk) 16:15, 13 January 2023 (UTC)

File:Reproduction of photo from Office of Chief Information Officer- President Barack Obama (working) at personal computer (PC) - DPLA - 58e3e10bf8dff46f2bbd48590d033b25.jpg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.

If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues.

Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Cryptic-waveform (talk) 03:58, 15 January 2023 (UTC)

File:Reproduction of photo from Office of Chief Information Officer- President Barack Obama (working) at personal computer (PC) - DPLA - e3e28acd0c58e662a366077bd8d54125.jpg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.

If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues.

Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Cryptic-waveform (talk) 05:11, 15 January 2023 (UTC)

Is there any chance of fixing File:The Town Crier, v.18, no.37, Sep. 15, 1923 - DPLA - e438417798fbdb5a6623db7550ebe337 (page 16).jpg? Instead of page 16, it's a flubbed copy of page 1. - Jmabel ! talk 05:22, 4 February 2023 (UTC)

@Jmabel: : Yes, that's an odd one. Usually a problem like this gets fixed in the next pass, as it will get overwritten if it doesn't match the current version. Let me see if I can figure out why that error is still there when it's not in the source. Dominic (talk) 14:47, 6 February 2023 (UTC)
File:Pine needles (1945) - DPLA - b440013659785e028c43701688d28c5a (page 44).jpg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.

If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues.

Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

77.7.53.10 08:31, 26 February 2023 (UTC)

Bad structured data edit

This seems wrong to me. The page in question has nothing, really, about Seattle or arts, and has a pretty clear topic which is neither of these. Are you just sticking those as "main topic" on every single page that comes from the Town Crier? If so, that seems like a bad thing to do. - Jmabel ! talk 17:25, 13 March 2023 (UTC)

@Jmabel: That may be what's happening in practice, yes. The item that is cataloged here, if you look at the source links, is the entire Town Crier issue. To clarify, I am not doing the describing myself, though—it's just that these are the subjects applied by the data source. That's why we use determined by GLAM institution and stated at its website (Q61848113). For any of these, you should be able to see that the subject added is reflected in the item's catalog record. I am aware there is sometimes imprecision here, caused by a couple of different issues, such as (1) sometimes the original cataloger was overly broad or otherwise imperfect in their subject headings, or (2) library subject headings are often specific narrow subtopics that don't map to a single Wikidata item and have to be broken up (e.g., there will not reasonable be a Wikidata item for Seattle newspapers, but Seattle and newspapers), or (3) our data is at the item level and not the page level. At the same time, subject headings are the main sort of topical linked data in library digital collections data, since they are not creating metadata for "depicts" themselves, so it has been a priority to get these subjects mapped to their Wikidata items and begin adding more. Dominic (talk) 17:55, 13 March 2023 (UTC)
If there has been some sort of consensus to do that, I'm not going to dispute it, but I will say one last thing: if we are slapping "Main topic: arts" on the 10,000+ pages of the Town Crier, maybe 25-20% of which is arts coverage, that's going to result in a lot of false positives. At the level of an entire issue (what the library was describing) this "subject" is correct, but to apply it by bot to every single page seems ham-fisted. On the one hand, "arts" is so vague that it's hard to see who it will help find anything, and on the other hand if it's wrong some 70% of the time it is hard to see how it helps that hypothetical user. - Jmabel ! talk 18:46, 13 March 2023 (UTC)
@Jmabel: I get it, but I am trying to explain to you the process, so we can get beyond "bad bot". And also to note that, even if you think it is 70% subjects that seem too vague in this particular item from this particular institution, we are applying this solution to 3+ million files from 300 institutions, so that will not always be the case. I would like to improve, and the situation is not so much that this is the consensus set in stone, but more that there is a vacuum when it comes to community discussion of data modeling for descriptive metadata coming from institutions. If you have alternatives, I would welcome them. If we don't apply the item-level subjects to each image, where do we apply them? I get that they are only relevant to a subset of the pages in some cases, but how is that to be determined ahead of time? And I see a substantive difference between the "not helpful" and "harmful", so it's also a question of what level of imperfect subject data is acceptable. Or is it that we just need a qualifier or way of modeling for statements that are item-level description, so they can all be more clearly described as such? There has been a lot of fragmented discussion around item-level vs. file-level description, but, as with a lot relating to SDC, not a lot of resolution—so all we can really do is act based on unclear community consensus. If there were a good way to describe item-level subjects, I would be happy to implement that in the code and make another pass. Part of the way this bot is designed is that we can iterate on the data model, since it will make updates as necessary when fed a list of files. Dominic (talk) 20:43, 13 March 2023 (UTC)
Maybe something other than "main subject" for these? I don't really know what choices are available. In my experience with that type of data from GLAMs, very often the subjects listed are not a "main subject" (they can be kind of a laundry list) and can even be a bit misleading, and this is really multiplied when we take individual pages from a large work. - Jmabel ! talk 21:29, 13 March 2023 (UTC)

Main subject Portrait Photographs

You are adding main subject (P921) -> Portrait Photographs (MoMA exhibition) (Q110891521): 1969 exhibition at Museum of Modern Art. That's not correct. Also this is a genre so you should use genre (P136). We generally don't mix in the medium so the target should be portrait (Q134307). Can you please clean this up? Multichill (talk) 20:53, 13 March 2023 (UTC)

@Multichill: Thanks, that while reconciling in OpenRefine. I can fix the mapping and rerun. In this case, the subject being reconciled was actually "portrait photography" and not just "portrait". Is there a reason to use portrait (Q134307) over portrait photography (Q182956)? Dominic (talk) 21:01, 13 March 2023 (UTC)
Both are correct. It's an editorial choice. For paintings this is documented at d:Wikidata:WikiProject sum of all paintings/Genre.
For other types of art and for Commons I don't think any guidelines exist yet so we now have 9000 portrait and 5000 portrait photography. Multichill (talk) 21:10, 13 March 2023 (UTC)

Very strange additional content showing up

@Dominic: at File:Elyse Blye and Ernestine Anderson performing at service club, August 23, 1951 - DPLA - bbd804bed77db5696904436b8f7f834e.jpg, there is now some very strange content that was not added explicitly, and that I know wasn't there when I made my edits back in November. I was wondering if you have any idea what is going on. There is a completely irrelevant thing about World War II at the top of the display for the "Artwork" template, an irrelevant thumbnail of File:Belgian World War Memorial stone (Leuven).jpg, and three irrelevant "other version" images. Figured I'd hit you up before bringing this to the Village pump, in case it's an accidental side effect of something you are doing for some purpose. - Jmabel ! talk 23:04, 14 March 2023 (UTC)

Might have to do with Property / DPLA subject term being "World War, 1939-1945" (which is, by the way completely incorrect for a nightclub performance in 1951), but even if that were correct it should not throw these irrelevant images into the template. - Jmabel ! talk 23:08, 14 March 2023 (UTC)

More weirdness: File:The Town Crier, v.12, no.14, Apr. 7, 1917 - DPLA - 3b434cb1909342952bfa6e6912cfa6d7 (page 17).jpg does a similar thing with Seattle to what File:Elyse Blye and Ernestine Anderson performing at service club, August 23, 1951 - DPLA - bbd804bed77db5696904436b8f7f834e.jpg did with World War II. In the display: Object type: "city in the United States / county seat / big city" (as against a magazine page); an irrelevant picture of the present-day Seattle skyline; and, again, to totally bogus "other versions", one of them that same skyline picture and the other a picture of Chief Seattle.

I would hope we can agree that these effects, which are visible to all users who look at these pages, constitute an actual problem. - Jmabel ! talk 00:33, 15 March 2023 (UTC)

Please respect to decipt rules

Hello! I've seen (and reverted) your edit Revision of 753453537. You're bot has set lighthouse (Q39715), but Eastern Channel Pile Light (Q5330051) already exists. Thank you. --XRay 💬 04:14, 4 May 2023 (UTC)

This is an idiosyncratic view of using depicts statements that you are espousing, which is certainly not held by all. Since this is an unsettled issue, you are very welcome to discuss your preferences, but it's a little aggressive to revert an edit and warn someone to respect rules which are non-existent. Dominic (talk) 05:21, 4 May 2023 (UTC)
Please see COM:DEPICTS What items not to add. --XRay 💬 07:54, 4 May 2023 (UTC)
Your quoted document is very interesting. Our two sources contradict each other in a certain way. A sensible solution does not seem easy to me. --XRay 💬 09:08, 4 May 2023 (UTC)
As I said, it is an unsettled issue. Both pages, including the one you are relying on, say they are works in progress. Which is why I was saying it's a bit aggressive to warn someone to follow a "rule" that is just a proposal. There is also a third competing proposal at Commons:Depiction guidelines. A recent discussion found no strong consensus, though by my reading there are more people who support including general terms, since that is how the software is designed to work (see comments by WMF). Dominic (talk) 18:59, 4 May 2023 (UTC)
File:Stuffed Toy Koala - DPLA - 497dd109f27414514701d37e7d43c28c.jpg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.

If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues.

Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

A1Cafel (talk) 07:15, 17 May 2023 (UTC)

Too much depicts

You've set gable (Q1161370) (Revision of 750048576), but crow-stepped gable (Q1939660) already set. Please do not add superfluous statements. To improve search results, the search engine should be improved. Superfluous statements only lead to confusion. --XRay 💬 17:30, 22 May 2023 (UTC)

It's unclear what you are suggesting. I should work on MediaWiki's software to make adding higher classes unnecessary? If changes are ever made to the search, and the community decides to remove more general terms, that would make sense. But that's not how it works now, and you aren't doing much to explain what the harm is in having these. Generally, I don't think it is a good practice to continue to revert and issue warnings on a subject that you know is unsettled policy where no consensus exists. Dominic (talk) 19:11, 23 May 2023 (UTC)
Please read COM:DEPICTS. There is a hint not to add generic items. BTW: You can't fix a missing feature of the search engine with superfluous items. --XRay 💬 12:47, 28 May 2023 (UTC)

Notification about possible deletion

Some contents have been listed at Commons:Deletion requests so that the community can discuss whether they should be kept or not. We would appreciate it if you could go to voice your opinion about this at their entry.

If you created these pages, please note that the fact that they have been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with them, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues.

Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Affected:

And also:

Yours sincerely, Yann (talk) 13:48, 2 August 2023 (UTC)

File:First day cover commemorating the launch of the Japanese nuclear ship “Mutsu” - DPLA - 695d9b93339dd8f20dffbb20755d8482.jpg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.

If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues.

Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Adamant1 (talk) 20:04, 4 August 2023 (UTC)

File:The Arm-co-operator, September 1953 - DPLA - 1e7808ec515b093b439f004ea64b23d8 (page 4).jpg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.

If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues.

Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Adamant1 (talk) 20:45, 6 August 2023 (UTC)

Adding data to SDC that doesn't seem to match source

https://commons.wikimedia.org/w/index.php?title=File:3rd_home_of_Seattle_Public_Library_in_the_Rialto_Building,_ca._1896_-_DPLA_-_b4d2f454666ff6472519a48dd5e3cb7d.jpg&diff=prev&oldid=791378136

Source has changed what they say since you uploaded this, but in any case they never said "1896" (and if they had, why handle that as a "some value..."?) They originally said "ca. 1896" they now say "ca. 1899".

(Separately from the technical issue, but not your affair: I think the date is way too early. Look at the vehicles.) - Jmabel ! talk 04:18, 9 August 2023 (UTC)

@Jmabel: So, it's a couple of different things going on here. First, we are syncing from the aggregated data in DPLA, not the original library (it would be impossible to individually look up hundreds of institutions' data on their own catalogs, many of which may not have APIs). The data in DPLA is not updated whenever a library changes their catalog, but rather when changes get ingested into DPLA, which only happens quarterly—and it might take longer, depending on how often the hub (Northwest Digital Heritage) is harvesting from their contributors. The fact that DPLA says 1896 means the record did say that originally, even if it has been a while (even months) since it was fixed on SPL's catalog. All of this is to say, if the data changes, it will get fixed... eventually.
This is actually a major undertaking! No other bulk upload project even tries to continually sync data changes from the source, and we have almost 4 million files we're maintaining at this point.
@Jmabel: The other thing worth noting is about the "ca." part, and the SDC modeling. Basically, where you're seeing "ca. 1899"/"ca. 1896" is as part of the title, which is free text. There is a separate date field, where the original value was simply "1896," since that's what is says in DPLA. So that's what we put in the SDC date field as of now. I see the SPL record now says "1899?" in the date, which wis what will be imported—with the question mark—next time it is harvested. Why use "some value"? This allows one to add the date as a string, since we have uncontrolled data (like the question mark). That field in DPLA can contain anything from "1896" to "1899?" to "Late 1970s or early 1980s approximately" to "1800-01-01/1814-12-31" to "Undated" to "Between 1860 and 1875" (all real values). At this point, I don't have a good way to convert them all to datetime format, except the ones that are already coming to us well-formatted (but I am not adding those as P571 values yet, because it also really complicates comparing values once you have two different data models with two different possible data types to compare when synchronizing). Dominic (talk) 16:36, 9 August 2023 (UTC)
So even the ones that are well-formatted still come in as "some value"? - Jmabel ! talk 17:32, 9 August 2023 (UTC)
This is the current stage, because dates were the last field left to implement due to the complexity and I only just started adding them. At least this way, we can move forward with the plan to make the templates fully powered by SDC instead of potentially displaying outdated information. I have been working on that here, with some test edits currently live (see here). But since we're continually synchronizing, it makes it easier to improve the process iteratively, because once I add better date handling, we can update all the files the next time the bot edits them. Adding a formatted date in the property's value isn't really the hard part, but it also means making sure the template handles all possible date types, and the change detection works for both models—and then it gets even more complicated because some of the ranges are formatted enough to parse as well, but you'd have to add that with a different property in SDC. Dominic (talk) 17:52, 9 August 2023 (UTC)
File:Endangered Species - DPLA - 3b359801d29415e46732175102b8af68 (page 9).jpg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.

If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues.

Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Trade (talk) 20:57, 18 August 2023 (UTC)

File:Monopoly- Go Green Edition - DPLA - 03e1dfbb805a415d73e077ace9d18118 (page 14).jpg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.

If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues.

Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Trade (talk) 21:00, 18 August 2023 (UTC)

Thousands of duplicates

Hello, Did you you notice that DPLA bot uploaded about ~2000 duplicates between 1st and 3rd of September, see https://commons.wikimedia.org/w/index.php?title=Special:ListDuplicatedFiles&limit=5000 ? Cheers. vip (talk) 20:56, 4 September 2023 (UTC)

Thanks for letting me know. The bot is no longer uploading. I am sorry it happened, of course. But I am going to have to sort it out first thing when I am back later this week. I am traveling for US holiday weekend in a rural area, and haven't had any time to work on it yet. Dominic (talk) 00:12, 5 September 2023 (UTC)

File:Front Cover Album-3 - DPLA - e0ff466e4c02b7ee526863936a6f1512 (page 3).jpg has been marked for speedy deletion. (Reason: Front_Cover_Album-3_-_DPLA_-_e0ff466e4c02b7ee526863936a6f1512_(page_2).jpg)

Why not upload a picture of a plant, animal, or anything else which fits into our scope. You can contribute any media type you want, including but not limited to images, videos, music, and 3D models. Start uploading now! If you don't have anything to upload at the moment, why not take a look at our best images or best videos, sounds and 3D models. If you have any doubts/questions don't hesitate to visit our help desk.

User who nominated the file for deletion (Nominator) : Dominic.

I'm a computer program; please don't ask me questions but ask the user who nominated your file(s) for deletion or at our Help Desk. //Deletion Notification Bot 2 (talk) 21:28, 6 September 2023 (UTC)

Creating empty categories?

@Dominic: why are you creating emtpy categories like Category:Media contributed by Granville County Library System/Views? Empty categories usually get speedy deleted. You should just put the views on Category:Media contributed by Granville County Library System Multichill (talk) 12:56, 3 September 2023 (UTC)

I'm putting it at subpages to avoid swamping the categories with bot edits and allow the bot to more easily maintain it. I've not had anyone delete these before or complain about using subpages in this way, but I could put them elsewhere if it's really necessary. Dominic (talk) 15:33, 3 September 2023 (UTC)
Probably belongs more on a discussion page (talk page) than the way you are doing it. If this is something you do once and don't update, just put it in Category talk:Media contributed by Granville County Library System. If this is something you update periodically, then one way to do it would be to put it in Category talk:Media contributed by Granville County Library System/Views and then transclude that in Category talk:Media contributed by Granville County Library System by placing {{Category talk:Media contributed by Granville County Library System/Views}} on the page. "Category" space should be just for categories. - Jmabel ! talk 18:37, 3 September 2023 (UTC)
They are all in one category with a standard name. It will be easy to move them with a single PWB command, I am just waiting to wrap up the bot run. This is not code I've been running for long, but mainly due to necessity because BaGLAMa is constantly down. Dominic (talk) 02:13, 4 September 2023 (UTC)
@Jmabel and Multichill: I have moved all these pages to the category talk namespace. Thanks! Dominic (talk) 19:17, 13 September 2023 (UTC)
The former Category:Media contributed by Granville County Library System/Views is now a redirect to oblivion, with an incorrectly formed "Category:Category talk:" prefix. I presume you meant to redirect to Category talk:Media contributed by Granville County Library System/Views. Probably you want either to fix or remove the redirects that go nowhere.
Also, probably Category talk:Media contributed by Granville County Library System (currently empty) should contain {{Category talk:Media contributed by Granville County Library System/Views}} so that the content of the "views" page can be seen where someone would most likely look for it. - Jmabel ! talk 19:26, 13 September 2023 (UTC)
@Jmabel: I've been fixing these in a two-step process, e.g. [3]. This is because Pywikibot is too clever, and when moving a Commons category it really wants to leave a soft redirect behind, so I am cleaning them each up with a subsquent edit. These data pages are already being transcluded on the category pages using {{Views from category}} (or will be soon) in a collapsible box. Dominic (talk) 19:31, 13 September 2023 (UTC)
Perfect. - Jmabel ! talk 20:04, 13 September 2023 (UTC)
Looks like you missed Category:"In The Beginning---Baptists"!- History of the First Baptist Church, New Bern, North Carolina/Views. Or is this still work in progress? - Jmabel ! talk 18:53, 21 September 2023 (UTC)

Question about changing categories created by the bot

Hi there. A couple of questions if you'll humor me. I was just trying to move from Category:Image sources of the United States to Category:Images from libraries in the United States and apparently it wouldn't let me because apparently the bot automatically adds "dpla cat" to categories when it creates them, which makes it impossible to remove or otherwise change parent categories. I subsequently dealt with by removing the template and re-adding most of the categories manually along with Category:Images from libraries in the United States, but that's a super big hassle. So is there any way that you could make it so the template doesn't force the addition of Category:Image sources of the United States to categories it creates?

The reason I ask is because the whole Category:Image sources scheme is a more ambiguous duplicate of Category:Images by source. So I'd like to merge the former into the later, which I can't do if it's impossible to edit the categories. The same also seems to go for Category:Images from GLAMs, which your bot automatically adds to categories by default when it creates them. At the end of the day though there's no reason we need three separate categories for essentially the same concept. Although Category:Images from GLAMs is especially problematic because it goes against the policy that category names shouldn't combine multiple subjects. But regardless I'd like to upmerge Category:Image sources and Category:Images from GLAMs into Category:Images by source and I can't do that when your bot automatically adds them to new categories it creates. Especially if there's no easy way to remove them without having to re-add other categories, page view templates, Wikidata infoboxes, and 15 other things in the process. Adamant1 (talk) 15:28, 23 September 2023 (UTC)

Moved a category to its own talk page?

I don't quite understand what the purpose of this would be. I also don't understand how it's within the scope of your bot. --R'n'B (talk) 17:35, 24 September 2023 (UTC)

@R'n'B: It was certainly not on purpose, sorry about that. I did a one-time move of other categories and this happened as well somehow, probably a quote mark left off in my list, or an error like that. I think I fixed it, if it was just supposed to be a soft redirect before. Dominic (talk) 17:38, 25 September 2023 (UTC)

Copyright status: File:Denver City Park. - DPLA - a73b7525b815d742320382a1cb0591f8.jpg

bahasa melayu  català  čeština  dansk  deutsch (Sie-Form)  deutsch  english  español  français  galego  hrvatski  italiano  magyar  nederlands  norsk  norsk bokmål  norsk nynorsk  português  polski  português do Brasil  română  sicilianu  slovenčina  slovenščina  suomi  svenska  türkçe  беларуская  беларуская (тарашкевіца)  български  македонски  русский  українська  ಕನ್ನಡ  ತುಳು  മലയാളം  한국어  日本語  中文(简体)  中文(繁體)  עברית  العربيَّة  فارسی  +/−
Warning sign
This media may be deleted.
Thanks for uploading File:Denver City Park. - DPLA - a73b7525b815d742320382a1cb0591f8.jpg. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear.

If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.)

If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the VRT system and follow the procedure described there.

Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you.

And also:

This action was performed automatically by AntiCompositeBot (talk) (FAQ) 08:24, 30 September 2023 (UTC)

Copyright status: File:State of Colorado - compiled from the official records of the General land office and other sources - DPLA - 5b56668182e1073538eba89ecc92d8c9.jpg

bahasa melayu  català  čeština  dansk  deutsch (Sie-Form)  deutsch  english  español  français  galego  hrvatski  italiano  magyar  nederlands  norsk  norsk bokmål  norsk nynorsk  português  polski  português do Brasil  română  sicilianu  slovenčina  slovenščina  suomi  svenska  türkçe  беларуская  беларуская (тарашкевіца)  български  македонски  русский  українська  ಕನ್ನಡ  ತುಳು  മലയാളം  한국어  日本語  中文(简体)  中文(繁體)  עברית  العربيَّة  فارسی  +/−
Warning sign
This media may be deleted.
Thanks for uploading File:State of Colorado - compiled from the official records of the General land office and other sources - DPLA - 5b56668182e1073538eba89ecc92d8c9.jpg. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear.

If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.)

If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the VRT system and follow the procedure described there.

Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you.

And also:

This action was performed automatically by AntiCompositeBot (talk) (FAQ) 09:24, 30 September 2023 (UTC)

Copyright status: File:Cherokee City - be it know, that ... is the owner of ..., in Cherokee City, as surveyed and platted. - DPLA - b38eaf77643e1bb698c501572647adab.jpg

bahasa melayu  català  čeština  dansk  deutsch (Sie-Form)  deutsch  english  español  français  galego  hrvatski  italiano  magyar  nederlands  norsk  norsk bokmål  norsk nynorsk  português  polski  português do Brasil  română  sicilianu  slovenčina  slovenščina  suomi  svenska  türkçe  беларуская  беларуская (тарашкевіца)  български  македонски  русский  українська  ಕನ್ನಡ  ತುಳು  മലയാളം  한국어  日本語  中文(简体)  中文(繁體)  עברית  العربيَّة  فارسی  +/−
Warning sign
This media may be deleted.
Thanks for uploading File:Cherokee City - be it know, that ... is the owner of ..., in Cherokee City, as surveyed and platted. - DPLA - b38eaf77643e1bb698c501572647adab.jpg. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear.

If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.)

If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the VRT system and follow the procedure described there.

Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you.

And also:

This action was performed automatically by AntiCompositeBot (talk) (FAQ) 10:24, 30 September 2023 (UTC)

Copyright status: File:Baist's real estate atlas of surveys of Denver, Col. (Plate 7) - DPLA - 56ea391df3243fb3bbab85f738034c1d.jpg

bahasa melayu  català  čeština  dansk  deutsch (Sie-Form)  deutsch  english  español  français  galego  hrvatski  italiano  magyar  nederlands  norsk  norsk bokmål  norsk nynorsk  português  polski  português do Brasil  română  sicilianu  slovenčina  slovenščina  suomi  svenska  türkçe  беларуская  беларуская (тарашкевіца)  български  македонски  русский  українська  ಕನ್ನಡ  ತುಳು  മലയാളം  한국어  日本語  中文(简体)  中文(繁體)  עברית  العربيَّة  فارسی  +/−
Warning sign
This media may be deleted.
Thanks for uploading File:Baist's real estate atlas of surveys of Denver, Col. (Plate 7) - DPLA - 56ea391df3243fb3bbab85f738034c1d.jpg. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear.

If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.)

If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the VRT system and follow the procedure described there.

Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you.

And also:

This action was performed automatically by AntiCompositeBot (talk) (FAQ) 11:24, 30 September 2023 (UTC)

Copyright status: File:YH 38-07 - DPLA - e7b69eead5d76c24e90db59bd6d75d92.jpg

bahasa melayu  català  čeština  dansk  deutsch (Sie-Form)  deutsch  english  español  français  galego  hrvatski  italiano  magyar  nederlands  norsk  norsk bokmål  norsk nynorsk  português  polski  português do Brasil  română  sicilianu  slovenčina  slovenščina  suomi  svenska  türkçe  беларуская  беларуская (тарашкевіца)  български  македонски  русский  українська  ಕನ್ನಡ  ತುಳು  മലയാളം  한국어  日本語  中文(简体)  中文(繁體)  עברית  العربيَّة  فارسی  +/−
Warning sign
This media may be deleted.
Thanks for uploading File:YH 38-07 - DPLA - e7b69eead5d76c24e90db59bd6d75d92.jpg. I notice that the file page either doesn't contain enough information about the license or it contains contradictory information about the license, so the copyright status is unclear.

If you created this file yourself, then you must provide a valid copyright tag. For example, you can tag it with {{self|GFDL|cc-by-sa-all}} to release it under the multi-license GFDL plus Creative Commons Attribution-ShareAlike All-version license or you can tag it with {{PD-self}} to release it into the public domain. (See Commons:Copyright tags for the full list of license tags that you can use.)

If you did not create the file yourself or if it is a derivative of another work that is possibly subject to copyright protection, then you must specify where you found it (e.g. usually a link to the web page where you got it), you must provide proof that it has a license that is acceptable for Commons (e.g. usually a link to the terms of use for content from that page), and you must add an appropriate license tag. If you did not create the file yourself and the specific source and license information is not available on the web, you must obtain permission through the VRT system and follow the procedure described there.

Note that any unsourced or improperly licensed files will be deleted one week after they have been marked as lacking proper information, as described in criteria for deletion. If you have uploaded other files, please confirm that you have provided the proper information for those files, too. If you have any questions about licenses please ask at Commons:Village pump/Copyright or see our help pages. Thank you.

And also:

This action was performed automatically by AntiCompositeBot (talk) (FAQ) 12:24, 30 September 2023 (UTC)