Using the
Custom e-Catalog Development Site
This page is under construction

The Custom e-Catalog (CeC) Development Site provides an environment in which to develop CeCs. From this site developers will be able to:
Get basic status information regarding an account.
Upload, delete and review files.
Validate files against the Thomas Register HTML and CeC Specifications.
Send review notifications. (Recipients of the review notifications will be directed to the 'CeC Proof Site' from which they can review and approve a catalog or submit revisions)

Accessing the CeC Development Site
Find the account by using the search options on ProofStat and navigate to the main 'Web Catalog Information' product screen.
Click the 'Custom e-Catalog Development' tab to access the suite of tools for developing CeCs.

Developing a CeC
Develop a Custom e-Catalog (CeC) according to the Custom e-Catalog Specifications.

Upload the files to the CeC Development Site for the account being worked on. It is not necessary to upload the entire catalog each time. Partial catalogs and individual files can be loaded. Existing files on the development site will be overwritten by files of the same name.

Currently it is necessary for all uploads to the CeC Development Site to placed in a .zip archive, with the .zip file being named 'az.zip', where 'az' is the 8-digit AZ Number of the account being worked on.

Within the development site are links to:

Review your Catalog: Review the catalog as it is being developed, ensuring that it displays and functions as intended.

Validate your CeC Catalog: Validate a 'work in progress' catalog against the standard Thomas Register Web Catalog and Custom e-Catalog specifications. Using this validation is not mandatory, but may help troubleshoot problems before they become widespread. Note that client review notifications cannot be sent for catalogs that do not pass validation, nor will invalid catalogs be submitted for publication.

View or Delete Files: Clicking the 'View or Delete Files' link will display the index of files. A total count of the files in the directory appears at the top of the file index.

To View a specific file:
Click on the file name in the list. The file will display in a new window.

To Delete files:
Select individual files to delete by clicking the check box to the left of the file names.
Select ALL files by clicking the 'Select All Files' button.
Deselect ALL files by clicking the 'Clear All Selections' button
Delete the selected files by clicking the 'Delete All Selected Files' button. Following a delete operation, the count of files in the directory is updated accordingly.

Proofing a CeC
All Thomas Register hosted Custom e-Catalogs require that an approval be recorded before being published. Upon receipt of approval the catalog will automatically be submitted for publication on the Thomas Register Web Site. For this reason the catalog must pass validation before a review notification can be sent.

The proofing process is initiated by clicking the 'Send a Proof Notification' link under step 2 on the CeC Development Site. Upon clicking this link the validation process will begin.

If the catalog fails validation a 'Review Notification' cannot be sent. The catalog will need to be revised accordingly.

If the catalog passes validation, the 'Review Notification' screen is displayed, with a field for entering any 'Developer Comments'. The 'Review Notifications' contain the following information:
Account name and address
The URL for accessing the proof
Developer contact information, as entered in the ProofStat registration
Developer comments

Works in Progress (WIP)

Notifications can be sent for the review of WIP catalogs. However, to avoid WIP catalogs being approved and submitted for publication it is strongly recommended that the developer include information relevant to this situation in the 'Developer Comments' field and either:
Request that the catalog reviewer 'Disapprove' the catalog, so it will not be submitted for publication or
Provide an alternate method of communication for providing feedback.

A method for better supporting WIP catalogs is being developed.

In ProofStat II the CeC developer cannot choose who receives the 'Review Notifications'. Notification recipients are designated by the Thomas Register Sales Rep via the 'Notification Management' feature available in the ProofStat interface for that User Group. The designated recipients will appear as static text on the 'Review Notification' screen, to the right of the 'Developer Comments' field. The Sales Rep will receive the notification by default. (The sales rep information is not currently displayed in this area).

Approved catalogs will be automatically submitted for publication to the Thomas Register Web Site. An approval confirmation will be e mailed to all notification recipients and the developer.
If a catalog is disapproved, the developer will be notified via email, which will contain any notes, comments, or instruction supplied by the reviewer.

Publishing a CeC

Approved catalogs are automatically submitted for publication to the Thomas Register Web Site. Unlike with the previous CeC procedures the developer does not need to return to the CeC Development Site to submit the catalog for publication.

Before being published catalogs undergo an internal review by Thomas Register Production staff. This review generally takes place the same day the submission is received.

Upon publication of the CeC, a confirmation will be e mailed to the sales rep, all notification recipients, and the developer.