null

Skip to end of banner
Go to start of banner

Pictures

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Pictures can be stored locally on the workstations (or network drives) or within a content server. With setting Log. Path in the navigation definition (please see Navigation Definition) the path can be defined, where local pictures will be stored or temporary pictures will be checked in, when they are stored in a content server.

Local Pictures

In order to retrieve locally stored pictures, the following name convention is required:
[KLASSENART]_[KLASSE].[ext], whereas [ext] stands for the file extension, which has been set under the navigation definition, parameter Type (see Navigation Definition).
Example: 001_KLASSE019.gif.

Pictures in Content Server

If pictures are stored within a content server, a class document must be created for each class. Therefore transaction CL02, Class administration, tab Document is used.


The picture to be shown must be checked-in and parameter Type must match the navigation settings (see Navigation Definition).
Furthermore the following name convention is required:
[KLASSENART][BELIEBIGERTEXT][KLASSE].[ext], whereas [ext] stands for the file extension, which has been set under the navigation definition (see Navigation Definition), parameter Type.
Before displaying the picture, a local copy is created. With [BELIEBIGERTEXT] it is possible to ensure, that only the current picture will be shown. It is recommended to use an increment or date value for [BELIEBIGERTEXT].
Example: After picture 001_20090101_KLASSE019.gif has been up-dated, it should be stored with a new name, e.g. 001_20090113_KLASSE019.gif.

Data Sheets

A data sheet can be assigned to each class, regardless the data format. Special name conventions are required. They are analog to the name conventions for pictures (see chapter Pictures), only text „datasheet_" must be put in front.
For locally stored datasheets the following convention must be used:
datasheet_[KLASSENART]_[KLASSE].[ext]
For data sheets which are stored on the content server:
datasheet_[KLASSENART][BELIEBIGERTEXT][KLASSE].[ext]

Because underscore "_" is used as a separator, it may not be used either within [BELIEBIGERTEXT] nor [KLASSE]. Also for the class names no underscore is allowed.

  • No labels