EPUB Creation with Series and Volume Metadata Kept Consistent

An abstract editorial scene showing how to transfer series name, volume number, volume title, and date from one authoritative card

Create a series volume by separating values shared across every book from values unique to the current volume. Keep series name, author, publisher, and language on a shared card; keep volume number, volume title, publication date, and edition on a volume card.

This guide creates a new second volume. Editing one existing EPUB and assembling navigation, cover, and colophon are separate workflows.

Use two source cards

Copy the canonical series spelling from the shared card. On the volume card, record numeric volume 2, the second volume’s title, and its date. Do not mix the display phrase “Volume 2” with a field that expects the number alone.

When starting from volume one, change only volume-specific values. Retyping the shared series name invites punctuation and spacing differences.

Build the second-volume test

  1. Enter the shared series, author, and language values.
  2. Enter volume number 2 and the second volume title.
  3. Select only the second volume’s chapters.
  4. Review title and chapter count before export.
  5. Inspect series name and volume number in the generated package.
  6. Compare shared and unique fields with volume one.

Rune Studio supports series and volume metadata in EPUB output. The completed test used volume number 0, the single-volume setting. It is not evidence for a generated volume two, so this article presents volume two as the required test rather than an accomplished result.

Recover without disturbing shared fields

If the volume remains zero, correct the volume card and leave the canonical series name untouched. If volume-one chapters appear, repair the selected files separately from metadata. Inspect package contents instead of trusting the output filename.

Repeat the smallest proof on another day

Before adopting the second-volume package, close the project and repeat the smallest useful path later. Record the shared card, volume card, chapter set, series name, and numeric volume field. A result that depends on memory or an already-open preview is not yet a dependable routine.

Keep one untouched copy and change a single condition per retry. If the second run differs, identify whether the source, operation, or inspection changed before expanding the scope. This rehearsal is also the point to keep volume two inferred from the single-volume setting clearly labeled as unverified rather than filling the gap with an assumption.

The next practical step for the second-volume package is to prepare the smallest useful copy and write down its expected result before touching the production manuscript. Extend this particular workflow only after the observed result matches.

Conclusion

Consistent series EPUB creation depends on keeping shared metadata stable while changing only the volume card. Testing completed so far covers volume zero, not volume two. Build a short two-volume test and compare both packages before using production manuscripts. Explore Rune Studio’s series metadata features