This topic describes a typical workflow of wire stories from ingestion till publishing and archiving.

Wire stories from multiple sources (A) get dropped, from a wire receiver, as XML or ANSI files, in a series of hot-folders on a Back4 server (B), where the Back4 service runs and polls all the hot folders, each with a separate Back4 queue. The service extracts the metadata from the processed content, and then stores wire stories in the database on the database server (C), that makes the content available to users through the IIS server(s) (D). The content appears as a wire story with no page geometry.

Each wire agency is imported as a separate content feed , so the users can search them also by the source.

There might be two typical scenarios for wire stories workflow: scenario #1, that includes the "wire scrollers" role, and scenario #2, where all users access all wires directly.

A typical wire stories workflow in the scenario #1 starts on the wire scroller screen (1). A wire scroller is a user that reviews all wire news and preselects those considered useful and important, and stores them in collections of wire stories. A newspaper may have one or more wire scrollers. In that scenario #1, all other users do not access the full wires listing, but only the collections. This provides a better efficiency to the wire stories processing, as it decreases number of entries the writers and other users have to review when dealing with wire stories.

The wire stories added to a collection may disappear from the wires listing (not deleted, but just hidden), or can remain within, but marked as a part of a collection.

Anyway, the wire scrolling is an optional role which does not exist in many newspapers; therefore, in such newspapers the scenario #2 takes the place: all the users access to all the wire stories, and may be using or not the collections for additional preselection. In such case, the role (1) is moved to the writers (2).

Writer (2) reviews the wire stories (preselected or all, depending on the previously mentioned scenarios; to review preselected wire stories, the writes opens the appropriate collection. At this point, a writer merges one or more wire stories to an article (existing, or new), and edits the copy. When done, writer sends the article to the appropriate editor (3).

Editor (3a) edits the article that contains wire stories, and optionally enriches it by adding a headline, images, multimedia etc, performs fact checking and spell checking.

In some newspapers, editors (some or all) create also the Web & channels related content, by adding to the article the channel-related elements (webhead, webbody)and so on, previewing article for Web, and scheduling it for publishing, or publishing it directly on Web. In other newsroom, this task is assigned to another role, named Web editor (3b).

In any case, the IIS server (D) sends the channel-related content to the Web server (E) that generates a Web page.

When done, the editor (3a) sends the article in the folder which is dedicated for the content ready to be laid out on page.

Page designer (4) lays out the article, linking it to the page. When the page designer saves the page, the geometry and formatting is added to the article, so a fit text to shape can be performed by someone, either by an editor (3) or by a sub (5) who edits to fit, writes and adjusts the headline and performs the final check of article.

Note: In some newspapers, the roles of page designers and subs are merged and such role is called a page sub (4-5): in that case, a page designer role (4) does not exist at all, but all the job is performed by the page sub: designing shapes and linking article, assigning formats, adjusting images, editing to fit and so on.

Page sub (4-5) also sends pages to press, in the PDF format, so they become a "newspaper".

The page, containing wire stories enclosed in articles and other content, together with other pages in the edition, gets archived, and eventually processed by librarians (6) that enrich the content.

Sometimes later, a scheduled process on the database server, automatically creates a virtual edition of the newspaper (M), and makes it available to subscribers over Web.

The items involved on the Back4 server:

•Back4 hot-folders

•Back4 queues

•Data source templates with workflows

•Logging of activities

The items involved on the Database server:

•Storage

•Searches

•Export of edition to the virtual newspaper

•Purging of old wire stories

The items involved on the Web server:

•Web export with workflows through publishing destinations

•Web templates

•Web comments

See also

Wires