iam4x / iam4x/bobarr

could not parse season number

Open
#219 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
1.7k
Forks
89
PR merge metrics
No merged PRs in 30d

Description

Hi all,
I just setup the project on my NAS using docker. I followed the setup guide on github. Right now the only problem i have is the scan library function is not detecting most of my content.

My structure is something like this and in the docker-compose.yml i have set volumes to /volume1/video:/usr/library. When I do scan library, for films the api shows 0 results. For tvshows, while the "bobarr-api" detects the tvshow names but does not find any episodes, except Onepunch man 😦

```
/volume1/video
|-films
|-- english
|---- Forest.Gump
|---- Iron.Man.3
|-- french
|---- ...
|-- spanish
|---- ...
|-- ...

|-tvshows
|-- Attack.On.The.Titans
|---- 1x01 - To You, 2000 Years in the Future The Fall of Zhiganshina.mp4
|---- ...
|-- Breaking.Bad
|---- Season.01
|------ 1x01 - Pilot.mkv
|-- One.Punch.Man
|---- One-Punch Man - 01 - The Strongest Man.mkv
|---- ...
|-- ...
```

After debugging further I found that, my NAS actually creates some metadata files for tracking internally using its media server module ( example : @eaDir / @SynoEAStream ).
`ScanLibrary - could not parse season number - {"season":"/usr/library/tvshows/Walking.Dead/@eaDir"}`

Would it be possible to provide a way in environment variable to ignore such files so that the scanner can work gracefully ?

Additionally, it does not seem to support nested structures. So can not find any content which has Season.01 under the tvshow name.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the ScanLibrary behavior described in the issue and the volume and environment settings in docker-compose.yml. Reproduce the scan using the shown nested TV-show layout and Synology metadata directories; done means metadata paths no longer cause parsing errors and episodes under Season.01 are detected.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose, typescript
Domain
backend, devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.