5.0
Table Of Contents
- Avid iNEWS User's Guide
- Contents
- Using This Guide
- iNEWS System
- Getting Started
- The iNEWS Workspace
- Toolbars
- Working with Queues
- Changing Forms for Viewing Queues
- Changing the Width of a Queue Form Field
- Easy Locking a Queue
- Key Locking a Queue
- Moving a Queue
- Opening a Queue
- Refreshing a Queue
- Searching for Text in a Queue
- Specifying a Destination Queue
- Unlocking a Queue
- Using Abstract Display in Queue
- Using Currency Total
- Viewing Queue Properties
- Working with Wires
- Stories - Creation and Modification
- Moving Stories
- Stories - Protection
- iNEWS Projects
- Scripted Stories
- Displaying a Production Cue
- Enabling Autoscript
- Adding a Production Cue to a Story
- Adding a CG Production Cue
- Adding a Video Production Cue
- Adding a Still Store Production Cue
- Moving a Production Cue
- Deleting a Production Cue
- Using Script Templates
- Using CG Title Entry
- Primary Machine Control Event Placeholder
- Using MOS Placeholders
- Unscripting a Story
- Production Tasks
- Producer Basics
- Endorsing a Story
- Inserting a Break Line
- Ordering a Queue
- Calculating Backtime from Out Time
- Displaying the Show Timing Clocks
- Establishing Broadcast Control in a Queue
- Loading a Rundown Queue into Broadcast Control
- Placing a Rundown Queue in Show Timing Mode
- Production Locking a Queue
- Setting Clock for Show Timing
- Setting Story Start Times in a Rundown Queue
- Synchronizing a Story
- Synchronizing the First Story
- Synchronizing a Rundown Queue During Broadcast
- Timing Story Text
- Timing a Show
- Floating a Story
- Tracking a Show
- Printing
- Messages and Mail
- Sessions and Preferences
- Macros
- Searching in iNEWS
- Local Databases
- Connecting to a Remote Service
- System Shortcuts
- Icons
- Glossary
- Index
Local Database Security
204
For instructions on creating folders and queues in your local database, see “Creating a Folder in
Your Local Database” on page 207
and “Creating a Queue in Your Local Database” on page 208.
Forms and Print Styles for Local Databases
In iNEWS, forms are created and assigned to queues to customize the type of information that
appears in the stories in those queues. These forms must be synchronized with forms in the
server database and assigned to local queues; otherwise, story forms might look unfamiliar in the
local database. Systems often contain many forms, but not all forms are necessary for a local
database.
Also, styles, defined in the server database for the purpose of printing stories, should be
synchronized so that those styles are accessible in the Local Printing dialog box when printing
stories from the local database.
When forms and styles are locally synchronized, copies of forms (
FORMS.QUE
) and styles
(
Styles.FLD
) on the remote server are copied to the local computer—the location varies
depending on the computer’s operating system—after which, you can select forms, via the
Queue Properties dialog box, to assign them to queues in the local database and choose styles
when printing stories from your local database.
To locally synchronize forms and styles, contact your system administrator.
In some cases, your system administrator will create a “starter” local database, synchronize
forms and styles, and assign forms to that local database’s queues. This starter database can be
kept as a master copy, and a batch file can be created that copies it to multiple workstations so
that all users begin with identical local databases. The system administrator might also want to
open
FORMS.QUE
for the “starter” local database to remove unnecessary forms and reduce the
local database size.
After the local database folder, forms, and styles are on the PC’s hard drive, you can choose the
local database when you log in to iNEWS.
Local Database Security
The system’s database has security on the iNEWS Server. Directories and queues in the database
on the remote server can be protected by read and write groups. In addition, users can lock their
queues and individual stories if they want.
However, local databases do not have the same security protection because they are not part of
the database on the iNEWS Server. Because they are not on the iNEWWS Server, it is not
possible to assign read or write groups to local databases, and users cannot lock queues or stories
in the local database.