- Moderator
- #71
Ok. All sections are exported to NFO, can be imported ?
In case of existing nfo file (I'm talking about GUI) F3 key will import only from nfo (it only will fetch cover and fanart, if they are not exists, from the web) but in Movie info screen Refresh button will fetch from web. Ok, that can be prevented.Hi Deda,
great work and great patch. At the moment i use "MovingPictures" for my movie collection - but in the future i will give "MyVideo" a try.
Last weekend i played a little with "MyVideo" and tried to import a few videos with cover, fanart and nfo files.
Maybe, i have two ideas for improvement:
1) "Local NFO-reader" to choose as "grabber script"
This would prevent to update the database "accidentally" from online resources.
2) If you import nfo files out of the tools, there is no possibillity to prevent duplicates. My suggestion would be to check, if there is an entry with the same IMDB-Number. Then the import should behave as an "update". The IMDB-number should be handled as a kind of "key-field" to prevent duplicates.
For better understanding: The way i build up my archive may be different from other users. I have a MediaPortal-Installation on my notebook in order to "build" the NFO-Files with a lot of handwork - cover, fanart, description, etc. If all informations are perfect, i export them into the NFO-File. Now the movie folder "is ready" to be imported into the database of the "main" MediaPortal.
This import should be the only way to update the database (-> point 1.)
If there is a change in the NFO-file - the Database should only be updated (-> point 2.)
Thanx for the great work
Schaeklovic
Deda said:Y, sounds reasonable. I will add that possibility.
I'm not sure, if outline is used in filelist, i think is only plot same as MovieinfoOutline is used but is visible only in list screen. Movie info shows full plot in skin.
Cast is constructed from <actor> nodes.
Media info is skipped because MP internally handles that and fills missing data and it's not related to movie info.