Nova accepts the following files.

  • Cover
  • PDF
  • XML
  • EPUB
  • Assets (various multimedia files)

Cover Image

The cover image is mandatory for books. The cover must be in this specification exactly.

The preferred format for the cover is a PNG. image of 600 x 800 pixels.

File naming convention: cover.png

The Nova platform supports GIF, BMP, JPEG, PNG images in your content. so you should usually provide your images with the maximum resolution.

The ZIP file can contain an “assets” folder (optional) that contains all other associated files such as images and supplemental data files.

Nova Structure

The nova package must contain a ZIP file and the Manifest.xml. Both should be in the same name.

Manifest Structure

The manifest.xml file should follow the below format. You will need to capture the additional informations as exactly mentioned in the sample below. And this has key information about the content, please ensure before upload the information in the mainfest.xml. Here, we have mentioned Price information for reference.

@access-type attribute: The access types:  COMPLIMENTARY  (or)  OA  (or)  PAID.

Package Type : full-book (without full text)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE nova PUBLIC "nova" "nova.dtd">
<nova content-type="full-book" full-text="no">
    <chapter type="sample" file= "sample1.zip" access-type= "OA"/>
    <chapter type="sample" file= "sample2.zip" access-type= "OA"/>
        <book file="fullbook.zip">
            <price GBP= "10" USD= "30"/>
        </book>
</nova> 

Package Type : full-book (with full text)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE nova PUBLIC "nova" "nova.dtd">
<nova content-type="full-book" full-text="yes">
    <chapter type="sample" file= "sample1.zip" access-type= "OA"/>
    <chapter type="sample" file= "sample2.zip" access-type= "OA"/>
       <book file="fullbook.zip">
            <price GBP= "10" USD= "30"/>
        </book>
</nova> 

Package Type : chunk-book (without full text)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE nova PUBLIC "nova" "nova.dtd">
<nova content-type= "chunk-book" full-text="no">
    <chapter type="sample" file="sample1.zip" access-type="OA"/>
    <chapter type="prelims" file="prelims.zip" access-type="OA"/>
    <chapter type= "sample" file= "sample2.zip"/>
    <chapter file= "ch01.zip">
        <price GBP= "10" USD= "30"/>
    </chapter>
    <chapter file= "ch02.zip">
        <price GBP= "10" USD= "30"/>
    </chapter>
    <chapter file= "ch03.zip">
        <price GBP= "10" USD= "30"/>
    </chapter>
</nova> 

Package Type : chunk-book (with full text)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE nova PUBLIC "nova" "nova.dtd">
<nova content-type= "chunk-book" full-text="yes">
    <chapter type= "sample" file= "sample1.zip" access-type= "OA"/>
    <chapter type= "prelims" file= "aaa.zip" access-type= "OA"/>
    <chapter type= "sample" file= "sample2.zip"/>
    <chapter file= "aaa.zip">
        <price GBP= "10" USD= "30"/>
    </chapter>
    <chapter file= "aaa.zip">
        <price GBP= "10" USD= "30"/>
    </chapter>
    <chapter file= "aaa.zip">
        <price GBP= "10" USD= "30"/>
    </chapter>
</nova> 

Package Type : in-press (upcoming books)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE nova PUBLIC "nova" "nova.dtd">
<nova content-type="in-press" full-text="no">
	<book file="filename.zip" released-on = "September 25, 2020" access-type="OA">
            <price GBP= "10" USD= "18" original_price = "$30.00" save = "$11.02" />
    </book>
</nova> 

Table 1: Element description

ElementAttributeDefinitionValue
novacontent-typeFormal reference identification of the contentchunk-book, book, chapter
full-textFormal reference identification of the content typeYES / NO
chaptertypeFormal reference identification of the sub divisionsample, prelims, Ch01, etc
fileName of the fileaaa.zip
access-typeDigital Price / Open AccessOA, Complimentary, Paid
priceGBPPrice type10
USDPrice type30
INRPrice type10

Zip File Structure (full-text= no)

The Zip file can contain Assets, EPub, XML, PDF files, and cover image.

Supplementary data, as characterized by the DTD documentation, are extra “information files that contain data straightforwardly supportive of the document, for instance, an audio clip, movie, database, spreadsheet, applet, or other external file.” When given, these should be described in the XML document and tagged with the <supplementary-material> tag.

Click here to download the sample packages.zip