<edititon> xml location in sql DB ?
#1
Question 
Hello,
can someone tell me where to find the entry <xml><edition>Example: Directors Cut</edition></xml> in the SQL DB ? Kodi's source is based on local NFO's before using SQL. So Kodi itself had this data before because I created it manually but I can't find anything in the SQL DB.

Or can I add it manually as a replacement if Kodi omits this entry ?
Reply
#2
The Versions data is contained in the MyVideos database.
The feature is incomplete. Still to be implemented is the code to read Versions data from NFO files.

If you want to allocate a Versions type, follow this guide... https://kodi.wiki/view/Video_versions
My Signature
Links to : Official:Forum rules (wiki) | Official:Forum rules/Banned add-ons (wiki) | Debug Log (wiki)
Links to : HOW-TO:Create Music Library (wiki) | HOW-TO:Create_Video_Library (wiki)  ||  Artwork (wiki) | Basic controls (wiki) | Import-export library (wiki) | Movie sets (wiki) | Movie universe (wiki) | NFO files (wiki) | Quick start guide (wiki)
Reply
#3
Perhaps I have completely misunderstood the xml <edition> in this case. I always have a movie only once and in a single video version, everything else is thrown out. I just wanted to have a simple text in the info that tells me if it is an “extended version”, for example.

I also maintain the SQL database manually via an database program and the video version method is a bit too much of a good thing. I had assumed <edition> creates a simple info line such as <tagline>. Then it makes more sense to simply adapt the movie poster.
Reply
#4
(2024-10-30, 21:05)Daimonicon Wrote: Perhaps I have completely misunderstood the xml <edition>
Where are you seeing <edition>?
The nfo file only has the following tags (which are exported but unused by Kodi)
xml:
<videoassettitle>Standard Edition</videoassettitle>
<videoassetid>40400</videoassetid>
<videoassettype>0</videoassettype>
<hasvideoversions>false</hasvideoversions>
<hasvideoextras>false</hasvideoextras>
<isdefaultvideoversion>true</isdefaultvideoversion>
My Signature
Links to : Official:Forum rules (wiki) | Official:Forum rules/Banned add-ons (wiki) | Debug Log (wiki)
Links to : HOW-TO:Create Music Library (wiki) | HOW-TO:Create_Video_Library (wiki)  ||  Artwork (wiki) | Basic controls (wiki) | Import-export library (wiki) | Movie sets (wiki) | Movie universe (wiki) | NFO files (wiki) | Quick start guide (wiki)
Reply
#5
(2024-10-30, 21:12)Karellen Wrote: Where are you seeing <edition>?
As I said under <edition>. I could swear that Kodi has also taken this into account before via NFO. Mostly I had exported the NFO's via Ember Media Manager where you can specify “Edition”.

xml:

  <title>96 Hours</title>
  <originaltitle>Taken</originaltitle>
  <set><name>96 Hours Filmreihe</name></set>
  <sorttitle>96 Hours 01</sorttitle>
  <edition>Extended Cut</edition>
Reply
#6
(2024-10-30, 21:26)Daimonicon Wrote: <edition>Extended Cut</edition>
That is not a Kodi tag.
It must be added to the nfo file by a media manager. Are you using a media manager to create your nfo files?
Even the <set> tag positioned between the <originaltitle> and <sorttitle> tags tell me it is not a Kodi nfo file.
Can you post the entire nfo file contents. Use Kodi Paste Site site if it is a big paste, and provide the link
My Signature
Links to : Official:Forum rules (wiki) | Official:Forum rules/Banned add-ons (wiki) | Debug Log (wiki)
Links to : HOW-TO:Create Music Library (wiki) | HOW-TO:Create_Video_Library (wiki)  ||  Artwork (wiki) | Basic controls (wiki) | Import-export library (wiki) | Movie sets (wiki) | Movie universe (wiki) | NFO files (wiki) | Quick start guide (wiki)
Reply
#7
The position of the tag can easily be due to the fact that I corrected the files manually because EMM exports entries twice. However, all this works without any problems, so Kodi probably doesn't care about the position.

You are probably right, the position at EMM export is different, but as I said above...

NFO File

I have made a test export and added all values without sense for illustration. I don't have access to the previous info at the moment.
Reply
#8
(2024-10-30, 23:16)Daimonicon Wrote: The position of the tag can easily be due to the fact that I corrected the files manually because EMM exports entries twice
No problems. I was just commenting that it didn't look like a Kodi generated nfo file.
Ok, so you are using Ember Media Manager. It is important to know this from the start as it becomes easier to diagnose your report.
Most Media Managers export tags that are either for their own internal use, or for compatibility with another Media Centre.
In that nfo file, there are a quite a few tags that are not Kodi tags. This is not a problem, as Kodi just ignores them and skips to the next tag in the nfo file.

(2024-10-30, 21:26)Daimonicon Wrote: <edition>. I could swear that Kodi has also taken this into account before via NFO
How?
What do you see, and where do you see it, to make you think Kodi uses the <edition> tag, or a similar tag, from the nfo file?
Post a screenshot where you see it, if you can.
My Signature
Links to : Official:Forum rules (wiki) | Official:Forum rules/Banned add-ons (wiki) | Debug Log (wiki)
Links to : HOW-TO:Create Music Library (wiki) | HOW-TO:Create_Video_Library (wiki)  ||  Artwork (wiki) | Basic controls (wiki) | Import-export library (wiki) | Movie sets (wiki) | Movie universe (wiki) | NFO files (wiki) | Quick start guide (wiki)
Reply
#9
(2024-10-30, 23:35)Karellen Wrote: This is not a problem, as Kodi just ignores them and skips to the next tag in the nfo file.

That explains a lot and probably makes sense.
 
(2024-10-30, 23:35)Karellen Wrote: How? What do you see, and where do you see it, to make you think Kodi uses the <edition> tag, or a similar tag, from the nfo file?

I thought he had used the <edition> tag by simply adding this tag to the end of the usual movie title. So movie “Taken 2” Kodi gives out “Taken 2 (Directors Cut)”. If Kodi doesn't use this tag at all, then I must have added it myself to the corresponding movies and simply forgot about it. So I don't have a screenshot, my assumption came from the time when I still used the NFO's as data storage.

Makes sense to make a DB export as NFO from Kodi itself to be sure that the NFO's then contain everything that is necessary and important as a backup.
Reply
#10
(2024-10-31, 10:58)Daimonicon Wrote: Makes sense to make a DB export as NFO from Kodi itself to be sure that the NFO's then contain everything that is necessary and important as a backup.
Yes.
Certainly use EMM to create your initial nfo files to add to Kodi.
After that, you should run a regular Export to Separate Files from Kodi. This keeps the nfo files updated with any changes you make to your library, like changing the titles, or making your own Sets/Collection. It also keeps track of the Playcount and Last Played data.
My Signature
Links to : Official:Forum rules (wiki) | Official:Forum rules/Banned add-ons (wiki) | Debug Log (wiki)
Links to : HOW-TO:Create Music Library (wiki) | HOW-TO:Create_Video_Library (wiki)  ||  Artwork (wiki) | Basic controls (wiki) | Import-export library (wiki) | Movie sets (wiki) | Movie universe (wiki) | NFO files (wiki) | Quick start guide (wiki)
Reply
#11
Thank you, I will do so. So I have a reasonable backup and a reference to pure Kodi NFO's.
Reply

Logout Mark Read Team Forum Stats Members Help
<edititon> xml location in sql DB ?0