E-Spec’s Tag-It! makes it easy to apply custom and standard XMP metadata to your assets and files.
In a nutshell:
• Collects metadata and embeds it in the Adobe Illustrator (.ai) file and all Convert-It! generated alternative files
When importing an image into a Product Lifecycle Management (PLM) system, the Designer is typically required to also enter relevant data into the PLM system. This means opening PLM, manually importing the image and then entering data into PLM before saving the image. By embedding the metadata in the image, the PLM system can automatically import the image along with the metadata and place both the image and the data into the PLM database. If the image or the metadata is modified the PLM system can automatically update the database.
Tag-It! allows the Designer to stay in the Illustrator application, simply entering the metadata and saving the file. The Designer does not need to switch to the PLM system, saving time and eliminating mistakes.
• Implements business rules while entering the metadata
Tag-It! is configured to match the metadata to the customer defined fields and standard fields in the PLM system. Features like required fields, validation lists, dependent validation lists, default values and hidden fields allow Tag-It! to provide valid data to the PLM system with minimum user interaction.
Tag-It! makes it easy for the Designer to provide the required data. Default values mean that repetitive data does not have to be entered. For example: If I usually work in “mens”, the division field can be defaulted to “mens”; if I am working on an exception, a “kids” style; I simply select “kids from the list. If I always work in “mens”, the division field can be defaulted to “mens” and also hidden so I don’t even see the field in Tag-It!’s dialog but the value “mens” is still embedded in the file. Dependent fields allow Tag-It! to provide only valid data to the PLM system. If the product type field is dependent on the division field then when I select “mens” the validation list for product type displays “pants”, “shorts”, “jeans”; when I select “womens” in the division field the validation list for product type changes to “dresses”, “skirts”, “pants”, etc. This means that valid data is provided to the PLM system.