MobileRead Forums - View Single Post

JimmXinu · 06-09-2014, 11:00 AM

Quote:

Originally Posted by davidfor

You can use the same test in the replace_metadata more than once. You could try something like:

Code:

replace_metadata:
 fandoms=>Thor \(Movies\)=>Thor
 fandoms=>Thor \(Movies\)=>Marvel Cinematic Universe
 fandoms=>Captain America \(Movies\)=>Captain America 
 fandoms=>Captain America \(Movies\)=>Marvel Cinematic Universe

It doesn't work that way. Each replace line is applied sequentially.

In the case shown above, "Thor (Movies)" is changed into "Thor" and then doesn't match the next 'Thor \(Movies\)' pattern any more.

I expect davidfor is actually using the technique where you add a new metadata item with extra_valid_entries, populate it with a copy of an existing one, then change each separately and merge back together.

Quote:

Originally Posted by davidfor

The thing that I fell is missing for this is being able to supply more that one tag. There have been a couple of times where what I really wanted was to split the found tag into two. The solution was to put two lines in, but it does mean I have two copies of the same match string to maintain if things change.

I've looked at that a bit before and again now. I've found a way that appears to work.

I've arbitrarily chosen '{{,}}' as a separator to indicate to split the replacement string at that point(s) into a list and append the new entries to the end of the list. Because they go to the end, they will in turn have replace_metadata applied.

There's a risk of infinite recursion, that I haven't thought about very deeply yet.

If you're curious, here's my test case:

Spoiler: