drtak34 / my-films

Automatically exported from code.google.com/p/my-films
0 stars 0 forks source link

Add 'Countries' and RegExp options to more (all?) fields in Grabber Editor #376

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What area does your enhancement or feature relate to? (i.e. Config/Setup,
GUI, options, Skin, AMC Updater, Grabber Interface, etc.)
Grabber Editor
What is the purpose or benefit of the new feature or enhancement?
RegExp allows much more flexibility in grabbing consistent results, especially 
for NFO/filebased readers or 'common' grabbers such as a generic TMDb for all 
languages. However, it is currently only supported for some fields, which has 
resulted in using 'other fields' that do support it and mapping them.

Similarly the 'Countries' parameter which was originally designed to select the 
country for Certification and Translated Titles (AKAs), has proven very useful 
for 'matching' text particularly for RegEx groups.

Providing these options for more or all fields would allow us to remove the 
'hacks' where we use other fields just to use those options. It may also allow 
us to create more common (i.e. fewer) grabbers that have only minor variations 
in data (e.g. common TMDB grabber).

How would you expect it to work? (Accessed via, new settings required, Skin
changes/new properties)
Like it does now for other fields, except COUNTRIES option should be renamed to 
something more generic such as MATCH?

Can you illustrate it with examples such
as images (screenshots), scenarios or examples from other Plugins?
One example (there are many) can be seen in NFO grabber which uses Photos field 
to extract only Writers from <credits> NFO tag when the credits tag contains 
other persons as well.
If this issue has been discussed in the MyFilms forum, add a link to the
related thread or post.
http://forum.team-mediaportal.com/conversations/nfo-grabber.109196/page-2

Original issue reported on code.google.com by Dade...@gmail.com on 30 Jan 2014 at 5:47

GoogleCodeExporter commented 9 years ago

Original comment by Dade...@gmail.com on 30 Jan 2014 at 5:47

GoogleCodeExporter commented 9 years ago
I know e initially wante dot introduce this as generic features with new 
grabber engine - but as this won't come too soon; are there any fields where we 
urgently need it to solve practical issues, so we ight want to add those in old 
core?

Original comment by Guzz...@googlemail.com on 30 Jul 2014 at 7:02

GoogleCodeExporter commented 9 years ago
Too many imho - i.e. any field that uses person/roles REGEX (which we have used 
as workaround in non-person fields as well)

Rather than doing double work, maybe better approach is to make the grabber 
engine rework a priority for next feature release ;)

Original comment by Dade...@gmail.com on 31 Jul 2014 at 3:56