Book Scanner

---

This guide describes how the book scanner works as of server v2.5.0.

tagBook library scanner steps

1. Library is scanned and files are grouped into books.
   • Each audio and ebook files in the root of a library folder are considered an individual books
   • Otherwise, every folder with a supported media file is considered to be a book (including subfolders of the top folder)
   • Ebook files are ignored if scanning an "Audiobooks only" library
2. Check for missing books (priority given to filepath, falls back to inode value to handle renames)
   • All books in the library are checked to see if any are missing
   • Books can also be set as missing if all audio and ebook files are removed
3. Each book found by the scanner is checked to see if it already exists in the library. If a book already exists, it is checked for updates. If this is a new book, the same steps are made.
   • Newly added or modified audio files are probed (using ffprobe)
   • Audio tracks are ordered
   • Ebook files are checked
     • If not "Audiobook only" library, primary ebook is set with priority given to epub format.
     • All other supported ebook formats are added as supplementary
   • Cover image is cleared if missing. If no cover is set, an attempt is made to set the cover.
     • Cover image is set using an image file in the folder, priority given to files named "cover"
     • Otherwise, check for image embedded in audio file
     • Otherwise, if "Find covers" server setting is enabled search online for a cover (Note: This setting is planned to be replaced by a more comprehensize lookup)
   • Book metadata is parsed according to configured priority (see more)
   • The metadata.json is created or updated accordingly.
4. Authors and series are checked for removal
   • Authors are removed if they have no books and have no additional metadata set (image, description or asin)
   • Series are removed if they have no books

---

tagBook metadata parsing

Metadata priority is set in the "Scanner" tab of the library settings. Lower priority sources can fill empty fields if a higher priority metadata source does not include that information.

tagFolder structure

Book metadata is pulled from folder names according to the directory structure, author folder naming and title folder naming docs. The following metadata can be pulled from here: title, subtitle, asin, authors, narrators, series, series sequence, and published year.

tagAudio file meta tags

Audio file meta tags are found from ffprobe. After the audio files are sorted into track order (only) the first audio file will be checked for meta tags following the audio metadata docs.

tagdesc.txt & reader.txt files

If a file named desc.txt is found in the books folder it will be used as the description. If a file named reader.txt is found in the books folder it will be used as the narrator.

tagOPF file

If a file with .opf extension is found in the books folder it will be parsed. (Example OPF file coming soon)

tagAudiobookshelf metadata file

The metadata.json file is automatically saved anytime book metadata is set. If the "Store metadata with item" server setting is enabled then the metadata file will be stored in the same folder as your book (only for books in subfolders). Otherwise, the metadata file is stored in /metadata/items/.

Every book metadata field is stored in this file including chapters.