Metadata FAQ | Scene7

Go to advanced search, select the parameters, and generate the search results.

Alternatively, browse to a folder. Select the items that you want using Ctrl-click or Shift-click. Then go to File > Import Metadata. Select the type of output (usually just the defaults), and click Generate.

A new window opens with the metadata of the selected items, and you can copy and paste it into a local file.

SPS supports dozens of built-in XMP metadata fields. XMP metadata includes many standard libraries, such as EXIF camera metadata (f-stop, shutter speed), IPTC metadata (which journalists use) and Dublin Core metadata (general-purpose metadata fields that apply across many industries).

In the past, the only way to populate these fields was by embedding the data into the asset and uploading it (for example, using Adobe Bridge to edit the fields on the desktop), manually by typing into the Detail page in SPS, or by creating a custom IPS web service API application. Unlike legacy user-defined field (UDF) metadata, XMP metadata fields that a metadata upload job could not populate.

But as of SPS 6, XMP metadata can now be imported via a metadata upload. The key to the process is to correctly name the fields. XMP Metadata properties must have the related XMP-prefix before the (property-) name. A colon separates the prefix and name. XMP properties names do not appear in the Generate file feature.

For example: The XMP property for keywords is the XMP schema "Dublin Core" with the prefix "dc" and “subject” is the technical XMP name. The prefix and technical XMP name are combined into the "dc:subject" full property name. In the XML metadata import format, "dc.subject" must be the property name. In the tab-delimited import format, it must be the column-header.

Here is an example of tab-delimited metadata for an upload:

ipsid dc:subject

img_001 word1,word2

And here is an XML example:

<ips xmlns:dc="http://purl.org/dc/elements/1.1/">

<ghw_object vc_objectname="img_001" dc:subject="word1,word2">

</ips>  

After importing this file, the image img_001 has two keywords: word1 and word2.

SPS documentation link for this workflow:

http://help.adobe.com/en_US/scene7/using/WS259993e42159a215-1c6a66df1265272619e-7fec.html#WS259993e42159a215-1c6a66df1265272619e-7fea 

You can associate metadata with uploaded content. First, generate the existing information. Go to advanced search, select the parameters, and generate the search results. Alternatively, browse to a folder.

Select the items that you want using Ctrl-click or Shift+click..

Then go to File > Import Metadata.

Select the type of output and click Generate.

A new window opens with the metadata of the selected items, and you can copy and paste it into a local file.

It takes a while for the data to populate.

This Help document goes through the process of creating a template:

http://help.adobe.com/en_US/scene7/using/WS259993e42159a215-1c6a66df1265272619e-7fec.html#WSef8d5860223939e2-e32148f12b17c9da22-8000

Once you edit the metadata, you can follow these instructions to import the metadata.

http://help.adobe.com/en_US/scene7/using/WS259993e42159a215-1c6a66df1265272619e-7fec.html#WS259993e42159a215-1c6a66df1265272619e-7fea

There are two different types of EPS files, vector and bitmap. SPS rasterizes vector images and does not handle metadata in the same way. For bitmap EPS files, the process is the same as any bitmap image such as jpg or png. The upload metadata process works on either rasterized images or static content.

Resolution tags in the image header determine the resolution for images. If these tags are not present, or are 0, then they don't show up in the resolution field when uploaded into SPS. You can open an image in PhotoShop to force the resolution fields to be populated, but be warned that if there is no resolution set in the image, PhotoShop simply says that  the resolution is 72 dpi.Adobe is not aware of a way to distinguish in Photoshop if an image resolution is set to 72 dpi, or not set at all.