User talk:Ahasuerus

See User talk:Ahasuerus/Archive for discussions prior to 2022.

PLEASE NOTE: If you're writing to inform me that you've either added a COVER IMAGE or NOTES to any of my VERIFIED PUBS, please follow THIS LINK and add it to the bottom of the list. A link to the pub record would be appreciated. Once the pub has been reviewed, I'll remove your note from the list. Thanks!

Author Merges & Alternate Names

I merged "J. C. H. Rigby" (148444) and "JCH Rigby" (287823) resulting in the "new" JCH Rigby. One of them (I'm not certain which at this point, but think it was the 287823 entry) had an alternate name of Charlie Rigby. When I did the merge, the alternate name was lost. That caught me by surprise. When a merge is done, the normal expectation would all the information is merged. Title merges handle variants so I would have expected author names to handle alternate names. Ideally, it should handle the alternate name. If not, there need to be a big warning that further action is required. I wonder if we have lost alternate names because of this... -- JLaTondre (talk) 09:06, 1 January 2022 (EST)

Let me take a look... Ahasuerus 11:33, 1 January 2022 (EST)

OK, I think I can see the sequence of events. Let me run the weekly/monthly backups and then I will try to recreate the problem on the development server. Ahasuerus 12:17, 1 January 2022 (EST)

I have wrapped up and deployed the cleanup reports which were in a semi-ready state yesterday. Hopefully I can recreate and fix this problem tomorrow. Ahasuerus 20:19, 2 January 2022 (EST)

I have been able to recreate the problem on the development server. Luckily, it doesn't seem to affect VTs, so any lost "alternate name" associates will appear on the cleanup report that looks for "stray" publications. Bug 795 has been created. Thanks for identifying the problem! Ahasuerus 17:11, 3 January 2022 (EST)

OK, I believe the bug has been fixed. Ahasuerus 18:06, 3 January 2022 (EST)

Out of curiosity: aren't we standardizing names anymore to J. C. H. Rigby? Regards, MagicUnk 05:32, 4 January 2022 (EST)

Originally, we always added a period and a space after an initial. As Template:PublicationFields:Author says:

• Initials should normally be entered followed by a period and a space as "Gordon R. Dickson" or "K. D. Wentworth", even if the period or space is omitted in the publication.

However, we later realized that some authors deliberately use their initials as a "pseudo-name" like "JCH" and that the practice has been getting more common recently. That's when we updated Template:PublicationFields:Author with the following caveat:

• However, when it is clearly the author's choice to omit the period, or when the author has a single letter name that is not an initial (e.g. "Harry S Truman") the period should be omitted. In the rare case where an author prefers two (or more) initials as if they were a name (such as "TG Theodore"), without a period or space, and is so credited, we follow the author's preference.

Ideally, our search logic would ignore periods and other punctuation in names, but we aren't there, so this s the best compromise we could come up with. Ahasuerus 10:08, 4 January 2022 (EST)

Given we can have alternate names for authors, would it make sense to create an ISFDB-standard name as an alternate for search purposes? ../Doug H 13:36, 1 February 2022 (EST)

It's been known to happen, e.g. see PS Cottier, an alternate name used by P. S. Cottier. I am not sure if this is the consensus approach at this time, though. Something to ask on the Rules and Standards page, perhaps? Ahasuerus 14:58, 1 February 2022 (EST)

Rejection Issue

I screwed up the HTML on this submission which is causing the moderator display to not show correctly. I tried editing the URL to change it to http://www.isfdb.org/cgi-bin/mod/reject.cgi?5187168, but that seems to get the ID from the post and not the URL. Need some help on how to reject this submission. Sorry for the inconvenience. -- JLaTondre (talk) 11:51, 2 January 2022 (EST)

Done. You were close -- the correct CGI script name is "hardreject" :-) Ahasuerus 12:19, 2 January 2022 (EST)

Misaligned

http://www.isfdb.org/cgi-bin/publisheryear.cgi?35762+1991; http://www.isfdb.org/cgi-bin/publisheryear.cgi?35762+1992; Another 2 cases where the ? mark after the last title causes it to be in a different row. I think you're the one who fixes this kind of stuff. --Username 11:43, 1 February 2022 (EST)

That's right, I usually handle software issues. However, I am looking at these two Web pages right now and they appear to be displayed correctly. I have tested it under Firefox, Google Chrome, MS Edge and Tor so far. Which browser and which version are you using? Ahasuerus 12:40, 1 February 2022 (EST)

I recall that months ago I brought this up and I think it was you who discovered it was some issue with covers with that rollover thing next to the title that were causing the problem, and then you fixed it; it's on 1 of these message boards somewhere. Recently, I brought it up again after discovering more of them, but was told you were in charge of that stuff, but I don't think I bothered asking you about it then. Now that I came across these 2 problems by the same publisher (in Poland), I see that the first 2 covers are displayed in 1 row and the 3rd cover (the ones with the ? next to them) are displayed below the first two, in a separate row. I believe this is exactly the same issue as the other times I brought it up, so I guess the answer is to do whatever you did that first time to fix it. I use Google Chrome on a laptop with Windows 8.1. --Username 12:49, 1 February 2022 (EST)

Oh, you are looking at http://www.isfdb.org/cgi-bin/publisheryear.cgi?35762+1991+1 and http://www.isfdb.org/cgi-bin/publisheryear.cgi?35762+1992+1 (note the additional "+1" at the end), which display cover scans for these publications. Now I see the issue. Let me check our archives to see what was causing similar problems in the past... Ahasuerus 13:06, 1 February 2022 (EST)

OK, it should be fixed now. Could you please check if everything looks OK? Thanks for reporting it! Ahasuerus 13:21, 1 February 2022 (EST)

Yes, they're fine now. I found my previous message, http://www.isfdb.org/wiki/index.php/ISFDB:Moderator_noticeboard#Jumbled_Covers, in case you want to look at those, too. --Username 13:26, 1 February 2022 (EST)

Thanks, I have updated that discussion on the Moderator Noticeboard page.

What happened was that I fixed this issue on the Title Covers page back when it was first reported some months ago, but I didn't realize that the Publisher Year page had the some problem. And then I missed your January post on the Moderator Noticeboard.

If you come across any other ISFDB pages which display mouseover help for covers and mess up the display, please let me know. Ahasuerus 14:28, 1 February 2022 (EST)

Author:W._A._Harbinson

It looks like there was only one use made of the Melvyl template. I notice you created the author wiki page Author:W._A._Harbinson and in the last sentence said what he'd been doing for 'the last eight years'. Checking the log, seems that was back in 2008. Bit misleading after 13 years. I wonder what kind of editor let that kind of thing get on the wiki. ../Doug H 14:55, 1 February 2022 (EST)

I have moved the author-provided autobiography to the database proper, clarified that it was posted in August 2006 and deleted the Wiki page. Thanks for catching it! Ahasuerus 15:08, 1 February 2022 (EST)

Dating publications - a thought

My last point in the discussion was that of verified data being sacrosanct and all else to be annotated with source. I've been digging through multiple sources to document some non-genre Asimov most recently OCLC. I dug into entry with 4 sources with a date of [1954] and got c1954, sixth printing (in associated scan only), one doesn't have the book, and the fourth connection just hung. I'm currently wrestling with how to record such references when I create a pub, because if I don't record it, someone else might either use it to create new publications or modify an existing one. With that for context, I can see that the idea of documenting sources will need to be addressed as a community. You're probably already wrestling with it, let me know if I can help. ../Doug H 12:42, 4 February 2022 (EST)

Sorry, I missed this message when it was posted. I will try to respond tomorrow. Ahasuerus 00:17, 8 February 2022 (EST)

Yes, secondary sources like OCLC and other online catalogs present a variety of challenges. At one point we tried to describe them in Help:How to parse data in library catalogs and Help:Using Worldcat data, but it's been a number of years since the instructions were last updated and they are still incomplete. For example, the former says "Need to add an explanation of the MARC family of standards, SUTRS and the OCLC guidelines here", which hasn't been touched since 2008.

If you have ideas/suggestions re: improving these Help pages, creating new ones or documenting third party information in Notes, please don't hesitate to post them on the Community Portal! Ahasuerus 09:01, 8 February 2022 (EST)

I've added some text to the Help Entry for parsing (sans discussion on a Portal as it is background and context) and came to the realization that I don't know why you'd want the MARC family of standards (et al) on there. OCLC won't give you the MARC version (as far as I can tell) and all it does is format what's displayed. So unless one plans on automating the pull, I don't see why one would want the machine-readable format. Particularly since it is notoriously difficult to parse. ../Doug H 15:53, 9 February 2022 (EST)

Mismatched Double Quotes

The Mismatched Double Quotes cleanup report might need an ignore option. A single double quote is a valid abbreviation for inch (which is the usage in the two current records). Or have it ignore word boundary + number + double quote (\w\d+"). -- JLaTondre (talk) 21:37, 7 February 2022 (EST)

Good point. FR 1485, "Allow ignoring records on the Mismatched Double Quotes cleanup report", has been created. Ahasuerus 08:54, 8 February 2022 (EST)

After examining the code, I see that this is a bigger mess than I realized. The report is actually limited to records with notes which contain mismatched double quotes AND the string "http". In other words, it's looking for malformed URLs. The logic works most of the time, but notes which contain a URL plus a separate mismatched quote throw it off. In addition, we have another cleanup report, "Invalid HREFs in Publication Notes", which does something similar -- but not the same -- for Publication notes only.

Let me see if I can expand the second report to cover all record types and then fold the first report into it. Ahasuerus 10:45, 8 February 2022 (EST)

Done. Ahasuerus 17:16, 8 February 2022 (EST)

Thanks. -- JLaTondre (talk) 18:39, 8 February 2022 (EST)

Info for authors

If you were to talk to a group of authors about ISFDB, what would be the first things you'd share with them? I'm going to be doing that, and I'd be interested to know the things you'd think are most important for them to know. Thanks! ···日本穣 · 投稿 · Talk to Nihonjoe 17:20, 8 February 2022 (EST)

Off the top of my head:

• Eligibility - what cannot be added to the DB. Their site or blog are not producing a "published" story. That magazine in Lithuania is.
• The fact that we are a historical DB - if you EVER published it, we won't delete it. No matter how ashamed you are of it.
• They won't see the magazines and anthologies they have stories in on their pages - they will see the stories themselves.
• If they need help, we will assist them by adding or editing or teaching them how to add to the DB. They are welcome to add their own stories and novels or have someone else add for them or ask for help for someone to add (and that includes translations and we have multi-language editors to assist).

For example... I may have done some of it with some of authors :) Annie 17:34, 8 February 2022 (EST)

Apologies for intruding, but a couple of observations/suggestions, based on stuff I've seen on social media:

* Re. eligibility, I don't think it's obvious to newbies that the way to add stories is via the pubs they appear in. See this exchange for an example

* It's not at all obvious to visitors that the primary means of communication is via the Wiki, hence stuff like that prior example or this one of authors crying into the void for help.

* I've also seen ISFDB described as a wiki, which I guess it is in the general sense of a community of contributed info, but not if you're thinking of stuff like MediaWiki, Confluence, Sharepoint (or whatever MS offer in that vein these days). In particular, it might be worth pointing out that having all submissions be moderator approved means that data should be more accurate than Wikipedia, Goodreads, etc ErsatzCulture 18:42, 8 February 2022 (EST)

How about asking them to make sure their full names, correct birth dates/places of birth, and updated websites (if any) are in their records; today I corrected over a dozen "Calfornia" misspellings for places of birth, plus many records have just a year for birth dates with no day or month (many death dates are also questionable, but you can't ask those authors because they're dead). --Username 18:48, 8 February 2022 (EST)

I would probably present it as two separate questions. The first one is "Why is bibliography important when you are an author?" The second one is "What makes ISFDB stand out among other online bibliographies?"

The primary answer to the first question is "Assistance with discovery". When you finish reading an exciting book/story, one of the first questions that you ask yourself is whether there are more books by the same author or similar books by similar authors. A comprehensive bibliography can answer the first question and help with the second question. For example, Mountaindale Press specializes in LitRPG, so it's a good place to check out if you are interested in LitRPG. Ditto Yen On, Airship, and J-Novel Club for light novels. Tor and Baen have their fans who pick books based on the publisher. Major media franchises like Star Trek, Star Wars, Warhammer, etc are good places for new authors to put their name on one or more bestseller lists. Etc. A bibliography which lets readers hop from author to series to publisher to author ad infinitum is a useful discovery tool.

The answer to the second question is that no single bibliography is perfect, but ISFDB has certain advantages compared to other online alternatives. Goodreads has more ISBNs and ASINs, but they are not as well organized and searching for short fiction can be challenging. Amazon has a LOT more ISBNs and ASINs, but, again, organization and short fiction can be problematic. On the flip side, they have reviews and more robust tag systems.

Finally, I have seen editors comment on how useful the ISFDB database can be when putting together anthologies and collections. It may not benefit authors directly, but it's likely an indirect benefit. Ahasuerus 18:56, 8 February 2022 (EST)

That's a good way to look at it - as long as the discoverability is paired with the "but we keep records of all the books we know of, even if you they are not available or you do not want them to be listed or if they were authorized editions". :) Annie 19:27, 8 February 2022 (EST)

Re: Eligibility: Thus my third point - which pivots into explaining how you add your stories :) Annie 19:27, 8 February 2022 (EST)

This is all great information, everyone. Thanks! ···日本穣 · 投稿 · Talk to Nihonjoe 16:19, 9 February 2022 (EST)

Ossuary

http://www.isfdb.org/cgi-bin/pl.cgi?647581; You entered this more than 4 years ago and today I saw it on FantLab. I added cover and fixed publisher, but there's a photo with contents that differ slightly from what you noted, plus there's a cover art credit but I don't see a name on the cover so I didn't enter it; if you're interested you might want to update some things. --Username 11:50, 9 February 2022 (EST)

Updated, thanks. Ahasuerus 13:24, 9 February 2022 (EST)

BTW, there's only 1 Kotarbinsky on ISFDB, Vasily, http://www.isfdb.org/cgi-bin/ea.cgi?271194, with an interior art credit on nearly the same date, so that's probably who it is. --Username 13:31, 9 February 2022 (EST)

Updated, thanks. Ahasuerus 16:47, 9 February 2022 (EST)

Just double-checking

To make sure my understanding is correct. Thanks! ···日本穣 · 投稿 · Talk to Nihonjoe 14:38, 9 February 2022 (EST)

Response posted. Ahasuerus 16:26, 9 February 2022 (EST)

Fateful Lightning cover - non /P/isbn cover

I've just attached a cover to [1] (when the edit goes through) which might match the printing you've PVed. --GlennMcG 01:26, 10 February 2022 (EST)

Yes, my first printing has the same cover art plus the following thin line:

• ROC * 451-LE5196 * (CANADA $6.99) * U.S. $5.99

at the bottom. I have also confirmed that it's the same cover as the one used on the fifth printing published in 1998-01, which Locus1 attributes to Sanjulian, so now we have the name of the cover artist. Thanks. Ahasuerus 10:20, 10 February 2022 (EST)

Account Recovery

Hello!

Attempted to login yesterday and today with no success. Granted it has been a long while... Used the Wiki feature to reset my password, and it claims an email was sent, but I've been checking my inbox and spam folder all day to no avail.

From what I recall the Wiki was always... quirky. I suspect that hasn't changed, so curious if this is a glitch of some sort or something actually wrong on my end. Regardless, not sure what my options are, or if I should just plan on soldiering on with a new username. Wasn't sure where else to turn.

Cheers, --Albinoflea-Spurned 21:24, 22 February 2022 (EST) (The user/former moderator once known as Albinoflea)

Welcome back :) Mails are... not working with all servers. Let's hope Ahasuerus can help! :) Annie 22:13, 22 February 2022 (EST)

Welcome back! Let's start with the basics -- are you still using s******.f*****@gmail.com as your email address? The reason I am asking is that I don't see this email address in the ISFDB server's outgoing mail queue, so I wonder if the address may have been changed. Ahasuerus 23:22, 22 February 2022 (EST)

Yes, that email is correct, and I still have copies of emails I received from ISFDB users and even an old password reset email from 2014 that were sent to my inbox. Albinoflea-Spurned 14:41, 23 February 2022 (EST)

I see. I have just changed your password using a Wiki maintenance script and sent the new password to your Gmail account. Could you please let me know when you get the email message and whether the new password worked? Ahasuerus 16:18, 23 February 2022 (EST)

Thanks, that one went to spam but I retrieved it without any trouble. Logged in, updated password and all seems good. Thanks! Albinoflea 16:52, 23 February 2022 (EST)

Excellent! :-) Ahasuerus 16:54, 23 February 2022 (EST)

Importing Content Labeled as Proposed Clone

Please see this submission: This is an import content submission, but the title at the top of the moderator screen is listed as "Proposed Clone Publication Submission". On the public view, it correctly states "Pending ImportExport Submission". Thanks. -- JLaTondre (talk) 08:38, 24 February 2022 (EST)

Yup, it's a known issue on my list of things to fix -- Bug 787, "Import/Export submission review has wrong header". Ahasuerus 11:31, 24 February 2022 (EST)

And fixed. Ahasuerus 17:58, 24 February 2022 (EST)

Thanks. -- JLaTondre (talk) 18:06, 27 February 2022 (EST)

Nav bar: something a bit disorienting for a new self-approver

When I clicked on a "Self-approver view" link (e.g. http://www.isfdb.org/cgi-bin/mod/submission_review.cgi?5243123) this added the "Moderator Links" section to the bottom of the nav bar. I wasn't sure what delights might await on those pages, so I clicked on each of the links, but they all give a "Moderator privileges are required for this option" page. My initial thought was that there was maybe some cookie/session magic involved, so I logged out and back in, and was a bit confused when that Moderator Links section had disappeared.

Having gone back through my browser history, and checked out the code, I can see now that that stuff gets added to the nav bar for any page with code in the /mod/ subdirectory. Assuming there aren't any cases where those sidebar links do work for self approvers, it might be nice to wrap the coder that outputs that section to be wrapped in a 'if moderator:' test, and so not render them for editors who can't make use of them?

This would be a very low priority change, as I guess the number of people affected is in the single digits, and they'll all work it out, but maybe it's a case of adding the if test and indenting the block of lines that output those links?

(I can see the code a bit further down mod/isfdblib.py references moderator, self_approver and SelfApprovalAllowed(userid), so perhaps there are complexities involved in the privileges that make this not as trivial as I might have made out though?) —The preceding unsigned comment was added by ErsatzCulture (talk • contribs) .

The "Self-approver view" link was added to the Pending Submission page just last week, so it's probably an oversight. Let me take a closer look... Ahasuerus 17:55, 25 February 2022 (EST)

OK, I think I got it. Could you please try again and see if everything looks OK on your end? Ahasuerus 18:20, 25 February 2022 (EST)

Thanks - I've just been through the edit/approval cycle a couple of times and didn't see the mod links appear. ErsatzCulture 18:32, 25 February 2022 (EST)

Excellent! :) Ahasuerus 18:35, 25 February 2022 (EST)

Reports Paging

Hi Ahasuerus

I've been working through my list of unstable amazon images and I noticed an entirely inconsequential bug with the paging. I just got the report down to one page, 200 rows, and there was still a link to the second page of records. Clicking the link brings you to an empty page. I've since dropped below 200 rows, and there is no link to the second page, as one would expect. I'm guessing that this is the difference between >= vs >. Although it's completely trivial, I thought I'd bring it to your attention. Thanks. --Ron ~ Rtrace^Talk 07:12, 3 March 2022 (EST)

Thanks, I'll take a look. Appreciate the heads-up! Ahasuerus 10:20, 3 March 2022 (EST)

OK, I see what's going on. Basically, the SQL query says "Give me the next 200 matches". If the database engine returns less than 200 matches, then the software doesn't display a link to the next page. If the engine returns 200 matches, then a link is displayed.

The problem with this logic is that it doesn't distinguish between "there are exactly 200 matches on file" and "there are more than 200 matches on file". What the software needs to do is request 201 matches. I'll see what I can do after finishing the round of changes that I currently have in the works. Ahasuerus 13:39, 3 March 2022 (EST)

OK, the 3 "My Primary Verifications" tables have been fixed. I still need to fix a bunch of other tables that have the same issue, but it may take a bit since they are all somewhat different. Ahasuerus 16:55, 4 March 2022 (EST)

Top Contributors et al

Hi Ahasuerus

I suspect that the Top Contributors and similar reports are stuck again. The most recent Last User Activity is for March 6. As before, this isn't urgent, but I thought you'd want to know. Thanks. --Ron ~ Rtrace^Talk 07:10, 8 March 2022 (EST)

All "Database Statistics" reports were moved to a weekly schedule last week -- see Nightly processing getting split for details. Most of them say "This report is generated once a week" at the top of the page, but I see that "Top Contributors" ones do not. Let me add that real quick... Ahasuerus 10:12, 8 March 2022 (EST)

Done -- see Top ISFDB contributors (All Submission Types). Thanks for the heads-up. Ahasuerus 12:01, 8 March 2022 (EST)

I won't say that I'm not disappointed, but I do understand the necessity of the change. I recall when these reports were on demand, and I did adjust after they went daily. Thanks for the explanation. --Ron ~ Rtrace^Talk 21:41, 8 March 2022 (EST)

In a way, we are victims of our success. The more records and submissions we have, the longer it takes to generate reports. Unfortunately, many reports draw data from multiple tables and lock them while the data is compiled.

Ideally, we would move all of our report-generating processes to a different server and then shuffle the backups and the compiled data back and forth between the production server and the backup server, but it would require a fair amount of juggling. Ahasuerus 22:23, 8 March 2022 (EST)

Patches, testing and a proposal

Hi. Sorry for not submitting any further patches after the last one. Offline life caught up to me and suddenly I have a lot less spare time. /Lokal_Profil 18:08, 13 March 2022 (EDT)

No worries whatsoever. Real life happens. Ahasuerus 19:47, 13 March 2022 (EDT)

I struggled a fair bit with setting up a local development environment. I simply don't have space for a full virtual machine running the right version of sql etc. so I aimed at just getting the python bit up and running. After some hacking I managed to get a virtual environment up and running for Python 2.5.4. My plan was to introduce some unit tests so that I could at least do some initial refactoring with a fairly high certainty that it wouldn't have any undesired effects. What I then came across was that the imports rely on the required python files from the common directory being copied across to the other directories when the system is built. This put a stop to my unit test plans.

What I wanted to check with you is if it would be of interest if I re-arranged the import and folder structure as a package instead. This would make unit testing possible but should also simplify both a future migration to a newer python version and make the codebase easier to understand for new developers. Even if it might be possible to split the patch up into a few incremental changes the end result still touches most of the codebase and as such would require extensive testing. I can therefore see how it might not be a desired change. If you want me to go ahead with it I will try to get it done in my spare time and let you know when it is ready for testing. If you don't then I fully understand =) Cheers, /Lokal_Profil 18:08, 13 March 2022 (EDT)

At one point I looked into restructuring our copy/import system. What I found was that the parts of Python which support packages and imports were significantly changed and expanded in Python 2.6 and 2.7. I figured it would be better to wait until we could upgrade to 2.7 and then revisit the issue. More recently, Al started looking into a possible Python 3.x upgrade -- see Development/HTTPS -- which may add another wrinkle. Ahasuerus 19:47, 13 March 2022 (EDT)

I believe the main changes are to how relative imports are handled. Since absolute imports are generally recommended I would have gone for that (should then still work for python 3). I believe the change is desirable before the python 3 migration (since it allows for easier testing) but can probably happen before or after a python 2.7 migration. Happy to wait until after such a migration but I'm also equally happy to go ahead as a preparatory step for auch a migration. /Lokal_Profil 05:07, 14 March 2022 (EDT)

Would it be possible/feasible to try it with a small, self-contained part of the system? For example, common/sfe3.py is copied to all directories, but it's only used in edit/cleanup.py, edit/sfe3_authors.py and nightly/weekly_job.py. Would it be a good guinea pig? Ahasuerus 09:43, 16 March 2022 (EDT)

I looked into what the file structure looks like once the files land in /www/cgi-bin/ and realised absolute imports won't work there unless bigger changes are made. Relative imports might be possible depending on how the files are executed, but this might also be where python 2.6 would be needed (for the __package__ attribute).

The smallest change I could envision is to change the scripts in rest/. I prepared a set of patches for this (1 2 3) before I spotted the above mentioned issue with absolute imports. Using relative imports instead the first of these patches could probably be dropped and the third would have to be modified somewhat.

But based on the above I'd say your original appraisal was right and these changes should probably await the python bump (to 2.7 at least). Even then since the directory structure in the execution environment doesn't mirror that of the repository (since /biblio becomes the cgi-bin root) there would still have to be some copying of common files left. /Lokal_Profil 19:14, 19 March 2022 (EDT)

Thanks for digging! It sounds like 2.7 is the first step then. I have it on my list of things to do and we need it to be able to do certain other things as well, so I will bump it up. Ahasuerus 09:41, 21 March 2022 (EDT)

Cleanup Reports

The "Cleanup Reports" link off the left menu bar is giving a "Internal Server Error". -- JLaTondre (talk) 15:55, 16 March 2022 (EDT)

Fixed -- sorry about that! Ahasuerus 16:03, 16 March 2022 (EDT)

Database backup files not working

(I wouldn't normally jump on these so quickly, but it looks like you updated the Wiki at the same time I made an unrelated edit...)

The Google Drive link doesn't seem to work for me - the header of the page says "backup-MySQL-55-2022-03-26.zip", but I don't get the usually slightly-crappy UI about the file being too large to virus check, and do I want to download it instead. Tried in latest(ish?) Chrome and Vivaldi so far; both should have Gmail/Google Apps user login/session cookies, should that make any difference.

Just tried last week's backup (which I had grabbed OK last week), and that similarly fails to offer me anything to d/l, although it did seem to have a spinner showing for a few seconds, which I don't recall seeing before.

I did see you'd updated the URLs for the image backups a few days ago, has something changed on Google Drive? ErsatzCulture 12:47, 26 March 2022 (EDT)

Update: If I click on the download icon in the top right of the Google Drive page, it does let me d/l the zip file, but the default UI just shows a largely empty page. Probably an issue on the Google side being funny with zip files, but it's rather disconcerting for an unaware user. Hopefully it's something they fix, but if not, maybe will need some help notes on the Wiki page? ErsatzCulture 12:51, 26 March 2022 (EDT)

Good point -- done. Thanks for the heads-up. Ahasuerus 13:15, 26 March 2022 (EDT)

Weird Record

Take a look at this title - no author and no date and it doesn't display the type. Something weird happened, though from the publication history, not clear what. This seems like an extransous record (there is another record in the pub of the same title for an essay) that can be removed and deleted. But thought I'd mention it first in case you wanted to take a look. -- JLaTondre (talk) 09:12, 3 April 2022 (EDT)

Thanks for reporting the issue. It turns out that this 2022-03-18 EditPub submission errored out, which is why it's not visible in Edit History. Luckily, it errored out while processing the last title record, The Third World: Space Powers of 2005?, and the rest of the submitted titles appear to be OK. I have removed and deleted the offending title. Ahasuerus 09:54, 3 April 2022 (EDT)

HTTPS-related bug when cloning pub without a cover image?

Just tried to clone this pub without a cover image, and get a Python stack trace error - the exception is "<type 'exceptions.AttributeError'>: 'NoneType' object has no attribute 'startswith'" and the relevant bits of the stack trace look to be:

 pub_image = ISFDBHostCorrection(pub_data[PUB_IMAGE])

and

 if value.startswith('http://www.isfdb.org/wiki/'):

I'm too lazy to get my dev box working with the latest code, but it feels like the second line should be "if value and value.startswith..." to protect against pubs without images? ErsatzCulture 14:49, 3 April 2022 (EDT)

That's exactly right. A fix has been deployed. Thanks for reporting the problem. Ahasuerus 17:13, 3 April 2022 (EDT)

Fixer and "recycled" ISBNs

Hi, please see this convo - any idea if Fixer will pick up the new pubs if they are using the older, apparently never-published, ISBNs? Thanks! ErsatzCulture 19:03, 9 April 2022 (EDT)

I am afraid Fixer has no way of telling that an ISBN has been reused. Once Fixer notices an ISBN in the main database, he makes a note of that ISBN's record in his data store so that it would never be submitted again. Ahasuerus 11:04, 10 April 2022 (EDT)

Thanks - at least this one is on the radar now, so it can be manually dealt with closer to the pub date. ErsatzCulture 15:36, 10 April 2022 (EDT)

(BTW, unrelated to this, but related to a talk item earlier on this page, when I d/led today's database backup, the Google Drive UI behaved as it used to, rather than presenting a blank-ish page. Guessing they fixed some bug/regression since I grabbed last week's backup...) ErsatzCulture 19:03, 9 April 2022 (EDT)

Updated, thanks. Ahasuerus 11:04, 10 April 2022 (EDT)

CC License update

We should probably update the license linked in the menu sidebar to point to here instead of here. The former is an updated version of the latter, while still being pretty much the same license. ···日本穣 · 投稿 · Talk to Nihonjoe 16:33, 18 April 2022 (EDT)

That's a good point, thanks. Let me ask Al, who knows a lot more about licenses. Ahasuerus 20:12, 18 April 2022 (EDT)

Database Errors

Seeing "<class '_mysql_exceptions.OperationalError'>: (1030, 'Got error 28 from storage engine')" errors all over the place (viewing authors, viewing titles, viewing submissions, etc.). -- JLaTondre (talk) 09:38, 23 April 2022 (EDT)

I am not seeing any errors right now. Given the timestamp of your message -- 09:38am -- I suspect that it was due to the backups which run every morning at 9:30am. I'll keep an eye on things. Ahasuerus 10:08, 23 April 2022 (EDT)

Bureaucrat warning needed?

Perhaps I'm prejudiced, but to me this looks like a personal attack. Despite Nihonjoe's attempts to cool things down, it could get out of control. --Willem 04:39, 27 April 2022 (EDT)

Thanks! Working on it... Ahasuerus 13:35, 27 April 2022 (EDT)

The Songs of Summer

In regards to this publication. If you look closely you will notice a vertical line along the whole of the artwork at the top. The first inch appears to be from a totally different piece of artwork, shows square structures on stilts - it's signed 'Heller' just below the Pan logo (top front cover) so definately the same artist but doesn't match the sea serpent part of the main image - I did an experiment by matching the top part of the book with the bottom in Photoshop and they definately don't marry. I'm going to make a note about this. --Mavmaramis 11:57, 14 May 2022 (EDT)

Interesting. There is this image on Twitter, but I don't think it sheds additional light on the mystery. Ahasuerus 12:40, 14 May 2022 (EDT)

That image comes from Heroic Dreams and is a cropped version of the image that appears on the book. Makes me think that at the composite stage of the book production - the part where they have the image and lay over the text and logos - they had a choice between two Heller imaages that were on seperate layers, added the text to the sea serpent layer and forgot about the 2nd image on the other layer and flattened/merged the layers. The image also appears in Six Fantasy Artists at Work: Dream Makers but I don't have a copy of that book to compare. I've written a message about it on Biomassbob's talk page as he's the only verifier of Dream Makers. Edit: I did find this image which shows the 'error' - whether deliberate or not I can't say but definaely very strange. --Mavmaramis 12:51, 14 May 2022 (EDT)

Preserving the PVs of a to-be-deleted pub record

Hello Ahasuerus. When you've got time, could you please have a look at this discussion re the problem evoked above ? I don't know whether it is solvable. Thanks a lot ! Linguist 11:08, 21 May 2022 (EDT).

I am afraid the software doesn't support the ability to move verifications from one publication record to another :-( Ahasuerus 13:13, 21 May 2022 (EDT)

Thanks for your response, anyway ! Cheers, Linguist 04:30, 22 May 2022 (EDT).

Request: WatchCover template similar to the WatchDate one

There are several upcoming pubs that have placeholder covers e.g. [2], [3], and I've fixed a number of older ones as I've encountered them. To try to make it easier to catch and fix these, could we have a { { watchCover } } template and associated report, so that these dodgy covers can be noted when they're first added, and fixed as-and-when better images come along?

I haven't looked at the code, but I'm guessing/hoping it should be a fairly straightforward copypaste from the existing { { watchDate } } functionality? Thanks ErsatzCulture 13:24, 31 May 2022 (EDT)

We have a spanking new bureaucrat option, "Add a New ISFDB Template" -- see Help:Screen:BureaucratMenu -- so a new template would be trivial to add. A cleanup report wouldn't take long to code either. I suggest you post a proposal on the Community Portal and see if there are any objections (unlikely) or alternative ideas.

Personally, I am all for it because it would help with light novels. US publishers frequently use original Japanese covers as placeholders for forthcoming translations. Ahasuerus 17:50, 31 May 2022 (EDT)

I wonder if we should not make that a more generic "watch (parameter)" template (where parameter can be date, format, cover, author name, title, subtitle, pages and anything else that looks suspicious and may need a second check (I use tags for that now but as they are up on the title level, it is not always easy to remember which pub they were about - especially with reprints). That way we don't have too many templates people keep forgetting to use. The wording will be the same (with the parameter notes in there and the cleanup report can show what is the watched element in a separate column (for example). Annie 18:06, 31 May 2022 (EDT)

That's an interesting idea. Currently "WatchDate" expands to "Publication date is based on questionable pre-publication information and may be incorrect." Will the parameter taken by the proposed "Watch" template be expected to be "Publication date", "Subtitle", "Page count", etc? And will the static text continued to be "is based on questionable pre-publication information and may be incorrect."?

If so, we may want to consider adding another template, "MultiWatch", which will expand to something like "The following values -- [list of field names like publication date, subtitle, page count, etc as the parameter value] -- are based on questionable pre-publication information and may be incorrect." Ahasuerus 18:42, 31 May 2022 (EDT)

Pretty much. We may want to tweak it to be "questionable pre-publication or other secondary sources information" to expand the scope a bit or we can have two separate templates (one for pre-pubs and one for other cases - they require different handling sometimes so having separate ones may make more sense) but that's the idea. That will also allow for new fields to be just added into the list without the need for a new template and without people trying to remember 10 different template names (and that way it can even be used on a title record for notes on translators, being or not genre (a common problem when adding early), author name form, the & vs and and so on).

The idea is to make these pubs (and eventually titles) easily foundable by editors who can assist with finding the data later (or elsewhere). We may even want to come up with a wording of the expanded sentence that will allow the reason for the suspicion to be part of the template (so we can say (watch|author name (title page not available), subtitle) but just being able to list the suspect values will be enormous help - especially on pre-publication records. For example "The following data is based on questionable pre-publication information and may be incorrect: (parameter here exactly as written by the editor)." or something along these lines. Then you don't even need two patterns (single and multi). Either way will give is better flexibility than what we have now. Annie 19:37, 31 May 2022 (EDT)

I like "The following data is based on questionable pre-publication information and may be incorrect: [parameter]" to cover both scenarios. The other template could expand to something like "The following data is based on information from secondary sources and may be incorrect: [parameter]". The new template names could be something like "Preliminary" and "SecondarySources". Ahasuerus 20:45, 31 May 2022 (EDT)

I am a bit worried about the second one becoming a default if it expands to that - just because you use secondary sources does not mean that the data is unreliable but a new editor won't know that when they see it (or a casual visitor). Tagging everything that does not have primary sources with it will be counterproductive and coming up with usage rules that discourage that is going to be hard (not to mention that if you do not know why the warning is there, it sounds like we do warn because the data is only from secondary sources). That's why I prefer to have the word "questionable" or go for something like "The following data is based on suspicious information from secondary sources and may be incorrect: " which makes it clearer that there is something iffy in this data - not just that the data comes from secondary sources. I'll think a bit more on the wording.

I kinda like "watch" more than Preliminary (easier to remember, less likely for someone to decide that it needs to be there for every book that is added pre-publication just by looking at the list). But I can use it either way. Annie 21:08, 31 May 2022 (EDT)

Upon reflection, I can see how both of the issues with my proposed wording would be problematic. Let's see what John thinks and then we can move this discussion to the Community Portal. Ahasuerus 21:27, 31 May 2022 (EDT)

(dedent) Thanks for responses. I don't have any particular opinions/preferences, but I agree about needing to be careful that whatever is built doesn't get applied to all advance listings. e.g. I'd guess that 99% of page counts listed by Amazon are only approximations compared to a count that strictly follows ISFDB rules, and lots of listed publisher values aren't accurate when you drill down to the imprint level, such as pretty much everything listed as "Cornerstone Digital" has a different PRH UK imprint shown on the title page.

Whilst my original request/proposal was primarily to have something to make it easier for editors to note and be reminded which records need cleaning up, there was a secondary benefit to having something that explicitly flags to a casual user of the site that it is known that the information shown is definitely incorrect. This is clearly the case when a image has text saying "Not final cover", but less so for other fields I think?

Anyway, I'm more than happy for this to be thrown out to a wider audience on Community Portal. ErsatzCulture 12:19, 1 June 2022 (EDT)

OK, let's summarize the consensus so far:

• We would like to create two templates as a replacement for "WatchDate", which is currently associated with 21 publication records.
• One template will be for "questionable pre-publication data" and the other one will be for "questionable data from secondary sources".
• Each template will take a parameter indicating which field's data is questionable.
• Each templates should expand in a way that supports both the name of a single field and the names of multiple fields, e.g. "The following data is based on questionable pre-publication information and may be incorrect: [parameter]".
• Template names should contain the word "Watch" in them in order to differentiate records with particularly questionable data from regular records which include data from pre-publication and secondary sources, e.g. "WatchPrePublication".

Is this everything?

Re-reading the list now, I am beginning to wonder if we may want to limit the current discussion to the first proposed template, which I will temporarily dub "WatchPrePublication" for the sake of convenience. A "WatchSecondarySources" template raises additional questions -- like "What exactly counts as a questionable secondary source?" -- and may need a separate discussion. Ahasuerus 14:58, 1 June 2022 (EDT)

I had been wondering the same about the secondary warnings and I agree that we should not try to fry the whole fish -- let's get the pre-publication templates set and then we can brainstorm for post-publication data issues.

We may also want to add that the parameter can be a list of fields, a reasoning or a combination of. Or words to that effect (so you can explain why you think something is suspicious or just list the fields.

Number of pages is often suspicious but tagging all pre-publications for that makes no sense - these will clear from a primary/secondary source. But that is about usage of the pattern and that will come from practice. Annie 15:30, 1 June 2022 (EDT)

I appreciate that the proposed functionality is a superset of WatchDate, but one benefit of the current setup is that the current cleanup report shows the date in question, which is potentially useful for identifying things that should have been published by now (which are worth investigating) vs future pubs (which are probably worth leaving until pub date, or close to that). It strikes me that a more flexible template may be harder to produce a cleanup report for, that isn't either hard to read, or relying on you to click through to the publication in question.

(BTW, I've just cleaned up one of the WatchDate records, and another one should become clear in ~2 weeks, so that'll get them down to 19 :-) ErsatzCulture 15:38, 1 June 2022 (EDT)

Show the parameter as a second column in the report. Then you can search for the word "date" or "cover" if this is what you want to work on only - or read through the strings and see if you can spot something else you may be able to work on. We are not expecting to have thousands of records tagged, do we? If we end up with too many tagged, these books maybe should not have been added before more data was available. :) Annie 15:46, 1 June 2022 (EDT)

We could enhance the cleanup report in 2 ways:

• Add a column for the template parameter
• Let the user re-sort the report by:
  • Publication date
  • Parameter name
  • Publication title

It would be similar to the way we currently let our users re-sort Publication Series tables by year/series number, e.g. see this publication series. Ahasuerus 12:40, 2 June 2022 (EDT)

(unindent) To summarize, here is what I think we currently have:

• Create a new template, "WatchPrePub" as a replacement for "WatchDate", which is currently associated with 20 publication records.
• The new template will be used for all types of "questionable pre-publication data".
• The new template will take a parameter indicating which field's (or multiple fields') data is questionable.
• The new template will expand to "The following data is based on questionable pre-publication information and may be incorrect: [parameter]".
• The associated cleanup report, which currently displays publication title and publication date, will have a "Parameter" column added. It will also let editors re-sort the table by publication name, publication date or parameter name.

If this looks about right, I can post the proposal on the Community Portal. Ahasuerus 14:58, 3 June 2022 (EDT)

This looks fine to me. ErsatzCulture 16:42, 3 June 2022 (EDT)

Done. Ahasuerus 11:24, 4 June 2022 (EDT)

Python Script Error?

'Show All Titles' for author Cindy O'Quinn results in 'A problem occurred in a Python script.' John Scifibones 14:26, 8 June 2022 (EDT)

Thanks, I'll take a look. Ahasuerus 14:58, 8 June 2022 (EDT)

Fixed. Thanks for reporting the problem. Ahasuerus 15:55, 8 June 2022 (EDT)

Needed Bureaucrat warning?

Perhaps I'm prejudiced, but to me this looks like a personal attack. Despite my attempts to cool things down, it could get out of control. --Username 08:34, 13 June 2022 (EDT)

Thanks, I'll take a look. Ahasuerus 11:07, 13 June 2022 (EDT)

Please see Stonecreek's answer here and his remark here. I do not think he has received the message. Thanks, --Willem 15:19, 15 June 2022 (EDT)

Yes, I saw them. When a request for self-approver privileges is posted after June 30, Stonecreek's submission history, his Wiki responses and other editors' feedback will be used to decide whether to approve it. Ahasuerus 16:42, 15 June 2022 (EDT)

Username

As you can see from last comment here, I've had it with Username. I have only limited time to spend working on ISFDB stuff, and he causes me too much annoyance and stress for me to deal with him anymore. So, I've told him I will not be handling his submissions in the future due to all the crap he heaps upon me and anyone else who tries to work with him. I'll continue working on the other submissions, but (despite the many good things Username does) I find he is more a detriment than a help here. I've bent over backward trying to break through his cantankerous shell, but I'm at a complete loss as to how to handle him. Sorry if I come off as rude here, but I've had it dealing with Username, so I'm choosing to not deal with him in the future. ···日本穣 · 投稿 · Talk to Nihonjoe 16:01, 16 June 2022 (EDT)

I wrote my (very long) reply to him already; as I explained there, he never handled most of my edits, anyway, so him not doing so anymore would hardly affect me. It happened at least once before with another mod last year, and I've made many thousands of edits since, so whatever. --Username 16:54, 16 June 2022 (EDT)

We have had a few similar situations over the years. In extreme cases most moderators stopped working on an editor's submissions and they lingered in the queue for such a long time that the editor lost interest and moved on to other projects. It's unfortunate, but there isn't much we can do about it. After all, we are all human and we are all volunteers. (Except Fixer, of course.) Ahasuerus 17:30, 16 June 2022 (EDT)

Amazon URL warning question

Hi. Can you tell me what's wrong with the URL in this submission? It looks ok to me, and I would ignore the warning and accept it, but I figured maybe I'm missing something? Thanks! --MartyD 14:16, 26 June 2022 (EDT)

The software expects "images/S/amzn-author-media-prod/" images to have a "ssl-images-amazon.com" domain. Let me see if there is an equivalent *.ssl-images-amazon.com URL or if we need to adjust the software check. Ahasuerus 14:30, 26 June 2022 (EDT)

It turns out that images-na.ssl-images-amazon.com had the same image -- fixed. Ahasuerus 14:33, 26 June 2022 (EDT)

Ok, thanks! --MartyD 10:31, 27 June 2022 (EDT)

HTML rendering issue - ea.cgi

As a non-logged in user, the author page - e.g. http://www.isfdb.org/cgi-bin/ea.cgi?206767 - shows the HTML button markup for "Never display translations". It doesn't do this for me as a logged-in user, not sure if that's just because I'm logged in, or if it's because of my personal prefs. I've not looked at the code (yet), but this feels like it might be a reasonably high-priority fix requirement, not so much in terms of overall functional impact, but it'll obviously appear on a lot of pages. ErsatzCulture 07:26, 30 June 2022 (EDT)

Yup, it's an unintended side effect of the latest patch, aka a "bug". Let me see if I can fix it real quick... Ahasuerus 08:22, 30 June 2022 (EDT)

Fixed. Thanks for reporting the issue! Ahasuerus 08:50, 30 June 2022 (EDT)

A much less important rendering issue I accidentally stumbled across are the page counts on a couple of pubs here. (Interestingly, the individual pub pages don't render the break, either as a visible HTML tag or as a break - are they being stripped out on that page perhaps?) One niggle is that one of those pubs is verified, so whilst I don't think there should be any issue with removing the HTML (and personally I'd argue it should never have been there in the first place), in theory I should contact the PVer to see that they are happy for the edit to be made. (In this particular case, it's moot, as the PVer is no longer active.) Depending on how much unwanted HTML is around, is it maybe worth relaxing the "contact PVer before making edits" for cleanup edits like this? I'll happily fix stuff like this as I come across it - and maybe even proactively query my local database to find offending records - but if the workflow has the overhead of checking with the PV(s) in order to do mundane cleanup, then I personally am going to be less inclined to spend time on this sort of thing. ErsatzCulture 07:26, 30 June 2022 (EDT)

Help:How to change verified publications makes a distinction between "significant changes" and "adding data", but it requires notifying primary verifiers in both cases. What it doesn't do is define "significant changes" or describe the process for "insignificant changes" like formatting tweaks. Back in January I proposed clarifying and expanding the language, but we were unable to reach consensus.

Perhaps a less ambitious clarification of the Help language would be easier to adopt. Something like "Insignificant and formatting changes can be made without notifying primary verifiers. What is deemed *insignificant* is left to the reviewing moderator's discretion". Not that it would it affect this particular scenario, of course, since it was a code issue, now fixed (see below.) Ahasuerus 09:10, 30 June 2022 (EDT)

I think the latter problem is code, not data. It's showing up for other titles with multiple pages (e.g. Verne, Wells. ../Doug H 08:02, 30 June 2022 (EDT)

Yup, it's another (related) bug. Looking into it... Ahasuerus 08:50, 30 June 2022 (EDT)

And fixed. Ahasuerus 09:02, 30 June 2022 (EDT)

Daughter(s) of Earth

Please see this pending edit. The note being added seems to suggest that we have the incorrect form of the title for the Merril story. I'm adding this same note on the other verifier's pages. Thanks. --Ron ~ Rtrace^Talk 09:55, 30 June 2022 (EDT)

My copy doesn't have its dust jacket any more, but I can confirm that it says "Daughters" in the table of contents but "Daughter" on page 198. Ahasuerus 12:30, 30 June 2022 (EDT)

Question re. views columns in titles table

Schema:titles (which I appreciate may be out of date) says:

title_views - The number of times this title has been viewed.

...

title_annualviews - The number of times this title has been viewed in the current calendar year.

However, I've just been looking at a handful of stories from the most recent database backup, and for those stories, the two columns are much closer than I'd expect:

   MariaDB [isfdb]> select title_id, title_title, title_views, title_annualviews from titles where title_id in (41692, 41300, 58836);
   +----------+-------------------------------------------+-------------+-------------------+
   | title_id | title_title                               | title_views | title_annualviews |
   +----------+-------------------------------------------+-------------+-------------------+
   |    41300 | I Have No Mouth, and I Must Scream        |       51937 |             51557 |
   |    41692 | "Repent, Harlequin!" Said the Ticktockman |       82185 |             76523 |
   |    58836 | The Ones Who Walk Away from Omelas        |       36974 |             32744 |
   +----------+-------------------------------------------+-------------+-------------------+
   3 rows in set (0.00 sec)

I would expect title_views to be many times bigger than title_annualviews? I could probably find this out for myself by reinstalling a backup from early January, but is it possible that title_annualviews isn't getting zeroed each year as the schema docs implies? Grepping for references to that column name, I could only find it used in SQLparsing.py, when incrementing for a view, so there doesn't seem to be an "official" annual script/job to reset that column.

Of course, that grep result implies there's nothing that exposes that figure to users of the site either, so if it isn't getting reset annually, no-one will see it :-)

(Spotted whilst looking into exactly how the counts are done, due to this blog post, which makes a minor error about the time period the counts cover.) ErsatzCulture 17:01, 30 June 2022 (EDT)

IIRC, at one point I discovered that we didn't have anything in the software that would actually reset the "annual view" count. We could probably add it to mod/marque.py, which is usually run at the beginning at each calendar year. However, it's a manual process which can be run "on demand" from the Bureaucrat menu, so there would be no guarantee that it doesn't get re-run at some random point. I guess we could add a warning to the menu option. Ahasuerus 17:54, 30 June 2022 (EDT)

Thanks. I don't think this is anything worth prioritizing/doing any time soon, I just thought it was worth mentioning after I'd stumbled across it. ErsatzCulture 10:28, 1 July 2022 (EDT)

Wikipedia template {isfdb name}

Hi. Last decade at English Wikipedia, I added hundreds of biography footer links to ISFDB author pages using Template {isfdb name}. Always I identified the ISFDB author by numeric ID, such as 'id=3845' for Jane Gaskell (and I do so again this spring at a slower rate). Probably it seemed best to start that way, because I was familiar with Wikipedia page moves --or name changes-- and considered them frequent. The alternatives are

• A. use such as 'id=Jane_Gaskell', which is adequate if it is correctly derived from the ISFDB canonical author name;
• B. rely on the default, which is to derive a similar value from the Wikipedia page name, which is adequate at "Jane Gaskell" only because and so long as her EN.wiki pagename matches our canonical name.

This spring in merely dozens of visits to biography footers, I have noticed extremely heavy use of the same template with alternative A, 'id=Jane_Gaskell' and so on. I suspect someone's steady effort during the last few years, if not a cooperative project or a robot, that adds biography footer links using template {isfdb name} with alphabetic ID values.

Do you know that the numeric ID is a better choice, as it seems to me? Or that the alpha is a better choice? (If the latter, please explain briefly.) Nowadays I do not add many new footer links from EN.wiki biographies to ISFDB authors; the template is in place, for most appropriate biography pages that I edit. But I would routinely change the ID value from alpha to numeric, or vice versa, if I were sure that one is a better choice. And I would explain the reason to prefer one or the other, if I would meet the right person at Wikipedia or Wikidata. --Pwendt|talk 13:04, 1 July 2022 (EDT)

In the past, linking by name didn't work if the name contained non-English characters. For example, http://www.isfdb.org/cgi-bin/ea.cgi?Stanisław Lem would have failed 2 years ago. I assume that's why Wikipedia editors preferred linking by ID since it was more reliable. However, the software was fixed in June 2021, which made linking by name more reliable.

At this point I would say that linking by name is slightly better. Our internal author IDs can potentially change, although it's fairly unlikely. For that to happen you'd need to either merge the author record with another record, or delete the author and then re-enter it. Linking by name doesn't have the same issue, as unlikely as it is. Hope this helps! Ahasuerus 18:30, 1 July 2022 (EDT)

Multi User Write Access Problem

Could you please take a look at this discussion and let me have your thoughts. Thanks. Teallach 18:43, 3 July 2022 (EDT)

Sure thing! Ahasuerus 21:17, 3 July 2022 (EDT)

Another page with exposed HTML markup

Bottom two items on the cleanup reports page have exposed button markup, although the links for both work fine, so it's only a cosmetic issue. ErsatzCulture 07:54, 4 July 2022 (EDT)

Fixed, thanks! Ahasuerus 12:29, 4 July 2022 (EDT)

TBH, I've never really understand why that pages uses buttons, so if it was up to me, they'd all just become vanilla HTML links to the reports ;-) ErsatzCulture 07:54, 4 July 2022 (EDT)

If I recall correctly, it originally used regular links. However, as the number of cleanup reports grew, it became increasingly difficult to click the right link. Hence the change to the "button" look. Ahasuerus 12:29, 4 July 2022 (EDT)

Crystal Warriors

http://www.isfdb.org/cgi-bin/pl.cgi?37703; I replaced unstable "P" cover with OL cover, which looks the same. --Username 10:38, 4 July 2022 (EDT)

Approved, thanks. (I remember reading this series shortly after it was published and thinking that it was gloriously pulpy. I wonder if it holds up...) Ahasuerus 12:33, 4 July 2022 (EDT)

New cleanup report

One of our very active editors has communicated that they are seeing abbreviations other than the six allowed under special designations in the Page field. He has offered to go in and correct them. A cleanup report to locate them is needed since the Page field is inaccessible with advanced search. I know you're busy, just want to get it on the list. Thanks, John Scifibones 22:24, 4 July 2022 (EDT)

Thanks, I'll take a look. Ahasuerus 22:58, 4 July 2022 (EDT)

It turns out that we already have a cleanup report that looks for invalid page numbers. As of yesterday, it was limited to "del" and invalid Unicode pipe characters. Earlier today I updated the report to look for invalid numbers following the pipe character. Anything before the pipe character is trickier because Help:Screen:NewPub says that "Uncommon page numbers like A-1, B-2, etc." are allowed. I could probably come up with another cleanup report which will look for suspicious values but allow moderators to ignore false positives. Ahasuerus 12:29, 5 July 2022 (EDT)

Looking at the first run, it appears the primary 'offender' is post pipe roman numerals. What Username was looking for is a way to find all the times he has used or seen 'fp' for frontispiece. He would like to correct them. This came up while I was reviewing some of his submissions. I have also seen 'N/A' and a few other oddities. Perhaps the answer is not a cleanup report, but the ability to search the Page field via advanced search. John Scifibones 15:10, 6 July 2022 (EDT)

I see. Yes, "fp" is invalid, so we can safely add it to the current report. I have changed the software; the new data will become available tomorrow morning. I expect around 90 additional publication records. Ahasuerus 18:29, 6 July 2022 (EDT)

Thank you for working on this. I'll let him know. John Scifibones 18:58, 6 July 2022 (EDT)

Sure thing! Ahasuerus 19:12, 6 July 2022 (EDT)

After working with the updated report, I suggest changing the description " 'fp' used instead of 'fep' ". While it is sometimes used instead for 'fep', the most frequent use was for frontispiece title records. Maybe " Nonstandard Special Designations (fp)". This is the title of the bullet point listing the allowed abbreviations in the help section. We can then add others as we discover them. John Scifibones 15:36, 9 July 2022 (EDT)

Makes sense. I have made the change. Thanks for working on the report! Ahasuerus 17:18, 9 July 2022 (EDT)

Same Image

See this submission: The image URL is exactly the same. Based on the pub history, it looks like the editor created a double submission by mistake. It would be nice if the proposed changes comparison recognized that as no change vs. the image already on file warning. Thanks. -- JLaTondre (talk) 09:09, 9 July 2022 (EDT)

Let me make sure that I understand the issue correctly. Normally, re-entering the same image URL (or any other field value) won't have an effect because the submission creation process will discard the new value after determining that it is the same as the current value. Thus this scenario only occurs if the same image URL change is submitted more than once, right? If that is the case, perhaps we still want a yellow warning, just a differently worded one. Something like "Submitted value is the same as the value already on file. This may be a duplicate submission." Does this make sense? Ahasuerus 09:50, 9 July 2022 (EDT)

Okay, looking at it closer I see what happened:

• At 15:53:22, Rosab618 submitted just the image change ([4] [5])
• At 15:53:38, Rosab618 submitted just same image change & updated pub notes ([6] [7])

They self-approved the second, but forgot to cancel the first.

I had assumed it was one of those cases where the submission button was clicked twice creating a duplicate entry. This all leads me to three thoughts of items that would be nice:

1. That the submission page showed the comparison to the current state of the record, not the comparison against the state at the time of submission (for some reason, I always think it is the former, but your description reminds me that I should know it is the later). This would help when people submit the same updates, especially with the long queue times lately.

   Let me make sure that we are on the same page. When a submission is created, only the affected record IDs and any changed values are saved within the XML payload. Unchanged values are not stored in the XML payload. When a submission review page is displayed, the software shows what is stored in the XML payload on the right hand side. The data on the left hand side is retrieved from the database using the record IDs stored in the XML payload. If one or more of the record IDs are no longer stored in the database, the submission is displayed as "non-approvable" and needs to be hard-rejected.

   The only exception to this rule is the "Subject" line of the submission. It is built by the submission creation process based on what was in the database at that time and is stored in the XML payload. Typically, the "Subject" line contains the title of the main record. If the title changes between the time the submission is created and the time it is reviewed, there will be a discrepancy between what's displayed and what's stored in the database.

   Are you suggesting that the software should be changed to build the "Subject" line dynamically? That shouldn't be too hard to do on submission review pages, but keep in mind that the "Subject" line is also used on all "Pending"/"Rejected"/"Approved" pages. If the software had to go to the database to get the current record title, it would slow things down. In addition, it would mess things up for approved/rejected submissions whose main record is no longer on file. Ahasuerus 12:54, 9 July 2022 (EDT)

   On reflection, what I'm suggesting is that the table be created as is currently, but the color coding for changes be based on a comparison to the current values. When the values on both sides are the same, show them both as green vs. the left side as red (similar to what is done with the merge screen). A warning note could also be added that there is no change. -- JLaTondre (talk) 14:40, 9 July 2022 (EDT)

   OK, that makes sense. FR 1514, "Enhance submission review pages to look for unchanged submitted values", has been created. Ahasuerus 17:52, 9 July 2022 (EDT)

2. That self-approver submissions were identified in the moderator queue (maybe another color?) and possibly skipped by the Next Submission button. I wouldn't have bothered with this one had I realized it was a self-approver and instead done another submission.

   Makes sense. I have created FR 1512, "Next Submission link to skip submissions by self-approvers". Re: color-coding them, I'll need to know which color to use since I am color-blind and can't tell which colors stand out to most people. Ahasuerus 12:32, 9 July 2022 (EDT)

   FR 1512 has been implemented. Ahasuerus 13:19, 12 July 2022 (EDT)

3. That the rejected submission page had the "View the submission as raw XML" link like the approved submission page does. Very minor, but since I assume it is also very easy I will toss it on the list.

   Re: #3, don't we already have this functionality in place? I am looking at this rejected submission and I see "View the submission as raw XML" above the "Submitted by" line. Ahasuerus 12:28, 9 July 2022 (EDT)

   Ah, it's the difference between the public view and the moderator view. See [8]. Not a biggie, but maybe add a link to get from the moderator view to the public view on approved & rejected submission pages? The unprocessed ones have a "Public View" button on the same line as the approve / reject buttons. Having a way back to the public page also from the approved & rejected moderator views would be useful when wanting to leave a follow-up message on the submitter's talk page with a link to the submission. -- JLaTondre (talk) 14:40, 9 July 2022 (EDT)

   Sounds reasonable. FR 1513, "Link 'moderator view' pages for processed submissions to public view pages", has been created. Ahasuerus 17:23, 9 July 2022 (EDT)

   FR 1513 has been implemented -- see the Moderator noticeboard for details. Ahasuerus 17:30, 11 July 2022 (EDT)

Thanks. -- JLaTondre (talk) 10:31, 9 July 2022 (EDT)

Thank you for making the two changes. Appreciated. -- JLaTondre (talk) 08:51, 13 July 2022 (EDT)

Sure thing. The last requested change will have to wait until I finish the rewrite of the way submissions are displayed. I am currently working on it in order to address Bug 673, "HTML tags in titles", so the timing is fortunate. Ahasuerus 08:59, 13 July 2022 (EDT)

Color-coding of self-approvers' submissions has been implemented -- see Moderator Noticeboard. Still working on rewriting the submission review pages. Ahasuerus 12:57, 22 July 2022 (EDT)

Cleanup report showing Python error/stack trace

http://www.isfdb.org/cgi-bin/edit/cleanup_report.cgi?288 reports "<type 'exceptions.NameError'>: global name 'SQLVersion' is not defined"

A very quick check of the most up-to-date code checkout I have from February doesn't have the offending line - I'm guessing it's a Python 2.7 or similar change? ErsatzCulture 13:34, 9 July 2022 (EDT)

It was a copy-and-paste error introduced while working on making the software support MySQL 8.0, now fixed. Thanks for reporting the problem! Ahasuerus 13:44, 9 July 2022 (EDT)

Peter McLean's Priest of Crowns - Fixer submission doesn't match current Amazon.com data

Hi, I see you've had the dubious honour of doing Fixer approvals the past week or so ;-) ErsatzCulture 16:58, 9 July 2022 (EDT)

Yes, indeed. Annie is currently on vacation. Ahasuerus 18:13, 9 July 2022 (EDT)

I've just been syncing up today's database backup with my local tools, and I was a bit surprised that this UK pub had already been added, albeit only a couple of days ago.

That in itself is no issue, but it seems there are differences between what Fixer submitted (apparently based on data from Amazon July 6th) versus [https://www.amazon.com/exec/obidos/ASIN/1529411343/isfdb-21 what Amazon.com is showing right now, notably the pub date:

• Fixer submitted 2022-07-19
• Amazon.com says right now 2022-11-08 (as does B&N)
• The UK publisher site (and all the UK retailer sites I've scraped) says 2022-08-04 (and has done since early February when I first grabbed any data for that title's pubs). (NB: these are the same pubs/ISBNs; the Jo Fletcher Books imprint seems to be licencing for both US and UK markets for many of their titles.)

Perhaps this is simply the product data being updated at an unfortunate time, but I'm just mentioning it in case there's something weirder afoot. Are you able to trigger Fixer to re-grab the data for this pub from Amazon's API, to see if it now matches what is on the public Amazon.com site, or if it serves you the wrong data? I know Amazon UK acquired a bug about a year ago on the customer wish-lists, where sorting based on price criteria seemed to use prices that might have been several days out of date.

NB: I'll update the data for this pub to what I believe is correct some time in the next few days, but I'll leave it as-is for now to make it easier for you to see what Fixer submitted. ErsatzCulture 16:58, 9 July 2022 (EDT)

Checking Fixer's database, I see that Fixer last queried the Amazon API for this ISBN on 2022-07-06, right before creating the submission. At that time the API returned "2022-07-19" as the expected publication date. Re-querying the Amazon API, I receive "2022-11-08", so it looks like Amazon.com's expected date has changed in the last 72 hours.

Re: Amazon UK, it's not uncommon for cancellation/delay notifications -- and especially transoceanic notifications -- to be lost in the shuffle. Moreover, experience suggests that a publication that has been delayed one time has much higher than average chances of being delayed again.

Given the above, I don't think there is a whole lot that we can do except add "WatchPrePub" warnings to Notes whenever we encounter something strange. When I come across really shoddy pre-publication records I tend to cancel the submission, "unsubmit" it in Fixer's internal database and change Fixer's "expected publication date" value to a month after the supposed publication date. That way Fixer will try to resubmit when the ISBN is already available for purchase -- or so we hope. Ahasuerus 18:13, 9 July 2022 (EDT)

Thanks for taking the time to look into this one. One of my long wanted to-do's is to add functionality to my tools for pubs that are in the database, to report on any inconsistencies compared to the data I've scraped. Unfortunately those tools are a big heap of spaghetti code, built on a bunch of incorrect assumptions about how I thought at the time how the ISFDB database worked, and naivity about how badly vendors and publishers can mangle the data on their sites, so I really need to do a major rewrite before embarking on anything more than the relatively simple task of writing scrapers for new sites. One day... ErsatzCulture 08:18, 10 July 2022 (EDT)

Sounds painfully familiar :-\ Ahasuerus 10:03, 10 July 2022 (EDT)

Invalid price check - decimal halfpenny

Just looking through the cleanup reports for any mess I might have created, and in the invalid price check report, I see there are a couple of false positives for the pair of issues of the Sfinx fanzine from the early seventies. These both have prices of "£0.075", which matches the cover images showing a price of "7 1/2p". Post decimalization, there was a halfpenny, but 1970s inflation did it in. In theory it might be worth extending the logic/regex for that cleanup report to cover these prices, but I suspect there won't be any other pubs entered with halfpenny prices, so perhaps it's just easier for a mod to mark those cleanup errors as to be ignored? ErsatzCulture 08:44, 10 July 2022 (EDT)

Thanks for the reminder! I came across these types of exceptions early on, but decided to wait for the cleanup report to be whittled down to a manageable subset of exceptions before deciding whether to add the ability to "ignore" records. And then I forgot about it...

Let me see if the remaining exceptions can be accounted for programmatically. Ahasuerus 10:24, 10 July 2022 (EDT)

You may remember this conversation, but I will call you attention to it to be on the safe side as $0.125 is also valid. -- JLaTondre (talk) 12:13, 10 July 2022 (EDT)

Yes, indeed! I have updated the software to skip "$.0__5" and "£0.__5" prices.

Of the remaining 5 records, "£1 4s" and "£5 5/-" presumably need to be converted to "24/-" and "105/-" respectively as per Template:PublicationFields:Price. On the other hand, prices like "-/4 1/2" are presumably legal and need to be skipped by the cleanup report. I'll see what I can do. Ahasuerus 13:11, 10 July 2022 (EDT)

Edit XML confusion

I'm slightly wary of mentioning this, given my confusion over the edit bug yesterday, but I've just had a notification about a change to a pub I PV that I'm a bit perplexed by.

As far as I can tell, the only material difference in #5362000 over what I originally submitted is adding the cover credit, but the XML view seems to indicate (nearly?) every field has changed. (NB There was an edit between those to fix a page number, and that does show as I'd expect).

So, the actual data in the database seems to be fine, but the XML view seems to be misleading about what actually got changed. Any ideas? I wonder if it's some sort of ASCII vs Unicode thing that isn't visible when the edit is rendered in a browser? (Perhaps it might be helpful to be able to download the XML as a file, so that you can run tools like diff or od/hexdump on?

Hopefully this is just something simple/obvious that I'm being clueless about... ErsatzCulture 10:48, 14 July 2022 (EDT)

UPDATE: I just looked at a different edit by a different editor, and I'm wondering if this is merely a weirdness of ImportExport including a bunch of fields in the XML that aren't actually relevant to the edit? If so, don't waste any time on looking into this. 10:56, 14 July 2022 (EDT)

it does seem to be the issue here. Unfortunately, ImportExport was originally coded to piggy-back on "NewPub" submissions, which is why it shares a significant amount of code and data structures with the latter -- note the "NewPub" tag in the raw XML view of 5362000. It causes all kinds of headaches as the same code needs to handle two very different types of submissions. I would have separated them a long time ago if not for the fact that we would still need to be able to display pre-change submissions. I am hoping that the current rewrite of the submission display logic will make it easier to get rid of some of this ugliness... Ahasuerus 11:58, 14 July 2022 (EDT)

Tom Watson

Thanks for catching and fixing the errors I created on this author's record. In my defence, the "other" Watson isn't an implausible person to have written an SF novel: "He was, by his own account, a nerdy geek with long hair, devouring Robert A Heinlein’s science fiction..." ;-) ErsatzCulture 09:35, 18 July 2022 (EDT)

The credit goes to John Clute who discovered that they are two different people while working on the new SFE article :-) Ahasuerus 11:14, 18 July 2022 (EDT)

Sunset Warrior

http://www.isfdb.org/cgi-bin/pl.cgi?244493; I replaced the unstable Amazon image with Bookscans.com image. --Username 09:13, 20 July 2022 (EDT)

Approved, thanks. Ahasuerus 09:17, 20 July 2022 (EDT)

Masters of Space

http://www.isfdb.org/cgi-bin/pl.cgi?273905; I replaced unstable Amazon cover with Bookscans.com's cover; the LCCN on the OL page gets nothing (and OL says Jove even though the Archive copy is Orbit) and neither does searching LCCN site for this title. Maybe your PV copy has a LCCN on the copyright page. --Username 10:56, 20 July 2022 (EDT)

I have approved the cover change. I have also checked the copyright page of my copy and added the LCCN number and other details. Thanks for the heads-up. Ahasuerus 12:14, 20 July 2022 (EDT)

So the LCCN listed on OL is correct but it's not on the LCCN site? That's odd; I wonder why that is. --Username 12:35, 20 July 2022 (EDT)

It's been a long time since I dealt with the Library of Congress, but back in the day they treated mass market paperbacks as "red-headed stepchildren". They stored them in boxes (crates?) at a remote facility and there was no easy way to access them. If memory serves, their explanation was that they needed to rebind all received books and there was no cost-effective way of rebinding mass market paperbacks. Perhaps it also meant that they didn't catalog them as thoroughly as they cataloged other books. Ahasuerus 13:12, 20 July 2022 (EDT)

Also, a minor point I see in a lot of records here, copyright symbol, ©, was entered as @ symbol. --Username 12:35, 20 July 2022 (EDT)

I suspect that it goes back to the typewriter era. Back then many typewriters didn't have the copyright symbol and "@" was used instead. That's how I got into the habit of using it. Ahasuerus 13:12, 20 July 2022 (EDT)

Possible Faulty Logic

There might be faulty logic in the Duplicate SHORTFICTION in Magazines/Fanzines cleanup report. It is reporting a publication that has two titles with the same name 'Summer Break' but by different authors. The duplicate finder on the publication level correctly reports no duplicates. John Scifibones 16:55, 21 July 2022 (EDT)

This report is basically trying to find (among other things) an interior art being coded as a story by mistake (it will look exactly like that - same title, different authors). In case when the story is a legitimate story with the same title as another one in the issue (as is here), we ignore (that's why this report have ignore). :) Annie 17:12, 21 July 2022 (EDT)

Makes sense, John Scifibones 17:22, 21 July 2022 (EDT)

Reddit admin blockage discussion

FYI in case you hadn't seen it... —The preceding unsigned comment was added by ErsatzCulture (talk • contribs) .

Thanks for letting me know. I first ran into this problem a couple of years ago and was unable to have our domain removed from the spam list. Hopefully this iteration will be more successful. Ahasuerus 14:31, 25 July 2022 (EDT)

Submission Warnings for Awards?

Please see this submission. In adding the additional contents, the submitter edited the two existing records to be different content. I have seen this happen before with users who think the content must be listed in order of appearance on the edit screen (i.e. are not aware of how sorting works). Generally not an issue, but in this case, the two existing records have associated awards. If this edit is accepted, the awards would now be associated to the wrong records. Is editing a record with an award something that should be flagged in the pub submission screen? Maybe it doesn't happen enough to worry about... I'm going to reject this submission and redo it. -- JLaTondre (talk) 09:37, 26 July 2022 (EDT)

Wouldn't that also mess up any reviews associated with the changed title records? Ahasuerus 11:16, 26 July 2022 (EDT)

Yup, good point. It would also impact variants/parents. -- JLaTondre (talk) 11:30, 26 July 2022 (EDT)

It would also mess up any series data, associated Web pages, transliterated titles, etc. That's not good. So I guess the question is "How do we distinguish between (a) changing something in the same title record, e.g. fixing a typo, and (b) changing the record to be something else entirely." I guess changing the title type would be one indication. Changing both the author name and the title would be another. Ahasuerus 12:17, 26 July 2022 (EDT)

We probably need a warning/note at the top of the contents section that the order on the Edit screen can be changed via the pages field (or something along these lines) -- that may help with the "I need to order these properly" editors. It crops up often enough and not always with new editors. Or we can rename the page fields in there to say page/order. Or both maybe? Annie 13:40, 26 July 2022 (EDT)

A warning should be easy enough to add. I'll postpone the addition of any new yellow warnings until after the current rewrite is finished. Ahasuerus 18:31, 26 July 2022 (EDT)

A warning has been added. Ahasuerus 18:26, 28 August 2022 (EDT)

Art of NASA

Hello. Thank you for your extensive commentary on this publication. In the original message on my talkpage (back in November 2020, just in case you missed it) I stated the following "It's a book of mostly conceptual illustrations giving a general idea of what things might look like in terns of various NASA missions from the earliest days and potential future missions such as habitat structures on other planets (Moon, Mars), Bernal and O'Neill and other tube-like or ring-like structures. These later images are almost certainly "fictional" in that regards. Whether they illustrate fiction or are used for fictional covers I know not." This may or may not be helpful although I have to say that art portfolios - particularly of this nature are elastic in regards to holding to a hard and fast rule. Although I don't know of many such art books of a similar nature. That being said I'd like your view on this publication, which I purchased via the Kickstarter project and will (hopefully) arrive at some point in the next month (possibly, it's stuck in America at the moment awaiting distribution). Thanks. --Mavmaramis 16:01, 27 July 2022 (EDT)

In this case, at least some illustrations are presumably related to speculative fiction, e.g. the 3 2001: A Space Odyssey titles by Robert McCall, so I suspect that the whole book may be eligible even if we use a more restrictive interpretation of the rules. That being said, my primary interest is in having the rules clarified and made unambiguous so that we would all be using the same standards for inclusion. Ahasuerus 18:23, 27 July 2022 (EDT)

There may well not be too many publications of a similar nature but you never know. I did forget to include a link to the other book I mentioned - Megastructures. Your views on whether it would qualify for inclusion or not would be welcome. --Mavmaramis 00:30, 28 July 2022 (EDT)

Unlike Art of NASA, I don't see any SF-related artwork in Megastructures, although some titles like "Ringworld" are ambiguous. That said, I am not the best person to ask since my knowledge of SF art is limited. Perhaps a more knowledgeable editor may be able to identify some paintings. Ahasuerus 09:56, 28 July 2022 (EDT)

Francis Cheynell author record

I have a very dumb shell script running right now to very slowly churn through the SFE links on the cleanup report, d/l the page, and then look to see if it has a link to ISFDB (and thus needs the SFE link adding here). One mysterious one is Francis Cheynell, which links to a non-existent ISFDB page. (FWIW, the SFE page has a May 2021 update date, but I imagine that doesn't necessarily mean the page here existed at that time.)

Do you have any (easy) way of checking what might have happened to that author record? (I can dig out and restore an older backup file myself, if that's all you have access to.) The sole title listed on the SFE page looks like it might be a debatable inclusion here, although from the brief description, it seems like it would probably get the benefit of the doubt? ErsatzCulture 13:29, 30 July 2022 (EDT)

Publicly available backups wouldn't help much because they don't include the submission table, which is how record histories are recreated. Here is what a scan of the submission table gives me:

• Publication Update
• Second Publication Update adding this work
• Title Remove
• Author Update
• Author Update
• Title Update
• Title Delete

The title deletion submission was created and approved by Hauck, who unilaterally deleted a number of titles which he believed should not have been in the database. It was the reason why his moderator privileges were revoked, at which point he left the project. We should be able to recreate the data based on the listed submissions. Ahasuerus 14:36, 30 July 2022 (EDT)

Francis Cheynell has been re-added and SFE has been notified about the changed link. Thanks for identifying the problem! Ahasuerus 13:22, 1 August 2022 (EDT)

This, http://www.isfdb.org/cgi-bin/pl.cgi?908711, has a note that seems to end prematurely. --Username 15:21, 1 August 2022 (EDT)

Updated, thanks. Ahasuerus 15:47, 1 August 2022 (EDT)

Also, I added the actual 1644 work from an online link at https://quod.lib.umich.edu, but it doesn't seem to work unless you use the cached text version, which I did. --Username 15:21, 1 August 2022 (EDT)

Google makes its cached pages available for a few weeks -- sometimes months -- but then they expire, which makes them unworkable for our purposes. However, I can see the original page, https://quod.lib.umich.edu/e/eebo2/B08742.0001.001?rgn=main;view=fulltext , using Firefox. Can you access it with your browser? Ahasuerus 15:47, 1 August 2022 (EDT)

Yes, I see that page, with some graphics at the top; maybe that's what wasn't loading properly. I'll cancel my text link and let you add yours since you did the previous edits. --Username 15:51, 1 August 2022 (EDT)

Added, thanks. Ahasuerus 16:09, 1 August 2022 (EDT)

Orphaned Elder Race chapbook record

Hi, just going through the cleanup reports, and saw Elder Race mentioned in the uncommon award types report.

I think what's happened here is:

• I incorrectly added an award nom to the chapbook rather than the novella a few weeks ago
• You then did the novella->novel conversion
• The chapbook record is still around, I dunno if that's due to the award nom, or if they always need manually removing after a novella->novel conversion?

I'll fix (re-link) the award nom (and delete the unwanted chapbook if it doesn't disappear authomatically) later, but I've left it in place just in case there's anything worth investigating? ErsatzCulture 10:26, 6 August 2022 (EDT)

CHAPBOOKs titles behave like other title types, at least in this respect. When they are dissociated from their last publication, they do not automatically disappear. They hang around and pop up on one of the cleanup reports.

In this case I believe I forgot to delete the CHAPBOOK title after converting the SHORTFICTION/novella title to a NOVEL. If I had tried to delete it, I would have received an error because of the linked award, at which point I would have realized that the award had been linked to the wrong title. Please feel free to go ahead and delete the CHAPBOOK title after linking the award to the NOVEL record. Thanks! Ahasuerus 12:58, 6 August 2022 (EDT)

Thanks - should be all cleaned up now. —The preceding unsigned comment was added by ErsatzCulture (talk • contribs) .

Republic of Hawaii

Please see Authors with Invalid Birthplaces: Is the issue that the report doesn't recognize the Republic of Hawaii? Otherwise I'm not sure what is wrong. Thanks. -- JLaTondre (talk) 09:27, 7 August 2022 (EDT)

That's right. At this time the report recognizes "Hawaii, USA" and "Kingdom of Hawaii", but not "Republic of Hawaii". FR 1524 has been created, but the fix will have to wait until I finish the big patch that I am currently working on. Thanks for reporting the problem. Ahasuerus 11:02, 7 August 2022 (EDT)

It turns out that the software changes required to implement this FR didn't create a conflict with the ongoing submission review changes. All done now. Ahasuerus 13:26, 7 August 2022 (EDT)

Library of contemporary science fiction in 15 volumes

Can you please see this series? It is currently empty so showing up on the clean-up reports to be deleted. But looks like the information should belong somewhere. Sounds like this should have been a pub series based on the description? I tried looking for one and for the contents from the FantLab page (using Google Translate) with no luck. As based on the edit history it looks like you entered the data, I was wondering if you wanted to look into this before it was deleted? -- JLaTondre (talk) 12:53, 7 August 2022 (EDT)

We had some books entered as a title series and some as a publication series. I consolidated the data a few days ago, but forgot to delete the empty title series. It's gone now. Thanks for the reminder! Ahasuerus 13:21, 7 August 2022 (EDT)

New cleanup report and/or yellow warning: NewPubs with translator info in pub note rather than title note?

Hi, any chance we could have something to catch stuff like this? I know there are plenty of cleanup reports that report on missing translators, but it strikes me that cases like this should be flagged up separately, given that the info isn't missing, just in the wrong place, and so it's easier to fix than a translation with an unknown translator, which likely requires an editor to go off and do some external research.

I stumbled across this one in part because there's a different Portuguese version of this title that I almost merged, until I realized that they have different translators - presumably for different Portuguese language markets - so should be separate variants of the English original, but this was harder to spot because the translator note was buried a level deeper at the pub rather than title level. I'll fix the records over the weekend - assuming no-one else beats me to it - but I'll leave them as-is for the moment so you can see to what I'm referring.

(Also makes me wonder if there might be cases where there's inconsistent translator info at title vs pub level - might have a look at that over the weekend...) Thanks ErsatzCulture 18:44, 19 August 2022 (EDT)

One caution, I have frequently put translator information in at the publication level as a confirmation that it is placed under the correct title. So please don't delete them as 'extraneous'. ../Doug H 22:08, 19 August 2022 (EDT)

Yep - I hope “fix” means copy and not move here. Having it in both places can be useful so if someone had added it in the publication notes, please don’t remove it. A report that flags that there is a Tr template in the publication but not one in the title note may be useful but technically, it will become superfluous one day when all translators are finally updated into the titles (I know I know). As for how these were left that way - a moderator should have worked with the editor- new editors mix the notes. But that’s another problem for another day. Annie 22:38, 19 August 2022 (EDT)

Good points, folks. FR 1525, "Find titles w/out the Tr template whose pubs have this template" has been created. It's a fairly straightforward SQL query, so it can be implemented easily. Ahasuerus 09:09, 20 August 2022 (EDT)

Re. moving/deleting translator info in the pub - sorry for any confusion, I did indeed only mean adding that info to the title note. That said, I do wonder if seeing translator info in pub notes may give the impression that that is the preferred location for it; I'll have a look through the relevant help pages shortly, and check that the wording indicates that title note=mandatory, pub note=optional.

I also sort out those Portuguese titles in a second. ErsatzCulture 09:24, 20 August 2022 (EDT)

We will need an ignore on that report (for multi-lingual works and for introductions and similar titles which are not translations in some cases for example). And I suspect you already plan to but we should exclude the 2 art types (Just thinking aloud). Annie 13:32, 20 August 2022 (EDT)

That shouldn't be a problem because the current FR is limited to "title type = publication type" cases. Expanding it to all title/pub type combinations would be tricky because the report would take minutes to run and lock all title/pub records for the duration. There are ways around it, but they would be more time-consuming to implement. Ahasuerus 13:55, 20 August 2022 (EDT)

That works as well. :) Annie 18:54, 20 August 2022 (EDT)

SFE link cleanup report possibly not updating?

I noticed a few weeks ago that SFE had their page for Donna Barba Higuera with a mis-spelled middle name. I reported it to them, and they mentioned it would (as I expected) change their URL, and I said I'd update the link here, either if I remembered and/or when I saw it in the cleanup report.

Well, I didn't remember to change it until today, but I notice it's not listed in the cleanup report either. It is updated on their author list, so I'm just mentioning this in case that report isn't getting updated. IIRC it should have run a couple of days ago, and I'm sure the SFE page/list is more likely to have been updated before then, rather than in the couple of days since that report ran.

I'll update the SFE link for that author later today. ErsatzCulture 07:01, 23 August 2022 (EDT)

The SFE report has been unable to run since SFE's migration to a new server (and HTTPS) in October 2021. It's an OpenSSL issue and will be automatically resolved when we upgrade our server to a more modern LAMP stack. Ahasuerus 07:08, 23 August 2022 (EDT)

Thanks. So am I right in thinking that any SFE pages it knew about before the OpenSSL issue will disappear from the report if the links are added here, but any new SFE pages won't show up in the report until that issue is fixed? ErsatzCulture 09:09, 23 August 2022 (EDT)

That's right. Only the download part of the nightly process is broken. Newly added links to SFE will result in the removal of matching author names from the report. Ahasuerus 12:01, 23 August 2022 (EDT)

I had been trying to keep up with the new additions (SFE tweets the a list weekly), but I'd been a bit slack recently, thinking that the report would catch any I've missed. If that isn't the case, then I'll try to get back to monitoring and fixing them as-and-when they get added over there. ErsatzCulture 09:09, 23 August 2022 (EDT)

Odd display error on all publications

Hi Ahasuerus. I found this when looking at a bad sum check and its on all the publications for this title[9].Kraang 15:49, 31 August 2022 (EDT)

Plus this submission[10]Kraang 16:05, 31 August 2022 (EDT)

It was a bug introduced in an earlier patch to support the server upgrade project. Fixed now -- thanks for letting me know! Ahasuerus 16:44, 31 August 2022 (EDT)

old edits

Is there any way I can access old editions beyond 3 months? I'm also an editor at Wikimedia Commons, I gave credit for a cover but I can't find the author, it was outer space art, I wanted to remember the artist's name for edits on Commons, I'm not sure he worked for NASA.Hyju 17:32, 2 September 2022 (EDT)

There is a "Submission Search" menu option which can be run by moderators. It creates a list of all submissions for a given user. If you know the title of the publication, it should be easy to find the submission. Ahasuerus 20:25, 2 September 2022 (EDT)

Thanks, I already found it, it was an art by Les Bossinas, this is the category on Commons: Artists who have produced work for NASA.Hyju 07:54, 4 September 2022 (EDT)

Excellent! :-) Ahasuerus 08:32, 4 September 2022 (EDT)

How about a way to find my older submissions (short of paging through all of the recent edits by everone)? I am not a moderator. I used to be able to get to these by paging back through "My Recent Edits" but now this is curtailed to the "Last 3 Months" only. Thanks. —Uzume (talk) 02:01, 7 September 2022 (EDT)

The change was made for performance reasons. For users with relatively few edits, the software had to scan the whole submission table, which contains millions of records. We'll need to add a new index before we can re-enable the functionality. Ahasuerus (talk) 08:06, 7 September 2022 (EDT)

I fail to see how having the server filter submission records by my user is less performant than my paging through all the committed submissions and searching the pages for my user in my browser (now all the records have to be transmitted across the network!). —Uzume (talk) 13:44, 12 September 2022 (EDT)

Sending record lists across the network is inexpensive; the performance issue is almost entirely on the database side. Are you trying to page through all submissions in https://www.isfdb.org/cgi-bin/recent.cgi ? That's rather expensive once you get past the first couple of dozen pages.

As in Hyju's case, if you know what kinds of records you are looking for, you could post a request on the Moderator Noticeboard to run "Submission Search" on your user name. Here are your submissions between 2020-02 and 3 months ago:

5292525 	TitleUpdate 	2022-04-12 23:51:07 	Uzume 	2022-04-13 09:08:56 	Rudam 	Llana di Gathol
5292316 	TitleUpdate 	2022-04-12 17:11:38 	Uzume 	2022-04-12 22:42:31 	Kraang 	Under the Moons of Mars and Carter of th
5292315 	TitleUpdate 	2022-04-12 17:11:14 	Uzume 	2022-04-12 22:42:27 	Kraang 	Carter of the Red Planet
5292314 	TitleUpdate 	2022-04-12 17:10:53 	Uzume 	2022-04-12 22:42:24 	Kraang 	Under the Moons of Mars
5292313 	PublisherUpdate 	2022-04-12 17:03:19 	Uzume 	2022-04-12 22:42:20 	Kraang 	Castle / Book Sales
5292312 	PublisherUpdate 	2022-04-12 17:03:05 	Uzume 	2022-04-12 22:42:16 	Kraang 	Castle Books
5292310 	TitleUpdate 	2022-04-12 16:56:08 	Uzume 	2022-04-12 22:42:06 	Kraang 	Le pedine di Marte
5292309 	TitleUpdate 	2022-04-12 16:55:45 	Uzume 	2022-04-12 22:41:46 	Kraang 	Jetan, or Martian Chess
5292308 	TitleUpdate 	2022-04-12 16:54:25 	Uzume 	2022-04-12 22:41:41 	Kraang 	La mente di Marte
5292307 	TitleUpdate 	2022-04-12 16:52:32 	Uzume 	2022-04-12 22:41:37 	Kraang 	I guerrieri di Marte
5292303 	TitleUpdate 	2022-04-12 16:43:28 	Uzume 	2022-04-12 22:41:33 	Kraang 	Tarzan of the Apes and The Prisoner of Z
5292273 	TitleUpdate 	2022-04-12 15:38:43 	Uzume 	2022-04-12 22:41:29 	Kraang 	Edgar Rice Burroughs: Thrillogy
5292266 	TitleUpdate 	2022-04-12 15:37:05 	Uzume 	2022-04-12 22:41:22 	Kraang 	The Hollow Earth
5292264 	TitleUpdate 	2022-04-12 15:34:16 	Uzume 	2022-04-12 22:41:16 	Kraang 	Tarzan of the Apes & Other Tales: Centen
5292260 	PubUpdate 	2022-04-12 15:29:33 	Uzume 	2022-04-12 22:41:11 	Kraang 	Carson of Venus: Pirates of Venus / Lost
5292252 	TitleUpdate 	2022-04-12 15:17:58 	Uzume 	2022-04-12 22:41:04 	Kraang 	Carson of Venus: Pirates of Venus / Lost
5292248 	TitleUpdate 	2022-04-12 15:15:39 	Uzume 	2022-04-12 22:40:57 	Kraang 	The Tarzan Duology of Edgar Rice Burroug
5292244 	TitleUpdate 	2022-04-12 15:12:43 	Uzume 	2022-04-12 22:37:14 	Kraang 	Out of This World Adventures
5292141 	MakeVariant 	2022-04-12 12:43:01 	Uzume 	2022-04-12 22:31:52 	Kraang 	Il morbo antico
5292133 	MakeVariant 	2022-04-12 12:34:20 	Uzume 	2022-04-12 22:30:42 	Kraang 	Tarzan na Selva
5292299 	TitleUpdate 	2022-04-12 16:29:01 	Uzume 	2022-04-12 22:29:03 	Kraang 	Tarzan Revisited
5290488 	PubUpdate 	2022-04-11 00:58:19 	Uzume 	2022-04-12 09:45:40 	Rtrace 	密林の謎の
5290487 	TitleUpdate 	2022-04-11 00:57:36 	Uzume 	2022-04-12 09:45:35 	Rtrace 	密林の謎の
5290486 	MakeVariant 	2022-04-11 00:57:07 	Uzume 	2022-04-12 09:45:32 	Rtrace 	密林の謎の
5290485 	PubUpdate 	2022-04-11 00:55:41 	Uzume 	2022-04-12 09:45:28 	Rtrace 	石器時代へ
5290483 	TitleUpdate 	2022-04-11 00:54:20 	Uzume 	2022-04-12 09:45:24 	Rtrace 	石器時代へ
5290482 	MakeVariant 	2022-04-11 00:53:40 	Uzume 	2022-04-12 09:45:20 	Rtrace 	石器時代へ
5290481 	PubUpdate 	2022-04-11 00:51:55 	Uzume 	2022-04-12 09:45:17 	Rtrace 	石器時代か
5290479 	TitleUpdate 	2022-04-11 00:50:48 	Uzume 	2022-04-12 09:45:12 	Rtrace 	石器時代か
5290478 	MakeVariant 	2022-04-11 00:49:37 	Uzume 	2022-04-12 09:45:09 	Rtrace 	石器時代か
5290477 	PubUpdate 	2022-04-11 00:47:30 	Uzume 	2022-04-12 09:45:05 	Rtrace 	モンスター
5290476 	TitleUpdate 	2022-04-11 00:46:24 	Uzume 	2022-04-12 09:45:00 	Rtrace 	モンスター
5290475 	MakeVariant 	2022-04-11 00:45:44 	Uzume 	2022-04-12 09:44:55 	Rtrace 	モンスター
5290474 	PubUpdate 	2022-04-11 00:41:49 	Uzume 	2022-04-12 09:44:50 	Rtrace 	ウォー・チ
5290473 	TitleUpdate 	2022-04-11 00:40:51 	Uzume 	2022-04-12 09:44:46 	Rtrace 	ウォー・チ
5290472 	MakeVariant 	2022-04-11 00:40:00 	Uzume 	2022-04-12 09:44:41 	Rtrace 	ウォー・チ
5290470 	PubUpdate 	2022-04-11 00:37:14 	Uzume 	2022-04-12 09:44:37 	Rtrace 	アパッチ・
5290468 	TitleUpdate 	2022-04-11 00:35:38 	Uzume 	2022-04-12 09:44:32 	Rtrace 	アパッチ・
5290466 	MakeVariant 	2022-04-11 00:35:00 	Uzume 	2022-04-12 09:44:27 	Rtrace 	アパッチ・
5290465 	PubUpdate 	2022-04-11 00:33:17 	Uzume 	2022-04-12 09:44:23 	Rtrace 	南海の秘境
5290464 	TitleUpdate 	2022-04-11 00:32:11 	Uzume 	2022-04-12 09:44:17 	Rtrace 	南海の秘境
5290463 	MakeVariant 	2022-04-11 00:31:26 	Uzume 	2022-04-12 09:44:12 	Rtrace 	南海の秘境
5290461 	PubUpdate 	2022-04-11 00:29:30 	Uzume 	2022-04-12 09:44:05 	Rtrace 	風雲のメキ
5290459 	TitleUpdate 	2022-04-11 00:27:14 	Uzume 	2022-04-12 09:43:50 	Rtrace 	風雲のメキ
5290456 	MakeVariant 	2022-04-11 00:25:18 	Uzume 	2022-04-12 09:43:40 	Rtrace 	風雲のメキ
5290454 	AuthorUpdate 	2022-04-11 00:24:17 	Uzume 	2022-04-12 09:43:36 	Rtrace 	E.R.バローズ
5290453 	Make Alternate Name 	2022-04-11 00:22:57 	Uzume 	2022-04-12 09:43:30 	Rtrace 	E.R.バローズ
5290449 	PubUpdate 	2022-04-11 00:19:56 	Uzume 	2022-04-12 09:43:17 	Rtrace 	砂漠のプリ
5290447 	TitleUpdate 	2022-04-11 00:18:02 	Uzume 	2022-04-12 09:43:10 	Rtrace 	砂漠のプリ
5290446 	MakeVariant 	2022-04-11 00:17:19 	Uzume 	2022-04-12 09:43:06 	Rtrace 	砂漠のプリ
5290442 	PubUpdate 	2022-04-11 00:13:52 	Uzume 	2022-04-12 09:42:43 	Rtrace 	カリグラ帝
5290441 	TitleUpdate 	2022-04-11 00:12:16 	Uzume 	2022-04-12 09:42:35 	Rtrace 	カリグラ帝
5290439 	MakeVariant 	2022-04-11 00:11:22 	Uzume 	2022-04-12 09:42:24 	Rtrace 	カリグラ帝
5290435 	TitleUpdate 	2022-04-11 00:04:14 	Uzume 	2022-04-12 09:42:05 	Rtrace 	ルータ王国
5290432 	MakeVariant 	2022-04-10 23:58:50 	Uzume 	2022-04-12 09:41:50 	Rtrace 	ルータ王国
5289919 	PubUpdate 	2022-04-10 16:30:28 	Uzume 	2022-04-10 23:10:47 	Kraang 	スピリット
5289913 	PubUpdate 	2022-04-10 16:22:57 	Uzume 	2022-04-10 23:10:25 	Kraang 	氷海のクジ
5289908 	PubUpdate 	2022-04-10 16:16:54 	Uzume 	2022-04-10 23:10:11 	Kraang 	名誉のかけ
5289905 	PubUpdate 	2022-04-10 16:09:42 	Uzume 	2022-04-10 23:09:56 	Kraang 	戦士志願
5289865 	PubUpdate 	2022-04-10 15:36:43 	Uzume 	2022-04-10 23:09:24 	Kraang 	自由軌道
5289384 	NewPub 	2022-04-10 03:03:24 	Uzume 	2022-04-10 22:58:15 	Kraang 	密林の謎の
5289381 	NewPub 	2022-04-10 02:53:34 	Uzume 	2022-04-10 22:58:09 	Kraang 	石器時代へ
5289370 	NewPub 	2022-04-10 02:38:28 	Uzume 	2022-04-10 22:57:46 	Kraang 	石器時代か
5289353 	NewPub 	2022-04-10 02:28:57 	Uzume 	2022-04-10 22:57:18 	Kraang 	モンスター
5288704 	TitleUpdate 	2022-04-09 11:27:55 	Uzume 	2022-04-10 22:38:47 	Kraang 	unknown
5288455 	NewPub 	2022-04-09 03:29:46 	Uzume 	2022-04-10 22:38:33 	Kraang 	ウォー・チ
5288454 	NewPub 	2022-04-09 03:29:42 	Uzume 	2022-04-10 22:38:20 	Kraang 	アパッチ・
5288453 	NewPub 	2022-04-09 03:11:20 	Uzume 	2022-04-10 22:38:15 	Kraang 	南海の秘境
5288452 	NewPub 	2022-04-09 03:11:16 	Uzume 	2022-04-10 22:38:05 	Kraang 	風雲のメキ
5288429 	NewPub 	2022-04-09 01:58:18 	Uzume 	2022-04-10 22:37:41 	Kraang 	砂漠のプリ
5288424 	NewPub 	2022-04-09 01:47:13 	Uzume 	2022-04-10 22:37:18 	Kraang 	カリグラ帝
5288409 	NewPub 	2022-04-09 01:38:19 	Uzume 	2022-04-10 22:37:08 	Kraang 	ルータ王国
5288717 	TitleUpdate 	2022-04-09 11:36:55 	Uzume 	2022-04-10 09:03:55 	JLaTondre 	The Oakdale Affair / The Rider
5288379 	TitleUpdate 	2022-04-09 00:13:36 	Uzume 	2022-04-09 10:51:24 	JLaTondre 	金星の火の
5288378 	TitleUpdate 	2022-04-09 00:12:47 	Uzume 	2022-04-09 10:51:22 	JLaTondre 	金星の独裁
5288377 	TitleUpdate 	2022-04-09 00:12:08 	Uzume 	2022-04-09 10:51:19 	JLaTondre 	金星の死者
5288375 	TitleUpdate 	2022-04-09 00:07:56 	Uzume 	2022-04-09 10:51:03 	JLaTondre 	金星の魔法
5287392 	AuthorUpdate 	2022-04-07 23:14:44 	Uzume 	2022-04-08 23:52:07 	Kraang 	リチャード
5287387 	TitleUpdate 	2022-04-07 23:04:35 	Uzume 	2022-04-08 23:52:02 	Kraang 	月人の地球
5287385 	TitleUpdate 	2022-04-07 23:02:44 	Uzume 	2022-04-08 23:51:57 	Kraang 	月の地底王
5287384 	MakeVariant 	2022-04-07 23:00:07 	Uzume 	2022-04-08 23:51:36 	Kraang 	時間に忘れ
5287382 	MakeVariant 	2022-04-07 22:58:31 	Uzume 	2022-04-08 23:51:33 	Kraang 	金星の魔法
5287381 	MakeVariant 	2022-04-07 22:57:27 	Uzume 	2022-04-08 23:51:20 	Kraang 	unknown
5287380 	Make Alternate Name 	2022-04-07 22:56:53 	Uzume 	2022-04-08 23:51:09 	Kraang 	リチャード
5287690 	TitleMerge 	2022-04-08 09:25:11 	Uzume 	2022-04-08 23:46:27 	Kraang 	The Cave Girl
5286983 	TitleUpdate 	2022-04-07 14:28:31 	Uzume 	2022-04-07 22:39:53 	Kraang 	時に忘れら
5286981 	PubUpdate 	2022-04-07 14:27:53 	Uzume 	2022-04-07 22:39:49 	Kraang 	時に忘れら
5286979 	TitleUpdate 	2022-04-07 14:25:02 	Uzume 	2022-04-07 22:39:45 	Kraang 	時に忘れら
5286977 	PubUpdate 	2022-04-07 14:24:27 	Uzume 	2022-04-07 22:39:42 	Kraang 	時に忘れら
5286970 	TitleUpdate 	2022-04-07 14:18:37 	Uzume 	2022-04-07 22:39:34 	Kraang 	時の深き淵
5286969 	PubUpdate 	2022-04-07 14:17:35 	Uzume 	2022-04-07 22:39:19 	Kraang 	時の深き淵
5286962 	PubUpdate 	2022-04-07 14:12:43 	Uzume 	2022-04-07 22:39:05 	Kraang 	時間に忘れ
5286956 	TitleUpdate 	2022-04-07 14:04:53 	Uzume 	2022-04-07 22:38:47 	Kraang 	時間に忘れ
5286955 	TitleUpdate 	2022-04-07 14:03:38 	Uzume 	2022-04-07 22:38:44 	Kraang 	月のプリン
5286951 	TitleUpdate 	2022-04-07 14:01:33 	Uzume 	2022-04-07 22:38:25 	Kraang 	月からの侵
5286942 	PubUpdate 	2022-04-07 13:57:57 	Uzume 	2022-04-07 22:38:07 	Kraang 	金星の海賊
5286941 	MakeVariant 	2022-04-07 13:56:49 	Uzume 	2022-04-07 22:38:01 	Kraang 	金星の海賊
5286935 	PubUpdate 	2022-04-07 13:55:28 	Uzume 	2022-04-07 22:37:58 	Kraang 	金星の死者
5286925 	MakeVariant 	2022-04-07 13:52:30 	Uzume 	2022-04-07 22:37:54 	Kraang 	金星の死者
5286921 	PubUpdate 	2022-04-07 13:50:56 	Uzume 	2022-04-07 22:37:46 	Kraang 	金星の独裁
5286919 	MakeVariant 	2022-04-07 13:48:11 	Uzume 	2022-04-07 22:37:37 	Kraang 	金星の独裁
5286918 	PubUpdate 	2022-04-07 13:45:57 	Uzume 	2022-04-07 22:37:34 	Kraang 	金星の火の
5286917 	MakeVariant 	2022-04-07 13:44:22 	Uzume 	2022-04-07 22:37:28 	Kraang 	金星の火の
5286912 	TitleUpdate 	2022-04-07 13:36:41 	Uzume 	2022-04-07 22:37:14 	Kraang 	さいはての
5286911 	TitleUpdate 	2022-04-07 13:34:00 	Uzume 	2022-04-07 22:37:08 	Kraang 	五万年前の
5286909 	TitleUpdate 	2022-04-07 13:33:12 	Uzume 	2022-04-07 22:37:04 	Kraang 	金星の魔法
5286907 	PubUpdate 	2022-04-07 13:31:20 	Uzume 	2022-04-07 22:36:55 	Kraang 	金星の魔法
5286904 	MakeVariant 	2022-04-07 13:24:33 	Uzume 	2022-04-07 22:36:08 	Kraang 	さいはての
5286902 	MakeVariant 	2022-04-07 13:23:43 	Uzume 	2022-04-07 22:34:14 	Kraang 	五万年前の
5286900 	MakeVariant 	2022-04-07 13:22:27 	Uzume 	2022-04-07 22:34:10 	Kraang 	金星の魔法
5286187 	MakeVariant 	2022-04-06 23:33:09 	Uzume 	2022-04-07 22:29:46 	Kraang 	時の深き淵
5286183 	TitleUpdate 	2022-04-06 23:31:11 	Uzume 	2022-04-07 22:29:42 	Kraang 	用語の手引
5286180 	MakeVariant 	2022-04-06 23:29:22 	Uzume 	2022-04-07 22:29:37 	Kraang 	時に忘れら
5286152 	MakeVariant 	2022-04-06 23:23:56 	Uzume 	2022-04-07 22:29:01 	Kraang 	時に忘れら
5286135 	TitleUpdate 	2022-04-06 23:19:22 	Uzume 	2022-04-07 22:28:49 	Kraang 	時間に忘れ
5286128 	TitleUpdate 	2022-04-06 23:16:33 	Uzume 	2022-04-07 22:28:37 	Kraang 	ブラッドリ
5286127 	TitleUpdate 	2022-04-06 23:15:46 	Uzume 	2022-04-07 22:28:33 	Kraang 	トーマス・
5286125 	TitleUpdate 	2022-04-06 23:14:49 	Uzume 	2022-04-07 22:28:27 	Kraang 	ボウエン・
5286117 	MakeVariant 	2022-04-06 23:12:41 	Uzume 	2022-04-07 18:05:29 	Kraang 	ブラッドリ
5286114 	MakeVariant 	2022-04-06 23:11:52 	Uzume 	2022-04-07 18:05:01 	Kraang 	トーマス・
5286111 	MakeVariant 	2022-04-06 23:11:11 	Uzume 	2022-04-07 18:04:53 	Kraang 	ボウエン・
5285589 	TitleMerge 	2022-04-06 13:00:42 	Uzume 	2022-04-07 17:57:40 	Kraang 	Tarzan and the City of Gold
5285587 	TitleMerge 	2022-04-06 12:59:11 	Uzume 	2022-04-07 17:57:31 	Kraang 	Tarzan and the Leopard Men
5285584 	TitleMerge 	2022-04-06 12:55:02 	Uzume 	2022-04-07 17:57:20 	Kraang 	Tarzan the Untamed
5285581 	TitleMerge 	2022-04-06 12:53:43 	Uzume 	2022-04-07 17:56:38 	Kraang 	Tarzan's Quest
5285578 	TitleMerge 	2022-04-06 12:50:56 	Uzume 	2022-04-07 17:56:30 	Kraang 	Tarzan, Lord of the Jungle
5285575 	TitleMerge 	2022-04-06 12:49:05 	Uzume 	2022-04-07 17:55:19 	Kraang 	The Beasts of Tarzan
5285573 	TitleMerge 	2022-04-06 12:46:39 	Uzume 	2022-04-07 17:53:54 	Kraang 	The Son of Tarzan
5285564 	MakeVariant 	2022-04-06 12:33:57 	Uzume 	2022-04-07 17:53:42 	Kraang 	Tarzan of the Apes: Four Volumes in One
5285314 	NewPub 	2022-04-06 03:14:08 	Uzume 	2022-04-07 11:48:39 	Kraang 	金星の魔法
5285313 	NewPub 	2022-04-06 03:00:19 	Uzume 	2022-04-07 10:03:57 	Rtrace 	金星の火の
5285312 	NewPub 	2022-04-06 03:00:09 	Uzume 	2022-04-07 10:03:50 	Rtrace 	金星の独裁
5285311 	NewPub 	2022-04-06 03:00:00 	Uzume 	2022-04-07 10:02:26 	Rtrace 	金星の死者
5285310 	NewPub 	2022-04-06 02:56:13 	Uzume 	2022-04-07 10:02:17 	Rtrace 	金星の海賊
5284139 	AuthorUpdate 	2022-04-04 23:35:38 	Uzume 	2022-04-06 22:55:38 	Kraang 	エドガー・
5284132 	NewPub 	2022-04-04 23:26:37 	Uzume 	2022-04-06 22:55:28 	Kraang 	時に忘れら
5284131 	NewPub 	2022-04-04 23:26:35 	Uzume 	2022-04-06 22:55:21 	Kraang 	時に忘れら
5284130 	NewPub 	2022-04-04 23:26:31 	Uzume 	2022-04-06 22:55:07 	Kraang 	時の深き淵
5283987 	PubUpdate 	2022-04-04 21:22:43 	Uzume 	2022-04-06 22:47:45 	Kraang 	月からの侵
5283985 	PubUpdate 	2022-04-04 21:19:54 	Uzume 	2022-04-06 22:47:39 	Kraang 	月のプリン
5283982 	NewPub 	2022-04-04 21:15:52 	Uzume 	2022-04-06 22:47:25 	Kraang 	時間に忘れ
5283737 	TitleUpdate 	2022-04-04 15:56:25 	Uzume 	2022-04-06 10:09:29 	Rtrace 	レッド・ホ
5283736 	TitleUpdate 	2022-04-04 15:55:37 	Uzume 	2022-04-06 10:09:24 	Rtrace 	月からの侵
5283734 	MakeVariant 	2022-04-04 15:53:34 	Uzume 	2022-04-06 10:07:57 	Rtrace 	レッド・ホ
5283733 	MakeVariant 	2022-04-04 15:52:55 	Uzume 	2022-04-06 10:07:47 	Rtrace 	月からの侵
5283732 	MakeVariant 	2022-04-04 15:51:27 	Uzume 	2022-04-06 10:07:42 	Rtrace 	月からの侵
5283731 	MakeVariant 	2022-04-04 15:50:06 	Uzume 	2022-04-06 10:07:30 	Rtrace 	月のプリン
5283723 	Make Alternate Name 	2022-04-04 15:16:22 	Uzume 	2022-04-04 15:20:07 	Kraang 	エドガー・
5281135 	NewPub 	2022-04-03 11:20:49 	Uzume 	2022-04-04 15:13:23 	Kraang 	月のプリン
5281134 	NewPub 	2022-04-03 11:20:46 	Uzume 	2022-04-04 15:13:12 	Kraang 	月からの侵
5281059 	PubUpdate 	2022-04-03 10:13:10 	Uzume 	2022-04-04 13:02:05 	Anniemod 	月人の地球
5282408 	Make Alternate Name 	2022-04-03 23:39:39 	Uzume 	2022-04-04 11:22:38 	Kraang 	C. M. Clarke
5281898 	AuthorUpdate 	2022-04-03 19:23:24 	Uzume 	2022-04-03 22:43:37 	Kraang 	Charles M. Clay
5281878 	PubUpdate 	2022-04-03 19:16:13 	Uzume 	2022-04-03 22:43:13 	Kraang 	How She Came Into Her Kingdom; a Romance
5281775 	PubUpdate 	2022-04-03 17:24:39 	Uzume 	2022-04-03 22:38:39 	Kraang 	Tales of the Caravan, Inn, and Palace
5280397 	ClonePub 	2022-04-02 23:40:32 	Uzume 	2022-04-03 22:24:21 	Kraang 	The Moon Maid
5280385 	PubUpdate 	2022-04-02 23:14:43 	Uzume 	2022-04-03 22:23:33 	Kraang 	The Moon Maid
5280381 	PubUpdate 	2022-04-02 23:12:06 	Uzume 	2022-04-03 22:23:28 	Kraang 	The Moon Maid
5280376 	PubUpdate 	2022-04-02 22:58:03 	Uzume 	2022-04-03 22:23:11 	Kraang 	The Moon Maid
5280365 	PubUpdate 	2022-04-02 22:38:48 	Uzume 	2022-04-03 22:22:30 	Kraang 	The Moon Maid
5280356 	PubUpdate 	2022-04-02 22:32:19 	Uzume 	2022-04-03 22:22:25 	Kraang 	The Moon Maid
5280284 	PubUpdate 	2022-04-02 21:52:31 	Uzume 	2022-04-03 22:21:31 	Kraang 	The Moon Maid
5280260 	PubUpdate 	2022-04-02 21:00:20 	Uzume 	2022-04-03 22:20:54 	Kraang 	The Land That Time Forgot and The Moon M
5278296 	AuthorUpdate 	2022-03-31 20:29:44 	Uzume 	2022-04-01 22:04:34 	Kraang 	Hugo Gernsback
5275434 	SeriesUpdate 	2022-03-29 20:09:16 	Uzume 	2022-04-01 19:59:38 	Kraang 	Blue Book
5274483 	PubUpdate 	2022-03-29 03:57:58 	Uzume 	2022-04-01 12:00:09 	Kraang 	The Land That Time Forgot and The Moon M
5243356 	SeriesUpdate 	2022-02-26 00:45:22 	Uzume 	2022-02-26 23:13:52 	Kraang 	The Windsor Magazine
5224081 	SeriesUpdate 	2022-02-10 23:45:14 	Uzume 	2022-02-11 21:33:46 	Anniemod 	Weird Tales Library
5224080 	SeriesUpdate 	2022-02-10 23:44:07 	Uzume 	2022-02-11 21:33:44 	Anniemod 	Weird Tales Magazine
5224079 	SeriesUpdate 	2022-02-10 23:41:16 	Uzume 	2022-02-11 21:33:41 	Anniemod 	The Weird Tales Collector
5224078 	SeriesUpdate 	2022-02-10 23:34:51 	Uzume 	2022-02-11 21:33:36 	Anniemod 	Weird Tales (Canada)
5224075 	SeriesUpdate 	2022-02-10 23:22:22 	Uzume 	2022-02-11 21:33:29 	Anniemod 	The Magic Carpet Magazine
5224072 	SeriesUpdate 	2022-02-10 23:06:59 	Uzume 	2022-02-11 21:33:12 	Anniemod 	Oriental Stories
5223312 	AuthorUpdate 	2022-02-10 14:08:44 	Uzume 	2022-02-11 09:59:02 	Rtrace 	Sabine Baring-Gould
5208674 	PubUpdate 	2022-01-27 12:27:14 	Uzume 	2022-01-27 22:39:37 	Kraang 	Tarnsman of Gor
5199705 	PubUpdate 	2022-01-16 14:50:56 	Uzume 	2022-01-16 20:04:18 	Kraang 	Bulldozer Rising
5199690 	ClonePub 	2022-01-16 14:21:03 	Uzume 	2022-01-16 20:03:14 	Kraang 	Altogether Elsewhere
5199613 	PubUpdate 	2022-01-16 13:57:51 	Uzume 	2022-01-16 19:58:30 	Kraang 	Altogether Elsewhere
5179549 	TitleUpdate 	2021-12-23 03:45:53 	Uzume 	2021-12-24 20:03:51 	Kraang 	ねぶそくの
5179546 	PubUpdate 	2021-12-23 03:34:56 	Uzume 	2021-12-24 20:03:36 	Kraang 	A Short History of Biology
5179545 	PubUpdate 	2021-12-23 03:33:19 	Uzume 	2021-12-24 20:03:28 	Kraang 	A Short History of Biology
5179544 	PubUpdate 	2021-12-23 03:31:27 	Uzume 	2021-12-24 20:03:20 	Kraang 	Crossing Over
5179542 	PubUpdate 	2021-12-23 03:30:10 	Uzume 	2021-12-24 20:03:16 	Kraang 	Dark Mist Rising
5179541 	PubUpdate 	2021-12-23 03:28:46 	Uzume 	2021-12-24 20:03:12 	Kraang 	Ipomoea
5179538 	TitleUpdate 	2021-12-23 03:12:26 	Uzume 	2021-12-24 20:03:07 	Kraang 	Clarkesworld, Issue 181
5179535 	TitleMerge 	2021-12-23 03:07:59 	Uzume 	2021-12-24 20:02:59 	Kraang 	Forever - 2021
5179534 	TitleMerge 	2021-12-23 02:59:57 	Uzume 	2021-12-24 20:02:35 	Kraang 	Simultaneous Times - 2021
5179533 	TitleUpdate 	2021-12-23 02:57:06 	Uzume 	2021-12-24 20:02:25 	Kraang 	Simultaneous Times, Ep.34
Submission 	Type 	Time Submitted 	Submitter 	Time Approved 	Reviewer 	Affected Record
5173448 	ImportExport 	2021-12-13 22:41:29 	Uzume 	2021-12-14 10:08:03 	Rtrace 	Percy Jackson and the Singer of Apollo
5170709 	AuthorUpdate 	2021-12-10 10:15:15 	Uzume 	2021-12-10 23:25:10 	Kraang 	С. Э. Кле&
5170704 	TitleUpdate 	2021-12-10 10:07:41 	Uzume 	2021-12-10 23:24:52 	Kraang 	Тарнсl
5170702 	TitleUpdate 	2021-12-10 10:07:11 	Uzume 	2021-12-10 23:24:41 	Kraang 	Вне за
5170701 	TitleUpdate 	2021-12-10 10:06:43 	Uzume 	2021-12-10 23:24:37 	Kraang 	Пиратm
5170700 	TitleUpdate 	2021-12-10 10:06:12 	Uzume 	2021-12-10 23:24:32 	Kraang 	Люди з
5170699 	MakeVariant 	2021-12-10 10:03:37 	Uzume 	2021-12-10 23:24:24 	Kraang 	Тарнсl
5170698 	MakeVariant 	2021-12-10 10:03:01 	Uzume 	2021-12-10 23:24:20 	Kraang 	Вне за
5170696 	MakeVariant 	2021-12-10 10:01:27 	Uzume 	2021-12-10 23:23:59 	Kraang 	Пиратm
5170695 	MakeVariant 	2021-12-10 09:59:54 	Uzume 	2021-12-10 23:23:57 	Kraang 	Люди з
5170693 	MakeVariant 	2021-12-10 09:57:33 	Uzume 	2021-12-10 23:23:47 	Kraang 	Вне за
5170688 	AuthorUpdate 	2021-12-10 09:47:20 	Uzume 	2021-12-10 23:23:03 	Kraang 	Э. Р. Бер&
5170687 	Make Alternate Name 	2021-12-10 09:41:53 	Uzume 	2021-12-10 23:22:56 	Kraang 	Э. Р. Бер&
5170066 	NewPub 	2021-12-09 15:17:51 	Uzume 	2021-12-10 09:36:23 	Rtrace 	Вне за
5170129 	TitleUpdate 	2021-12-09 16:56:02 	Uzume 	2021-12-09 23:28:50 	Kraang 	The Chronicles of Counter-Earth: Tarl Ca
5170079 	PubSeriesUpdate 	2021-12-09 15:56:01 	Uzume 	2021-12-09 23:25:47 	Kraang 	Хозяеk
5170078 	PubSeriesUpdate 	2021-12-09 15:54:50 	Uzume 	2021-12-09 23:25:40 	Kraang 	Gold Collection (вто&#
5170076 	PubUpdate 	2021-12-09 15:50:33 	Uzume 	2021-12-09 23:25:17 	Kraang 	Танец
5167576 	TitleUpdate 	2021-12-06 14:14:30 	Uzume 	2021-12-06 20:43:04 	Anniemod 	The Chronicles of Counter-Earth: Tarl Ca
5167568 	TitleUpdate 	2021-12-06 13:53:19 	Uzume 	2021-12-06 20:41:54 	Anniemod 	The Calpa & Notes Pertaining to a Panel
5167567 	ClonePub 	2021-12-06 13:52:04 	Uzume 	2021-12-06 20:41:43 	Anniemod 	The Calpa & Notes Pertaining to a Panel
5167438 	PubUpdate 	2021-12-06 05:40:57 	Uzume 	2021-12-06 20:32:27 	Anniemod 	Nomads of Gor
5167437 	PubUpdate 	2021-12-06 05:29:17 	Uzume 	2021-12-06 20:32:15 	Anniemod 	Time Slave
5167436 	PubUpdate 	2021-12-06 05:21:50 	Uzume 	2021-12-06 20:31:58 	Anniemod 	Hunters of Gor
5167434 	PubUpdate 	2021-12-06 05:17:06 	Uzume 	2021-12-06 20:31:08 	Anniemod 	Guardsman of Gor
5167433 	PubUpdate 	2021-12-06 05:13:02 	Uzume 	2021-12-06 20:29:10 	Anniemod 	Priest-Kings of Gor
5167432 	PubUpdate 	2021-12-06 05:01:38 	Uzume 	2021-12-06 20:29:01 	Anniemod 	Assassin of Gor
5167431 	PubUpdate 	2021-12-06 04:55:45 	Uzume 	2021-12-06 20:28:52 	Anniemod 	Raiders of Gor
5167430 	PubUpdate 	2021-12-06 04:51:13 	Uzume 	2021-12-06 20:28:46 	Anniemod 	The Chieftain
5167429 	PubUpdate 	2021-12-06 04:45:30 	Uzume 	2021-12-06 20:28:41 	Anniemod 	The Captain
5167417 	PubUpdate 	2021-12-06 04:40:03 	Uzume 	2021-12-06 20:28:13 	Anniemod 	Hunters of Gor
5167411 	PubUpdate 	2021-12-06 04:29:07 	Uzume 	2021-12-06 20:26:42 	Anniemod 	Explorers of Gor
5167410 	PubUpdate 	2021-12-06 04:21:24 	Uzume 	2021-12-06 20:26:35 	Anniemod 	Captive of Gor
5167408 	PubUpdate 	2021-12-06 04:07:34 	Uzume 	2021-12-06 20:26:09 	Anniemod 	Raiders of Gor
5167406 	PubUpdate 	2021-12-06 03:51:04 	Uzume 	2021-12-06 20:25:47 	Anniemod 	Assassin of Gor
5167405 	PubUpdate 	2021-12-06 03:44:24 	Uzume 	2021-12-06 20:25:42 	Anniemod 	Priest-Kings of Gor
5051751 	AuthorUpdate 	2021-08-09 08:39:29 	Uzume 	2021-08-11 10:06:12 	Rudam 	Craig Nova
4978889 	TitleUpdate 	2021-05-06 16:16:47 	Uzume 	2021-05-06 20:14:18 	JLaTondre 	Voyagers II: The Alien Within
4883040 	TitleUpdate 	2021-01-14 21:06:19 	Uzume 	2021-01-18 22:43:05 	Dirk P Broer 	Histoire d'un casse-noisette
4883597 	PubUpdate 	2021-01-15 15:14:47 	Uzume 	2021-01-18 22:39:53 	Dirk P Broer 	Historja Dziadka do Orzechów
4883595 	MakeVariant 	2021-01-15 15:12:27 	Uzume 	2021-01-18 22:39:39 	Dirk P Broer 	Skarb Bobowy
4883594 	MakeVariant 	2021-01-15 15:11:04 	Uzume 	2021-01-18 22:39:28 	Dirk P Broer 	Histoire d'un casse-noisette
4883592 	MakeVariant 	2021-01-15 15:08:57 	Uzume 	2021-01-18 22:39:16 	Dirk P Broer 	Historja Dziadka do Orzechów
4883591 	Make Alternate Name 	2021-01-15 15:07:54 	Uzume 	2021-01-18 22:39:09 	Dirk P Broer 	Aleksandra Dumasa
4883590 	MakeVariant 	2021-01-15 15:05:17 	Uzume 	2021-01-18 22:39:02 	Dirk P Broer 	Histoire d'un casse-noisette (138)
4883588 	MakeVariant 	2021-01-15 15:04:13 	Uzume 	2021-01-18 22:38:56 	Dirk P Broer 	Histoire d'un casse-noisette
4885359 	PublisherUpdate 	2021-01-16 20:32:47 	Uzume 	2021-01-18 20:27:02 	Biomassbob 	Księgarnia Polska Bernarda Poł
4883585 	Make Alternate Name 	2021-01-15 14:58:26 	Uzume 	2021-01-18 18:15:19 	Biomassbob 	P. Bertalla
4883572 	MakeVariant 	2021-01-15 14:54:29 	Uzume 	2021-01-18 18:14:34 	Biomassbob 	Histoire d'un casse-noisette
4883037 	NewPub 	2021-01-14 21:00:31 	Uzume 	2021-01-15 13:06:49 	Rtrace 	Historja Dziadka do Orzechów
4882802 	NewPub 	2021-01-14 18:38:45 	Uzume 	2021-01-15 13:02:27 	Rtrace 	Histoire d'un casse-noisette
4881954 	TitleUpdate 	2021-01-13 14:35:29 	Uzume 	2021-01-14 09:37:54 	Rtrace 	Nutcracker and Mouse-King
4881763 	MakeVariant 	2021-01-13 12:58:15 	Uzume 	2021-01-13 13:41:21 	Rtrace 	The Nutcracker
4881759 	TitleUpdate 	2021-01-13 12:55:28 	Uzume 	2021-01-13 13:41:11 	Rtrace 	The Nutcracker
4881736 	TitleUpdate 	2021-01-13 12:49:36 	Uzume 	2021-01-13 13:40:59 	Rtrace 	The Nutcracker
4881734 	TitleUpdate 	2021-01-13 12:47:23 	Uzume 	2021-01-13 13:39:51 	Rtrace 	The Nut-Cracker
4881731 	TitleUpdate 	2021-01-13 12:44:27 	Uzume 	2021-01-13 13:39:46 	Rtrace 	Nut-Cracker Proclaims His Victory Over M
4881727 	TitleUpdate 	2021-01-13 12:42:24 	Uzume 	2021-01-13 13:39:41 	Rtrace 	The Disenchantment of the Princess
4881724 	TitleUpdate 	2021-01-13 12:39:44 	Uzume 	2021-01-13 13:39:37 	Rtrace 	Story of the "Hard Nut."
4880495 	TitleUnmerge 	2021-01-12 09:17:14 	Uzume 	2021-01-13 10:16:31 	Rtrace 	The Nutcracker
4879889 	PubUpdate 	2021-01-11 00:11:20 	Uzume 	2021-01-11 17:50:33 	JLaTondre 	Nutcracker and Mouse-King
4876565 	ClonePub 	2021-01-07 13:11:36 	Uzume 	2021-01-10 14:27:27 	JLaTondre 	The Nutcracker
4685597 	TitleUpdate 	2020-06-20 11:42:33 	Uzume 	2020-06-21 05:10:40 	Rudam 	Benny and Omar
4685596 	TitleUpdate 	2020-06-20 11:42:18 	Uzume 	2020-06-21 05:10:31 	Rudam 	Benny and Babe
4652054 	PubUpdate 	2020-05-18 13:48:27 	Uzume 	2020-05-19 18:54:56 	Anniemod 	Last Chance To See
4652052 	AuthorUpdate 	2020-05-18 13:21:45 	Uzume 	2020-05-19 18:54:34 	Anniemod 	Frederic Vincent Huber
4633806 	PubUpdate 	2020-04-28 14:17:15 	Uzume 	2020-04-28 16:30:14 	MagicUnk 	Captive of Gor
4633802 	PubUpdate 	2020-04-28 14:15:35 	Uzume 	2020-04-28 16:28:07 	MagicUnk 	Assassin of Gor
4633799 	PubUpdate 	2020-04-28 14:13:28 	Uzume 	2020-04-28 16:28:02 	MagicUnk 	Outlaw of Gor
4611100 	MakeVariant 	2020-03-31 20:40:23 	Uzume 	2020-04-01 06:15:26 	Stonecreek 	Daniël in LA
4611102 	MakeVariant 	2020-03-31 20:41:21 	Uzume 	2020-03-31 23:50:00 	Stonecreek 	Wat er met Trevor gebeurde
4610650 	PubUpdate 	2020-03-30 21:13:39 	Uzume 	2020-03-31 14:06:52 	Biomassbob 	Angels in the Dark
4607380 	TitleUpdate 	2020-03-25 10:52:30 	Uzume 	2020-03-25 11:09:50 	Stonecreek 	わが名はコ
4607379 	AuthorUpdate 	2020-03-25 10:45:24 	Uzume 	2020-03-25 11:09:36 	Stonecreek 	Darrin Perez
4606027 	NewPub 	2020-03-22 21:09:23 	Uzume 	2020-03-22 21:35:27 	Dirk P Broer 	Whispers of Dawn
4602135 	PubUpdate 	2020-03-17 14:03:03 	Uzume 	2020-03-17 14:15:57 	Stonecreek 	Out of the Sun
4602134 	ClonePub 	2020-03-17 14:02:01 	Uzume 	2020-03-17 14:15:20 	Stonecreek 	Out of the Sun
4602125 	PubUpdate 	2020-03-17 13:45:24 	Uzume 	2020-03-17 13:51:32 	Stonecreek 	Out of the Sun
4602117 	ImportExport 	2020-03-17 13:29:33 	Uzume 	2020-03-17 13:47:12 	Stonecreek 	Out of the Sun
4590342 	NewPub 	2020-03-02 10:13:38 	Uzume 	2020-03-02 12:34:11 	Dirk P Broer 	Yo, bruja
4589071 	NewPub 	2020-03-01 01:30:56 	Uzume 	2020-03-01 06:05:00 	Dirk P Broer 	ブロークン
4576805 	PubUpdate 	2020-02-16 04:01:25 	Uzume 	2020-02-16 06:27:17 	Dirk P Broer 	Tales and Sketches, Illustrating the Cha
4576791 	PubUpdate 	2020-02-16 01:51:47 	Uzume 	2020-02-16 06:18:56 	Dirk P Broer 	Whims and Oddities: In Prose and Verse:
4576790 	PubUpdate 	2020-02-16 01:46:36 	Uzume 	2020-02-16 06:18:12 	Dirk P Broer 	Near Enemy
4576789 	PubUpdate 	2020-02-16 01:43:12 	Uzume 	2020-02-16 06:17:58 	Dirk P Broer 	Travels in Phrenologasto
4576636 	NewPub 	2020-02-15 15:27:40 	Uzume 	2020-02-16 06:14:01 	Dirk P Broer 	ダンジョン
4576597 	AddPub 	2020-02-15 13:50:54 	Uzume 	2020-02-15 14:48:15 	Dirk P Broer 	ダンジョン
4576097 	TitleUpdate 	2020-02-14 14:42:30 	Uzume 	2020-02-14 18:10:57 	Dirk P Broer 	Tales, in Verse, and Miscellaneous Poems
4575941 	TitleUpdate 	2020-02-14 11:05:00 	Uzume 	2020-02-14 13:31:27 	Dirk P Broer 	Tales, in Verse, and Miscellaneous Poems
4575934 	PubUpdate 	2020-02-14 10:59:22 	Uzume 	2020-02-14 13:31:14 	Dirk P Broer 	Tales, in Verse, and Miscellaneous Poems
4575925 	PubUpdate 	2020-02-14 10:49:16 	Uzume 	2020-02-14 12:35:16 	Hitspacebar 	Tales, in Verse, and Miscellaneous Poems
4575400 	PublisherUpdate 	2020-02-13 15:09:26 	Uzume 	2020-02-13 20:20:13 	Dirk P Broer 	Scott & Seltzer
4575389 	PublisherUpdate 	2020-02-13 15:02:17 	Uzume 	2020-02-13 20:20:06 	Dirk P Broer 	Thomas Seltzer
4575369 	AuthorUpdate 	2020-02-13 14:02:42 	Uzume 	2020-02-13 17:27:35 	JLaTondre 	Youngman Carter
4575362 	PubUpdate 	2020-02-13 12:56:05 	Uzume 	2020-02-13 12:59:11 	Stonecreek 	The Dragon's Brood
4575228 	AddPub 	2020-02-13 10:56:48 	Uzume 	2020-02-13 12:23:37 	MartyD 	The Dragon's Brood
4575160 	PubUpdate 	2020-02-13 09:25:03 	Uzume 	2020-02-13 10:03:21 	MartyD 	Sacrilegious Hands
4575154 	AuthorUpdate 	2020-02-13 09:15:44 	Uzume 	2020-02-13 10:02:46 	MartyD 	William Henry Warner
4575153 	NewPub 	2020-02-13 09:04:05 	Uzume 	2020-02-13 10:02:38 	MartyD 	The Dragon's Brood
4574862 	PubUpdate 	2020-02-12 19:32:46 	Uzume 	2020-02-13 03:06:20 	Dirk P Broer 	The Bridge of Time
4574864 	PubUpdate 	2020-02-12 19:34:08 	Uzume 	2020-02-13 00:12:52 	Stonecreek 	Sacrilegious Hands
4574779 	ClonePub 	2020-02-12 16:35:28 	Uzume 	2020-02-12 17:16:30 	Dirk P Broer 	The Bridge of Time
4574772 	PubUpdate 	2020-02-12 16:14:36 	Uzume 	2020-02-12 17:15:59 	Dirk P Broer 	অজানা �
4574771 	PubUpdate 	2020-02-12 16:13:00 	Uzume 	2020-02-12 17:15:53 	Dirk P Broer 	After the Fall
4574770 	PubUpdate 	2020-02-12 16:11:42 	Uzume 	2020-02-12 17:15:46 	Dirk P Broer 	Million-Dollar Duck
4574687 	PubUpdate 	2020-02-12 14:14:07 	Uzume 	2020-02-12 17:15:31 	Dirk P Broer 	Fool
4574686 	PubUpdate 	2020-02-12 14:11:39 	Uzume 	2020-02-12 17:15:21 	Dirk P Broer 	Living Proof
4574685 	PubUpdate 	2020-02-12 14:09:41 	Uzume 	2020-02-12 17:15:12 	Dirk P Broer 	The Nostradamus Prophecy
4574684 	PubUpdate 	2020-02-12 14:07:42 	Uzume 	2020-02-12 17:15:01 	Dirk P Broer 	Time Travel in Einstein's Universe: The
4574766 	PubUpdate 	2020-02-12 16:08:13 	Uzume 	2020-02-12 17:14:30 	Dirk P Broer 	2001: A Space Odyssey
4574682 	PubUpdate 	2020-02-12 14:04:31 	Uzume 	2020-02-12 17:12:50 	Dirk P Broer 	The Bridge of Time
4574368 	PubUpdate 	2020-02-11 21:37:08 	Uzume 	2020-02-12 03:10:11 	Stonecreek 	The Moon Metal
4574371 	PubUpdate 	2020-02-11 21:40:22 	Uzume 	2020-02-12 02:19:30 	Stonecreek 	A Columbus of Space
4574365 	TitleUpdate 	2020-02-11 21:17:48 	Uzume 	2020-02-12 02:18:58 	Stonecreek 	黄昏の遊歩
4574221 	NewPub 	2020-02-11 14:55:35 	Uzume 	2020-02-11 16:07:34 	Dirk P Broer 	黄昏の遊歩
4574186 	AuthorUpdate 	2020-02-11 14:11:01 	Uzume 	2020-02-11 15:36:34 	Dirk P Broer 	A. K. Otterness
4574214 	ClonePub 	2020-02-11 14:38:31 	Uzume 	2020-02-11 15:33:32 	Dirk P Broer 	The White Body of Evening
4573379 	ClonePub 	2020-02-10 18:31:56 	Uzume 	2020-02-10 18:39:01 	Biomassbob 	Le Città Perdute
4573372 	AuthorUpdate 	2020-02-10 18:27:04 	Uzume 	2020-02-10 18:38:50 	Biomassbob 	Tiziana Triana
4573340 	SeriesUpdate 	2020-02-10 18:05:36 	Uzume 	2020-02-10 18:07:53 	Dirk P Broer 	Luna Nera
4573288 	NewPub 	2020-02-10 16:42:06 	Uzume 	2020-02-10 18:03:15 	Dirk P Broer 	Le Città Perdute
4573285 	PublisherUpdate 	2020-02-10 16:38:52 	Uzume 	2020-02-10 18:02:49 	Dirk P Broer 	Marsilio
4573271 	PublisherUpdate 	2020-02-10 16:30:11 	Uzume 	2020-02-10 18:02:45 	Dirk P Broer 	Sonzogno
4570263 	PubUpdate 	2020-02-07 05:32:26 	Uzume 	2020-02-07 06:57:57 	Dirk P Broer 	わが名はコ
4570262 	PubSeriesUpdate 	2020-02-07 05:29:39 	Uzume 	2020-02-07 06:57:51 	Dirk P Broer 	ハヤカワSFਧ
4570261 	PubSeriesUpdate 	2020-02-07 05:28:58 	Uzume 	2020-02-07 06:57:47 	Dirk P Broer 	ハヤカワ文
4570260 	PubSeriesUpdate 	2020-02-07 05:25:22 	Uzume 	2020-02-07 06:57:42 	Dirk P Broer 	ハヤカワ・
4570259 	PubSeriesUpdate 	2020-02-07 05:24:14 	Uzume 	2020-02-07 06:57:32 	Dirk P Broer 	ハヤカワ・
4570256 	PubUpdate 	2020-02-07 05:14:09 	Uzume 	2020-02-07 06:57:26 	Dirk P Broer 	明日を越え
4570247 	PubUpdate 	2020-02-07 04:54:15 	Uzume 	2020-02-07 06:57:22 	Dirk P Broer 	明日を越え
4570243 	PubUpdate 	2020-02-07 04:38:24 	Uzume 	2020-02-07 06:45:43 	Rtrace 	ジョナサン
4570242 	PubUpdate 	2020-02-07 04:38:04 	Uzume 	2020-02-07 06:45:39 	Rtrace 	ジョナサン
4570116 	SeriesUpdate 	2020-02-06 21:47:08 	Uzume 	2020-02-07 01:24:17 	MagicUnk 	Science Fiction Adventures (1958-1963) (
4570115 	SeriesUpdate 	2020-02-06 21:40:43 	Uzume 	2020-02-07 01:24:10 	MagicUnk 	Science Fiction Adventures (1952-1954)
4569755 	ClonePub 	2020-02-06 18:15:53 	Uzume 	2020-02-06 18:30:28 	Biomassbob 	明日を越え
4569754 	ClonePub 	2020-02-06 18:14:19 	Uzume 	2020-02-06 18:30:22 	Biomassbob 	明日を越え
4569743 	PubUpdate 	2020-02-06 18:07:11 	Uzume 	2020-02-06 18:30:11 	Biomassbob 	竜の卵
4569742 	PubUpdate 	2020-02-06 18:06:49 	Uzume 	2020-02-06 18:30:04 	Biomassbob 	竜の卵
4569740 	ClonePub 	2020-02-06 18:01:54 	Uzume 	2020-02-06 18:29:47 	Biomassbob 	地球からの
4569733 	ClonePub 	2020-02-06 17:54:23 	Uzume 	2020-02-06 18:29:40 	Biomassbob 	プロテクタ
4569485 	PubUpdate 	2020-02-06 14:51:01 	Uzume 	2020-02-06 16:59:50 	Dirk P Broer 	セックス・
4569483 	PubUpdate 	2020-02-06 14:48:00 	Uzume 	2020-02-06 16:59:46 	Dirk P Broer 	ソフトウェ
4569480 	PubUpdate 	2020-02-06 14:46:00 	Uzume 	2020-02-06 16:59:37 	Dirk P Broer 	ニューロマ
4569477 	PubUpdate 	2020-02-06 14:45:26 	Uzume 	2020-02-06 16:59:32 	Dirk P Broer 	ニューロマ
4569475 	PubUpdate 	2020-02-06 14:44:27 	Uzume 	2020-02-06 16:59:27 	Dirk P Broer 	ニューロマ
4569465 	PubUpdate 	2020-02-06 14:37:27 	Uzume 	2020-02-06 16:59:22 	Dirk P Broer 	時間外世界
4569459 	PubUpdate 	2020-02-06 14:33:37 	Uzume 	2020-02-06 16:59:12 	Dirk P Broer 	リングワー
4569455 	PubUpdate 	2020-02-06 14:30:32 	Uzume 	2020-02-06 16:58:50 	Dirk P Broer 	パーマ・エ
4569452 	PubUpdate 	2020-02-06 14:29:26 	Uzume 	2020-02-06 16:58:46 	Dirk P Broer 	パーマ・エ
4569440 	TitleUpdate 	2020-02-06 14:25:47 	Uzume 	2020-02-06 16:58:42 	Dirk P Broer 	パーマ·エル
4569437 	PubUpdate 	2020-02-06 14:22:51 	Uzume 	2020-02-06 16:58:33 	Dirk P Broer 	明日を越え
4569436 	PubUpdate 	2020-02-06 14:20:24 	Uzume 	2020-02-06 16:58:28 	Dirk P Broer 	竜の卵
4569434 	PubUpdate 	2020-02-06 14:16:55 	Uzume 	2020-02-06 16:58:24 	Dirk P Broer 	地球からの
4569430 	PubUpdate 	2020-02-06 14:14:15 	Uzume 	2020-02-06 16:58:19 	Dirk P Broer 	プロテクタ
4569427 	PubUpdate 	2020-02-06 14:09:13 	Uzume 	2020-02-06 16:58:14 	Dirk P Broer 	ユービック
4569424 	PubUpdate 	2020-02-06 14:08:04 	Uzume 	2020-02-06 16:58:09 	Dirk P Broer 	ユービック
4569420 	PubUpdate 	2020-02-06 14:05:55 	Uzume 	2020-02-06 15:08:15 	Stonecreek 	アンドロイ
4569419 	PubUpdate 	2020-02-06 14:05:16 	Uzume 	2020-02-06 15:08:10 	Stonecreek 	アンドロイ
4569415 	TitleUpdate 	2020-02-06 14:00:55 	Uzume 	2020-02-06 15:08:05 	Stonecreek 	アンドロイ
4569395 	PubUpdate 	2020-02-06 10:23:32 	Uzume 	2020-02-06 11:20:11 	Dirk P Broer 	明日を越え
4569393 	TitleUpdate 	2020-02-06 10:18:34 	Uzume 	2020-02-06 11:20:02 	Dirk P Broer 	龍の卵
4569392 	PubUpdate 	2020-02-06 10:18:09 	Uzume 	2020-02-06 11:19:57 	Dirk P Broer 	竜の卵
4569391 	PubUpdate 	2020-02-06 10:17:06 	Uzume 	2020-02-06 11:19:44 	Dirk P Broer 	竜の卵
4569389 	TitleUpdate 	2020-02-06 10:13:25 	Uzume 	2020-02-06 11:19:37 	Dirk P Broer 	アンドロイ
4569386 	TitleUpdate 	2020-02-06 10:12:29 	Uzume 	2020-02-06 11:19:31 	Dirk P Broer 	アンドロイ
4569383 	PubUpdate 	2020-02-06 10:11:37 	Uzume 	2020-02-06 11:19:27 	Dirk P Broer 	アンドロイ
4569380 	PubUpdate 	2020-02-06 10:10:25 	Uzume 	2020-02-06 11:19:22 	Dirk P Broer 	アンドロイ
4569363 	TitleUpdate 	2020-02-06 09:38:58 	Uzume 	2020-02-06 09:49:11 	Dirk P Broer 	人間以前
4569362 	TitleUpdate 	2020-02-06 09:38:29 	Uzume 	2020-02-06 09:48:52 	Dirk P Broer 	小さな黒い
4569361 	TitleUpdate 	2020-02-06 09:37:59 	Uzume 	2020-02-06 09:48:42 	Dirk P Broer 	変種第二号
4569360 	TitleUpdate 	2020-02-06 09:37:20 	Uzume 	2020-02-06 09:48:34 	Dirk P Broer 	変数人間
4569359 	TitleUpdate 	2020-02-06 09:36:32 	Uzume 	2020-02-06 09:48:19 	Dirk P Broer 	トータル・
4569358 	TitleUpdate 	2020-02-06 09:35:53 	Uzume 	2020-02-06 09:48:09 	Dirk P Broer 	アジャスト
4561980 	PubUpdate 	2020-01-28 11:54:51 	Uzume 	2020-01-28 14:32:51 	Biomassbob 	Japanese Fairy World
4561979 	ClonePub 	2020-01-28 11:41:24 	Uzume 	2020-01-28 14:32:42 	Biomassbob 	Japanese Fairy World
4561976 	MakeVariant 	2020-01-28 11:25:07 	Uzume 	2020-01-28 13:49:27 	Stonecreek 	The Ghost Bride: Pengantin Arwah
4561975 	MakeVariant 	2020-01-28 11:24:52 	Uzume 	2020-01-28 13:31:48 	Stonecreek 	La novia fantasma
4561831 	NewPub 	2020-01-28 06:44:13 	Uzume 	2020-01-28 08:27:14 	Dirk P Broer 	The Ghost Bride: Pengantin Arwah
4561827 	NewPub 	2020-01-28 06:25:46 	Uzume 	2020-01-28 08:27:08 	Dirk P Broer 	La novia fantasma
4561614 	AddPub 	2020-01-27 21:43:24 	Uzume 	2020-01-28 08:20:13 	Dirk P Broer 	Japanese Fairy World
4561572 	AddPub 	2020-01-27 19:47:05 	Uzume 	2020-01-28 08:19:33 	Dirk P Broer 	彼岸之嫁
4561696 	MakeVariant 	2020-01-28 01:11:24 	Uzume 	2020-01-28 03:39:11 	Stonecreek 	A noiva fantasm
4561568 	NewPub 	2020-01-27 19:35:31 	Uzume 	2020-01-28 00:12:56 	Stonecreek 	A Noiva Fantasm
4561567 	AuthorUpdate 	2020-01-27 19:15:35 	Uzume 	2020-01-28 00:03:24 	Stonecreek 	Yangsze Choo
4561566 	Make Alternate Name 	2020-01-27 19:07:33 	Uzume 	2020-01-28 00:03:17 	Stonecreek 	朱洋熹
4561565 	MakeVariant 	2020-01-27 19:06:35 	Uzume 	2020-01-28 00:03:11 	Stonecreek 	彼岸之嫁
4561432 	TitleUpdate 	2020-01-27 13:55:47 	Uzume 	2020-01-27 17:27:58 	Biomassbob 	Death Beast
4561428 	PubUpdate 	2020-01-27 13:55:18 	Uzume 	2020-01-27 17:27:39 	Biomassbob 	Starlog, #15 August
4561394 	NewPub 	2020-01-27 13:27:42 	Uzume 	2020-01-27 17:26:21 	Biomassbob 	彼岸之嫁
4561438 	PubUpdate 	2020-01-27 13:59:28 	Uzume 	2020-01-27 15:49:02 	MagicUnk 	Starlog, #4
4559351 	PubUpdate 	2020-01-24 13:15:01 	Uzume 	2020-01-24 17:12:11 	Dirk P Broer 	File 770, #166 July 2016
4559350 	PubUpdate 	2020-01-24 13:13:53 	Uzume 	2020-01-24 17:12:03 	Dirk P Broer 	File 770, #165 December 2015
4559349 	PubUpdate 	2020-01-24 13:12:58 	Uzume 	2020-01-24 17:11:51 	Dirk P Broer 	File 770, #164 December 2014
4559356 	TitleUpdate 	2020-01-24 13:17:56 	Uzume 	2020-01-24 14:09:25 	PeteYoung 	File 770 - 1981
4559355 	TitleUpdate 	2020-01-24 13:17:24 	Uzume 	2020-01-24 14:09:03 	PeteYoung 	File 770 - 1986
4559354 	TitleUpdate 	2020-01-24 13:17:07 	Uzume 	2020-01-24 14:08:49 	PeteYoung 	File 770 - 1987
4559353 	TitleUpdate 	2020-01-24 13:16:11 	Uzume 	2020-01-24 14:08:31 	PeteYoung 	File 770 - 2001
4559348 	PubUpdate 	2020-01-24 13:12:01 	Uzume 	2020-01-24 14:07:21 	PeteYoung 	File 770, #163 December 2013
4559352 	TitleUpdate 	2020-01-24 13:15:45 	Uzume 	2020-01-24 14:06:51 	PeteYoung 	File 770 - 2015
4559357 	TitleUpdate 	2020-01-24 13:18:36 	Uzume 	2020-01-24 13:53:14 	Stonecreek 	File 770 - 1978

Yes, I am aware I could pull the database backups and run SQL queries myself but that does not improve accessiblity that was removed (short of expensively paging through recent.cgi). My point is that this punishes users that make a few edits every so many months as they cannot see past an arbitrary three month cutoff without more extreme measures. —Uzume (talk) 17:21, 17 September 2022 (EDT)

Publicly accessible backups do not include the submission table, so it wouldn't be possible. Ahasuerus (talk) 17:25, 17 September 2022 (EDT)

Non-ISBNs

The examples in this discussion led me to realize our ISBN handling has a couple of shortcomings:

• The formatting logic ought to skip any number > 10 digits that does not start with 978 or 979. Regardless of what the check-digit logic thinks, such a number is not an ISBN and should not be reformatted as such. I forget if that code also supplies a missing check digit; we wouldn't want it adding a digit to any 12-digit number not starting with 978 or 979, either.
• The ISBN value check for the submission review screen ought to warn when a value longer than 10 digits does not start with 978 or 979. Such a value is not an ISBN. It's pretty easy to not pay close attention to ISBNs when reviewing the submission contents.

Thanks for listening. --MartyD 13:04, 3 September 2022 (EDT)

Very good points. FR 1529, "Improve display of invalid ISBNs", has been created. I have also responded on the Rules and Standards page. Thanks. Ahasuerus 15:08, 3 September 2022 (EDT)

Deryni Magic title

Please look at the title page of your copy of Deryni Magic: A Grimoire and see if it matches mine which only reads "Deryni Magic". I'd like to change the both the title and canonical title to "Deryni Magic" as well as add a note that the cover shows the title as "Deryni Magic: A Grimoire". I'll also have to change the cover image title to match. I'd also like to add the map titles on pages vi and vii. The other active PVs have this same request. Thanks! Phil 16:58, 5 September 2022 (EDT)

I can confirm that it says "Deryni Magic" on the title page of my copy. I also note that our title record is dated "1990-00-00" and presumably needs to be changed to "1991-01-00". Ahasuerus 17:09, 5 September 2022 (EDT)

Links on the public boards

If you need a volunteer to fix the links on the current page of the public boards, I'll be glad to do it. It might become a cause of confusion as editors come back online. John Scifibones 11:42, 8 September 2022 (EDT)

Which links? HTTP links like http://www.isfdb.org/cgi-bin/pl.cgi?463527 which redirects to https://isfdb.org/cgi-bin/ea.cgi?15478 ? It's a bit irksome that it doesn't redirect to https://www.isfdb.org/cgi-bin/ea.cgi?15478 , but I didn't think it would confuse anyone. Or did you have a different type of links in mind? Ahasuerus (talk) 12:34, 8 September 2022 (EDT)

Click on the link you provide, and you will see you are no longer logged in. (The problem discussed in the Bookmark thread). I corrected all my pages. Only took a few minutes per page. P.S. Just offering to help, maybe it was only a pain for me. John Scifibones 12:43, 8 September 2022 (EDT)

Ah, I see. I am actually logged in both on www.isfdb.org and on isfdb.org, so I didn't immediately recognize the problem when I followed the links. Sure, if you have the time, I would appreciate the help. Ahasuerus (talk) 12:52, 8 September 2022 (EDT)

The links on the current pages of all five 'public' boards are fixed. I'll work on the archived pages as I get a chance. John Scifibones 13:58, 8 September 2022 (EDT)

Many thanks! Ahasuerus (talk) 14:03, 8 September 2022 (EDT)

Murder of a Wife

https://www.isfdb.org/cgi-bin/pl.cgi?23124; I replaced cover with FantLab's which shows full spine. --Username (talk) 12:11, 12 September 2022 (EDT)

Approved, thanks. Ahasuerus (talk) 12:25, 12 September 2022 (EDT)

Searching

Hi. See User_talk:Alvonruff#Searching for a random thought about the search behavior. --MartyD (talk) 14:40, 14 September 2022 (EDT)

Time slip (content tag)

Good evening. You are the primary user of tag "time slip" by a wide margin with 24, about 2/3 of the total (latest title dates: two 2019 novels by Kathryn Lasky). Do you recall your intended scope? Among my own 5 (of ~30 tags total), i recall only the Philippa Pearce novel Tom's Midnight Garden, which is laden with ambiguity: Is time displacement only a dream for Tom? Is there anyone's agency? --Pwendt|talk 20:27, 15 September 2022 (EDT)

I use SFE's definition:

• Rather than deal with a [time] machine's theory and construction [...] many authors prefer to stipulate a "natural", usually one-off, accident that effects whatever time-transfer the story requires. In this encyclopedia's Terminology, the device is referred to as a timeslip.

Time slips are commonly used in romance fiction, which is why so many of my "time slip" titles also have some kind of "romance" tag attached. Ahasuerus (talk) 20:39, 15 September 2022 (EDT)

User Settdigger

Hi, thanks for your reply. I did try my gmail address; no pw reset email ever arrived.

Is there anything else we can do? —The preceding unsigned comment was added by Everyman (talk • contribs) .

I have reset your password manually. I am going to send the new, temporary, password to your email address. Hopefully it will work. Ahasuerus (talk) 12:16, 20 September 2022 (EDT)

Unmerging Contents of a Omnibus Publication

I was updating an omnibus whose contents did not match the publication author credit. It contained a novel that appeared in multiple publications. When I went to the novel record and used Unmerge Titles to unmerge the omnibus from the novel record, it helpfully changed the author name of the new record to match the omnibus, but unhelpfully changed the title to match the omnibus' title. The later would seem to be an error? I'm having trouble thinking of a case where you would want to rename the novel within an omnibus to the omnibus' title automatically. Thanks. -- JLaTondre (talk) 20:24, 20 September 2022 (EDT)

Thanks for the heads-up. I'll take a look, but it may take me a bit longer than usual. I'll be unavailable much of tomorrow. Ahasuerus (talk) 21:29, 20 September 2022 (EDT)

Just as a note so you do not chase it in newer updates - As annoyingly as it works, this had always (or at least for as long as I had been here) worked like that. So when I need to get a title out of an omnibus, I use RemoveTitle and then Edit or Import. Fixing it to actually work as one would expect is not a bad idea - I wonder why it had been implemented that way… I wonder if the multiple possible reference titles (now that the novel is the reference title, it grabs the values from the older work?) are causing the mess. Annie (talk) 23:46, 20 September 2022 (EDT)

Thanks for letting me know. Since it's established behavior, I suggest that we create a Feature Request to change it. Ahasuerus (talk) 11:20, 21 September 2022 (EDT)

Application

First of all: thanks for the tremendous work you and Al did on migrating our project to the new server. It does seem now to run as smoothly as before. Christian Stonecreek (talk) 09:27, 23 September 2022 (EDT)

Thanks. There is still some work that needs to be done behind the scenes -- like tweaking email and automatic log rotation settings -- but we are pretty close to the finish line. Ahasuerus (talk) 11:01, 23 September 2022 (EDT)

I'd also like to apply to be allowed to self-moderate / self-approve. I have learned my lesson and things like not communicating on vital things that were cared for by other editors will not happen again. And on the other hand I'm working on a number of projects which seem to be stuck in the queue for an ever expanding time span - entering European magazines (well, mostly German), adding months of publication based on infos stated in magazines (like here), the seemingly neverending Perry Rhodan complex, and caring for some European authors, at last especially Sławomir Mrożek whose bibliography needs original titles & dates and misses lots of relevant speculative work. Regards, Christian Stonecreek (talk) 09:27, 23 September 2022 (EDT)

The process of becoming a self-approver starts with getting Community Portal support for the application. I didn't comment on your application because I rarely work on other editors' submissions these days, so I am not in a good position to judge. Ahasuerus (talk) 11:01, 23 September 2022 (EDT)

ISBN warnings missing

Can you look at this one? The ISBN the editor tried to add was an ISBN10 form of an ISBN13 we already had - see here - the paper book was already in. I am not sure if the warning for "ISBN already on file" was supressed because it is a 10/13 or because the pre-2007 warning replaced it. In both cases, this seems like a bug. Thanks! Annie (talk) 14:25, 23 September 2022 (EDT)

The old way of displaying yellow warnings supported only one warning per field except for authors. The first yellow warning generated by the code was the one displayed. In this case "10-digit ISBN for a post-2007 publication" happened to be the first warning.

The new way of displaying yellow warnings which I have been working on lately supports multiple warnings per field. I plan to upgrade the rest of the post-submission pages once I finish prioritization and the post-migration cleanup. Still 1,600 ASINs to go... Ahasuerus (talk) 17:06, 23 September 2022 (EDT)

OK then. I was making sure you are aware of the behaviour - I don't remember seeing it before (but then the combination is not very common). Thanks! Annie (talk) 17:12, 23 September 2022 (EDT)

Druid's Tune

https://www.isfdb.org/cgi-bin/view_submission.cgi?5433000; Very old PV by you, 1985 printing uploaded to Archive about 10 years after your PV, I added Amazon cover which says 1984 and looks the same, also changed cover artist, do you disagree with the cover or the change? --Username (talk) 13:07, 25 September 2022 (EDT)

Good points. I have checked my copy, approved the submission and clarified/expanded my original notes. Thanks. Ahasuerus (talk) 13:30, 25 September 2022 (EDT)

COVERART merge review funkiness

Hi. Noticed something a little funky with the "TitleType" field in the review screen for this submission. Captured it here too, just in case -- please delete when you no longer need it. I freely admit it may have always worked this way and I only now noticed.... --MartyD (talk) 10:27, 8 October 2022 (EDT)

Title Merge -- unlike Make Variant -- submissions are still handled by the old submission review code. It uses the "TitleType" row to display:

• title types for non-COVERART titles
• associated cover images for COVERART titles

It's wonky, which is why it was changed in the new submission review code. The latter displays two rows for COVERART titles: one for the title types and one for the associated images. Ahasuerus (talk) 11:21, 8 October 2022 (EDT)

Charles Sheffield / The Nimrod Hunt

Posted on the talk pages of active PVs: Ahasuerus, Willem H., GlennMcG
I am editing and PVing The Nimrod Hunt. There is a pub note stating "Price in Canada: C$4.95". My copy has no Canadian price. Is there a Canadian price on your copy? If we all agree there is not then I will delete this note. I also propose to add a pub note about the discrepancy in the heading of the excerpt on page [407]. This states "...coming in July 1985..." despite Nimrod Hunt being published in August 1986. Teallach (talk) 13:57, 13 October 2022 (EDT)

My copy doesn't have a Canadian price anywhere. Checking Publication Edit History for this pub, I see that the Canadian price was added by User:Bluesman in submission 1045746:

• C$4.95 in Canada. The Canadian books have the US$ price on the spine, but on the cover it is 'blocked" out and the C$ price printed beside the "blocked out" rectangle.

This explanation was simplified in submission 5134917.

Since we have a separate publication record for the Canadian version of this book, I agree that we should delete "Price in Canada: C$4.95". Perhaps we could add something like "Not to be confused with the Canadian edition of this book, which has the US price is on the spine C$4.95 printed on the cover." Ahasuerus (talk) 14:34, 13 October 2022 (EDT)

Excellent: we have 100% agreement amongst the four of us. I have just submitted the edit to make the changes as per my original proposal and have also added the "Not to be confused..." note suggested by Ahasuerus. Teallach (talk) 16:10, 13 October 2022 (EDT)

Minor login bug

Probably been there for years, no real negative impact, so probably not worth spending time on, but just for the record:

• Go to https://www.isfdb.org/cgi-bin/award_directory.cgi as an unlogged in user
• Click on Log In on the sidebar
• Enter credentials and submit (NB: I'm getting the username and password auto-populated by the browser, but I doubt this makes any difference)
• You get sent to https://www.isfdb.org/cgi-bin/directory.cgi (note award_ prefix has been lost) which has the message "First parameter not specified"

Occurs for me in latest Vivaldi and Firefox on Linux. Suspect it affects the other directory pages.

I don't think there's any other impact, but it might be a bit disconcerting for a new user? ErsatzCulture (talk) 11:20, 17 October 2022 (EDT)

Thanks, I'll take a look. I think we have a few Web pages which do not redirect newly logged in users properly. Ahasuerus (talk) 12:29, 17 October 2022 (EDT)

Should be fixed now. Ahasuerus (talk) 12:39, 17 October 2022 (EDT)

All looks good from this end, thanks. ErsatzCulture (talk) 14:22, 18 October 2022 (EDT)

Minor query about Selected Forthcoming Books algorithm

Something that I'm slightly puzzled by, which I'm mentioning only in case it's an indication of something stranger going on...

On Sunday 23rd, I added an ebook reissue of a Gwyneth Jones novel, which is published today. A query of the database shows that Jones has author_marque = 1, which (AIUI) means that new pubs of her work should appear in Selected Forthcoming Books - but this pub doesn't appear, nor do any other works of hers that might have pushed this pub off due to the recent "there can only be one" change. Of the 20 pubs shown, there is a single pub from the 26th, and a couple for the 27th, so it doesn't appear to be the case that there were too many "marque" pubs released today, causing her pub to be pushed out of the 20 slots available.

Re-reading the recent discussion on Community Portal, I see that the list of 20 titles is only regenerated daily, which is why I've held off mentioning this until more than 24 hours have elapsed since I added that pub. However, I'm not sure why it wouldn't show up now? (It's a juvenile title, but I don't think that has any impact on whether something shows in the list?)

NB: in and of itself, this isn't a big problem - however it does make me wonder if the list of 20 titles hasn't been updated in a timely manner? ErsatzCulture (talk) 10:45, 25 October 2022 (EDT)

That's a good question. Let me finish the patch that I am working on at the moment and I will review the logic on the development server. Thanks for reporting the issue. Ahasuerus (talk) 14:31, 25 October 2022 (EDT)

Well, there is good news and then there is bad news.

The good news is that my review of the code that builds the list of front page publications identified a flaw which could cause some pubs to be sorted incorrectly within each date. The flaw has been corrected.

The bad news is that I couldn't recreate the reported problem on the development server. The ebook in question was correctly identified and displayed by the software. Also, running the MySQL query on the live server returned a list of pubs which included it and the nightly job log didn't show any errors. My guess is that something went wrong during the post-processing phase of the nightly job, but I can't figure out what it was after the fact. There may be a difference between the way the development server and the live server are configured. (I have checked the time zone settings and they are identical.)

Let's wait and see if this issue pops up again. When it does, I will try to debug it while it's still happening on the live server. Ahasuerus (talk) 17:57, 26 October 2022 (EDT)

Thanks for checking. I'll let you know if I see it occur again, although I wonder if the closeness of adding the pub, and its pub date is a factor - obviously ordinarily I'd prefer to get new pubs in more than than a couple of days before their due date. ErsatzCulture (talk) 08:28, 27 October 2022 (EDT)

Before we changed to daily calculation, I was adding books and seeing them showing up on the list as soon as they were added to the DB so if it is because of the close date, that's something new with the new mechanisms. Annie (talk) 16:02, 27 October 2022 (EDT)

I can't think of anything in the current code that would rely on the "close date" factor. Except for a 1-23 hour delay due to the nightly job running once a day, of course, but this 2022-10-25 pub was entered on 2022-10-23 at 12:27pm, so it should have been picked up by the nightly job on 2022-10-24 ans well as on 2022-10-25. Since the nightly job ran successfully on 2022-10-25, I am at a loss to explain the anomaly :-\ Ahasuerus (talk) 19:49, 27 October 2022 (EDT)

When are you filtering for one per author - that is the other thing changed lately so I wonder if we did not lose it because of that? I wonder if this one did not end up kicking the other one out somehow. It is added on the same day and both its variant title and its canonical are newer than the one we missed. It should not make a difference as it was not making the list at that point but if you are filtering too early, it WILL supplant the other. Annie (talk) 13:47, 28 October 2022 (EDT)

That's a good question. I'll take a look. Thanks. Ahasuerus (talk) 15:06, 28 October 2022 (EDT)

Annie's guess was right on target. I plan to update the algorithm tomorrow. Ahasuerus (talk) 20:27, 4 November 2022 (EDT)

I am still working on it. There are more scenarios with co-authors than I originally realized. For example, if a publisher is reprinting Kuttner/Moore's books, you can have a 1940 Kuttner title, a 1957 Moore title and a 1947 Kuttner/Moore title reprinted on the same day. Normally, it wouldn't be a major issue, but we have Anderle and his legion of collaborators. It would be nice to avoid having the front page taken over by them. Ahasuerus (talk) 18:53, 6 November 2022 (EST)

I have installed the latest version which should fix the issue that we ran into with Gwyneth Jones. However, I had to give up on handling multi-author permutations like the Kuttner/Moore one outlined above. I now use each pub's first author ID (starting with the lowest number) for author identification purposes. There are just too many possible scenarios and they are not worth the headaches that they cause. Ahasuerus (talk) 19:00, 12 November 2022 (EST)

(dedent)

Something that might be worth adding, is to exclude any pubs which have the WatchPrePub template. I've just added a new reprint of a Philip Pullman novel that comes out in a couple of days, but Amazon still have a placeholder cover. We probably wouldn't want that to show up on the front page, and whilst in this particular case I could probably avoid that by not attaching the placeholder cover to the submission, it might be good to avoid these pubs which an editor has marked as potentially dubious. (NB: there's a different hc reprint of this same novel on the same day, so that might be the one that gets picked up anyway.) ErsatzCulture (talk) 17:11, 7 November 2022 (EST)

I strongly disagree - the template is used for a LOT of things not just for cover. It may be added for a price check or to check illustrator or a narrator on an audiobook or a suspect length of a book. This does not mean we should not show it. If a book is so suspect that it needs to be removed from the list, it should not have been added pre-publication to start with. Now if you want to suppress WatchPrePub|cover, then maybe but even that... the lack of cover is not a reason not to show a book IMO. Annie (talk) 17:16, 7 November 2022 (EST)

Actually, the algorithm has always excluded pubs without covers. Ahasuerus (talk) 17:54, 7 November 2022 (EST)

Ah, I see. Then nothing to change I guess :) Annie (talk) 17:56, 7 November 2022 (EST)

It should be easy enough to add a check for "WatchPrePub|cover" in the Notes field. We couldn't easily do it back when the list of pubs was built dynamically, but now that it's done once a day it shouldn't be an issue. Ahasuerus (talk) 18:20, 7 November 2022 (EST)

When I use it, I don't add a cover anyway so if you are already filtering for that, the ones I add are in the clear. Not sure if John adds the cover in such cases or not. Annie (talk) 18:29, 7 November 2022 (EST)

I usually put the placeholder cover in, just so it's super clear that it's a screw-up by Amazon and/or the publisher, as opposed to a case of me forgetting to enter the URL. In theory WatchPrePub covers either case, but having the placeholder image stands out more. ErsatzCulture (talk) 14:05, 8 November 2022 (EST)

I disagree. Having the placeholder cover looks sloppy to me and I would usually remove placeholder covers when I see them and I am editing a book - we are better off without a cover than with a "Coming in November 2022" cover or a cover that never existed (even with the template - things happen, books and details remain unfixed for a long time). Trying to untangle if a cover was ever published 10 years down the road is a long and complicated process... We are not an Amazon-copy - we do not repeat their screw-ups when we know they are messed up. We can note that the sources do not have a proper cover but using a cover we know is a placeholder because a source uses it sounds a bit counter-logical to me. What if Kobo and Amazon have a different placeholder - which one would you use? :) But that's just me. Annie (talk) 14:11, 8 November 2022 (EST)

This was a common issue with American translations of Japanese "light novels" a few years back. Publishers typically reuse Japanese cover art, so they would upload the original Japanese cover 3-4 months ahead of the publication date, then replace it with the release version which has the Japanese text replaced with English words.

It was one of the main reasons why I changed my policy of entering "forthcoming" light novels. I now wait for them to be published and enter them after the fact. However, back when I was still trying to be proactive, I never linked to Amazon's Japanese URLs and left publication records cover-less until English-language URLs became available. Ahasuerus (talk) 14:46, 9 November 2022 (EST)

Unless I hear an objection, I will change the algorithm to skip pubs with "WatchPrePub|cover" in Notes tomorrow. Ahasuerus (talk) 19:02, 12 November 2022 (EST)

I am afraid I am sick again, so this will have to wait until after I recover. Ahasuerus (talk) 13:15, 14 November 2022 (EST)

Done. The new logic will kick tomorrow morning. Ahasuerus (talk) 19:28, 15 November 2022 (EST)

Thanks for working on this. ErsatzCulture (talk) 16:05, 16 November 2022 (EST)

Sure thing. Ahasuerus (talk) 16:07, 16 November 2022 (EST)

Another slightly weird one: Top Forthcoming page

This is only showing 6 titles as I type this just after midnight UK time Sunday/Monday. I've not checked the code, but the following query returns the same results as that page:

   select title_id, title_title, title_copyright, title_views
   from titles
   where title_copyright >= '2022-10-31' and title_copyright <= '2023-12-31'
   and title_views > 0
   order by title_views desc limit 100;

IIRC there was an issue when the server/database was upgraded, that seemed to be related to write locks on this table, and that you'd changed something to get around it. My suspicion is that maybe the views counts aren't being updated - I'm not sure, but some of those titles are ones that have been in the DB for a while, but got delayed, so I'd not be in the least bit surprised to find the counts are all from before the DB upgrade.

I'm not sure that the pages get enough traffic for the view metrics to be meaningful (in the past I've seen stuff that has had problematic pubs that needed multiple edits, and I've wondered if that has caused those titles to move up in the table), so personally I'd be quite happy to have the link to that page removed, until such time as any fixes can be put in place. ErsatzCulture (talk) 20:21, 30 October 2022 (EDT)

You are right -- this query wasn't updated when the counters were moved to separate tables. I thought I found all of them, but apparently I missed this one. Unfortunately, I am too sick to code at the moment, but I'll add it to my list of things to tackle when I feel better. Thanks for identifying the problem. Ahasuerus (talk) 23:02, 30 October 2022 (EDT)

Thanks for checking. Obviously there's no hurry on this fairly minor part of the site. ErsatzCulture (talk) 12:26, 31 October 2022 (EDT)

And fixed. The new version will become available next Sunday morning. Ahasuerus (talk) 14:20, 31 October 2022 (EDT)

We are back in business. Again, thanks for identifying the issue. Ahasuerus (talk) 21:45, 6 November 2022 (EST)

Thanks - just had a quick look at it, and it seems a lot more plausible now. ErsatzCulture (talk) 17:12, 7 November 2022 (EST)

Hungarian Publications without Transliterated Titles

It appears the Hungarian Publications without Transliterated Titles didn't run this week, I cleared the 101 publications last week. No rush, just letting you know. John Scifibones 14:27, 31 October 2022 (EDT)

Checking... Ahasuerus (talk) 15:10, 31 October 2022 (EDT)

I have identified and recreated the bug on the development server. When a weekly job doesn't find any problematic records for certain cleanup reports, it doesn't delete what the previous weekly run had found. The bug only affects a subset of the weekly reports. Thanks for reporting the issue. Ahasuerus (talk) 17:38, 31 October 2022 (EDT)

Thanks for looking into this. John Scifibones 18:10, 31 October 2022 (EDT)

The software has been fixed. The counts should be corrected next Sunday morning when the weekly job runs again. Ahasuerus (talk) 16:12, 2 November 2022 (EDT)

Everything appears to have been fixed. Ahasuerus (talk) 21:45, 6 November 2022 (EST)

Question about an author image

Hello Ahasuerus,

Can you take a look at this submission. There is (and was) no warning for unknown site but the site is not on the list. Do we miss entries in the Wiki page or is there a software issue not detecting something properly? Thanks! Annie (talk) 12:38, 14 November 2022 (EST)

I'll take a look. Thanks for the report. Ahasuerus (talk) 13:06, 14 November 2022 (EST)

A recent change made as part of the post-submission upgrade project messed up yellow warnings for Edit Author submissions. Bug 823, "Unauthorized author images do not display a yellow warning", has been created. Ahasuerus (talk) 13:14, 14 November 2022 (EST)

It should be fixed now. Ahasuerus (talk) 13:48, 23 November 2022 (EST)

Counts of pending submissions by submitter coloring

First, thank you for adding the filtering option on the submission list. That has been very useful. However, in the normal process of "if you add a feature, you will just get asked for more" ;-) , would it be possible to color the usernames in the 'Counts of pending submissions by submitter' table with the same colors used in the submission table? That would make it easy to see which ones can be skipped vs. clicking on it and then seeing the coloring. Thanks. -- JLaTondre (talk) 09:52, 19 November 2022 (EST)

Originally I planned to use the same colors in the new table. Unfortunately, it turned out to be somewhat more difficult to do than expected. I wasn't feeling well, so I deployed what I had as "version 1.0". I plan to add color-coding once I feel better and finish the current patch. Ahasuerus (talk) 13:32, 19 November 2022 (EST)

And done. Ahasuerus (talk) 09:22, 20 November 2022 (EST)

Thank you! -- JLaTondre (talk) 12:06, 20 November 2022 (EST)

Glad to be able to help. Ahasuerus (talk) 13:07, 20 November 2022 (EST)

More potential finessing of the forthcoming books algorithm

These are pretty minor in the overall scheme of things, and may well be more hassle than it's worth, but just mentioning for the record:

The US tp of Adrian Tchaikovsky's Eyes of the Void is out today. However it doesn't show up in forthcoming books because it has been usurped by Thursday's UK release of Children of Memory. For the "highlander" there-can-only-be-one display logic, it might be nicer to priorize earlier pubs over later ones, as the latter will get their chance after the earlier ones drop off the page after their pub date. ErsatzCulture (talk) 11:32, 22 November 2022 (EST)

At this time the "Highlander" algorithm picks the latest title date. In this case Eyes of the Void was first published on 2022-04-28 while Children of Memory was first published on 2022-11-24, so the algorithm picked the latter. This is primarily done to account for publishers re-releasing multiple books in the same series at the same time since we want the latest installment to be displayed. Ahasuerus (talk) 07:22, 23 November 2022 (EST)

Also, I think you said the most recently entered pub is the one that gets picked? ErsatzCulture (talk) 11:32, 22 November 2022 (EST)

Not quite. The algorithm uses the lowest author ID for each pub. Thus, if you have two pubs co-authored by Michael Anderle and Co, the algorithm will likely use Anderle's author record for the purposes of determining the author because Anderle probably has a lower author ID than his co-conspirators. Ahasuerus (talk) 07:25, 23 November 2022 (EST)

Purely for aesthetic reason, it might be nice to prefer hc/tp/pb pubs over audio ones, so that all the images are a consistent size/ratio. The aforementioned Children of Memory is the only square audio cover against 19 rectangular print/ebook ones, and it could just have easily been the UK hc or ebook cover. ErsatzCulture (talk) 11:32, 22 November 2022 (EST)

Al is currently experimenting with a front page redesign on isfdb2.org, our staging server. I am not sure how this new layout will handle audio books. Ahasuerus (talk) 07:30, 23 November 2022 (EST)

Thanks for response(s). I note that today Children of Memory has switched to the ebook, so I guess that determination is down to whatever arbitrary ordering the SQL query returns? ErsatzCulture (talk) 12:58, 23 November 2022 (EST)

Pretty much. The SQL query is sorted by "publication date", then by "Publication title". If 2+ pubs have the same publication date and the same title -- which is what usually happens when multiple editions of the same book are released on the same day -- their order is arbitrary. We could certainly make the query pick hardcovers over paperbacks and paperbacks over ebooks if desired. Ahasuerus (talk) 13:47, 23 November 2022 (EST)

Neither of these are particularly common scenarios - although I'm trying to be more proactive on adding UK audios, so maybe it might happen more often in future - so any fix for this would be very low priority IMHO; perhaps something that might be worth looking at if/when other changes are made to that logic? ErsatzCulture (talk) 11:32, 22 November 2022 (EST)

Web Page Diffs

Please see this submission: The web page field is showing a diff. However, the two URLs displayed are the same. Minor issue, but would be nice to know there is no change. -- JLaTondre (talk) 08:38, 25 November 2022 (EST)

This 2022-11-15 submission is effectively a duplicate of submission 5493645, which added the same URL on 2022-11-23. The underlying software issue will be addressed in FR 1514, "Enhance submission review pages to look for unchanged submitted values". Unfortunately, I need to finish upgrading the "submission review" logic before I can get to it. Still 7 pages to go and they happen to be some of the more complex pages... Ahasuerus (talk) 08:56, 25 November 2022 (EST)

Oh, so the diffs are computed at submission time? I knew the listing of changed values was, but I thought the coloring was done at review time. Thanks for the explanation. -- JLaTondre (talk) 09:40, 25 November 2022 (EST)

Perhaps I misunderstood the question. When I look at the linked submission, I don't see anything in the "Warnings" column. Are you seeing something different? Ahasuerus (talk) 12:48, 25 November 2022 (EST)

I was referring to the web page field being red in the Current Record column and green in the Proposed Changes column even though the values are the same. I was expecting them to both be green since they are the same value (same as is done on with comparisons on other change types). I was assuming the coloring was applied based on comparisons at the time the moderation screen is created. -- JLaTondre (talk) 14:22, 25 November 2022 (EST)

Oh, I see. Sorry, I am colorblind, so colors do not stand out to me. Currently the coloring logic is based on the presence/absence of data on the left and on the right at the time the submission is displayed. The logic doesn't compare/analyze the values. I plan to change it as per FR 1514, but it will have to wait until the submission review rewrite is finished. Ahasuerus (talk) 14:44, 25 November 2022 (EST)

No problem. It is a minor issue. Thanks. -- JLaTondre (talk) 16:13, 25 November 2022 (EST)

The Russian Quartet

Please see this. The two displayed series names are identical. A hidden character issue? I tried editing them, but it showed no change. Thanks. -- JLaTondre (talk) 16:12, 25 November 2022 (EST)

The two series names appeared to be identical, so something must have gone wrong at the software level. I have fixed the data on the main server and will do more poking once I restore the latest backup on the development server. Thanks for letting me know. Ahasuerus (talk) 17:37, 25 November 2022 (EST)

I should have realized that restoring the backups from 9:30am wouldn't help because these series records were created at 4:09pm. So much for that.

One thing that stands out is that the two submissions which created two identical series records -- 5490674 and 5490675 -- were both approved at 16:09:04. My best guess is that it is this simultaneous approval that caused the issue. Approval processes check the database to see whether a series record with the specified series name already exists. If it does, then they determine the series ID and use it. If it doesn't, then they creates a new one. In this case two approval processes ran in parallel, so each thought that "The Russian Quartet" was a new series and proceeded to create a new series records. (There is no locking at the application or database level.)

Do you happen to remember how you were able to approve two submissions at the same time? Did you have two separate Web pages open, by chance? Ahasuerus (talk) 19:48, 25 November 2022 (EST)

Yeah, when processing a series of submissions, I tend to open them in multiple tabs and work through the tabs. That is especially true when using the new 'filter submissions by user' option since when doing that the next submission button is not guaranteed to take you to that user's next submission (since it is based on the whole queue and not the filtered queue). However, I would not have thought I would have clicked through them fast enough for it to be the same second - even when using keyboard shortcuts, it's not instantaneous. However, there were a couple of periods when things were acting a little slow (some page loads were slower than typical). It's possible the first approval hung-up a bit so it ended up being simultaneous with the second. -- JLaTondre (talk) 22:12, 25 November 2022 (EST)

Yes, it seems likely. Certain combinations of queries lock entire tables, which is particularly impactful when the affected table is "titles" since it has over 2 million records. While a table is locked, all other queries that want to access it are put on hold. This can lead to two "Edit Title" approvals getting queued up right next to each other. When the lock is released, the two "Edit Title" processes are executed in parallel and you can get the result that you ran into.

Unfortunately, I don't think there is a simple fix for this problem. We would need to add locking to our queries, which would take a fair amount of development time to implement. Ahasuerus (talk) 22:35, 25 November 2022 (EST)