Richard Bamford (Extensis UK) has suggested I get in touch with you via this forum to get some advice on the MediaScript/API capabilities. We are implementing Portfolio at a client in the UK and their workflow process is dependent on what we can achieve with this.
There are three different functions they are looking to achieve:
- Automate the File > Import Field Values and Item > Embed Properties functionality. I have attached a diagram to explain the process they are trying to achieve.(Please note that the “Placeholder” mentioned is just a dummy image, nothing to do with the Placeholder function within Portfolio)
a) Will this be achievable?
b) Is it possible to schedule this to happen automatically or does it need to be user triggered?
c) Has anything like this been done before i.e. is there any code to use as a starting point or will this need to be created from scratch?
d) Do you have any recommendations or can foresee any issues with what we are trying to do?
- Create logic to handle their “Best Image” process. They are an apparel company and have two stages in the product development process where they take photos of the products. The first stage is when a sample comes in. This is known as a Lookbook image. The 2nd is when the production product comes in. This is called the Web image. The Web image is considered the “best” image as things like trims and colours can change between Lookbook and Web, so only Web is the final, true representation of what will be sold. It is the Lookbook images that get created in the process in point (1). The Web images get created later. Ideally Lookbook images will be stored in Catalog 1 and Web images will be stored in Catalog 2. As they have 1000’s of products they don’t want to view Lookbook images in searches if they have Web images available. What they want to do is have some sort of logic in place that filters out Lookbook images if there are Web images available instead.
What we were thinking was this:
There would be a field (custom or default renamed) called “Best Image”. When the Lookbook image was created (as per process in point 1) this field would be auto-populated to be true when image was first created. Later on down the line when a Web image was created this would also get the “best image” field auto-populated to be true, however, at the same time there would need to be logic in place that would say match up the product number from the new Web image to the Lookbook image and on the Lookbook image set the “best image” field to false.
a) Would this be possible?
b) If so, can Lookbook image and Web images be in different catalogs or would it be better if they were in the same one? (what the pros/cons to either approach)
c) How best to set up the configuration (custom field or rename standard field etc) in order to achieve this?
d) Could this be done automatically as soon as Web images are created or would it need to be a user triggered script?
- They need to be able to produce a report called the “Focus List”. I have attached an example of what this report needs to look like (layout not yet finalised). The bit that we need advice on is the size ratio grid with the colour coding (green, orange, red etc). This colour coding represents the stock levels they have for each size. For example if there are under 400 units it will be red, if it is between 401 and 1000 units it will be orange, if it is greater than 1000 units if will be green. This information comes from another system as part of the metadata import described in point 1. Ideally they want a “Make PDF” menu option that will generate this report from Portfolio for any search view i.e. they search to see all Mens Polo Tops then they would run this report.
a) Will this be possible to produce as a PDF from Portfolio?
b) In terms of getting the stock info per size in via meta-data they are pretty flexible in terms of how to set up the import file. For example they could have 1 field that contains all the size/stock info i.e. [S-456, M-239, L-1003, XL-388] or they could have a different field for each size i.e. [S-456] [M-239] [L-1003] [XL-388]. They could have the size and stock in different fields as well i.e. [S] , [M] . What they would like advice on is how would be best to format the text file data import and the field configuration in Portfolio in order to facilitate creating this report.
c) They would also need the date/time of the last update (so the time the metadata import happened) stamped in either the footer or header of each page - would this possible?
d) Based on the visual I have provided, can you see anything else that would be problematic to achieve?
Apologies for all the questions - hopefully it all makes sense! We have an update call Friday am (UK time) so if you could come back to me before then that would be much appreciated.