EPUB metadata editing should begin with a field-by-field inventory, not with the prose. A duplicated volume can contain the new manuscript while retaining the old language, edition, or publisher metadata. The title visible in a reader is therefore not enough evidence. The useful question is whether the intended values reached the package document in the exported file.
Build a two-column record before touching the duplicate
Create a small metadata card with the source volume on the left and the intended volume on the right. Give the title, series, volume number, edition, manuscript language, author, publisher, and publication date their own rows. If a value is supposed to remain unchanged, repeat it instead of leaving the cell blank. A blank cannot tell a later reviewer whether the value was deliberately inherited or simply forgotten.
Consider a Japanese first volume reused for an English second volume. The series and publisher may stay, while the display title, volume, language, and edition change. That decision belongs on the card before the editor opens. Proofreading the manuscript or replacing artwork belongs to a different pass. Mixing those jobs makes it difficult to identify which action changed the package.
This method does not depend on Rune Studio. With another EPUB tool, preserve the source package, export a numbered duplicate, unzip that copy, and inspect content.opf. The important safeguard is keeping the original and the candidate side by side. Never repair the only copy while you are still trying to discover which metadata is wrong.
Map each value to the six-page EPUB wizard
In Rune Studio, open EPUB Output. Page 1 holds series-level information: work title, author, publisher, writing direction, file name, and manuscript language. The volume choice and volume-specific metadata are handled later. Page 3 chooses source manuscripts, page 4 fixes chapter order and table-of-contents inclusion, page 5 contains edition and publication details, and page 6 summarizes the package before export.
The controlled STUDIO-141 run used four chapter files. The command-line counterpart supplied a synthetic title, an author, Publisher-141, horizontal writing, and ja to rune epub series set. It then supplied volume number 0, version 1.1, and a test publication date to rune epub volume set. rune epub select fixed the four-file order. Before writing a package, rune epub plan reported the planned chapters and destination.
Those command names expose the same separation the wizard presents. Changing manuscript text does not change the package language. Editing a volume value does not repair a missing navigation entry. When a page 6 value is wrong, return to the page that owns it, make the correction, and advance to the summary again. The exported file belongs in the workspace’s EPUB directory, not over the source manuscript.
Read the package instead of trusting the form
The four-chapter specimen was exported to a new file and reopened with rune inspect epub. The local inspection returned valid=true, seven spine entries, a navigation document, an NCX file, and four navigation links. Seven spine entries do not mean that the specimen contained seven manuscript chapters; generated title, navigation, or colophon pages can also participate in reading order. Use the spine to check sequence and the navigation document to check links.
The package’s content.opf contained the synthetic work title, the language value ja, the test publisher, and version 1.1. These are measured facts for this specimen. A series relationship or volume label may use different metadata vocabulary depending on the export design, so it should be accepted only after the relevant OPF element has been identified. Do not infer a package field merely from the wording of an interface label.
EPUB 3 requires a navigation document, but the presence of that document does not prove that the bibliographic values are correct. Likewise, valid=true here is a local structural result. It does not promise retailer acceptance or identical presentation in every reading system.
Route each stale value to its actual owner
If an English derivative still reports ja, return to the manuscript-language choice on page 1. If the old edition or date remains, return to the volume metadata. If the title is correct but the chapter links are wrong, the repair belongs in page 4’s order and table-of-contents choices. This routing prevents an unrelated manuscript edit from becoming part of a metadata fix.
Do not hand off a package that contains both the old and new value without an explanation. Export another numbered candidate. Search the complete package for the old title, old language, and old edition, then search for the intended replacements. Record “old value absent” separately from “new value present.” Keeping the rejected candidate makes the correction reproducible and gives a reviewer a real before-and-after comparison.
A common failure is to rename the EPUB file and assume its internal title changed with it. The filename and OPF title are independent. Another is to see the new title on the title page and skip the language field. A third is to count four chapters and reject a seven-item spine without noticing generated pages. All three errors come from asking one visible clue to stand in for a different package property.
Decide when Rune Studio is the right tool
Rune Studio fits projects that keep manuscripts, ordering decisions, and EPUB settings in one workspace and repeat the same export route across volumes. Its wizard makes the ownership of the values visible, while the CLI provides a bounded way to plan, export, and inspect a synthetic copy. That combination is useful when several people must repeat the handoff.
An EPUB specialist or direct OPF inspection may be better when a finished package contains unusual third-party metadata, when only one obscure element needs investigation, or when a distributor requires a vocabulary not covered by the current workflow. In either case, the metadata card remains useful. The tool changes; the need to compare intended values with the exported package does not.
This article does not cover encoding repair, image rights, retailer-specific review, or device-by-device rendering. Those questions need their own evidence. Limiting the claim makes the metadata decision stronger, because a clean OPF is not presented as proof of every other property of the book.
Close the handoff only when three columns agree
Finish with three columns: intended value, wizard summary, and exported OPF. The work title, language, publisher, and version should agree across all three. Record the reading order and navigation results in separate rows. For the controlled specimen, the measured package had four navigation links, seven spine entries, version 1.1, language ja, and a successful local inspection.
The completion point for EPUB metadata editing is not pressing Export. It is reopening the numbered EPUB, proving that stale values are gone, and locating the new values in their actual package fields. Start with one short duplicate rather than the production master. Once that card can be repeated, apply the same field ownership and readback to the real volume.