Getting Started

Steps for Starting a Catalog

The production of online catalogs at Rutgers utilizes database management software called Catalog Navigator (CN), which was developed by a Canadian software vendor, Decision Academic (DA), now part of CSDC Systems.  Two servers host CN: a development site (https://cndev.rutgers.edu) that is useful for testing and trainings new users and a production site (https://cn.rutgers.edu) where the catalog actually is built.

1. Make a copy of old catalog and paste it into the current Catalog Group (e.g., Rutgers 2012) and Karen’s Catalogs (for safekeeping).
2. Contact the client.
3. Have the client identify all users and what level access/permission they will need access (read-only/edit, etc.).
4. Set up appropriate access groups, users, and workflows following these guidelines:
   
   1. Set up Access Groups.  Name them according to what level they will be in the workflow.
   2. Input user information and apply them to an Access Group.
   3. Create a Workflow. Name each stage according to what level they will be approving (i.e., Editor 1, Editor 2, Approver, etc.). Apply the appropriate access group to the appropriate level.
   4. Apply the Workflow to the catalog.
5. Have the client identify editors and approvers for the workflow.
6. Get all users names, emails, Net ID’s and enter them into the system, assigning them to the correct catalog and access group. The catalog editor (Karen Imperiale) can do this for the catalog project manager or see the sidebar instructions on this page
7. Conduct training if necessary. Go over simple editing. Hand out Users Manuals. See simple CN Training Notes.
8. Create production schedule with client’s input.
9. 9. During the production process: develop first page of useful URLs for specific catalog: use last online version, work with client to update, approve. Submit as WORD document to lab when catalog is done.

Sample Catalog Production Schedule

After clients have been trained and have had a chance to test CN skills on the development site (cndev.rutgers.edu) give them one month to make first-round edits

• First-round edits done by school by 11/12
• First-round edits approved by PM by 11/19
• Second-round edits by school due 12/7
• PM approves these and passes on to proofreader by 12/14
• PM approves proofreader's changes and submits to school for final read by 1/14
• School final reads done by 1/28
• UR does an in-house final read by 2/18 (this takes a long time based on workload of unit)
• PM approves and enters all/generates catalog in HTML in conjunction with web lab by 2/29 (see instruction below).
• PM sends out memo announcing availability and URL of online catalog to client group and specified others (See University Announcement)

{NOTE:  If the client school is taking too long in making its first-round edits, the second round may need to be skipped in order to get the catalog completed within a reasonable time frame.}