Microsoft Word



June 2011

For eText Production

Presented by:

The eText Team

Revision Sheet

|Release No. |Date |Revision Description |

|Rev. 0 |7/21/09 |Re-write (Charlene Smith) |

|Rev. 1.0 |2/22/11 |Update to Content Manager FTP, iPad view information |

|Rev 1.1 |6/09/11 |Update to Content Manager FTP |

NOTE: Revision requests are submitted ONLY for published (live) eText products. If you have not yet produced an eText product for your title, you will need to follow the traditional eText File Submission Process documentation and fill out the eText File Conversion Request online form.

Replacement source files (XML from ETM or Hi-res PDF) are required for any changes, additions, or deletions to the actual page content of your eText title. This includes textual changes, image/chart/graph/figure updates or any other content changes to the individual pages of the product. Please follow the guidelines below, assemble and upload all pages that you would like to be corrected for your eText product.

Types of changes often seen in revisions:

• Updating of actual textbook content such as Table of Contents, headings, any text, images, tables, etc.

• Changes, removal or additions of pages, sections or chapters.

• Masking of non-permissioned text and images.

• Revisions to existing hotspot or glossary linking if your original source files were XML from ETM and they have been re-worked and re-processed.

• Revisions to existing hotspot or glossary linking if an associated spreadsheet is going to be provided.

• New hotspot linking or glossary linking if an associated spreadsheet is going to be provided.

• Cover image(s) changes.

• iPad view creation

Required files for eText production of current titles

Page content changes: Assemble the high-resolution student edition print PDFs (see eText PDF Guidelines) for all of the pages which will need to be revised. If the revision to the product encompasses a re-flow of page numbering, ALL pages will need to be supplied for the revision to be completed.

This applies to:

• Updating of actual textbook content such as Table of Contents, headings, any text, images, tables, etc.

• Changes, removal or additions of pages, sections or chapters.

• Masking of non-permissioned text and images.

• iPad view creation

Cover artwork changes: cover, thumbnail and navigationbar artwork files (see Art Assets Guidelines) must be supplied.

This applies to:

• Cover images changes.

• High Resolution Cover etext pdf file for iPad view

Page ETM linking changes: If the title’s print production is based on the Quark-based ETMv2 workflow, the XML-EBOOK-PLUS folder, and the LOGS folder will also be required. The XML-EBOOK-PLUS folder contains XML files derived from the Quark production files using the latest Final File QA for ETMv2 tools.

This applies to:

• Revisions to existing hotspot or glossary linking if your original source files were XML from ETM and they have been re-worked and re-processed.

Linking spreadsheet changes: If the original eText title did not have custom hotspots, glossary or custom basket linking, and you would like to add these features to your title, the appropriate spreadsheets can be submitted during the revision process. Information on these spreadsheets is available through the spreadsheet information page, located on the CMSNA eText wiki production area.

This applies to:

• Revisions to existing hotspot or glossary linking if an associated spreadsheet is going to be provided.

• New hotspot linking or glossary linking if an associated spreadsheet is going to be provided.

Depending on the types of files being submitted for revisions, create the appropriate folder structure:

o Create a parent folder on a local hard drive.

o Name the folder with the corresponding eText 10-digit ISBN, the primary author’s last name, separated by an underscore (“_”) and “REV”. An example is 0321616618_ChaisREV. Do NOT use spaces or special characters in the filename, and the entire folder name must not exceed 20 characters

o Create three folders within the parent folder (all folder names are case-sensitive):

▪ ingest

▪ source_files

▪ info

o Inside the ingest folder, create two subdirectories:

▪ pdf

▪ assets

o Inside the pdf folder, create a subdirectory:

▪ hi-res-pdf

o Place the high-resolution print PDFs (see eText PDF Guidelines) from the student edition text in the hi-res-pdf folder.

o Place the cover, thumbnail and navigationbar images (see Art Assets Guidelines) in the assets folder.

o Place the High Resolution Cover text pdf (see Art Assets Guidelines) in the info folder.

If appropriate for this title, place the Glossary, Custom Basket, and/or the Custom Hotspots spreadsheet in the assets folder. (The Custom Hotspot spreadsheet, introduced with Release 3, replaces the Media Assets Link Map spreadsheet used with earlier eBook releases and enables automated ingestion of links to a variety of resources.)

o If the student edition was produced using the Quark-based ETMv2 workflow, create a qxp_xml subdirectory in the source_files folder

▪ Inside this qxp_xml folder, place the XML-EBOOK-PLUS folder and the LOGS folder, with their contents, that were generated using the latest Final File QA for ETMv2 tools.

Please note that any submissions which are not formatted or uploaded according to the instructions above will not be processed, will delay delivery of the eBook and will incur additional costs.

Uploading file(s) for production

Upload the folder containing the required file(s) to the following eText Content

Manager FTP location:

URL:

 

Username: ebookcmftp_prod

 

Upload starting paths:

 

 upload/highered (this is where files for eTexts for Higher Education titles are uploaded for conversion).

 

upload/international (this is where files for eTexts for Pearson businesses outside the US are uploaded for conversion).

Contact your CMS Project Manager for access credentials.

-----------------------

Revision Guidelines

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download