Due to the triggers involved in import, scripts will sometimes not be applied to newly added movies.

The typical use case is:

• nfo has been generated at time t1
• last import ran at t2, with t2 > t1
• video libray scan launched and finishing at t3 > t2 > t1
  In this case, Kodi will create the entry for the new video, based on the original nfo only. Patch will not run, because nfo is considered too old.

Possible solutions:

• change trigger to VideoLibrary.OnScanStarted? This won't work, as issue will stay the same: nfo will not be considered by import, due to t2 > t1
• catch trigger on VideoLibrary.OnUpdate, with 'added' in payload?
  • => to be investigated
  • this could require having an import task running on a single video, rather than on all the sources
  • warning not to enter an infinite loop: VideoLibrary.OnUpdate => import single => VideoLibrary.OnUpdate => import single => ...
    • this may require using a temp file to hold the entries we should ignore once

As of now, having a quick view on the process results is tricky, in particular when large updates are launched. And because processes are launched in background, the users can hardly know what is the task progress, especially when many files are involved.

We should propose dumping the results in a convenient way, so that users can easily review the result and the current status of tasks.

We could also, in the future, have a GUI to easily navigate into these results.

could someone please help? :-)

For the moment, only changes to the watched state are detected.

Check if we can also react to:

• user rating:
  • it seems nothing is triggered by Kodi => check w/ Team Kodi?
• resume point:
  • to be investigated

Although a full re-import could normally be performed by re-scanning the full library, there is one case where it won't work: if import was already done, and the patch script has been modified since then. In this case, the last_import resume point won't allow us to re-apply the script on all NFO.

This can be done manually by clearing out the last_import.tmp file, but this may be considered not user-friendly enough.

One possibility would be to add an action through a dedicated setting.

on large scans, this will dramatically impact performance

This would simplify solution to issues #4 and #7.

And having separate scripts for import and export is definitely a killer feature that won't be useful for 99% of the users.
We could, though, find an acceptable workaround by providing another variable task_type in locals, for use with ScriptHandler.execute(). User will then be able to have separate processes based on it.

Implementation:

• settings.xml
• import_base.py and export_base.py

To cover all relevant aspects, useful for various types of users:

• rationale
• overview
• installation & configuration
• Kodi configuration
• advanced addon configuration
• using scripts
• script examples / tutorial

We should have:

• ExportSingleTask: export a single entry
• ExportAllTask: export all entries of a given type

Both of them will rely on 2 possible strategies: UpdateExportStrategy and RebuildExportStrategy

Simply because modified date of the nfo has changed, this file will (should?) be processed at next import.

While not being a "bug", this is definitely something we could improve.
Probably by allowing import of a single entry, and by using a temp file to hold the file names to be ignored at next import (only), similarly to issue #4.

However, there is a drawback: import and export scripts could be different. By ignoring next import, we would ignore the script configured for import, too.

As of now, import will only be processed on files modified after a given timestamp.
We could want to also import single NFO files.

This would help for issue #7

This is a major reorganization of the way tasks are structured: see dedicated page on wiki for more details.

Shoudn't be able to fallback to ExportAll anymore

As of now, this addon is only supported by v18, check how we can make it compatible with v17

Improve the way notifications to users are done.

We could also add member 'silent' to tasks: this will allow to bypass notify, useful for tasks that are being launched by another one

Definitely a must-have, but we are focusing on stabilizing the addon for movies first...

No filter in Monitor.onNotification()

However, we could think about removing these settings. Having a "smart" addon that will automatically adapt its behavior (as described in #7) is probably better for users.

Setting priority high as it is easy to fix, and the issue is definitely confusing for users.

If debug mode is off, Kodi will only write to kodi.log records with level > xbmc.LOG_NOTICE.

For this reason, we need to carefully review which levels are set for given steps of the processes.