Silva
Silva Documentation

QuickStart Guides

Authors

Login

Adding Content

Kupu

Adding Properties to a Document

Importing Spreadsheet Data

Authoring Workspace

Editor Screen

Forms Editor

Document Publish Screen

Editors

Content Organization

Publishing

Access Keys & Shortcuts

Content Management Screens

Contents Screen

New Screen

Import Screen

Preview Screen

Properties Screen

Addables Screen

Publish Screen

Export Screen

Chief Editors

Author / Editor / Chief Roles

Groups

Viewer Roles

Roles and Permissions

Role Management Screens

Access Screen

Lookup Screen

Group Management

Access Roles Diagrams

Managers

Login Managers

Manager Roles

Adding Users

Adding External Sources

Groups

Improving Accessibility

API

Template Design

Silva Overview

Silva in an Organization

Silva Features

Index

The Publish Screen and Publishing Workflow

Approve, publish, and export content

Bulk publishing operations occur in the Publish screen. Documents, folders, and publications can be published to the web (opened to the public). Having the right to publish depends on your role. If you are an Author, you may request approval of your content, and the responsible Editor will review it. In order to make changes to the publicly visible site you need at least an Editor role.

Since the operations allowed depend on the role you play, the Publish screen changes accordingly. Authors and Editors see different controls.

publishj1.png

Fig. 1  Editors publish screen.

Author requests for approval

There are two ways to request approval, in the Publish Screen of a document, and via a bulk operation in the Publish screen of a Folder or Publication.

The advantage of using the Publish screen of a document is an Author can include a message that is received by the Editor. Likewise, the Editor can reply if for some reason the request is rejected. If Silva is setup with an Email Message Service, these messages will be sent by email, including an automatic link to the corresponding location. When using the Publish screen of a container, an automatically generated message is sent to the other party.

The following steps describe the process for an Author. (Fig. 2)

  1. Go to the Publish screen of the container where your content is located. The tab is located in the top navigation bar.
  2. Place a checkmark next to the items you want approved. You can use the “select all” selector (alt-a) as well.
  3. Fill in the “publish time”. If you wish you can fill in “expiration time”. See the section on publish time below for an explanation.
  4. Click the request approval button (alt-r) to send the approval request to the responsible Editor. Please check the feedback on the returning page regarding the success or failure of sending your request.
  5. If the Editor approves or rejects your request, you will be notified. At any time in between you can redraw your request by visiting the location and clicking the revoke
    approval button (alt-v).


approval.png

Fig. 1  Authors publish screen.

Editor publishes content

  1. Go to the Publish screen located in the top navigational bar.
  2. Place a checkmark next to the items you wish to publish. You can use the “select all” selector (alt-a) as well. (Fig. 1)
  3. Fill in a publication date (time is optional), or check the “publish right now” selector, which will use the current time as publish date. If necessary, fill in an expiration date and set it by checking “set expiration time?”.
  4. Click the open to public button (alt-o).
  5. Check the returning screen for success or failure of your approval.
  6. Any time after approval you can intercept the publication via the revoke approval button (alt-v). In this case it's a good idea to do this via the Publish screen of the content, since you can fill in a message in the “Message to author(s)” textarea to inform the author about the reason for the revocation.
  7. Alternatively you can close public content via the close (alt-c) button if you decide it should taken offline.


Notes

Publication and expiration date

If your content is approved, it will become publicly visible only within the time frame between publish time and expiration time. If you do not give an expiration date, the published content will remain public forever, or until someone closes it. Note that you have to check the “set expiration time?” checkbox when you want to set an expiration date, otherwise the expiration date will be ignored.

Content that is approved or published can have its expiration date settings changed. Fill in the new dates (time is optional) and click the set timing button (alt-s).

Publication state of Publications and Folders

You cannot publish publications and folders. Instead their publication state is managed via the content. A folder is considered published if it contains published content.

Reading information in the Publish screen

If you want to check the condition of the content, you'll find the information in the listing table of the Publish screen. This does not depend on your role; the information is always visible. In the listing ids are shown on the left (note that only publicly visible items appear, no folders or assets). Titles are indented to show the publication structure.

The relevant status information can be found in the three rightmost columns of the listing table (discussed from left to right).

Revision column

Displays information about the current version. The possible states are:

Publication due column

If a there is a publish time set in the future, the date is listed. Otherwise the cell is empty.

Expiration due column

If a there is an expiration time set, the date is listed. Otherwise the cell is empty.

Published column

Information about the published, non-editable version. This may contain a blue “published” link for currently public versions, a gray “closed” note for closed or expired versions, or be empty if there is no public version. If the content is published then it’s linked to the publicly visible page.

Versioning of documents

Once content is published a new version can be created. The published version stays online for the public, while the editable version can be worked on, or approved with a publication date in the future.

When published, content cannot be reverted back to an editable state. The content can only be closed, which takes it offline, or a new version can be created.

Content that is closed can be re-published directly, without having to first make a new version.

Exporting content

The entire text of publications, folders, and documents can be exported as Silva XML, or – if the Docma server is running on your network – as an MSWord document, which can be edited and imported. These activities occur in the Export screen.



© Copyright 2002-2004 Infrae.
All rights reserved. mail