edit: just found your article with more info on your process! https://compellingsciencefiction.com/posts/how-i-curate-an-a...
The code and open-source tools I used to produce a science fiction anthology
11–20 of 50 posts
Re: The code and open-source tools I used to produce a science fiction anthology
#12I saw this on amazon the other day and picked it up. As an avid reader of short form science fiction, I was really excited to see an anthology that focused on interesting ideas. I'm three stories in and my only gripe so far is Twenty-Four Hours, I just can't find the outstanding idea in it. I think it is a lovely and touching story, it just lacks the punch I'd expect to find in this type of collection. I'd love to he…
As I wrote in that blog you linked, I tried to interleave the stories so that you get alternating vibes as you go through the book. I know not every story will be for everyone, but I hope you find most of them interesting!
I plan on pursuing as close to the same process as I can next year, I want to put out the most consistently concept-focused Year's Best out there.
Re: The code and open-source tools I used to produce a science fiction anthology
#13I did this 10 or so years ago when I taught an ebook course to elementary students. We learned about ebooks, HTML, and they each write a short story, which was included in an ebook (and a physical book). Pretty amazing the tools we have access to. Of course, now I would use typst instead of latex for the physical book part.
Re: The code and open-source tools I used to produce a science fiction anthology
#14I did this 10 or so years ago when I taught an ebook course to elementary students. We learned about ebooks, HTML, and they each write a short story, which was included in an ebook (and a physical book). Pretty amazing the tools we have access to. Of course, now I would use typst instead of latex for the physical book part.
Have a preferred typst template for ebooks?
Re: The code and open-source tools I used to produce a science fiction anthology
#15It's quite an achievement. I was once interested in publishing a SF anthology. Formatting and editing was nbd -- I was going to use Amazon's KDP software package for most of it, which can take a .docx and output an ebook in 5 minutes. I've done it before for non-anthology books I've published, and it couldn't be easier, though I understand why people might avoid Amazon in this day and age. The real trouble was gettin…
From a macro societal perspective, would this evolve "copyright" into a more balanced (value generating) deal for all of society?
Re: The code and open-source tools I used to produce a science fiction anthology
#16It's quite an achievement. I was once interested in publishing a SF anthology. Formatting and editing was nbd -- I was going to use Amazon's KDP software package for most of it, which can take a .docx and output an ebook in 5 minutes. I've done it before for non-anthology books I've published, and it couldn't be easier, though I understand why people might avoid Amazon in this day and age. The real trouble was gettin…
Just a thought... would it make sense to maintain a govt/central registry of copyright owners, and have an "official" means of contacting them, on which they have an SLA to respond (say 3 months) which might be part of the ground rules for maintaining rights. From a macro societal perspective, would this evolve "copyright" into a more balanced (value generating) deal for all of society?
> Japan has a scheme for orphaned games where if you can prove you did due diligence in searching for a rightsholder and couldn't find one, you can go ahead with rereleasing the game and the royalty payments get held in escrow by the government in case the rightsholder comes forward. I wish the US had something similar for cases like these.
Source:
Re: The code and open-source tools I used to produce a science fiction anthology
#17I did this 10 or so years ago when I taught an ebook course to elementary students. We learned about ebooks, HTML, and they each write a short story, which was included in an ebook (and a physical book). Pretty amazing the tools we have access to. Of course, now I would use typst instead of latex for the physical book part.
Have a preferred typst template for ebooks?
Re: The code and open-source tools I used to produce a science fiction anthology
#18It's quite an achievement. I was once interested in publishing a SF anthology. Formatting and editing was nbd -- I was going to use Amazon's KDP software package for most of it, which can take a .docx and output an ebook in 5 minutes. I've done it before for non-anthology books I've published, and it couldn't be easier, though I understand why people might avoid Amazon in this day and age. The real trouble was gettin…
Just a thought... would it make sense to maintain a govt/central registry of copyright owners, and have an "official" means of contacting them, on which they have an SLA to respond (say 3 months) which might be part of the ground rules for maintaining rights. From a macro societal perspective, would this evolve "copyright" into a more balanced (value generating) deal for all of society?
This is contrary to most (all?) other parts of the law where everything is allowed that isn't forbidden.
So it's the right of authors to ignore email requests to discuss a re-publication if they so wish.
Re: The code and open-source tools I used to produce a science fiction anthology
#19The leverage the simple (perhaps messy) scripts and code that these tools gave the author is simply incredible. So satisfying to read and a a really great achievement. Congratulations and thanks for the write up.
Re: The code and open-source tools I used to produce a science fiction anthology
#20I saw this on amazon the other day and picked it up. As an avid reader of short form science fiction, I was really excited to see an anthology that focused on interesting ideas. I'm three stories in and my only gripe so far is Twenty-Four Hours, I just can't find the outstanding idea in it. I think it is a lovely and touching story, it just lacks the punch I'd expect to find in this type of collection. I'd love to he…
Thanks for your support! I believe I understand where you're coming from, some of the stories have more novel concepts than others -- Twenty-Four Hours is hard to discuss without spoilers, but I selected it because the characters and setting felt very real, while at the same time it would completely fall apart without the technological concept. As I wrote in that blog you linked, I tried to interleave the stories so…
Are you comfortable speaking about the financial side? What does an editor get per copy sold, what does an author get? (In the science world, for instance, editors tend to get money often, but authors never get paid for articles or book chapters.)
Hopefully, now that you have experience in the process and all your code ready, you can repeat the exercise with higher efficiency and profitability.