Difference between revisions of "User talk:Ahasuerus"

From ISFDB
Jump to navigation Jump to search
(→‎Weird series ordering: More thoughts)
 
(352 intermediate revisions by 19 users not shown)
Line 1: Line 1:
See [[User talk:Ahasuerus/Archive]] for discussions prior to 2023.
+
See [[User talk:Ahasuerus/Archive]] for discussions prior to 2024.
  
 
{| style="width: 85%" cellpadding="20" align="center"
 
{| style="width: 85%" cellpadding="20" align="center"
Line 7: Line 7:
 
|}
 
|}
  
== Cornish ==
+
== Corrupted publication record ==
  
Hi, and Happy New Year!  Sorry to add to your plate, but it looks like we need Cornish for {{A|Myghal Palmer}} and {{P|371453|Rebellyans}}. In the obituary, his brother-in-law says this was published in Cornish and that at the time (2005) Palmer was responsible for 4 of the 6 (sic) books published in revived Cornish.... --[[User:MartyD|MartyD]] ([[User talk:MartyD|talk]]) 14:02, 3 January 2023 (EST)
+
I saw [https://www.isfdb.org/cgi-bin/pl.cgi?589785 this one] on one of the cleanup reports. The software will not allow corrections. Do we need to create a new publication record and delete this one? [[User:Scifibones|<b>John</b> <small>Scifibones</small>]] 08:53, 27 January 2024 (EST)
  
: No worries! Cornish is an [https://www.loc.gov/standards/iso639-2/php/code_list.php ISO 639-2-recognized language], so it doesn't cause any issues. I added it [https://www.isfdb.org/cgi-bin/view_submission.cgi?5529294 a couple of minutes ago]. Happy New Year! [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 14:23, 3 January 2023 (EST)
+
: Could you please clarify what you mean by "the software will not allow corrections"? The External ID field had a very long URL (instead of an ID), which distorted the display in some browsers, but I could still access the "Edit" link by scrolling to the right in Firefox. I then found the right PORBASE ID and replaced the long URL with it. It seems to have fixed the issue. Does it look OK now? [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 10:28, 27 January 2024 (EST)
  
::Such speedy service!  TYVM! --[[User:MartyD|MartyD]] ([[User talk:MartyD|talk]]) 20:51, 4 January 2023 (EST)
+
:: When I entered the correct PORBASE ID, It reverted back to the incorrect previous link when looking at the Proposed Publication Update Submission' screen. As a result, I cancelled the edit. Not sure why that didn't happen to you. Regardless, it is correct now.
 +
::P.S. It probably was allowing the change but the proposed changes column was likely off my screen. Thanks, [[User:Scifibones|<b>John</b> <small>Scifibones</small>]] 12:37, 27 January 2024 (EST)
  
== AddPub Approval page issue ==
+
::: Oh, I see. I vaguely recall experimenting with HTML tables to ensure that they wouldn't do this at some resolutions, but I think I ran into various technical issues and catch-22s. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 13:44, 27 January 2024 (EST)
  
When the title of the new publication does not match the title of the record you are adding into, there is no warning anymore. See [https://www.isfdb.org/cgi-bin/view_submission.cgi?5561004 here]. It cannot happen outside of an API call (as the field is greyed out) but that makes processing Fixer's AddPub submissions extremely finicky (and is potentially going to lead to more missed mismatches if anyone else uses the API to submit these and the handling moderator relies on the screens to tell them of a mismatch). [[User:Anniemod|Annie]] ([[User talk:Anniemod|talk]]) 14:28, 27 January 2023 (EST)
+
== Human-Machines ==
: PS: I think that the problem is that you never show the Publication title now on the screen - so there is no place for the warning to be shown. [[User:Anniemod|Annie]] ([[User talk:Anniemod|talk]]) 14:30, 27 January 2023 (EST)
 
  
:: I see. Thanks for reporting the problem. Let me finish testing the patch that I put together this morning and then I'll work on fixing the bug. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 15:04, 27 January 2023 (EST)
+
https://www.isfdb.org/cgi-bin/pl.cgi?17511; Archive.org cover has a price sticker so you may want to find another image to replace the unstable Amazon one that's there now. --[[User:Username|Username]] ([[User talk:Username|talk]]) 18:22, 2 February 2024 (EST)
  
::: OK, I think I have it fixed on the development server, but it's 6:30pm on the East Coast and I don't trust my brain to test things thoroughly at this hour. I'll do the testing tomorrow morning. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 18:38, 27 January 2023 (EST)
+
: Updated, thanks. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 18:33, 2 February 2024 (EST)
:::: No worries - I know to watch out for it and I do not think we have anyone active now that uses the API so we should be fine for a few days. [[User:Anniemod|Annie]] ([[User talk:Anniemod|talk]]) 19:11, 27 January 2023 (EST)
 
  
::::: OK, I think I fixed everything. Please let me know if anything looks wrong. Thanks. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 13:31, 28 January 2023 (EST)
+
== Hidden World ==
:::::: Looks good. Will take a second to get used to it being down there but it makes more sense with how the submission page is structured anyway :) [[User:Anniemod|Annie]] ([[User talk:Anniemod|talk]]) 17:59, 30 January 2023 (EST)
 
  
::::::: I figured that having a complete Title record in the Title table and a complete Publication record in the Publication table made more sense. The reviewer no longer needs to guess which Title field values are re-used by the Publication table.
+
https://www.isfdb.org/cgi-bin/view_submission.cgi?5884849; PDF, cover, Mantong. --[[User:Username|Username]] ([[User talk:Username|talk]]) 23:14, 7 February 2024 (EST)
  
::::::: I also realized that, for manually created AddPubs, it's possible for the pub's title/authors to get out of sync with the associated title's title/authors. All it takes is for an Edit Title submission to be approved before the AddPub submission is processed. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 18:07, 30 January 2023 (EST)
+
: Approved, thanks. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 08:56, 8 February 2024 (EST)
  
== Mismatched Quotes Weirdness ==
+
== Deryni Magic Question ==
  
There is a mismatched quotes warning for the synopsis field in [https://www.isfdb.org/cgi-bin/mod/submission_review.cgi?5583057 this] submitted edit.  The warning appears in the proposed value column with the warning cell completely missing.  I realize that this is because the missing closing quote makes the browser think that the anchor tag is not finished.  I don't know if we want to consider escaping values here, or if this is a rare enough occurrence that we shouldn't worry about a cosmetic issue.  In any case, I'll leave it un-approved so you can take a look.  Thanks. --Ron ~ [[User:Rtrace|Rtrace]]<sup>[[User talk:Rtrace|Talk]]</sup> 11:05, 16 February 2023 (EST)
+
Hi Ahasuerus -
  
: I see. I think this issue is limited to Notes and Synopsis fields because they are the only ones where we allow embedded HTML (although I see that [[Help:Using Templates and HTML in Note Fields]] doesn't mention Synopsis.) I suppose the ideal solution would be to tell the browser that it should stop parsing HTML at the end of the current table cell, but I am afraid I don't know of a way to do it. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 12:04, 16 February 2023 (EST)
+
[[User:Anniemod|Annie]] has posed [[User talk:Rtrace#Deryni_Magic|this question]] on my talk page. I found that original edits may may have been yours back in 2006.  Could you take a peek when you have a moment (and if you can remember why you did something 18 years ago!).  Thanks. --Ron ~ [[User:Rtrace|Rtrace]]<sup>[[User talk:Rtrace|Talk]]</sup> 21:18, 13 February 2024 (EST)
  
== Yellow warning request ==
+
: Done. Thanks for the ping. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 22:49, 13 February 2024 (EST)
  
I think we need one more yellow warning on the approval screen: when AddPub had been already submitted and someone changes the type of the original we are adding to, you don't get any indication of it. Example [https://www.isfdb.org/cgi-bin/view_submission.cgi?5589034 here]. I swapped the type from novel to chapbook pre-approval so I can make it in one step so I knew to check but if the approver does not open the resulting new publication, there is nothing to tell them that the work just approved needs work (And with the type missing from the top, they cannot even spot it on the screen). [[User:Anniemod|Annie]] ([[User talk:Anniemod|talk]]) 11:48, 23 February 2023 (EST)
+
== What we enter in the "Artist" field ==
: PS: I think we may end up in the same situation with a ClonePub as well - I just don't have one handy as an example. Thanks! [[User:Anniemod|Annie]] ([[User talk:Anniemod|talk]]) 11:56, 23 February 2023 (EST)
 
  
:: Excellent points. {{FR|1561}}, "Enhance AddPub/ClonePub post-submission pages". [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 17:54, 23 February 2023 (EST)
+
Ahasuerus: The table 'What we enter in the "Artist" field' which you created in your post 11:33, 19 February 2024 (EST) under [https://www.isfdb.org/wiki/index.php/Rules_and_standards_discussions#Secondary_source_artist_credit_in_face_of_credit_change_over_time this thread] is very useful. It is much easier to follow and understand than the wording under bullet point "Artist" in [[Template:PublicationFields:CoverArt]]. I recently referred to the table for a separate issue about cover artists [https://isfdb.org/wiki/index.php/User_talk:GlennMcG#Theodore_Sturgeon_.2F_Beyond here].
 +
<br>
 +
Could you please add the table to the help page. [[User:Teallach|Teallach]] ([[User talk:Teallach|talk]]) 17:04, 24 February 2024 (EST)
  
::: All done. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 23:41, 7 March 2023 (EST)
+
: Thanks for the reminder! I have been sick most of the last week and didn't want to touch Rules and Standards discussions until I was back up to 100%. Once I feel better, I'll make sure to check on the R&S page that it's OK to add the table to Help. Thanks. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 17:50, 24 February 2024 (EST)
:::: Awesome! Can you look at [https://www.isfdb.org/cgi-bin/view_submission.cgi?5597998 this one]. See the top of the screen that says The Scourge Between Stars • (2023). Historically, and everywhere on the server, the year is shown that way anywhere ONLY if the title date is different from the one of the publication you are working on - so different from 2023-04-04. So seeing a year in bracket, always sent me doing sanity check on dates to see if one may need adjusting. But they match here. Is that intentional? [[User:Anniemod|Annie]] ([[User talk:Anniemod|talk]]) 11:20, 9 March 2023 (EST)
+
::No problem. There is no hurry. I am sorry to hear you have been unwell and wish you a speedy recovery. [[User:Teallach|Teallach]] ([[User talk:Teallach|talk]]) 12:47, 25 February 2024 (EST)
  
::::: It looks like it was an oversight in SVN patch 1108, which implemented {{FR|1227}}, "Display the full title line for Add/ClonePub submissions", on 2023-03-05. I am busy today, but I hope to get it fixed tomorrow. Thanks for identifying the issue! [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 14:30, 9 March 2023 (EST)
+
::: Thank you! [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 13:20, 25 February 2024 (EST)
  
:::::: No rush and if it ends up being too complicated, I can get used to it behaving this way going forward. It looked like a quick way to see that the ebook date is not the same as the paper we are adding it to when I do the ebooks for Forthcoming books - that made me recheck the date on the paper one as well a few times today. I can just start comparing the dates on my own instead and ignore the year up there - both dates are on the screen now after all. :) [[User:Anniemod|Annie]] ([[User talk:Anniemod|talk]]) 18:23, 9 March 2023 (EST)
+
== Image backups ==
  
::::::: It should be fixed now. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 17:03, 11 March 2023 (EST)
+
Hi,
  
== Author birthplace question ==
+
I see you updated the downloads page to note that image backups are being redone.  This reminds me of something that's puzzled me for a while, and which I meant to ask you about months (years?) ago.
  
The editor originally entered the birthplace for [https://www.isfdb.org/cgi-bin/ea.cgi?356698 M. L. Weems] as 'Anne Arundel County, Province of Maryland, Thirteen Colonies, British America'; triggering an exception for noncompliance with [https://www.isfdb.org/wiki/index.php?title=Template:AuthorFields:BirthPlace this template]. I tried substituting 'England, Kingdom of Great Britain' for 'Thirteen Colonies, British America', but the software still see it as an exception. Is 'Province of Maryland' causing the software to look for USA? What is the correct fix? I'm stumped. [[User:Scifibones|<b>John</b> <small>Scifibones</small>]] 16:55, 25 February 2023 (EST)
+
Am I right in thinking that when those zips are generated, it's not an incremental backup style thing where you just need to download the changes/deltas, but rather that they are completely regenerated, and that you'd have to download the full set of zips to have an accurate and complete collection? I vaguely recall that at some point in the past, I'd been downloading the zips in a fairly leisurely manner over a period of days/weeks, and had got maybe 80% of the way through them, and then the zips were regenerated, and I assumed that I had to restart the set.
  
: Checking the code, I see that it expects the names of US states to be followed by ", USA" with a few exceptions: California allows "Baja California", Hawaii allows "Kingdom of Hawaii" and "Republic of Hawaii", Montana allows "Bulgaria", etc. Some of the original 13 colonies allow ", British Empire", but Maryland is not one of them. I'll need to update the code to support ", British Empire" for Maryland and the rest of the colonies. Thanks for identifying the problem! [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 17:12, 25 February 2023 (EST)
+
Would it be possible to have a bit more information on the download page about how they work?  NB: I haven't actually ever done anything with the zips I downloaded - I rarely run the full Apache website locally, which I imagine is the main intended use case for the image backups - but I always thought they had the potential to be the foundation of an interesting project. Thanks! [[User:ErsatzCulture|ErsatzCulture]] ([[User talk:ErsatzCulture|talk]]) 04:35, 5 March 2024 (EST)
  
:: {{Bug|828}} has been created. We'll probably need to update the Help template as well. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 17:14, 25 February 2023 (EST)
+
: That's right: the images hosted by Google Drive are a complete copy of the images hosted by the live ISFDB server. I have added a few more details to the description. Does it make more sense now? [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 14:31, 5 March 2024 (EST)
 +
:: Thanks.  What you've added makes sense, but it's still not clear (to me at least) from the text there that the directories all get updated when new zips are created. Are the 0-9/a-f (and the 2 digit subdirectories) just arbitrary hex digits, maybe the first digits of a checksum or something like that?  (That question is slightly rhetorical; I imagine I could find the answer out for myself if I looked through the source code.)
 +
:: If the tarballs had date suffixes, similar to the database backups, then I think that would make it more obvious that the full set needs re-downloading.  However, I guess the downside of that is that it would break any existing tooling for downloading the image backups, and that if you weren't careful you might end up with multiple dated tarballs and/or image directories.  [[User:ErsatzCulture|ErsatzCulture]] ([[User talk:ErsatzCulture|talk]]) 18:25, 5 March 2024 (EST)
  
:: Should I go ahead and update the author in anticipation of the change? [[User:Scifibones|<b>John</b> <small>Scifibones</small>]] 17:42, 25 February 2023 (EST)
+
::: Oh, oh... OK, I think I see what the problem is. "0-9" and "a-f" are subdirectory names created by the MediWiki software to store uploaded images. I am so used to this naming convention that it never occurred to me that it may be confusing. A blind spot, if you will. Let me edit the page and explain the naming convention. Thanks! [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 19:15, 5 March 2024 (EST)
  
::: Please do. It may take me a couple of days to get to it since there is a lot going on right now. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 17:45, 25 February 2023 (EST)
+
:::: Ha, I think this is also a blind spot on my part. Because I don't generally upload my own images (I think it must be in single digits) I forgot that that is all handled by the Mediawiki side of things, and it didn't cross my mind that the directory structure of the images was something that wasn't part of the core ISFDB code. Thanks for clarifying! [[User:ErsatzCulture|ErsatzCulture]] ([[User talk:ErsatzCulture|talk]]) 05:31, 6 March 2024 (EST)
  
:::: I have installed a patch to address the issue. All 13 colonies should be handled properly now. The counts will be updated when the cleanup reports run at 1am EST. Sorry about the delay. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 19:40, 3 March 2023 (EST)
+
== New hotlink site permission ==
  
== Self-Approver ==
+
We have permission to hotlink cover images to a new site, possibly. You can see it [https://www.isfdb.org/wiki/index.php?title=User_talk%3ALawDagstine&type=revision&diff=682322&oldid=682319 here]. If that is sufficient, can we add it to the list? ···[[User:Nihonjoe|<font color="darkgreen">日本穣</font>]] · <small>[[Special:Contributions/Nihonjoe|<font color="blue">投稿</font>]] · [[User talk:Nihonjoe|Talk to Nihonjoe]]</small> 13:18, 21 March 2024 (EDT)
 +
:In anticipation of this being acceptable, there is [https://www.isfdb.org/cgi-bin/pl.cgi?1000727 one publication] that is currently hotlinking to the site. ···[[User:Nihonjoe|<font color="darkgreen">日本穣</font>]] · <small>[[Special:Contributions/Nihonjoe|<font color="blue">投稿</font>]] · [[User talk:Nihonjoe|Talk to Nihonjoe]]</small> 13:29, 21 March 2024 (EDT)
  
Hello, can you please comment on https://isfdb.org/wiki/index.php/ISFDB:Community_Portal#Self-Moderation_Request? --[[User:Stoecker|Stoecker]] ([[User talk:Stoecker|talk]]) 06:44, 11 March 2023 (EST)
+
:: All done. The [https://www.isfdb.org/cgi-bin/pl.cgi?1000727 publication page] now credits "Lawrence Dagstine". [[Template:Image Host Sites]] has been updated. Thanks. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 15:58, 21 March 2024 (EDT)
  
: Done. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 10:03, 11 March 2023 (EST)
+
:::Thanks! ···[[User:Nihonjoe|<font color="darkgreen">日本穣</font>]] · <small>[[Special:Contributions/Nihonjoe|<font color="blue">投稿</font>]] · [[User talk:Nihonjoe|Talk to Nihonjoe]]</small> 17:12, 21 March 2024 (EDT)
  
== Offutt EILSB ==
+
== Place Submission on Hold ==
  
https://www.isfdb.org/cgi-bin/view_submission.cgi?5606444; Do you think the day of publication or the ISBN should be entered? --[[User:Username|Username]] ([[User talk:Username|talk]]) 08:49, 13 March 2023 (EDT)
+
After placing a submission on hold, it would be nice if the resultant page had links back to the submission - both the moderator view and the public view. Currently, it only has a link to the Submission List. But usually when I put something on hold, it is because I plan to do something with that submission. Yes, I can just hit the back button to get the moderator view again. But I often want the public view so I can include the link in a question to the submitter so having that on the on hold page would save a click. Thanks. --&nbsp;[[User:JLaTondre|JLaTondre]] ([[User talk:JLaTondre#top|talk]]) 10:21, 24 March 2024 (EDT)
  
: [[Help:Screen:NewPub#Date]] says that:
+
: Thanks, I'll take a look. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 10:45, 24 March 2024 (EDT)
:* The base date optionally may be made more precise (e.g., supplying the month or day of publication) using information from a secondary source, if that source's date is otherwise consistent with publication's stated date. The source, and which details of the date were obtained from that source, must be recorded in the publication notes.
 
: so we could make the date more precise and state the source in Notes.
 
: Re: ISBN, [[Help:Screen:NewPub#ISBN]] allows padding a 9-digit SBN with a zero to make it a valid 10-digit ISBN, but creating a 10-digit ISBN based on a much shorter catalog ID ("64-490") seems like a stretch. We could always raise the question on the Rules and Standards page. For now I have approved the submission. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 13:49, 13 March 2023 (EDT)
 
  
== Problem with an approved edit ==
+
:: Done. Hopefully, the layout and the colors look OK. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 18:07, 24 March 2024 (EDT)
 +
:::Thank you! Looks fine. --&nbsp;[[User:JLaTondre|JLaTondre]] ([[User talk:JLaTondre#top|talk]]) 18:52, 24 March 2024 (EDT)
  
When you have a few minutes, would you mind taking a look at the thread [https://isfdb.org/wiki/index.php/User_talk:Scifibones#Neal_Stephenson_.2F_Snow_Crash Neal Stephenson / Snow Crash]? Thanks [[User:Scifibones|<b>John</b> <small>Scifibones</small>]] 19:31, 18 March 2023 (EDT)
+
:::: Great! [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 19:00, 24 March 2024 (EDT)
  
: That's odd. I will restore the full backups (which include submission history) on the development server tomorrow morning and see what I can find. Thanks for reporting the issue. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 23:55, 18 March 2023 (EDT)
+
== Galactic Central  ==
  
:: It turns out that this and 4 other publication records were corrupted in 2007-2008. At the time we had major issues with server stability and our software was still going through a "growing pains" phase. I am going to create a database patch and apply it to the live server in a day or two. Until then these 5 publication records' Notes fields will remain uneditable. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 17:06, 19 March 2023 (EDT)
+
Given that the ISFDB is currently heavily dependent on Galactic Central images (12k publication images as of last database dump) and they seem to be in no hurry to implement HTTPS, --&nbsp;[[User:JLaTondre|JLaTondre]] ([[User talk:JLaTondre#top|talk]]) 13:52, 3 April 2024 (EDT)
  
::: Thank you for taking care of this, I know you're busy. [[User:Scifibones|<b>John</b> <small>Scifibones</small>]] 17:11, 19 March 2023 (EDT)
+
: Last I heard the owner had no plans to convert to HTTPS. It's possible that his plans may change at some point since browser manufacturers continue to add restrictions to HTTP-only sites. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 14:08, 3 April 2024 (EDT)
::::Thanks for investigating. I'll wait until you give the all clear and then re-submit the edit. [[User:Teallach|Teallach]] ([[User talk:Teallach|talk]]) 16:56, 20 March 2023 (EDT)
 
  
::::: Glad to be able to help. I have fixed the data and left a note on your Talk page. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 16:15, 21 March 2023 (EDT)
+
have you given consideration to implementing a proxy service?  Apache has a [https://httpd.apache.org/docs/2.4/mod/mod_proxy.html mod_proxy] module or it's pretty straightforward to implement your own[https://stackoverflow.com/questions/3011222/dealing-with-http-content-in-https-pages]. --&nbsp;[[User:JLaTondre|JLaTondre]] ([[User talk:JLaTondre#top|talk]]) 13:52, 3 April 2024 (EDT)
  
::::::Yes, the pub record looks fine now. Thanks for the fix. [[User:Teallach|Teallach]] ([[User talk:Teallach|talk]]) 17:36, 21 March 2023 (EDT)
+
: Thanks for letting me know about these options. I wasn't aware of them. I'll add it to my list of things to look into, but it's a long list, so I am not sure when I may get to it. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 14:08, 3 April 2024 (EDT)
 +
 
 +
Or should we create a clean-up project to start moving these images over to the ISFDB wiki? --&nbsp;[[User:JLaTondre|JLaTondre]] ([[User talk:JLaTondre#top|talk]]) 13:52, 3 April 2024 (EDT)
 +
 
 +
: It would certainly make things easier, in part because of the HTTPS issue and in part because they would be incorporated into our publicly available backup files. However, 12K images is a lot images to migrate. Do we expect to have enough volunteer man-hours to make it feasible? [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 14:08, 3 April 2024 (EDT)
 +
:: Part of the price of self-moderation? ../[[User:Holmesd|Doug H]] ([[User talk:Holmesd|talk]]) 21:53, 3 April 2024 (EDT)
 +
::I have been migrating them as I edit pubs that use them. It will be slow going, but the current broken images are not ISFDB user friendly. --&nbsp;[[User:JLaTondre|JLaTondre]] ([[User talk:JLaTondre#top|talk]]) 08:44, 6 April 2024 (EDT)
 +
 
 +
::: I have created {{FR|1601}}, "Enhance display of HTTP-served images". [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 10:44, 6 April 2024 (EDT)
 +
 
 +
== Baen ISBNs ==
 +
 
 +
''{{p|998070 |Toll of Honor}}'' just came out, and we have the ISBN formatted as 978-1-982193-31-7. The back of the book as well as the copyright page have it formatted as 978-1-9821-9331-7. Do we need to look at the code that adds in the dashes? This may affect more than just Baen books. ···[[User:Nihonjoe|<font color="darkgreen">日本穣</font>]] · <small>[[Special:Contributions/Nihonjoe|<font color="blue">投稿</font>]] · [[User talk:Nihonjoe|Talk to Nihonjoe]]</small> 17:33, 5 April 2024 (EDT)
 +
 
 +
: Checking [https://www.isbn-international.org/range_file_generation the official "ISBN Ranges" page], I see that the hyphenation rules have changed and become more complex. It used to be that the rules for "978-0-" ISBNs had only 6 cases, but now it's up to 21. "978-1- ISBNs also used to have 6 cases, but now they are up to around 50 cases. Other language-specific ISBN rules have also been affected, although not as severely. Let me create a new FR for this change. Thanks for letting me know! [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 17:55, 5 April 2024 (EDT)
 +
 
 +
:: {{FR|1600}} "Update the ISBN hyphenation rules" has been created. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 18:02, 5 April 2024 (EDT)
 +
 
 +
::: And done -- see [https://isfdb.org/wiki/index.php/ISFDB:Community_Portal#ISBN_hyphenation_changed this Community Portal announcement]. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 14:08, 16 April 2024 (EDT)
 +
 
 +
== Murder in Millennium VI ==
 +
 
 +
Please see [https://www.isfdb.org/cgi-bin/view_submission.cgi?5896021 this edit] that impacts your verified pub. Let me know if you agree with changing the credit. Thanks. --&nbsp;[[User:JLaTondre|JLaTondre]] ([[User talk:JLaTondre#top|talk]]) 08:41, 6 April 2024 (EDT)
 +
 
 +
: I don't have this issue handy right now, but the [https://archive.org/details/Dynamic_Science_Fiction_v01n03_1953-06_slpn/page/n65/mode/2up Archive.org copy] is readable. Here is what I see:
 +
:* The title page of the review column, "Readin' and Writhin'" (p.46), credits "Damon Knight and the Editor".
 +
:* There are three reviews. The first two, "Murder in Millennium VI" and "Seetee Ship", are not credited. The third one, "Beachheads in Space" on page 67, is signed "RWL".
 +
:* Of the three reviews, only "Murder in Millennium VI" was reprinted in Damon Knight's ''In Search of Wonder''.
 +
:* We currently credit "Damon Knight and Robert A. W. Lowndes" as the authors of the first two reviews and "RWL" as the author of the third review. We then variant them to their actual authors based on reprint history and textual research.
 +
:* The publication record has notes explaining who the actual authors are and what our evidence is, but individual REVIEW records do not.
 +
: Based on the above, how about we use "uncredited" as the author of the first two reviews instead of "Damon Knight and Robert A. W. Lowndes"? The current variants would remain in place, but we would copy explanatory notes from the publication record to each title record. What do you think? [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 10:00, 6 April 2024 (EDT)
 +
::I pointed Swfritter to this discussion since he has also verified the pub. As you two are the verifiers, I will defer to you both, but your suggestion makes sense to me. --&nbsp;[[User:JLaTondre|JLaTondre]] ([[User talk:JLaTondre#top|talk]]) 10:08, 6 April 2024 (EDT)
 +
:::Sounds OK to me. Especially since there will be plenty of documentation.--[[User:Swfritter|swfritter]] ([[User talk:Swfritter|talk]]) 20:40, 6 April 2024 (EDT)
 +
 
 +
:::: OK, I think I [https://www.isfdb.org/cgi-bin/pl.cgi?102771 got it]. Thanks! [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 23:37, 6 April 2024 (EDT)
 +
:::::Thanks. Original edit has been rejected with an explanation of the change. --&nbsp;[[User:JLaTondre|JLaTondre]] ([[User talk:JLaTondre#top|talk]]) 06:56, 7 April 2024 (EDT)
 +
 
 +
== Wily Writers ==
 +
 
 +
https://www.isfdb.org/cgi-bin/title.cgi?2112269; The web page link gave me a red warning for not being safe. Also, shouldn't title/variant be 2013, not 2014? --[[User:Username|Username]] ([[User talk:Username|talk]]) 19:10, 15 April 2024 (EDT)
 +
:It gives me a 403 error when I try to visit. There must be something going on with the server there. ···[[User:Nihonjoe|<font color="darkgreen">日本穣</font>]] · <small>[[Special:Contributions/Nihonjoe|<font color="blue">投稿</font>]] · [[User talk:Nihonjoe|Talk to Nihonjoe]]</small> 19:43, 15 April 2024 (EDT)
 +
 
 +
:: Apparently the "Wily Writers"' Web site died at some point in the late 2010s. Eventually it was picked up by someone else, but the new owners didn't configure their security certificate correctly, hence the security warning displayed by the browser. I have changed the dates from 2014 to 2013 and replaced the affected links with Wayback machine versions. Thanks for the heads-up. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 20:23, 15 April 2024 (EDT)
 +
 
 +
== How Far Alongside Night? ==
 +
 
 +
https://www.isfdb.org/cgi-bin/pl.cgi?428089; I have some edits adding archived links to the Crown and Ace editions of Alongside Night and another adding afterword mentioned in '87 Avon edition's note; searching for the name Konkin and not finding anything I then noticed you entered the essay in this 2013 edition but name is Konklin (as it also is for another essay). So I think after approval the 2 essays should be merged under the name Konkin; the '99 Pulpless edition is on Google Books and it says Samuel Edward Konkin, III so that's how I entered it, not having any copies or photos of the Avon to verify (no page number, of course). --[[User:Username|Username]] ([[User talk:Username|talk]]) 09:39, 20 April 2024 (EDT)
 +
 
 +
: It was, indeed, a typo. Everything has been approved and merged. I have moved the URL associated with the essay to the Title record and updated Konkin's author page with biographical data and links. Thanks. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 13:29, 20 April 2024 (EDT)
 +
 
 +
== Space Viking ==
 +
 
 +
Adding cover artist, notes and external IDs to your PVd [https://www.isfdb.org/cgi-bin/pl.cgi?31466 Space Vikings].10:59, 21 April 2024 (EDT) {{unsigned|SFJuggler}}
 +
 
 +
: I have approved the submission and expanded the Notes section. One thing to keep in mind is that the dates listed in early Catalog of Copyright volumes are actually "dates of publication as given in the application". It's possible for the actual publication date to be different due to printer- or publisher-originated delays, so I find it useful to add the phrase "date of publication as given in the application" to the Notes field. I have updated the Title record as well. (Later Catalog of Copyright volumes distinguish between "Date of Publication" and "Registration Date", but that's a different kettle of fish.) Thanks! [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 12:45, 21 April 2024 (EDT)
 +
 
 +
== Weird series ordering ==
 +
 
 +
On [https://www.isfdb.org/cgi-bin/pe.cgi?29172 this series], it's not numbering them in order as it ought to. Any ideas why it's switching things around? ···[[User:Nihonjoe|<font color="darkgreen">日本穣</font>]] · <small>[[Special:Contributions/Nihonjoe|<font color="blue">投稿</font>]] · [[User talk:Nihonjoe|Talk to Nihonjoe]]</small> 14:16, 24 April 2024 (EDT)
 +
: That looks like expected actually - titles and subseries do not mix in the series ordered views so you got all numbered Titles first followed by all numbered subseries. [[User:Anniemod|Annie]] ([[User talk:Anniemod|talk]]) 14:57, 24 April 2024 (EDT)
 +
 
 +
:: That's exactly right. If the ISFDB software displayed numbered titles and numbered sub-series together, then we'd have anomalies like:
 +
::* Book #1
 +
::* Sub-series trilogy #1
 +
::** Book A
 +
::** Book B
 +
::** Book C
 +
::* Book #2
 +
::* Sub-series trilogy #2
 +
::** Book X
 +
::** Book Y
 +
::** Book Z
 +
::* Book #3
 +
:: That said, titles and sub-series currently use the same offset and font. Perhaps we should make them look different to facilitate distinguishing between the two type of elements that title series can contain. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 15:12, 24 April 2024 (EDT)
 +
 
 +
:::From my view, if the subseries is ''numbered'' as part of the series, that numbering should be in order. I can see pushing subseries to the bottom of the main series if they aren't ''numbered'' as part of the series. That makes sense. But doing it so that the numbering is 1, 2, 3, 4, 6, 5, 7 doesn't make any sense and will likely cause confusion for anyone viewing the page because people generally expect numbered things to be in order. ···[[User:Nihonjoe|<font color="darkgreen">日本穣</font>]] · <small>[[Special:Contributions/Nihonjoe|<font color="blue">投稿</font>]] · [[User talk:Nihonjoe|Talk to Nihonjoe]]</small> 16:18, 24 April 2024 (EDT)
 +
 
 +
(unindent)
 +
(I have moved the discussion of archive.org-derived information to [[ISFDB:Research_Assistance#Moribito_series]]). [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 20:16, 24 April 2024 (EDT)
 +
 
 +
After mulling it over and running a few database searches, I am beginning to suspect that we may have two different scenarios here. The first one can be seen on [https://www.isfdb.org/cgi-bin/pe.cgi?26381 this Series page] for {{A|Jonathan Maberry}}'s ''Pine Deep''. The original trilogy (2006-2008) is numbered 1-3. There is a follow-up series, [https://www.isfdb.org/cgi-bin/pe.cgi?58892 ''Monk Addison''], which an editor tried to configure -- cumulatively -- as number 4 in the main series. It didn't work too well because the sub-series appears after various unnumbered short fictions titles within the main series.
 +
 
 +
The second scenario can be found [https://www.isfdb.org/cgi-bin/pe.cgi?7597 here]. ''Gotrek and Felix'' consists of 17 novels and a few dozen works of short fiction. It also contains 3 sub-series for the 3 different omnibus editions of the main series. The sub-series are numbered 1, 2 and 3 and appear at the bottom of the page, i.e. after the short fiction. Unlike the ''Pine Deep'' scenario, this is, unambiguously, the expected behavior since the omnibus sub-series are not part of the main numbering scheme.
 +
 
 +
If my understanding is correct, then the ISFDB software currently supports the second scenario, but not the first one. Does this sound about right? [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 20:32, 24 April 2024 (EDT)
 +
:Yes, that seems accurate. ···[[User:Nihonjoe|<font color="darkgreen">日本穣</font>]] · <small>[[Special:Contributions/Nihonjoe|<font color="blue">投稿</font>]] · [[User talk:Nihonjoe|Talk to Nihonjoe]]</small> 20:43, 24 April 2024 (EDT)
 +
 
 +
:: I guess the next question is what we can do about this situation. Let me sleep on it... [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 21:13, 24 April 2024 (EDT)
 +
 
 +
::: No bright ideas so far, I am afraid. I can't think of a way to accommodate these two different scenarios using the database fields that we currently have. Maybe something will germinate over the next few days. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 14:34, 25 April 2024 (EDT)
 +
:::: How about an obvious solution: add a flag/checkbox on the series page which tells the software if it needs to show series and titles mixed based on the numbers OR if they need to be kept separate? With the default being showing them separately (aka "things as they stand now"). [[User:Anniemod|Annie]] ([[User talk:Anniemod|talk]]) 17:32, 25 April 2024 (EDT)
 +
:::: PS: Oops. Did not see your note about using  existing DB fields. You know... maybe we can use the "Series Parent Position" creatively? Add a letter to the number if you want them to sort inside of the titles series (so instead of 1, use 1M (for mixed))? [[User:Anniemod|Annie]] ([[User talk:Anniemod|talk]]) 17:34, 25 April 2024 (EDT)
 +
:::: And we do not even need to show that weird numbering scheme to the editors - make that the DB field value but change the UI to actually show a checkbox. Or something along these lines. The only thing that may be a bit of a hassle is that this field is actually integer, right? So... add an big number to the actual value and drop it for sorting? So instead of 1, record 1001 (how many series we need that need 1000 as a number on the series order?). [[User:Anniemod|Annie]] ([[User talk:Anniemod|talk]]) 17:38, 25 April 2024 (EDT)
 +
 
 +
::::: Re: "flag/checkbox on the series page which tells the software if it needs to show series and titles mixed based on the numbers OR if they need to be kept separate", it's possible for a series to have both types of sub-series. The first type covers sub-series which should be treated as titles for ordering purposes. The second type covers sub-series which should be displayed after all regular titles, including unnumbered titles. If a new flag is to be implemented, it will presumably need to be added to each sub-series, specifying what kind of sub-series it is.
 +
 
 +
::::: That said, I think the first thing that we need to do is to determine what kind of impact having certain sub-series displayed within the main title sequence would have. A few things come to mind:
 +
:::::* We have a cleanup report that finds duplicate series numbers within a series. It would presumably need to be enhanced to look for duplicate numbers of the new type (or a new cleanup report will need to be created.)
 +
:::::* Having a long sub-series -- especially if it has nested sub-series of its own -- appear in the middle of numbered titles could make it harder for our users to understand what the actual order of the main series is. For certain major universes like Warhammer, the resulting "series tree" could be overwhelming.
 +
:::::* Development considerations. Currently the software module responsible for displaying series (a) calls itself recursively AND (b) shares code with our Bibliographic pages. It's a delicate and messy area which is high on my list of things to rewrite once I am done with Fixer migration. Adding additional complexity to it before the code is rewritten may not be optimal.
 +
::::: [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 20:49, 25 April 2024 (EDT)
 +
 
 +
== Japanese collaboration ==
 +
 
 +
I haven't asked them yet, but [https://www.isfdb.org/cgi-bin/ea.cgi?212106 one of the authors in our database] was the creator of the [https://staff.fukuoka-edu.ac.jp/kanamitu/sf/sfdb/index.html Japanese SF Book Database] and the [https://staff.fukuoka-edu.ac.jp/kanamitu/sf/sfdb/sfmgz.html Japanese SF Magazine Database]. He's in his 90s now, and I wondered if I should reach out to him to see if he (or one of his colleagues) might be interested in entering all the information from those databases into ISFDB in order to make it more broadly accessible (since most people outside of Japan have never heard of his two databases). I don't know what their database system is, but there might even be a way to (at least partially) automate the transfer of information. I know they've had some database issues recently so their sites aren't working properly, so I think it's even more important to try to get that information into ISFDB before he dies. Thoughts? ···[[User:Nihonjoe|<font color="darkgreen">日本穣</font>]] · <small>[[Special:Contributions/Nihonjoe|<font color="blue">投稿</font>]] · [[User talk:Nihonjoe|Talk to Nihonjoe]]</small> 17:46, 25 April 2024 (EDT)
 +
 
 +
: The idea certainly has merit. Here are some steps that come to mind:
 +
:* We'll need to determine whether the current database owners/maintainers are able and willing to share the data. There may be pre-existing obligations or commitments which may prevent them from sharing the data.
 +
:* The fact that the Web site is currently partially non-functional raises a flag. We'll need to determine whether they have coherent database backups, database documentation and how many records the backups contain.
 +
:* If they have a coherent database backup and are willing to share it, then it's likely that we should be able to use it. Directly importing data into the ISFDB database would be suboptimal, in part because it would leave us without Edit History, but creating Fixer-style submissions using their data should be viable. We have a number of people with software development backgrounds who may be interested in working on this task.
 +
:* The ISFDB Web API supports putting submissions on hold on behalf of a moderator. We'll probably want to hold these submissions for moderators who have a working knowledge of Japanese.
 +
: Based on the above I would suggest that we start by contacting the owners/maintainers to get answers to the first two issues listed above. [[User:Ahasuerus|Ahasuerus]] ([[User talk:Ahasuerus|talk]]) 18:24, 25 April 2024 (EDT)

Latest revision as of 20:49, 25 April 2024

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

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!

Corrupted publication record

I saw this one on one of the cleanup reports. The software will not allow corrections. Do we need to create a new publication record and delete this one? John Scifibones 08:53, 27 January 2024 (EST)

Could you please clarify what you mean by "the software will not allow corrections"? The External ID field had a very long URL (instead of an ID), which distorted the display in some browsers, but I could still access the "Edit" link by scrolling to the right in Firefox. I then found the right PORBASE ID and replaced the long URL with it. It seems to have fixed the issue. Does it look OK now? Ahasuerus (talk) 10:28, 27 January 2024 (EST)
When I entered the correct PORBASE ID, It reverted back to the incorrect previous link when looking at the Proposed Publication Update Submission' screen. As a result, I cancelled the edit. Not sure why that didn't happen to you. Regardless, it is correct now.
P.S. It probably was allowing the change but the proposed changes column was likely off my screen. Thanks, John Scifibones 12:37, 27 January 2024 (EST)
Oh, I see. I vaguely recall experimenting with HTML tables to ensure that they wouldn't do this at some resolutions, but I think I ran into various technical issues and catch-22s. Ahasuerus (talk) 13:44, 27 January 2024 (EST)

Human-Machines

https://www.isfdb.org/cgi-bin/pl.cgi?17511; Archive.org cover has a price sticker so you may want to find another image to replace the unstable Amazon one that's there now. --Username (talk) 18:22, 2 February 2024 (EST)

Updated, thanks. Ahasuerus (talk) 18:33, 2 February 2024 (EST)

Hidden World

https://www.isfdb.org/cgi-bin/view_submission.cgi?5884849; PDF, cover, Mantong. --Username (talk) 23:14, 7 February 2024 (EST)

Approved, thanks. Ahasuerus (talk) 08:56, 8 February 2024 (EST)

Deryni Magic Question

Hi Ahasuerus -

Annie has posed this question on my talk page. I found that original edits may may have been yours back in 2006. Could you take a peek when you have a moment (and if you can remember why you did something 18 years ago!). Thanks. --Ron ~ RtraceTalk 21:18, 13 February 2024 (EST)

Done. Thanks for the ping. Ahasuerus (talk) 22:49, 13 February 2024 (EST)

What we enter in the "Artist" field

Ahasuerus: The table 'What we enter in the "Artist" field' which you created in your post 11:33, 19 February 2024 (EST) under this thread is very useful. It is much easier to follow and understand than the wording under bullet point "Artist" in Template:PublicationFields:CoverArt. I recently referred to the table for a separate issue about cover artists here.
Could you please add the table to the help page. Teallach (talk) 17:04, 24 February 2024 (EST)

Thanks for the reminder! I have been sick most of the last week and didn't want to touch Rules and Standards discussions until I was back up to 100%. Once I feel better, I'll make sure to check on the R&S page that it's OK to add the table to Help. Thanks. Ahasuerus (talk) 17:50, 24 February 2024 (EST)
No problem. There is no hurry. I am sorry to hear you have been unwell and wish you a speedy recovery. Teallach (talk) 12:47, 25 February 2024 (EST)
Thank you! Ahasuerus (talk) 13:20, 25 February 2024 (EST)

Image backups

Hi,

I see you updated the downloads page to note that image backups are being redone. This reminds me of something that's puzzled me for a while, and which I meant to ask you about months (years?) ago.

Am I right in thinking that when those zips are generated, it's not an incremental backup style thing where you just need to download the changes/deltas, but rather that they are completely regenerated, and that you'd have to download the full set of zips to have an accurate and complete collection? I vaguely recall that at some point in the past, I'd been downloading the zips in a fairly leisurely manner over a period of days/weeks, and had got maybe 80% of the way through them, and then the zips were regenerated, and I assumed that I had to restart the set.

Would it be possible to have a bit more information on the download page about how they work? NB: I haven't actually ever done anything with the zips I downloaded - I rarely run the full Apache website locally, which I imagine is the main intended use case for the image backups - but I always thought they had the potential to be the foundation of an interesting project. Thanks! ErsatzCulture (talk) 04:35, 5 March 2024 (EST)

That's right: the images hosted by Google Drive are a complete copy of the images hosted by the live ISFDB server. I have added a few more details to the description. Does it make more sense now? Ahasuerus (talk) 14:31, 5 March 2024 (EST)
Thanks. What you've added makes sense, but it's still not clear (to me at least) from the text there that the directories all get updated when new zips are created. Are the 0-9/a-f (and the 2 digit subdirectories) just arbitrary hex digits, maybe the first digits of a checksum or something like that? (That question is slightly rhetorical; I imagine I could find the answer out for myself if I looked through the source code.)
If the tarballs had date suffixes, similar to the database backups, then I think that would make it more obvious that the full set needs re-downloading. However, I guess the downside of that is that it would break any existing tooling for downloading the image backups, and that if you weren't careful you might end up with multiple dated tarballs and/or image directories. ErsatzCulture (talk) 18:25, 5 March 2024 (EST)
Oh, oh... OK, I think I see what the problem is. "0-9" and "a-f" are subdirectory names created by the MediWiki software to store uploaded images. I am so used to this naming convention that it never occurred to me that it may be confusing. A blind spot, if you will. Let me edit the page and explain the naming convention. Thanks! Ahasuerus (talk) 19:15, 5 March 2024 (EST)
Ha, I think this is also a blind spot on my part. Because I don't generally upload my own images (I think it must be in single digits) I forgot that that is all handled by the Mediawiki side of things, and it didn't cross my mind that the directory structure of the images was something that wasn't part of the core ISFDB code. Thanks for clarifying! ErsatzCulture (talk) 05:31, 6 March 2024 (EST)

New hotlink site permission

We have permission to hotlink cover images to a new site, possibly. You can see it here. If that is sufficient, can we add it to the list? ···日本穣 · 投稿 · Talk to Nihonjoe 13:18, 21 March 2024 (EDT)

In anticipation of this being acceptable, there is one publication that is currently hotlinking to the site. ···日本穣 · 投稿 · Talk to Nihonjoe 13:29, 21 March 2024 (EDT)
All done. The publication page now credits "Lawrence Dagstine". Template:Image Host Sites has been updated. Thanks. Ahasuerus (talk) 15:58, 21 March 2024 (EDT)
Thanks! ···日本穣 · 投稿 · Talk to Nihonjoe 17:12, 21 March 2024 (EDT)

Place Submission on Hold

After placing a submission on hold, it would be nice if the resultant page had links back to the submission - both the moderator view and the public view. Currently, it only has a link to the Submission List. But usually when I put something on hold, it is because I plan to do something with that submission. Yes, I can just hit the back button to get the moderator view again. But I often want the public view so I can include the link in a question to the submitter so having that on the on hold page would save a click. Thanks. -- JLaTondre (talk) 10:21, 24 March 2024 (EDT)

Thanks, I'll take a look. Ahasuerus (talk) 10:45, 24 March 2024 (EDT)
Done. Hopefully, the layout and the colors look OK. Ahasuerus (talk) 18:07, 24 March 2024 (EDT)
Thank you! Looks fine. -- JLaTondre (talk) 18:52, 24 March 2024 (EDT)
Great! Ahasuerus (talk) 19:00, 24 March 2024 (EDT)

Galactic Central

Given that the ISFDB is currently heavily dependent on Galactic Central images (12k publication images as of last database dump) and they seem to be in no hurry to implement HTTPS, -- JLaTondre (talk) 13:52, 3 April 2024 (EDT)

Last I heard the owner had no plans to convert to HTTPS. It's possible that his plans may change at some point since browser manufacturers continue to add restrictions to HTTP-only sites. Ahasuerus (talk) 14:08, 3 April 2024 (EDT)

have you given consideration to implementing a proxy service? Apache has a mod_proxy module or it's pretty straightforward to implement your own[1]. -- JLaTondre (talk) 13:52, 3 April 2024 (EDT)

Thanks for letting me know about these options. I wasn't aware of them. I'll add it to my list of things to look into, but it's a long list, so I am not sure when I may get to it. Ahasuerus (talk) 14:08, 3 April 2024 (EDT)

Or should we create a clean-up project to start moving these images over to the ISFDB wiki? -- JLaTondre (talk) 13:52, 3 April 2024 (EDT)

It would certainly make things easier, in part because of the HTTPS issue and in part because they would be incorporated into our publicly available backup files. However, 12K images is a lot images to migrate. Do we expect to have enough volunteer man-hours to make it feasible? Ahasuerus (talk) 14:08, 3 April 2024 (EDT)
Part of the price of self-moderation? ../Doug H (talk) 21:53, 3 April 2024 (EDT)
I have been migrating them as I edit pubs that use them. It will be slow going, but the current broken images are not ISFDB user friendly. -- JLaTondre (talk) 08:44, 6 April 2024 (EDT)
I have created FR 1601, "Enhance display of HTTP-served images". Ahasuerus (talk) 10:44, 6 April 2024 (EDT)

Baen ISBNs

Toll of Honor just came out, and we have the ISBN formatted as 978-1-982193-31-7. The back of the book as well as the copyright page have it formatted as 978-1-9821-9331-7. Do we need to look at the code that adds in the dashes? This may affect more than just Baen books. ···日本穣 · 投稿 · Talk to Nihonjoe 17:33, 5 April 2024 (EDT)

Checking the official "ISBN Ranges" page, I see that the hyphenation rules have changed and become more complex. It used to be that the rules for "978-0-" ISBNs had only 6 cases, but now it's up to 21. "978-1- ISBNs also used to have 6 cases, but now they are up to around 50 cases. Other language-specific ISBN rules have also been affected, although not as severely. Let me create a new FR for this change. Thanks for letting me know! Ahasuerus (talk) 17:55, 5 April 2024 (EDT)
FR 1600 "Update the ISBN hyphenation rules" has been created. Ahasuerus (talk) 18:02, 5 April 2024 (EDT)
And done -- see this Community Portal announcement. Ahasuerus (talk) 14:08, 16 April 2024 (EDT)

Murder in Millennium VI

Please see this edit that impacts your verified pub. Let me know if you agree with changing the credit. Thanks. -- JLaTondre (talk) 08:41, 6 April 2024 (EDT)

I don't have this issue handy right now, but the Archive.org copy is readable. Here is what I see:
  • The title page of the review column, "Readin' and Writhin'" (p.46), credits "Damon Knight and the Editor".
  • There are three reviews. The first two, "Murder in Millennium VI" and "Seetee Ship", are not credited. The third one, "Beachheads in Space" on page 67, is signed "RWL".
  • Of the three reviews, only "Murder in Millennium VI" was reprinted in Damon Knight's In Search of Wonder.
  • We currently credit "Damon Knight and Robert A. W. Lowndes" as the authors of the first two reviews and "RWL" as the author of the third review. We then variant them to their actual authors based on reprint history and textual research.
  • The publication record has notes explaining who the actual authors are and what our evidence is, but individual REVIEW records do not.
Based on the above, how about we use "uncredited" as the author of the first two reviews instead of "Damon Knight and Robert A. W. Lowndes"? The current variants would remain in place, but we would copy explanatory notes from the publication record to each title record. What do you think? Ahasuerus (talk) 10:00, 6 April 2024 (EDT)
I pointed Swfritter to this discussion since he has also verified the pub. As you two are the verifiers, I will defer to you both, but your suggestion makes sense to me. -- JLaTondre (talk) 10:08, 6 April 2024 (EDT)
Sounds OK to me. Especially since there will be plenty of documentation.--swfritter (talk) 20:40, 6 April 2024 (EDT)
OK, I think I got it. Thanks! Ahasuerus (talk) 23:37, 6 April 2024 (EDT)
Thanks. Original edit has been rejected with an explanation of the change. -- JLaTondre (talk) 06:56, 7 April 2024 (EDT)

Wily Writers

https://www.isfdb.org/cgi-bin/title.cgi?2112269; The web page link gave me a red warning for not being safe. Also, shouldn't title/variant be 2013, not 2014? --Username (talk) 19:10, 15 April 2024 (EDT)

It gives me a 403 error when I try to visit. There must be something going on with the server there. ···日本穣 · 投稿 · Talk to Nihonjoe 19:43, 15 April 2024 (EDT)
Apparently the "Wily Writers"' Web site died at some point in the late 2010s. Eventually it was picked up by someone else, but the new owners didn't configure their security certificate correctly, hence the security warning displayed by the browser. I have changed the dates from 2014 to 2013 and replaced the affected links with Wayback machine versions. Thanks for the heads-up. Ahasuerus (talk) 20:23, 15 April 2024 (EDT)

How Far Alongside Night?

https://www.isfdb.org/cgi-bin/pl.cgi?428089; I have some edits adding archived links to the Crown and Ace editions of Alongside Night and another adding afterword mentioned in '87 Avon edition's note; searching for the name Konkin and not finding anything I then noticed you entered the essay in this 2013 edition but name is Konklin (as it also is for another essay). So I think after approval the 2 essays should be merged under the name Konkin; the '99 Pulpless edition is on Google Books and it says Samuel Edward Konkin, III so that's how I entered it, not having any copies or photos of the Avon to verify (no page number, of course). --Username (talk) 09:39, 20 April 2024 (EDT)

It was, indeed, a typo. Everything has been approved and merged. I have moved the URL associated with the essay to the Title record and updated Konkin's author page with biographical data and links. Thanks. Ahasuerus (talk) 13:29, 20 April 2024 (EDT)

Space Viking

Adding cover artist, notes and external IDs to your PVd Space Vikings.10:59, 21 April 2024 (EDT) —The preceding unsigned comment was added by SFJuggler (talkcontribs) .

I have approved the submission and expanded the Notes section. One thing to keep in mind is that the dates listed in early Catalog of Copyright volumes are actually "dates of publication as given in the application". It's possible for the actual publication date to be different due to printer- or publisher-originated delays, so I find it useful to add the phrase "date of publication as given in the application" to the Notes field. I have updated the Title record as well. (Later Catalog of Copyright volumes distinguish between "Date of Publication" and "Registration Date", but that's a different kettle of fish.) Thanks! Ahasuerus (talk) 12:45, 21 April 2024 (EDT)

Weird series ordering

On this series, it's not numbering them in order as it ought to. Any ideas why it's switching things around? ···日本穣 · 投稿 · Talk to Nihonjoe 14:16, 24 April 2024 (EDT)

That looks like expected actually - titles and subseries do not mix in the series ordered views so you got all numbered Titles first followed by all numbered subseries. Annie (talk) 14:57, 24 April 2024 (EDT)
That's exactly right. If the ISFDB software displayed numbered titles and numbered sub-series together, then we'd have anomalies like:
  • Book #1
  • Sub-series trilogy #1
    • Book A
    • Book B
    • Book C
  • Book #2
  • Sub-series trilogy #2
    • Book X
    • Book Y
    • Book Z
  • Book #3
That said, titles and sub-series currently use the same offset and font. Perhaps we should make them look different to facilitate distinguishing between the two type of elements that title series can contain. Ahasuerus (talk) 15:12, 24 April 2024 (EDT)
From my view, if the subseries is numbered as part of the series, that numbering should be in order. I can see pushing subseries to the bottom of the main series if they aren't numbered as part of the series. That makes sense. But doing it so that the numbering is 1, 2, 3, 4, 6, 5, 7 doesn't make any sense and will likely cause confusion for anyone viewing the page because people generally expect numbered things to be in order. ···日本穣 · 投稿 · Talk to Nihonjoe 16:18, 24 April 2024 (EDT)

(unindent) (I have moved the discussion of archive.org-derived information to ISFDB:Research_Assistance#Moribito_series). Ahasuerus (talk) 20:16, 24 April 2024 (EDT)

After mulling it over and running a few database searches, I am beginning to suspect that we may have two different scenarios here. The first one can be seen on this Series page for Jonathan Maberry's Pine Deep. The original trilogy (2006-2008) is numbered 1-3. There is a follow-up series, Monk Addison, which an editor tried to configure -- cumulatively -- as number 4 in the main series. It didn't work too well because the sub-series appears after various unnumbered short fictions titles within the main series.

The second scenario can be found here. Gotrek and Felix consists of 17 novels and a few dozen works of short fiction. It also contains 3 sub-series for the 3 different omnibus editions of the main series. The sub-series are numbered 1, 2 and 3 and appear at the bottom of the page, i.e. after the short fiction. Unlike the Pine Deep scenario, this is, unambiguously, the expected behavior since the omnibus sub-series are not part of the main numbering scheme.

If my understanding is correct, then the ISFDB software currently supports the second scenario, but not the first one. Does this sound about right? Ahasuerus (talk) 20:32, 24 April 2024 (EDT)

Yes, that seems accurate. ···日本穣 · 投稿 · Talk to Nihonjoe 20:43, 24 April 2024 (EDT)
I guess the next question is what we can do about this situation. Let me sleep on it... Ahasuerus (talk) 21:13, 24 April 2024 (EDT)
No bright ideas so far, I am afraid. I can't think of a way to accommodate these two different scenarios using the database fields that we currently have. Maybe something will germinate over the next few days. Ahasuerus (talk) 14:34, 25 April 2024 (EDT)
How about an obvious solution: add a flag/checkbox on the series page which tells the software if it needs to show series and titles mixed based on the numbers OR if they need to be kept separate? With the default being showing them separately (aka "things as they stand now"). Annie (talk) 17:32, 25 April 2024 (EDT)
PS: Oops. Did not see your note about using existing DB fields. You know... maybe we can use the "Series Parent Position" creatively? Add a letter to the number if you want them to sort inside of the titles series (so instead of 1, use 1M (for mixed))? Annie (talk) 17:34, 25 April 2024 (EDT)
And we do not even need to show that weird numbering scheme to the editors - make that the DB field value but change the UI to actually show a checkbox. Or something along these lines. The only thing that may be a bit of a hassle is that this field is actually integer, right? So... add an big number to the actual value and drop it for sorting? So instead of 1, record 1001 (how many series we need that need 1000 as a number on the series order?). Annie (talk) 17:38, 25 April 2024 (EDT)
Re: "flag/checkbox on the series page which tells the software if it needs to show series and titles mixed based on the numbers OR if they need to be kept separate", it's possible for a series to have both types of sub-series. The first type covers sub-series which should be treated as titles for ordering purposes. The second type covers sub-series which should be displayed after all regular titles, including unnumbered titles. If a new flag is to be implemented, it will presumably need to be added to each sub-series, specifying what kind of sub-series it is.
That said, I think the first thing that we need to do is to determine what kind of impact having certain sub-series displayed within the main title sequence would have. A few things come to mind:
  • We have a cleanup report that finds duplicate series numbers within a series. It would presumably need to be enhanced to look for duplicate numbers of the new type (or a new cleanup report will need to be created.)
  • Having a long sub-series -- especially if it has nested sub-series of its own -- appear in the middle of numbered titles could make it harder for our users to understand what the actual order of the main series is. For certain major universes like Warhammer, the resulting "series tree" could be overwhelming.
  • Development considerations. Currently the software module responsible for displaying series (a) calls itself recursively AND (b) shares code with our Bibliographic pages. It's a delicate and messy area which is high on my list of things to rewrite once I am done with Fixer migration. Adding additional complexity to it before the code is rewritten may not be optimal.
Ahasuerus (talk) 20:49, 25 April 2024 (EDT)

Japanese collaboration

I haven't asked them yet, but one of the authors in our database was the creator of the Japanese SF Book Database and the Japanese SF Magazine Database. He's in his 90s now, and I wondered if I should reach out to him to see if he (or one of his colleagues) might be interested in entering all the information from those databases into ISFDB in order to make it more broadly accessible (since most people outside of Japan have never heard of his two databases). I don't know what their database system is, but there might even be a way to (at least partially) automate the transfer of information. I know they've had some database issues recently so their sites aren't working properly, so I think it's even more important to try to get that information into ISFDB before he dies. Thoughts? ···日本穣 · 投稿 · Talk to Nihonjoe 17:46, 25 April 2024 (EDT)

The idea certainly has merit. Here are some steps that come to mind:
  • We'll need to determine whether the current database owners/maintainers are able and willing to share the data. There may be pre-existing obligations or commitments which may prevent them from sharing the data.
  • The fact that the Web site is currently partially non-functional raises a flag. We'll need to determine whether they have coherent database backups, database documentation and how many records the backups contain.
  • If they have a coherent database backup and are willing to share it, then it's likely that we should be able to use it. Directly importing data into the ISFDB database would be suboptimal, in part because it would leave us without Edit History, but creating Fixer-style submissions using their data should be viable. We have a number of people with software development backgrounds who may be interested in working on this task.
  • The ISFDB Web API supports putting submissions on hold on behalf of a moderator. We'll probably want to hold these submissions for moderators who have a working knowledge of Japanese.
Based on the above I would suggest that we start by contacting the owners/maintainers to get answers to the first two issues listed above. Ahasuerus (talk) 18:24, 25 April 2024 (EDT)