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# | Binary | Description |
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
Field | Name | Description |
f200 | eLinkFile | File name this media is contained in. This can vary from time to time as information is reorganised on the server. |
f201 | Bytes | Raw 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. |
f202 | LocalUrl | A 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). |
EXIF | SubPacket | Information 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,locationsReturns:
<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
- Products (area 202, "&9=101,0,202") and
- For Single product #14779 ("&9=100,0,14779") and
- Include EXIF information if available ("&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 Name | Exif Tag | Description |
f271 | Make | 01:0f | Make |
f272 | Model | 01:10 | Model |
f306 | ModDt | 01:32 | Modification date/time |
f33432 | Copyright | 82:98 | Copyright information |