Full_Service_Vendor_Guide_to_eText_Production (3)

The Full-Service Vendor'sGuide to eText ProductionContents1. System Requirements for eText v4.8.x2. Pearson's eText Production Process3. Getting Started4. Acquiring Metadata from the Content Manager5. Assembling and Preparing Source Files for eText Ingestion6. Upload contents of etext folder to the Content Manager FTP Server7. Initiate Ingestion with the Standard eBook Workflow8. Additional eText Enhancements9. Update the Title Metadata10. Validate the eText11. Upload to the Authoring Server12. Other Important Content Manager Features13. Related Documentation1. System Requirements for eText v4.8.xNote: The following are the platforms and operating systems in which the eText is officiallysupported, although an eText may operate correctly using other versions of operating systemsand browsers or with other configurations.Windows RequirementsWindows XP, Windows 7, Windows 8Intel® Pentium® II 450 MHz or faster processor (or equivalent)128 MB available RAM (256 MB or higher recommended)20 MB hard drive spaceSupported browsers: IE 8.0, IE 9.0, IE 10 (Desktop Version), Chrome 23.0 or higher, andFirefox 16.0 or higherMacintosh RequirementsOS X version 10.6.x or 10.7.x*Intel Processor256 MB or higher RAM20 MB hard drive spaceSupported browsers: Safari 5.1, Safari 6, Firefox 16.0 or higher*One-finger and two-finger swipe gestures are not supportedChromebookOS 23.0 or higherNote: there is no offline CD-ROM package support for the Chromebook. 1

Other RequirementsAdobe Flash Player 10.2, 10.3, 11.1 and 11.2iPad app Requirements v1.2iPad1, iPad2, iPad3 or iPad mini w/ iOS5 or higherAndroid app Requirements v1.2Android 7\" and 10\" tablets w/ OS v3.1 or higherAccessible via Google Play onlyMost Android tablets come pre-loaded with a single app store. The most popular is Google Playbut there are others including Amazon Appstore for Android, GetJar, AppBrain, and SlideME.Each store is different and, in addition to having its own UI and connections to its servers, eachapp store offers customers and app sellers its own sales/purchase rules and incentives.The Pearson eText apps for Android are available only from Google Play. If you are supportingor selling to a customer that is using an Android device which does not use Google Play, it maybe because the device does not comply with Google's compatibility requirements or the devicemanufacturer does not support Google's licensing agreement. The Pearson eText for Androidapps only run on Android devices that meet these requirements. There are no immediate plansto support alternative app stores.Although the eText Authoring system includes a Mobile Preview, it does not actually display thePDFs that will be used with a Pearson eText app. the Mobile PDFs can be reviewed using aContent Manager utility. The primary purpose of the Mobile Preview is to confirm thatappropriate links are included and incompatible links have been excluded.2. Pearson's eText Production ProcessAn eText OverviewThe Pearson eText system includes four components: the Content Manager FTP server, andthe Content Manager, Authoring and Viewer applications. Customers use the Viewer to accessand interact with the finished eText using a computer, while Pearson eText apps are used with atablet, such as the iPad. When used with a computer, Pearson’s eText is essentially a SWFviewer with an interactive overlay provided by XML. For tablet delivery, pages are presented byPDFs and use more or less the same XML for interactivity. Because the iPad does not work withAdobe's Flash, some of the links or other enhancements to an eText may not be appropriate foruse with the iPad, so they're filtered out.During eText ingestion, hi-res printer PDFs and other files are uploaded to the Content ManagerFTP server, where they are processed to generate a set of high-resolution SWFs for use withthe eText Viewer, and a set of thumbnail images that will be used to display search results. ThePDFs are also processed to extract the text contents of every page, which is then distilled tobecome a keyword database for that eText. In addition, a set of highly-optimized, lower-resolution PDFs are generated for use with Pearson’s eText mobile apps. Finally, for thoseeTexts that will be used in conjunction with the Pearson eText Digital Library, the ContentManager can generate the 2

Multiple Environments, Multiple ServersThere are several instances of the eText system: DEV, used by the eText developers toformulate the code for upcoming improvements and new features for the eText system; CERT,which is where the new code is tested and any bugs resolved; PPE, the Pre-ProductionEnvironment, is used for a last review before installation into the Production environment and isalso used for eText test ingestions; and PROD, the Production Environment, where eTexts thatwill be published to the Viewer and used by customers are produced. Each of these systemshas unique URLs for the Content Manage component, as well as a corresponding FTP server,and each has multiple Authoring servers. PROD1 Authoring is used mostly for Higher Ed,International and PLS eTexts. PROD2 Authoring is primarily reserved forSchool group use, andPROD3 Authoring is used exclusively by the Pearson Custom Library.3. Getting StartedCreating an eText will require separate accounts for the Content Manager FTP server, as wellas the Content Manager and Authoring applications. Contact [email protected] [email protected] for access accounts to the Content Manager FTP server and theContent Manager and Authoring applications. Various resources are available for eTextproduction. All of the guidelines, MS Excel spreadsheet templates, examples and instructionsfor their use can be found on the Media server athttp://media.pearsoncmg.com/cmg/intranet/ebookplus/spreadsheet.html. Other resources arecurrently available on the Pearson Knowledge Base athttp://kb.pearsoned.com/eText_Production, though this resource will soon shift to Neo.The eText Content Manager FTP serverThe eText Content Manager FTP server uses Secure File Transfer Protocol (SFTP) whichrequires use of an FTP client that supports the SFTP protocol. In preparation for eText ingestion,PDFs and other files are uploaded to a series of folders that are created on the server -- anenclosing parent folder with several subdirectories within it. It is essential to reset thepermissions of any folders/subdirectories uploaded or created on the server so that the ContentManager is able to process the materials and generate various files and folders during ingestion.Using a Macintosh with an FTP client, the process of resetting folder permissions is relativelysimple and straightforward. After creating the various folders and subdirectories, all of thenewly-created folders can be selected and their permissions can be adjusted by typingCommand-I or selecting Get Info from the File menu. Clicking the Group Write checkbox willresult in the permissions configured to 775. Failure to properly reset the permissions of thefolders will result in an immediate failure as soon as ingestion is initiated.With a PC FTP client, and a folder selected, choose Properties and adjust the folderpermissions.The URL for the PROD Content Manager FTP server issftp://ftp.ebookcm.pearsoncmg.com//home/ebookcmftp_prod/ . See the eText File SubmissionGuidelines for more detailed information about uploading files.The PROD eText Content Manager URL is http://ebookcm.pearsoncmg.com/ebook/The eText PROD1 Authoring server is athttp://auth.ebookplus.pearsoncmg.com/ebook/authoring.do (for Higher Ed/International/PLS) 3

PROD2 Authoring is at http://auth.etext.home2.pearsoncmg.com/ebook/authoring.do (forSchools)PROD3 Authoring is at http://auth.etext.home3.pearsoncmg.com/ebook/authoring.do(exclusively for Pearson Custom Library)The eText Content ManagerBe careful when entering the case-sensitive username and password for either the ContentManager or Authoring applications. Three unsuccessful attempts will lock the account.On initial entry into the Content Manager, the Workflow Status tab is displayed. There areseveral other tabs that may be available, depending on the level of access a particular accounthas. For typical eText production, the following workflow tabs are available: Standard eBook;Simple eBook; Accessibility; Offline Packaging; Audio Text Synch Up; and Quiz. In addition tothe various workflow tabs, the Content Manager has a History button in the lower left corner ofthe window. With the radio button of a particular eText selected, clicking the History button willdisplay all of the actions, successes and difficulties that have been encountered whileprocessing an eText.By default, the Content Manager Workflow Status tab displays the most recent projectsprocessed by the account used to access the application. When Show All Jobs is selectedinstead of Show My Jobs from the Jobs selector and the Search button is clicked, all of the Jobscurrently in progress will be displayed. The search can be further refined by making selectionsfor Workflow and/or Business Unit, as well as by entering Identifier, Title, Authors, Global BookID, and/or Book ID and clicking the Search button.The Accessibility tab is not used with the PROD Content Manager. The Accessibility tab hasbeen designed to produce an HTML-based eBook using NIMAS files and other material for input.Because the process puts heavy demands on the server, a separate system has been set up tohandle processing of Accessible eBooks.The Offline Packaging tab is used to produce eText offline packages -- self-contained versionsof the eText that will work when hosted on a server other than the eText live Viewer, or whendelivered on a CD or DVD. The right side of the Offline Packaging tab is also used to makederivative and self-derivative copies of an eText.The Audio Text Synch Up tab is used to incorporate additional XML and audio files that togetherprovide highlighting of words or sentences or other sections of text synchronized with audioplayback. This feature is used primarily by the Schools group.The recently introduced Quiz tab is used to process spreadsheets containing quizzes andquestions to generate a collection of files for a simple quiz that can be linked from an eText.The two most important Content Manager tabs for eText production are the Standard eBookand Simple eBook workflow tabs, which correspond to the two main ways that an eText can beproduced. 4

Standard eBookThe Standard eBook workflow uses XML that has been extracted, and processed through theCompositor's Toolkit, which is comprised of FileQA and the Desktop Conversion Toolkit. Whenproperly tagged during the composition phase, the page geometry of those tags from QuarkXpress or Adobe InDesign pages is transformed into the x/y location and width/height of\"hotspots\" or clickable links in the eText. These links can be table of contents or index links,which when clicked brings the user to a specific page within the eText. Cross-reference linksmay link from one part of the eText to another, such as when referencing another section, afigure or an illustration.The Standard eBook workflow uses: 1. Extracted and processed XML, including bookinfo.xml, regioninfo.xml, basket.xml and (if available) glossary.xml 2. Optional Basket, Hotspot or Audio spreadsheets 3. High-resolution printer PDFs 4. Required cover, thumbnail and navigation bar artworkSimple eBookThe Simple eBook workflow was developed to provide an alternative way of producing an eTextwhen properly tagged XML isn't available or won't process correctly. Instead of XML, theessential table of contents information is provided through a formatted MS Excel spreadsheetthat lists the various entries and associated PDF files.The Simple eBook workflow uses 1. Required Table of Contents spreadsheet 2. Optional Basket, Glossary, Hotspot or Audio spreadsheets 3. High-resolution printer PDFs 4. Required cover, thumbnail and navigation bar artwork4. Acquiring Metadata from the Content ManagerWhen the Standard eBook workflow will be used to produce an eText, the following steps arerecommended prior to processing the XML with the Compositor's Toolkit. The full-servicevendor should: 1. Log into Content Manager application at http://ebookcm.pearsoncmg.com/ebook/ 2. Select the Standard eBook workflow tab 3. Determine the appropriate Content Manager FTP server directory path for uploading the eText production files by first selecting the appropriate Business Unit (for the Full-Service Vendor, this will be HigherEd in most instances), and then selecting the appropriate Sub-Business Unit and finally, the appropriate Directory. The available choices for Sub-Business Unit are determined by is first selected for Business Unit. In turn, the available choices for Directory are determined by what has been selected 5

for Sub-Business Unit. Appropriate selections can usually be determined from the title of an eText, For example, the appropriate selections for the Higher Ed title \"Introductory Statistics: Exploring the World Through Data\" should be standardebook / highered / math_sciences / statistics. If the appropriate selection is not evident, contact the Business Unit project manager for guidance.4. With those selections, log into the Content Manager FTP server and navigate to the appropriate corresponding directory on the Content Manager FTP server. In that directory, create a new subdirectory, naming it with the ISBN-10 or ISBN-13 of the eText. If that folder name is already in use, the name can be further modified by adding a prefix or a suffix to make it unique. The name of this parent enclosing folder will be used by the Content Manager as the eText's Identifier. Be sure to reset the folder’s permissions to 775. If the folder permissions are not reset, ingestion or any other processing will immediately fail.5. Again log into the Content Manager application and select the Standard eBook tab.6. Enter the Identifier (the name of the newly-created parent enclosing folder for the eText) into the Identifier field and click the Acquire Metadata button.7. If the BU has properly planned for this eText and entered certain information in the Publication Control System (PCS), clicking the Acquire Metadata button will result in an automated message being sent to the email address of the account used to log into the Content Manager. That automated message will include a link to the metadata.xml for that title which will include the Global Book ID for this eText, along with other essential information such as title, author names and publisher/imprint. The Global Book ID is identified by \"eBookCM########”. The automated message may also include a link to a text (.TXT) file that details any missing values in the metadata.xml file. Contact the BU project manager to determine the appropriate information to be entered for any missing values.8. If the metadata.xml file is successfully generated, and any missing information has been entered, replace the default metadata.xml included with the Desktop Conversion Toolkit with this file prior to processing the XML files with the Compositor's Toolbox (See Section 5.1 for more details on compositor's use of metadata.xml).9. If the BU has not properly entered the required information into PCS, or if the Identifier of the enclosing parent folder is something other than just an ISBN, the Content Manager will display a message indicating that no metadata could be found when the Acquire Metadata button is clicked. Although acquiring metadata has failed, the Content Manager will still generate a Global Book ID that will now be displayed on the Workflow Status tab. This Global Book ID must replace the Global Book ID in the default metadata.xml included with the Desktop Conversion Toolkit prior to processing the XML files. The bookinfo.xml file can also be further edited to include the correct Author(s), Title, Edition, Publisher, Imprint, Publication Date, Copyright Year and the ISBN-10 and -13 for the eText, as well as the ISBN-10 and -13 for the parent text.10. Between the <art></art> tags in the bookinfo.xml file, enter the appropriate file names of the various artwork elements for cover, thumbnail, navigationbar, and 6

ipadcoverart. Each relative file path must begin with /assets/ followed by the corresponding file name.5. Assembling and Preparing Source Files for eText IngestionOnce the metadata.xml or global book id has been acquired, the compositor can beginpreparing the files for eText ingestion.5.1 XML 1 The compositor runs Full File QA validation on Final Pass XML until all files pass validity check (the compositor must be using version 3.401 or greater of the Compositor Toolkit. See Pearson_File_QA_v3401_documentation_XID.pdf for details on required software). a If the job is a legacy title, you must run xmlcheck on the legacy XML files before proceeding. The most recent version of xmlcheck tests more rigorously for errors that can cause issues with etext workflow (e.g., it is more robust in detecting untagged url's). 2 Once final pass XML is successfully validated, the compositor places the metadata.xml file acquired in step 4. Acquiring Metadata in the /Application/etm folder (replacing the existing metadata.xml file) a If the compositor received only a Global Book ID and not a full metadata.xml file, the compositor: i Opens the metadata.xml located in /Applications/etm ii Finds the global book id (which looks like this: <book bookid=\"CM32591130\">) and replaces it with the Global Book ID acquired in the Acquiring Metadata step b Do not proceed to the next unless you have an updated metadata.xml file or at least the Global Book ID. 4 The compositor selects xml-to-be-validated folder and drops it on the Compositor Toolkit Applescript 5 The compositor selects eText: Generate bookinfo, regioninfo, glossary, and basket XML option then presses OK. 7

a The toolkit will process the XML-FINAL folder and i transform XML-FINAL into a modified format called XML-EBOOK-PLUS (a form of the XML better understood by the conversion toolkit) ii run eText-specific QA checks on the XML iii run the eText Conversion Toolkit to create an etext output folder with the following structure:iv shows validation report 8

6 The compositor reviews the error logs via eText_qa.html report 7 If there are any errors, the compositor a Fixes the XML-FINAL located in XML-TO-BE-VALIDATED then runs process again 8 If the compositor is not sure what caused the error, post a query to Pearson Knowledge Base at http://kb.pearsoned.com5.2 Book PDFsPlace the high-resolution print PDFs following the eBook+ PDF guidelines [update link to PDFguidelines] in the ingest/pdf/hi-res-pdf folder. If the book is a 2-color book, the PDF's CYANmust be changed to the appropriate Pantone Color in CMYK. • The PDFs must be PDF 1.4 or PDF 1.5, using CMYK color space, cropped or uncropped • If uncropped, PDFs must include valid trim box • If cropped, PDFs should not be cropped by adjusting the media box • When composition is with Adobe InDesign, export as PDF • Optimization within Acrobat highly recommended • What you see is more or less what you get. • No spot colors, no replacement colors • No hidden elements • No larger than 30 MB for a single page PDF • No larger than 300 MB for a multi-page PDF, with no single page larger than 30 MB • For additional information, refer to the eText PDF Guidelines.5.3 Cover, Thumbnail, and Navigation Bar ImagesThe cover image must be provided as both PNG and rasterized PDF at 150 dpi ~1008 pixelswide, and will typically have a file size of 1-1.6 MBA thumbnail of the cover image should be provided in PNG format at 150 dpi / 90 pixels wide,and proportionately highThe navigationbar image should be provided by the Business Unit in PNG format at 150 dpi /120 pixels wide by 80 pixels high. 9

Place the cover, thumbnail and navigationbar images (see Art Assets Guidelines in theingest/assets folder.6. Upload contents of etext folder to the Content ManagerFTP ServerUsing an FTP client, upload all of the contents of the \"etext\" folder – except – the root-levelXML folder to the previously created Identifier folder on the Content Manager FTP server. It isessential that the permissions of these newly uploaded folders are set to 775 or 777. If thefolder permissions are not reset, ingestion or any other processing will immediately fail.7. Initiate Ingestion with the Standard eBook Workflow 1. Log into the Content Manager application and search for the eText using the Global Book ID or Identifier. 2. With the appropriate eText selected by clicking the Select radio button on the Content Manager Workflow Status tab, navigate to the Standard eBook tab. 3. Click the check box next to \"Glossary XML, Basket XML, Region Info XML & Audio XML\", then click the Create button. This action should generate a manifest.xml file in the xml folder within the 1.0 folder. Verify successful generation on the Workflow Status tab. The manifest.xml file serves as something of a packing list and enables finer control of many eText ingestion processes. 4. Once the manifest is successfully generated, select the eText in the Content Manager Workflow Status tab and return to the Standard eBook workflow tab. 5. Click on any of the checkboxes in the PDF processing section. Note that clicking on any of them selects all of them: PDF Cropping, SWF, Thumbnail & Text; iPad PDF Processing; Process from Optimized PDF. It also selects the Process For Digital Library checkbox. Any of these checkboxes can then be individually deselected. At this time, because of server space issues, the Process For Digital Library checkbox should be de- selected -- unless the BU has indicated that this eText is to be part of a Digital Library. This general guidance may be modified at some future date. 6. Click the Create button to initiate PDF processing. 7. Click on the Workflow Status tab to confirm that processing is in progress. An instantaneous failure is usually an indication that folder permissions have not been set correctly or some required materials are not available where the Content Manager expects to find them. The status of an ingestion can be periodically updated by clicking the Workflow Status tab. The time it takes for ingestion processing of the PDFs to complete depends on the number of pages in the text and the complexity of artwork on the pages. Processing of 600 pages typically takes about 30 minutes. 8. Upon completion of processing, an automated message will be sent to the email address of the account used to initiate ingestion indicating whether processing was successful or not. If processing is not successful, the email will include links to various logs that will help to diagnose what needs to be corrected. 10

8. Update the Title MetadataIf the metadata.xml file for an eText was not successfully generated, or if the defaultbookinfo.xml file included in the Compositor’s Toolbox was not modified to include the actualtitle, edition, author, publisher, imprint, prices and ISBNs prior to processing the ETMv2/XIDXML files through the Compositor’s Toolbox, the correct author, title, edition and otherinformation will need to be manually entered. While it’s possible to download the bookinfo.xmlfile for editing offline, the Content Manager provides a convenient user interface to facilitate thisprocess. 1. After successful ingestion and transformation of the files, log into the Content Manager and with the eText selected from the Workflow Status tab, navigate to the Standard eBook workflow tab. 2. Click on the Manage Bookinfo button. This will open a separate window. 3. Update the fields as necessary to incorporate the appropriate information for the title 4. Click the Update Bookinfo button at the bottom of the window9. Validate the eTextDuring validation, the Content Manager validates all of the XML ensuring that it’s well-formedand complete, and checks to make sure that all of the component XML, TXT, SWF, iPad PDF,cover artworks and other required files are present. Successful validation is required before theeText can be uploaded to the Authoring server. By default, HigherEd, International and PLSeTexts will be sent to PROD1 Authoring, School eTexts will be uploaded to PROD2 Authoring,by default. PROD3 Authoring is reserved for Pearson Custom Library (PCL) use. 1. After successful ingestion and transformation of the files, log into the Content Manager and with the eText selected from the Workflow Status tab, navigate to the Standard eBook workflow tab. 2. Click the Validate button in the lower left corner to initiate validation of the eText. When validation is complete, an automated message will be sent to the email address of the account that initiated validation, confirming successful validation or failure. If validation has failed, the message will include links to logs that will be useful in diagnosing and correcting any issues encountered.9. Launch the Content Manager Preview 1. After successful validation, the title of the eText becomes hyperlinked in the Workflow Status tab. Click this link to launch a new window with two frames. Above each frame is a selector which permits side-by-side comparison of any combination of the original source PDF (the cropped PDF, actually), the Optimized PDF, iPad PDF, SWF, Thumbnail and extracted Text. If the eText has also been processed for Pearson’s Digital Library (DL), the DL page Images, Masked Images and Thumbnails can also be viewed and compared. 11

2. Select Source PDF in one frame, SWF in the other, and then use the next/previous buttons to navigate through the range of pages, noting any discrepancies between the two frames. It’s also possible to jump to a specific page by entering the page number in the field at the top of the window and pressing Enter or Return on the keyboard. 3. In transforming from PDF to SWF, it’s not unusual to encounter slight color or density shifts, but more pronounced rendering issues should be resolved before proceeding. If any rendering issues are encountered, compare the Optimized PDF to the Source PDF. When the entire range has been compared, select Source PDF in one frame and iPad PDF in the other and repeat the process. The Content Manager’s Preview is the only place that the iPad PDFs to be used in the mobile view can be seen prior to publishing the eText to the live Viewer. Rendering issues are generally caused by Source PDFs that were not prepared according to specifications, such as use of colors other than CMYK, hidden elements or layers, or problems caused by intense vector graphics. 4. The cover images can also be reviewed from this window by clicking either the View Cover Image or the View iPad Cover pdf. 5. After initial ingestion, it’s possible to select the pages of a previous version by selecting a version with the dropdown selector in the upper left corner of the window. 6. If no rendering issues are encountered, proceed to 11. Upload to the Authoring Server.10. Replace Selected PagesIf any pages display rendering issues, replacement PDFs will need to be ingested afterconstruction issues have been resolved. Rather than re-ingesting the entire eText, the ContentManager provides a convenient utility to enable ingestion of selected replacement pages. Whilethe Content Manager can ingest single pages or one or more range of pages, the replacementpages must be in a PDF which has the same total number of pages. For example, if the originalPDF had 35 pages and one page presented a rendering issue, the replacement PDF must alsohave 35 pages. 1. With an FTP client, navigate to the eText’s ingest / pdf / hi-res-pdf folder, identify the problem PDF and rename it by appending “-old” to the filename. 2. Upload the replacement PDF to the eText’s ingest / pdf / hi-res-pdf folder. 3. Log into the Content Manager and with the eText selected, navigate to the Standard eBook workflow tab and click the Replace Selected Pages checkbox. This will launch a new window. 4. In the Content Manager – Replace Pages window, enter one or more individual comma- separated page numbers in the Pages field. One or more page ranges can also be entered in the page ranges fields. Add another page range by clicking the plus sign (“+”) to the right of the page range fields. Page ranges should span similar kinds of numbers. For example, use one or more page ranges for Arabic numbers, and one or more separate ranges for Roman numbers. 5. Once all of the pages that need to be replaced have been listed as either comma- separated individual numbers or as one or more page ranges, click the Update Manifest button. 12

6. The Content Manager will send an automated message indicating that the manifest has been updated and will begin to generate optimized PDFs of the replacement pages – whether or not they are selected for subsequent ingestion(s). 7. When the optimized PDFs of the replacement pages have been successfully generated, the Content Manager sends an automated confirmation message. 8. Once the message is received or the Workflow Status tab confirms successful generation of the optimized PDFs, navigate to the Standard eBook workflow tab and click on any of the PDF processing check boxes. Unless the eText is also being processed for Digital Library, deselect the Process for Digital Library check box. If the replacement pages are not to be rendered from the Optimized PDFs, deselect the Process from Optimized PDF check box. 9. Click the Create button in the lower left corner of the window. The Content Manager will queue the job and begin to process the replacement PDFs, sending an automated confirmation message when the process is complete. 10. Review the replacement pages using the Content Manager’s preview feature to ensure that any rendering issues have been resolved. 11. Once all rendering issues are resolved, and with the eText selected in the Content Manager, return to the Standard eBook workflow tab and click the Process All Chapters check box. Click the Create button again. This resets the manifest so that all of the pages will be handled. 12. Validate again, and once validation is successful, proceed to 11. Upload to the Authoring Server.11. Upload to the Authoring Server 1. Once validation is successful, and the pages have been reviewed, navigate to the Standard eBook workflow tab of the Content Manager with the eText selected. While it’s not likely that the eText will need to be sent to a different server than the default selection, an eText can be uploaded to a different server by clicking one of the radio buttons on the Standard eBook workflow tab. When ready, click the Upload to Authoring button at the bottom of the window. 2. Two automated messages will be sent to the email address associated with the account used to initiate the action. The first will indicate that the eText has been sent to the Authoring server, and the second will indicate whether the eText has been successfully ingested into the Authoring. If there is a problem with ingestion into the Authoring server, the message will include links to logs that should be helpful in diagnosing and correcting the situation. 3. Once the eText has been successfully uploaded to the Authoring server, a hyperlinked “PROD1” or “PROD2” will appear in the Status (“S”) column of the Content Manager’s Workflow Status tab. Clicking the link will launch the Authoring server’s Preview for this eText in a separate window. To access the eText Preview, a login name and password are required. The shared account credentials for accessing the Preview currently are login name: viewonly / password: pa55word 13

With successful uploading to the Authoring server, the Book ID will also appear in the Workflow Status tab under the eText’s Global Book ID.12. Review the eText in the Authoring serverAfter receiving an automated message confirming successful uploading to the appropriateAuthoring server, or after verifying that success in the Content Manager’s workflow status tab,log into the Authoring server:PROD 1 (Higher Ed, International, PLS):http://auth.ebookplus.pearsoncmg.com/ebook/authoring.doPROD2 (School group): http://auth.etext.home2.pearsoncmg.com/ebook/authoring.doOn initial entry into the Authoring server for the first time, the Authoring Home bookshelf will beempty. After a few eTexts have been found and entered, as many as five eTexts will bedisplayed in the Authoring Home bookshelf, with the most recently viewed eText at the top ofthe list. In contrast to the eText Content Manager, the Authoring server has an online contextualHelp system, accessed by clicking the Help link in the upper right corner of the window. Clickingthe link will open a new window with information relevant to the currently viewed page. While it’spossible to search by the various available parameters listed in the dropdown selector, such asAuthor, Title, ISBN, etc., none of them are as reliable as the Book ID or Global Book ID.Searching by ISBN, for example, can yield four or more results, and while some of those resultsmay be pointing to the same eText, there are some instances where more than one eText mayshare an ISBN with another. In similar fashion, many authors have written more than onetextbook, and several textbooks have similar titles. 1. Search for the eText by entering either the Global Book ID or the Book ID in the Search For field, then select Book ID or Global Book ID (as appropriate) from the dropdown selector and click the Search button. This will display a list, along with a thumbnail of the cover, of all eTexts that meet the search parameter. 2. Verify that the cover thumbnail displays correctly and click on either the eText’s book cover or the eText’s title next to it to open that eText and access its Authoring Menu. 3. If the eText is designed to open with a left-hand page, instead of the default right-hand page, click the first link in the Authoring Menu to open “Preview and Enter Book Metadata”. a. Scroll down to the Orientation section b. Click the Verso radio button c. Scroll to the bottom of the window d. Click Save. 4. If the eText interface is to display an interface language other than English, or if the eText is to use the Elementary skin, or use underlined hotspots, or something other than the other default interface selections, click on the fourth link of the Authoring menu, 14

“Specify eText Language and Interface”, and make the appropriate changes. After making any changes, scroll to the bottom of the window and click Save.5. If a hotspot color other than the default has been specified in the conversion request, click the fifth link in the Authoring Menu, “Specify eText Interface Colors”, and enter the hex value for the color (http://www.webmonkey.com/2010/02/color_charts/). Scroll to the bottom of the window and click Save.6. If any custom icons have been provided and are to be installed, select the eighth link, “Upload Custom Icons”. The left half of the screen is for installing the Flash-based icons for use with the Mac/Windows view. The right side is for installing the PNG format icons that will be used with the Mobile view. Select the icon to be installed from the dropdown selector and then click the associated Browse button, navigate to the icon artwork in the window that appeared when the Browse button was clicked, select the artwork and click Open.7. With the appropriate modifications entered, click on the second link in the Authoring Menu, “Review eText Pages, Region Hotspots and Zoom Areas”, which will open the main eText authoring and editing window. Verify that the cover and navigationbar images8. Verify that all of the baskets that should be available, such as the Table of Contents and Glossary (if applicable) are visible and functional in the left-hand navigation bar.9. Verify the organization and structure of the Table of Contents, and confirm that the links in the Table of Contents work correctly by clicking various listings in the Table of Contents and verify that they point to the correct pages.10. Verify that any special characters in the TOC display correctly11. If a Glossary is included, verify that terms in the Glossary basket when clicked launch the Glossary window and display the correct term.12. Launch the eText Authoring Preview by choosing Student from the dropdown selector in the upper right corner of the window. Select the two-page view by clicking the two-page view icon above the navigationbar artwork. In the two-page view of the Preview, click the page forward arrow to view the first page of the eText and verify whether the first page is displayed correctly as a right- or left-hand page. Advance through the pages using the forward/backward arrows in the upper left corner of the window, verifying that the pages are cropped correctly, rendered correctly and that there is no unsightly gap between the pages. Verify that any hotspots are correctly sized and positioned, and function correctly. Though the links should not need editing, they can be adjusted using the eText Authoring Link Editing panel. When the eText is ready for First Review, copy the URL of the eText and send it and the shared access credentials (viewonly / pa55word) to the BU contact. 15

13. First CorrectionsAfter the BU has reviewed the eText, there may be a need to replace pages or to make othermodifications. Before any modifications are made to the eText, a self-derivative copy should bemade to capture and incorporate any edits that may have been made in the Authoring server.To create a self-derivative copy, the eText must first be exported from the Authoring server. Thebest way to export the eText from the Authoring server is to use the Content Manager utility.Creating a Self-Derivative 1. Log into the Content Manager and search for the eText using either the Book ID or Global Book ID. 2. With the eText selected, navigate to the Standard eBook workflow tab 3. Click the Backup button 4. Once the automated message is received confirming successful export, select the eText in the Workflow Status tab and navigate to the Offline Packaging tab. 5. Click the Verify button in the upper-right quadrant of the Offline Packaging tab to confirm that the exported files are available for use. 6. Copy the Identifier from the left-hand side of the tab and paste it into the Identifier field on the right-hand side. 7. Click the Generate Derivative e-Book button along the bottom edge of the tab. 8. An automated message will confirm successful validation of the self-derivative. 9. If any validation errors are encountered, they will need to be resolved before proceeding.With the eText successfully backed up and those files used to create a self-derivative, the eTextcan be safely edited to make further modifications or add various enhancements, such asadditional baskets, a glossary (if one was not originally included) and links to externally hostedrich media assets by ingesting the CustomBasket.xls, CustomGlossary.xls orCustomHotspot.xls spreadsheets. The backup serves as a snapshot of what was on theAuthoring server prior to modifications and can be used to restore what was there if anythinggoes wrong.Exporting to MS ExcelContent exported from the Authoring server can, in many cases, also be transformed back intoa Microsoft Excel spreadsheet. This is particularly useful when additional baskets or additionallinks are to be added to the eText. 1. Log into the Content Manager and search for the eText using either the Book ID or Global Book ID 2. With the eText selected, navigate to the Standard eBook workflow tab 3. Click the Export to Excel button 4. The automated message confirming successful export will have links to download the various Excel spreadsheets that have been generated. The exported spreadsheets can also be found in the final / recycle directory found at the top level of the eText’s parent enclosing folder, and can be downloaded from there with an FTP client. 16

Merging Additional ContentExported spreadsheets can be merged with any other corresponding spreadsheets provided bythe Business Unit to be incorporated into the eText. This is especially important for ingestingadditional links via a CustomHotspot.xls spreadsheet that the BU may provide, because theexported spreadsheet will have captured the location and size of any existing links in theAuthoring server. When the BU provides additional links in the form of a CustomHotspot.xlsspreadsheet, such as select the content of the cells, copy it and paste it into the exportedspreadsheet at the end of that spreadsheet’s existing content, ensuring that the columns alignand leaving no blank rows.Ingestion Processing of the CustomHotspot.xls spreadsheet 1. Upload the edited spreadsheet to the eText’s ingest / assets directory using an FTP client. 2. Log into the Content Manager and search for the eText using the Book ID or Global Book ID. 3. With the eText selected in the Content Manager’s Workflow Status tab, select the Standard eBook workflow tab 4. Click the Manage Manifest button 5. In the window that appears, configure the manifest to process the spreadsheet by selecting the check boxes for regioninfo and for replaceregions in both the Content Manager and Authoring columns. 6. Click the Update Manifest button 7. In the Standard eBook workflow tab, click the check box for Glossary XML, Basket XML, Region Info XML & Audio XML 8. Click the Create button. 9. Once ingestion is completed and the automated confirmation message is received, click the Validate button on the Standard eBook workflow tab.Ingestion Processing of the CustomBasket.xls spreadsheet 1. Upload the edited spreadsheet to the eText’s ingest / assets directory using an FTP client. 2. Log into the Content Manager and search for the eText using the Book ID or Global Book ID. 3. With the eText selected in the Content Manager’s Workflow Status tab, select the Standard eBook workflow tab 4. Click the Manage Manifest button 5. In the window that appears, configure the manifest to process the spreadsheet by selecting the check boxes for glossary in both the Content Manager and Authoring columns. 6. Click the Update Manifest button 7. In the Standard eBook workflow tab, click the check box for Glossary XML, Basket XML, Region Info XML & Audio XML 8. Click the Create button. 17

9. Once ingestion is completed and the automated confirmation message is received, click the Validate button on the Standard eBook workflow tab.13. Related Documentation ● Art Asset Guidelines (last update November 2011) http://media.pearsoncmg.com/cmg/intranet/ebookplus/eText_Art_Asset_guidelines.pdf ● eText PDF Guidelines (last update January 2012) http://media.pearsoncmg.com/cmg/intranet/ebookplus/eText_PDF_guidelines.pdf ● eText File Submission Guidelines (last update January 2012) http://media.pearsoncmg.com/cmg/intranet/ebookplus/eText_File_Submission_Guideline s.pdf (This document describes how files should be organized and uploaded to the eText Content Manager FTP server in the upload directory. FSVs will instead upload directly to the specified ingestion folders.) ● Pearson File QA Documentation [Available on the Knowledge Base] ● Troubleshooting bookinfo, regioninfo, glossary, and basket xml creation [To be posted on the Knowledge Base by Ben Ko.] 18