Fieldpine Logo Documentation Home  
Library
» Overview
» eLink API

eLink retailmax.elink.media.list

Returns metadata about the available media for a given item and area. This might be a single product, customer, store or a complete "area" such as all stores. It is not possible to get all information from all areas in a single call (too much data)


Media information, typically photographs, is uploaded via each areas normal edit methods. For example images of products are added by calling retailmax.elink.product.edit and supplying the image in f199

Input Arguments

Arg#BinaryDescription
3's'Required. Constant 'retailmax.elink.media.list'
9's'Predicates to select data to return.
8 or 20'E'Maximum rows to return.
100'E'Mode Control. What information is to be returned: This is a bitmask of the following values

Output Fields

FieldNameDescription
f200eLinkFileFile name this media is contained in. This can vary from time to time as information is reorganised on the server.
f201BytesRaw size of media in bytes. This is the amount of physical storage being used to hold this piece of media. For images it is very likely to be the size of the image returned.
f202LocalUrlA Url that can be used to reference this media. This is a relative url that can be used against this server. Urls can change over time depending on format. Urls that start with "/geni/lib_rtphys_" do not change and retrieve the media by fetching against its physical key. Urls that start with a different pattern should be considered short lived (days).
EXIFSubPacketInformation from EXIF headers if available
f300?Experimental, do not use

Examples

Return metadata information about all available media related to locations

/gnap/buck?3=retailmax.elink.media.list&9=f101,0,locations

Returns:

	<ARAY>
		<DATS>
			<f200>RetailLogicData_IQAAAAAAAAAAAAA_media_0.dati</f200> 
			<f201>264515</f201> 
			<f202>/geni/lib_rt204_rk4_rn0</f202> 
		</DATS>
		<DATS>
			<f200>RetailLogicData_IQAAAAAAAAAAAAA_media_0.dati</f200> 
			<f201>364681</f201> 
			<f202>/geni/lib_rt204_rk4_rn1</f202> 
		</DATS>
	</ARAY>

Return information about

/gnap/M/buck?3=retailmax.elink.media.list&9=f100,0,14779&101=202&100=1

Returns:

	<ARAY>
		<DATS>
			<eLinkFile>RetailLogicData_IT8LVUP8KQ84GQA_media_0.dati</eLinkFile> 
			<Bytes>364681</Bytes> 
			<LocalUrl>/geni/lib_rt202_rk14779_rn0</LocalUrl> 
			<f300>1</f300> 
			<EXIF>
				<Make>OLYMPUS CORPORATION</Make> 
				<Model>C770UZ</Model> 
				<ModDt>2010:07:23 11:47:37</ModDt> 
			</EXIF>
		</DATS>
	</ARAY>

EXIF Packet Structure

If an EXIF packet is supplied it will include any relevant tags it can understand. The "tag numbers" used in EXIF are used directly to encode the field numbers, so unknown fields can be referenced from the EXIF specification. The following is some of the more common fields.

The EXIF structure is not designed to return ALL information available, you should use external applications if you wish to fully analyse the contents

Field #Field NameExif TagDescription
f271Make01:0fMake
f272Model01:10Model
f306ModDt01:32Modification date/time
f33432Copyright82:98Copyright information