Use one source card for an EPUB series name and volume number, then compare the entered values with the generated package. In the controlled test, the series “北風航路” (North Wind Route) and volume 3 were confirmed. “白い岬” (White Cape), the requested volume title, was not: the current CLI has no separate volume-title field. The accurate result is therefore a partial pass, not a completed three-field setup.
Answer: Separate the two confirmed fields from the blocked field
Series name, volume number, and volume title should be separate rows in a metadata plan. Combining them into one improvised title may produce a visible label, but it changes the model of the book and makes later reconciliation unreliable.
The Rune Studio test set the series title to “北風航路” and selected volume 3. The generated OPF title was exactly “北風航路Vol.3,” and the volume read-back was 3. No independent field was available for “白い岬,” so the volume-title comparison remains blocked. This limitation must stay visible in the record.
Sample: A source card for North Wind Route, volume 3
The controlled card contained the series “北風航路” (North Wind Route), volume 3, the volume title “白い岬” (White Cape), author “高瀬凪,” and a publication date of August 31, 2026. Before touching the application, create rows for the requested value, the value actually entered, the value found in the exported package, and the final status.
- Series name: 北風航路
- Volume number: 3
- Requested volume title: 白い岬
- Status choices: matched, unverified, or unavailable
Keep “白い岬” on the card when the application has no matching field. Do not silently append it to the series name. That would turn a blocked field into different metadata rather than resolve it.
Operation: Create the series, select volume 3, and inspect the EPUB
The product-independent method is straightforward: freeze the source card, enter only supported fields, export the EPUB, and inspect the package document. A settings screen is an intermediate state; the exported metadata is the result that must be reconciled.
The title-specific Stage 4 run used a dedicated workspace and 12 recorded operations. It set the series with epub series set, using “北風航路,” author “高瀬凪,” horizontal writing, and language ja. It then added volumes 1, 2, and 3, set volume 3 to version 3.0 with the publication date 2026-08-31, selected two chapters, exported volume 3, and read the OPF and stored volume data back.
The resulting filename contained vol003. That is evidence for the selected volume number in this run, not evidence for a separate volume title.
Measured result: Series and volume matched; volume title was blocked
The title-specific result has status partial.
- Entered series title: 北風航路
- Entered volume number: 3
- Generated OPF
dc:title: 北風航路Vol.3 - Read-back volume number: 3
- Spine count: 5
- Image count: 0
- Missing images: 0
- Navigation document: present
- NCX: present
- Navigation items: 2
- NCX items: 2
- Local package check:
valid=true - Separate field for 白い岬: unavailable
A separate common Stage 4 run exercised the general EPUB path with four chapters, horizontal writing, and version 1.4. It returned spine=8, images=1, missing=0, nav=true, NCX=true, and valid=true. That record proves the bounded export path; it does not prove the blocked volume-title field.
Limits: Local validity is not retailer acceptance
valid=true is a local package result. It does not establish retailer acceptance, identical rendering in every reader, or the state of retailer-side series metadata. Retailer listing fields, review outcomes, and service-side metadata changes were not checked.
Use a field-specific return path. If the series differs, return to series information. If the volume differs, return to volume selection. If no volume-title field exists, return to the source card and keep “白い岬” marked as blocked until a supported mapping is chosen. Do not declare the whole card complete.
What Rune Studio covers
Current documentation for the Mac version describes a six-page EPUB wizard for series information, volume selection, manuscript selection, chapter order and table-of-contents inclusion, metadata, and final export. It generates an EPUB 3 package that includes nav.xhtml, NCX, and content.opf.
That workflow is Rune Studio functionality. The role of package metadata itself comes from the EPUB 3.3 specification; it is not a Rune-specific invention. The test supports using Rune Studio to set and reconcile a series name and volume number, but not to claim an independent volume-title field that the run did not find. The unfinished iPad implementation is also outside this article.
Conclusion: Keep the volume title unresolved instead of hiding the gap
For this source card, “北風航路,” volume 3, the exact OPF title “北風航路Vol.3,” and read-back volume 3 agreed. “白い岬” did not have a separate destination field and remains unverified.
Start by creating separate rows for the series name, volume number, and volume title. Reconcile the two supported rows with the exported package, and leave the unsupported row visibly blocked. Language metadata, edition switching, and supported language codes are separate decisions. See the Rune Studio product page for the current Mac feature scope.
