External sources: SQL, CSV, and Code Sources
Calling Code Sources from templates
Each Silva Publication, Folder and Document has
a property screen that can contain metadata and other settings
describing that item. Some of the metadata is used to create so-called
‘metatags’ in HTML, that are used by Internet search engines when indexing your site’s pages.
Navigate to the Document, Folder or Publication and click on properties in the top navigation bar of the Silva management area. (Fig. 1.)
Fig. 1. Metadata elements in properties
You
can change the metadata associated with an item by filling in values in the properties screen.
For
some metadata
elements, it is very useful to be able to acquire values from the
Folder or Publication the content is in. This way an element like
“description” only needs to be
filled in once per subsite, instead of for each and every page
of the
subsite. In Figure 1 you can see that the description is acquired from above.
When the content of an element can be acquired from its parent this is indicated by a dagger (†) in the “acquired content” column for that element. If there’s nothing entered higher up in the tree, then this column will be empty except for the dagger. If an acquired value is present then the dagger is shown at the end of the text.
Certain information is filled in automatically by Silva. The core items such as creation time, modification time etc. in the silva-content and silva-meta sets are defined by Silva itself and are needed for Silva’s operation.
Metadata of Publications, Folders and Assets is not versioned and can always be edited.
In case of versioned content like a Silva Document, metadata is versioned along with the document content. The metadata becomes uneditable as soon as the document version is approved. In this case the properties screen will just display the metadata without allowing the user to edit it. As soon as a new editable version of the item is created, the metadata becomes editable again. The published version’s metadata is still available to the public site, however, until a new version with changed metadata is published.
(Developers should note that on a code level this set is termed silva-extra, a misleading name because today it’s essential.)
In the properties screen a radio button can be checked to allow the item to be displayed or hidden in Tables of Content. The “hide from tables of content” option is visible at the bottom of Fig. 1.
When a Table of Contents is displayed in a public page, the hidden items are filtered out. This filter does not function when previewing a document containing or TOC because it could be a temporary setting that the will be changed for publication.
© Copyright 2002-2008 Infrae.
All rights reserved.