Set EPUB series and volume metadata from one human-readable source card rather than inventing values while moving through an export wizard. A card containing series name, volume number, volume title, author, edition, and publication date gives every rebuild the same reference point.
Separate numbers that answer different questions
A volume number identifies a book's place in a series. An edition identifies a revision of that volume. A publication date belongs to that edition. A “2” embedded in a file name cannot reliably tell you which meaning was intended.
Some workflows use volume zero to represent a standalone book. Do not silently treat zero as an empty field. “No series,” “standalone volume in a managed series record,” and “volume one” are different states. Write the intended meaning beside the number on the source card.
Make the source card understandable without the software
List series name, volume number, volume title, author, publisher, language, edition, publication date, and output name. One document should own those values. If two spreadsheets can each overwrite the other, the publishing software cannot determine which one is correct.
The EPUB package document has distinct areas for metadata, its manifest of resources, and its spine of reading-order items. Those standard roles are described by EPUB 3.3. They are not the same as a retailer's product form.
Transfer the card through Rune Studio's wizard
Enter work title, author, publisher, language, and output name on Series Information. Use Volume Selection to choose the standalone or numbered volume. After source and chapter choices, use Metadata for edition, publication date, and cover. The Review and Export page is the moment to compare every visible value with the card.
For volume two, also check that volume-one artwork or dates have not survived from a copied workspace. Give the output a name that identifies the work as well as the number; a bare digit is easy to misfile.
In a three-chapter structural run, a series title and volume number 2 were entered and later found in the generated package information. Title, author, and language values were also present, and the local package check succeeded. This supports the local metadata transfer. It does not test how a store will display, replace, or group those fields after upload.
Return to the field that owns the mismatch
A wrong volume number belongs back on Volume Selection, not in a renamed output file. A wrong series title belongs on Series Information. A wrong date belongs on Metadata. If the source card itself conflicts with another approved record, settle that source conflict before making another EPUB.
The card becomes most valuable when volume three begins: shared series values stay stable while volume-specific values are intentionally replaced. Rune Studio can carry those decisions through its six-page EPUB workflow, but it cannot decide the authoritative publishing data for you. Consult its current Mac feature scope and reconcile retailer fields separately.
