Flagging Removed Stories

TwiFanfictionRec · 09-01-2014, 04:54 AM

Is there a way, when running the FFDL update, to flag stories which have been removed from sites? Maybe an option to populate a column?

I really want to avoid overwriting a story in my Calibre library if it no longer exists on a site.

Apologies if this is in the wrong forum.

Any advice gratefully received

aleyx · 09-01-2014, 08:56 AM

I've never used it, but the "Reject List" in the Basic tab of the config panel should do what you want.

BookJunkieLI · 09-01-2014, 11:19 AM

What archives are you downloading from that they're overwriting your story if they no longer exist on that site? Can you give a couple of examples? I just checked a story that I know used to be on AO3 but no longer is and it wasn't overwritten. I'm 90% sure the same goes for FFN and TTHFanfic, the main sites I'm currently downloading from.

The Reject List really would only work if you already knew which stories no longer existed on the site so that you could mark them beforehand and you run the risk of accidentally deleting them if you don't uncheck the Delete Books option in the dialogue box. That's not a risk I'd be willing to take.

I think what you want to do is create a custom column for FFDL errors. You can use a text or long text column. Personally, I use a Long Text column called FFDL Errors. Once that's setup go to the Custom Columns tab of Configure Plugin and down the bottom you'll see an option for Special Column: Update/Overwrite Error Column. Tell it which column to update and you're good to go.

aleyx · 09-01-2014, 11:35 AM

Also, there's some cases where the author "removes" the story by replacing every chapter by a note saying "Sorry, I'm done with this". Which is a rather unkind thing to do, despite being entirely in their right.

Still, I don't know how FFDL would react to this.

In any case:

1) Only update those stories you know (by a site notice) is updated,
2) Backup, backup, backup.

Actually, I would really advise authors to use Calibre+FFDL as a backup solution to their online works, if they currently only rely on a site's doc manager and not a real authoring workflow.

N.

BookJunkieLI · 09-01-2014, 12:14 PM

Quote:

Originally Posted by aleyx

Also, there's some cases where the author "removes" the story by replacing every chapter by a note saying "Sorry, I'm done with this". Which is a rather unkind thing to do, despite being entirely in their right.

Okay, that's a horrifying thought. I have to imagine FFDL would see it as an update and then, if overwrite newer/always is selected,would overwrite the entire story with that. Worse you probably wouldn't even notice right away unless you're only downloading a handful of stories.

Quote:

Still, I don't know how FFDL would react to this.

In any case:

1) Only update those stories you know (by a site notice) is updated,
2) Backup, backup, backup.

Actually, I would really advise authors to use Calibre+FFDL as a backup solution to their online works, if they currently only rely on a site's doc manager and not a real authoring workflow.

N.

Based on what you said above I think I may start dropping each backup into a date labelled zip file rather than just continually overwriting like I've been doing.

aleyx · 09-01-2014, 01:17 PM

Quote:

Originally Posted by BookJunkieLI

Based on what you said above I think I may start dropping each backup into a date labelled zip file rather than just continually overwriting like I've been doing.

Delta backups FTW. I use rdiff-backup, but I'm a Linux guy.

A shallow search gives DeltaCopy for Windows, although I have no idea how good it is.

N.

BetterRed · 09-01-2014, 05:50 PM

Quote:

Originally Posted by BookJunkieLI

Based on what you said above I think I may start dropping each backup into a date labelled zip file rather than just continually overwriting like I've been doing.

Free File Synch will retain previous versions in context of doing an incremental backup.

Quite a few MR folks use FFS - I don't for legacy reasons, but were I making the decision I made several years ago, FFS would be a major contender. The product I do use retains previous versions.

BR

TwiFanfictionRec · 09-05-2014, 02:00 PM

I think what you want to do is create a custom column for FFDL errors. You can use a text or long text column. Personally, I use a Long Text column called FFDL Errors. Once that's setup go to the Custom Columns tab of Configure Plugin and down the bottom you'll see an option for Special Column: Update/Overwrite Error Column. Tell it which column to update and you're good to go.[/QUOTE]

Thanks, I shall give this a go

09-01-2014, 04:54 AM	#1
TwiFanfictionRec Junior Member Posts: 3 Karma: 10 Join Date: Nov 2013 Device: none	Flagging Removed Stories Is there a way, when running the FFDL update, to flag stories which have been removed from sites? Maybe an option to populate a column? I really want to avoid overwriting a story in my Calibre library if it no longer exists on a site. Apologies if this is in the wrong forum. Any advice gratefully received

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Glo Shelve that cannot bo removed	magphil	Kobo Reader	4	02-15-2013 06:30 PM
Ended removed	smallhagrid	Flea Market	4	08-06-2012 05:20 PM
Antivirus flagging calibre	Jane A	Calibre	4	07-03-2012 10:27 PM
Finereader flagging em dashes	proxy	Workshop	0	11-25-2010 12:17 PM

09-01-2014, 08:56 AM	#2
aleyx Addict Posts: 250 Karma: 20386 Join Date: Sep 2010 Location: France Device: Bookeen Diva, Kobo Clara BW	I've never used it, but the "Reject List" in the Basic tab of the config panel should do what you want.

09-01-2014, 11:19 AM	#3
BookJunkieLI Evangelist Posts: 435 Karma: 572984 Join Date: Jan 2010 Location: Long Island Device: Kobo Libra 2, Kindle 4, Nook Gl4, Nook STR, REB 1100, Ebookwise 1500,	What archives are you downloading from that they're overwriting your story if they no longer exist on that site? Can you give a couple of examples? I just checked a story that I know used to be on AO3 but no longer is and it wasn't overwritten. I'm 90% sure the same goes for FFN and TTHFanfic, the main sites I'm currently downloading from. The Reject List really would only work if you already knew which stories no longer existed on the site so that you could mark them beforehand and you run the risk of accidentally deleting them if you don't uncheck the Delete Books option in the dialogue box. That's not a risk I'd be willing to take. I think what you want to do is create a custom column for FFDL errors. You can use a text or long text column. Personally, I use a Long Text column called FFDL Errors. Once that's setup go to the Custom Columns tab of Configure Plugin and down the bottom you'll see an option for Special Column: Update/Overwrite Error Column. Tell it which column to update and you're good to go.

09-01-2014, 11:35 AM	#4
aleyx Addict Posts: 250 Karma: 20386 Join Date: Sep 2010 Location: France Device: Bookeen Diva, Kobo Clara BW	Also, there's some cases where the author "removes" the story by replacing every chapter by a note saying "Sorry, I'm done with this". Which is a rather unkind thing to do, despite being entirely in their right. Still, I don't know how FFDL would react to this. In any case: 1) Only update those stories you know (by a site notice) is updated, 2) Backup, backup, backup. Actually, I would really advise authors to use Calibre+FFDL as a backup solution to their online works, if they currently only rely on a site's doc manager and not a real authoring workflow. N.

09-05-2014, 02:00 PM	#8
TwiFanfictionRec Junior Member Posts: 3 Karma: 10 Join Date: Nov 2013 Device: none	I think what you want to do is create a custom column for FFDL errors. You can use a text or long text column. Personally, I use a Long Text column called FFDL Errors. Once that's setup go to the Custom Columns tab of Configure Plugin and down the bottom you'll see an option for Special Column: Update/Overwrite Error Column. Tell it which column to update and you're good to go.[/QUOTE] Thanks, I shall give this a go

Advert

Advert