Save "update movies" tab in AMCu cfg

[GoogleCodeExporter]

What area does your enhancement or feature relate to? (i.e. Config/Setup,
GUI, options, Skin, AMC Updater, Grabber Interface, etc.)

AMC updater

What is the purpose or benefit of the new feature or enhancement?
Make easier the frequentest performed updates, like replacing characters in a 
field, or updating missing fields

How would you expect it to work? Can you illustrate it with examples such
as images (screenshots), scenarios or examples from other Plugins?
When you load a cfg in AMCu, the "update movies" tab (operation and parameters) 
would be automatically populated.

Please sign with your MP forum username as often google accounts are quite
different.
z3us
NOTE: feature requests will be evaluated based on the number of
users who 'star' the issue as well as the details provided.

Original issue reported on code.google.com by vivamiloro on 9 Sep 2012 at 4:14

[GoogleCodeExporter]

What settings would you see as permanent?
I understand the request, as whenever you want to make an update, you have to 
make the appropriate settings first.
So does this relate to "update profiles"? Or just talking about keeping last 
settings persistant in config?
What settings exactly should be remembered?

Original comment by Guzz...@googlemail.com on 15 Sep 2012 at 7:19

[GoogleCodeExporter]

- What settings? : all the settings in this tab that are not being saved  with 
the cfg: "Operation..." and "Parameters..." areas
- Where? in the config .xml file, just as the of the settings in AMCu do

Original comment by vivamiloro on 15 Sep 2012 at 9:14

[GoogleCodeExporter]

The issue is that currently there is no way to save AMCU config settings for 
Update Movies tab! Although you can save and load custom config settings for 
AMCU - they do not contain any settings from Update Movies tab.

However, IIUC what you mean by 'Update Profiles' I think that might even be a 
better solution?  Example: On Update movies tab add a new button to save the 
current Update Settings/Profile - independent of main AMCU Config settings? 
This might also work with the option we discussed to provide some 'preset' 
options for Update movies - e.g. update all ratings, update mediainfo, update 
to AMC4 or some such.

Original comment by Dade...@gmail.com on 15 Sep 2012 at 11:38

[GoogleCodeExporter]

Yes, all this is somehow related to the "update profiles" issue.
However, in any case, we'll need the support to store the settings.
And indeed, I think to have this somehow "separate" from general config should 
help to implement those update use cases.
So what we need is the specification, what settings actually have to be stored 
as an update profile.
Unfortunately, we currently share the Database tab setting for both - import 
and updates - so those might require separation, as otherwise, running an 
update would change the import settings.
Other (probably simpler) solution is:
Use different AMCU settings files per profile - so as before, one for import - 
plus adding new ones for updates, which contain stored update settings...

Original comment by Guzz...@googlemail.com on 23 Sep 2012 at 2:40

[GoogleCodeExporter]

I'm not sure if I understand what a 'profile' is for AMCU ;) - do you mean 
Import is one 'profile' 'Update' is another?  

However, I would be OK with the 'simpler' solution i.e. separate AMCU settings 
files:
Example:
1. MyFilms_AMCImportSettings_[configname].xml
2. MyFilms_AMCUpdateSettings_[configname].xml

But what happens when you have Import settings loaded (as it is currently by 
default) then you change to Update Movies tab - will AMCU auto load the current 
Update settings for that catalog and change the name of the settings file in 
top status bar display?  

Still lots to consider!

Original comment by Dade...@gmail.com on 23 Sep 2012 at 4:04

[GoogleCodeExporter]

Indeed, there is a lot of things to consider - and we should make sure, that 
changes we apply are compatible to the planned rework of AMCU.
Alternatively, we could just add what this issue is about in a first step - 
saving settings on update tab (which are A LOT - be aware, that many of the 
elements are ony visible, if certain stuff is selected!).
My fear is: When we save the settings - and user changes some basic functions 
(e.g. update record to replace calue) - the stored items areN#t matching 
properly anymore - and we have to add a lot of logic to make sure that happens!
Practically, I think the most used function of the update tab is "Update 
record" - all other are probably rarely used.
So we should focus on that one.
And again - the question is, if we should save separate settings for DB fields 
for update vs. import - as usually those are NOT the same!

Original comment by Guzz...@googlemail.com on 24 Sep 2012 at 10:08

[GoogleCodeExporter]

Yes you need to save DB fields separately for Update as that is often one of 
the most imp. settings I change. I agree that first priority is Update Record.

Can we not save operations and parameters similar to Filters and restore those?

Original comment by Dade...@gmail.com on 25 Sep 2012 at 5:12

[GoogleCodeExporter]

Original comment by Guzz...@googlemail.com on 27 Oct 2012 at 9:52

• Added labels: Milestone-7.0.0
• Removed labels: Milestone-6.1.0

[GoogleCodeExporter]

Original comment by Guzz...@googlemail.com on 30 Oct 2012 at 3:32

• Added labels: Difficulty-Minor

[GoogleCodeExporter]

I think, we should first define the exact use cases, we want to support - and 
afterwards think about the best implementation.
Implementation could go different ways - handover settings when calling update, 
only call a profile, that has to be create before or other approaches.
To judge, which approach fits best, we need to know in advance, what should be 
supported, that is:
What parameters need to be set/defined for such an update operation, e.g. "wht 
grabber" "matching option", "what field to update", "update rule", etc.
Maybe, even implementing some sort of API is even the better and more flexible 
approach, as it avoids, that such profiles always have to be defined and stored 
in advance...

Original comment by Guzz...@googlemail.com on 23 Nov 2012 at 8:59

• Added labels: Difficulty-Medium
• Removed labels: Difficulty-Minor

[GoogleCodeExporter]

This could be used instead of the "translation table" that Guzzi said here 
http://forum.team-mediaportal.com/threads/my-films-6-0-beta-released-19-10-2012-
v6-0-0-2616-mp-1-2-x-1-3-alpha.113261/page-3#post-930231

Original comment by vivamiloro on 28 Nov 2012 at 3:54