Metadata

Custom document metadata and predefined system metadata can be sent as HTTP header fields and extracted to variables by the StreamServer application.

Custom metadata

To enable the use of custom metadata in HTTP header fields, the metadata must be stored in the archive.

To extract custom metadata, you must use the following syntax:

strs-document-metadata-<metadata name>

Example 2

Extracting custom metadata

In this example, Customer name and Invoice number are stored as custom metadata.

$customer_name=GetHttpHeaderValue(Customer name);

$invoice_no=GetHttpHeaderValue(Invoice number);

 

Predefined system metadata

Some predefined system metadata must be stored in the archive to enable the use of it in HTTP header fields. Other metadata are always available to use in HTTP header fields.

Example 3

Extracting predefined system metadata

In this script example, the values of predefined system metadata External job ID, Sender number and Document type are extracted to variables.

$ExtJobID=GetHttpHeaderValue("FixedMetaData.ExternalID");

$Sender=GetHttpHeaderValue("FixedMetaData.Sender");

$doctypename=GetHttpHeaderValue("strs-document-type");

 

 

Predefined system metadata listed in the table below are available if they are stored in the archive.

Must be stored in archive	HTTP header field name
External job ID	FixedMetaData.ExternalID
Receiver	FixedMetaData.Receiver
Sender	FixedMetaData.Sender
Content type	BlobInfo.ContentType
Expiring date time	BlobInfo.ExpiringDateTime
Total BLOB size	BlobInfo.TotalBlobSize
Tracker ID	Part.TrackerID
Application domain ID	Part.ApplicationDomainID

Predefined system metadata listed in the table below are always available.

Always available	HTTP header field name
Part ID	Part.PartID
Creation date	BlobInfo.CreationDateTime
Control flags	DocumentControlFlags
Device independent copy flags	DeviceIndependentControlFlags
Document type	strs-document-type