You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
No. This is a distinct feature request, not correction of existing behavior.
Describe the solution you'd like
Kodi and related systems use .NFO files (XML formatted) with the same name as the media file to store metadata. Feature would entail reading this file to obtain information to populate data fields for import.
Describe alternatives you've considered
Scraping from a Kodi web interface is one possibility, but it really isn't ideal.
Additional context
Kodi NFO to Stash Schema mapping (approximate)
Direct map:
title -> title
plot -> details
More complex mapping:
genre(s) -> scene_tags (scene_tag mapped to tag with same name, create new tag if new)
actor(s) -> performer_scenes entries connecting to performer with name of actor entry
rating -> rating (converting float n/10 to int n/5)
studio -> studio_id of studio with like name (complicated by possibility of multiple studios in Kodi format)
Import of images specified in the NFO file is another matter altogether, and should probably be relegated to another issue.
This is distinct from For conversion from #428 in that it involves actual import of metadata from a Kodi-esque library.
This is distinct from stashapp/CommunityScrapers#413 in that it involves scraping from Plex/Kodi, not the export of data from Stash.
This issue is connected to that filed at stashapp/CommunityScrapers#429
The text was updated successfully, but these errors were encountered:
Hey, guys, i created an Emby scrapper if you are interested, i am still testing it but it basically takes the exact path of the file from the stashdb database, and makes an itemssearch on the emby api with that path and some additional filters and maps everything together.
Is your feature request related to a problem? Please describe.
No. This is a distinct feature request, not correction of existing behavior.
Describe the solution you'd like
Kodi and related systems use .NFO files (XML formatted) with the same name as the media file to store metadata. Feature would entail reading this file to obtain information to populate data fields for import.
Describe alternatives you've considered
Scraping from a Kodi web interface is one possibility, but it really isn't ideal.
Additional context
Kodi NFO to Stash Schema mapping (approximate)
Direct map:
More complex mapping:
Import of images specified in the NFO file is another matter altogether, and should probably be relegated to another issue.
This is distinct from For conversion from #428 in that it involves actual import of metadata from a Kodi-esque library.
This is distinct from stashapp/CommunityScrapers#413 in that it involves scraping from Plex/Kodi, not the export of data from Stash.
This issue is connected to that filed at stashapp/CommunityScrapers#429
The text was updated successfully, but these errors were encountered: