[REQ] Tag Mapper default ruleset

Bug #1603687 reported by JP
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
calibre
Invalid
Undecided
Unassigned

Bug Description

Can there be an option to use a particular ruleset as the default in all three locations?
It occurs to me now that this might actually be a bug.

Currently, it takes FOREVER it seems to load Tag Mapper. In my case, this is likely because there are A LOT of tags. Since you made the "shortcut" to easily pull them up and add to rules, I believe that made it a database where the tag exists in that database and thus must load a large database. It's unfortunate that this keeps even those tags set to "remove" in a database of "available in rules" making the load time larger.

THE EFFECT:
Multiply this load (and save) time by 3. In order to use a standard set of Tag Mapper rules (I name the set TAGS), I have to load the ruleset in 3 places where I want it active:
   1) Adding Books ruleset
   2) Download metadata ruleset on import
   3) Tag Mapper as available to run on a group of books.

When I update my Tag Mapping rules (named TAGS), I have to load that ruleset in two more locations after saving it in one (usually via Tag Mapper shortcut). Saving it to replace the previous set under the same name does NOT update it in the other locations. The last I knew this was only one file where the Tag Mapper rulesets store, so I have to wonder if you have it set to copy the individual ruleset to something else when being used in the individual ways (import, metadata import, Tag Mapper). I AM NOT the expert on that. I'm just wondering why it wouldn't pull the updates to the (or what used to be) single ruleset which I name TAGS.

Before knowing about locations 1 and 2 above, I would just run the Tag Mapper on my new books and those changed in other ways. However, the long loading time for the Tag Mapper made this a literal wast of time. I then found the adding book rule area and happened upon in the metadata download. While it has helped with the imports and new metadata downloads, it is still very time-consuming to load in each location now.

Even if that stays the same, it would be A BIG HELP to be able to set a ruleset NAME as the default for all three locations such that when you save changes in one location under that name, it applies the new changes to all three.

JP (jecilop)
description: updated
Revision history for this message
Kovid Goyal (kovid) wrote : Re: calibre bug 1603687

I dont find it taking forever to load the tag mapper with ~ a 100
rules? How many do you have? And attach the ruleset file to this bug
report.

 status incomplete

Changed in calibre:
status: New → Incomplete
Revision history for this message
Kovid Goyal (kovid) wrote :

no followup

Changed in calibre:
status: Incomplete → Invalid
Revision history for this message
JP (jecilop) wrote : Re: [Bug 1603687] Re: [REQ] Tag Mapper default ruleset
Download full text (3.6 KiB)

Hello, Kovid.
I haven't been able to stop to follow up. I'm dealing with family
emergencies and health issues and haven't had Calibre open since shortly
after this.

I still can't stop to send you the tags file, but the request of a default
setting is still valid as saving changes in a ruleset does NOT apply them
to that same ruleset in another place (ie, tag mapper vs book import rules
for tags vs tag rules on metadata searches) even though its the same
ruleset. I have to go to each area mentioned, open the rules, and resave
as applicable to that function.
This alone is the part easily overlooked and tedious.
The fact that my rulesets are taking so long to open is secondary and
mentioned only to illustrate why I'm asking. An additional side note, if
it matters... I only have two rulesets.

....sent from my phone while on the go....

On Aug 11, 2016 10:46 AM, "Kovid Goyal" <email address hidden> wrote:

> no followup
>
> ** Changed in: calibre
> Status: Incomplete => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1603687
>
> Title:
> [REQ] Tag Mapper default ruleset
>
> Status in calibre:
> Invalid
>
> Bug description:
> Can there be an option to use a particular ruleset as the default in all
> three locations?
> It occurs to me now that this might actually be a bug.
>
> Currently, it takes FOREVER it seems to load Tag Mapper. In my case,
> this is likely because there are A LOT of tags. Since you made the
> "shortcut" to easily pull them up and add to rules, I believe that
> made it a database where the tag exists in that database and thus must
> load a large database. It's unfortunate that this keeps even those
> tags set to "remove" in a database of "available in rules" making the
> load time larger.
>
> THE EFFECT:
> Multiply this load (and save) time by 3. In order to use a standard set
> of Tag Mapper rules (I name the set TAGS), I have to load the ruleset in 3
> places where I want it active:
> 1) Adding Books ruleset
> 2) Download metadata ruleset on import
> 3) Tag Mapper as available to run on a group of books.
>
> When I update my Tag Mapping rules (named TAGS), I have to load that
> ruleset in two more locations after saving it in one (usually via Tag
> Mapper shortcut). Saving it to replace the previous set under the
> same name does NOT update it in the other locations. The last I knew
> this was only one file where the Tag Mapper rulesets store, so I have
> to wonder if you have it set to copy the individual ruleset to
> something else when being used in the individual ways (import,
> metadata import, Tag Mapper). I AM NOT the expert on that. I'm just
> wondering why it wouldn't pull the updates to the (or what used to be)
> single ruleset which I name TAGS.
>
> Before knowing about locations 1 and 2 above, I would just run the Tag
> Mapper on my new books and those changed in other ways. However, the
> long loading time for the Tag Mapper made this a literal wast of time.
> I then found the adding book rule area and happened upon in the
> metadata ...

Read more...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.