Answers.Body: <p>Since there is several moving parts here, i'll make a few assumptions.</p>
  
  <ol>
  <li>You got a list of some kind with the product images and their containing metadata.</li>
  <li>Your product image filenames have a consistent naming scheme. Something like product-condition1-01,product-condition2-01, product-condition2-02</li>
  <li>You are able to write a couple PHP scripts and/or some frontend code that uploads your images, and then creates an list with the returned fileIds and the matching image filename. Take a look at <a href="http://buildwithcraft.com/classreference/services/AssetsService" rel="nofollow noreferrer">AssetsService</a> and the uploadFile action in <a href="http://buildwithcraft.com/classreference/controllers/AssetsController#actionUploadFile-detail" rel="nofollow noreferrer">AssetsController</a>. For the uploading part, you can probably make a simple JS snippet that loops through the file list and <a href="https://craftcms.stackexchange.com/questions/2113/does-anyone-have-a-working-example-of-frontend-form-with-multiple-file-upload-d/2163#2163">uploads them</a>.</li>
  <li>After you got that list, write a script that runs through the product list (an CSV or something), and replace the placeholders matching your image filenames (product-condition-xx etc.) with the previous fetched fileId(s).</li>
  <li>You will then end up with a comma-separated list of fileIds in your CSV fields, which Craft expects to able to relate the Assets to the imported Entries.</li>
  <li>Import the entries with Import.</li>
  <li>List the connected assets in your entries template the normal way.</li>
  </ol>
  
  <p>I have not looked into how to save field info for Assets, but you can for sure make fields and then add them to the field layout for your Assets Sources.</p>
  
  <p>(Not sure I understand all the conditions, but I think my outline should work pretty well for your case. Not able to comment yet, so I could not ask any questions beforehand. I'll update my answer if you add some follow-up information).</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-09-16T22:03:51.613Z
Answers.Text: 1. Yes I have a CSV containing image names in one cell and has several other cells with product information.  Woops hit enter by mistake, still replying!                        2. The product image filenames do not, in all circumstances, yet have a consistent naming scheme, but a quick trip through a Photoshop action can fix that  3. I am not sure I follow this. Can I not simply upload the images into an asset folder and then use the.....Ah wait, I just went back and looked at the import plugin documentation, different than what was reported to me by an employee.  I have to dig deeper. Thanks!
Answers.UserDisplayName: cmcjane
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-09-16T13:20:33.543Z
Answers.LastActivityDate: 2014-09-16T13:47:36.260Z
Answers.LastEditDate: 2017-04-13T12:51:00.253Z
Answers.UserDisplayName: Fred Carlsen
Body: <p>Apologies if I am dense, it won't be the first time.</p>
  
  <p>I have thousands of product images that I will output on more than one page, under varying conditions.  Rather than having to do an entry for each product in these circumstances, can I just:</p>
  
  <ol>
  <li>attach product  description fields to the asset field</li>
  <li>upload the assets </li>
  <li>use Bob Olde Hampsink's import plug-in to populate all the product info to assets fields</li>
  <li>fetch the asset and the associated fields in a template</li>
  <li>skip the entry part altogether?</li>
  </ol>
  
  <p>This way I could use the same asset in multiple instances without having to reinvent the wheel.</p>
  
  <pre><code>  A. Is this possible?
    B. Is this wise?
    C. If A and B =='yes' what is the most direct way to go about this?
  </code></pre>
  
Tags: <templating><entries><assets>
Title: Outputting Assets Instead of Entries
ThreadText: # Outputting Assets Instead of Entries
  
  (Asked by: username_0 on 2014-09-16)
  
  Apologies if I am dense, it won't be the first time.
  
  I have thousands of product images that I will output on more than one page, under varying conditions. Rather than having to do an entry for each product in these circumstances, can I just:
  
  1. attach product description fields to the asset field
  2. upload the assets
  3. use Bob Olde Hampsink's import plug-in to populate all the product info to assets fields
  4. fetch the asset and the associated fields in a template
  5. skip the entry part altogether?
  
  This way I could use the same asset in multiple instances without having to reinvent the wheel.
  
  ```
    A. Is this possible?
    B. Is this wise?
    C. If A and B =='yes' what is the most direct way to go about this?
  
  ```
  
  **Tags:** templating, entries, assets
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2014-09-16. Score: 2 | Accepted answer
  
  Since there is several moving parts here, i'll make a few assumptions.
  
  1. You got a list of some kind with the product images and their containing metadata.
  2. Your product image filenames have a consistent naming scheme. Something like product-condition1-01,product-condition2-01, product-condition2-02
  3. You are able to write a couple PHP scripts and/or some frontend code that uploads your images, and then creates an list with the returned fileIds and the matching image filename. Take a look at [AssetsService](http://buildwithcraft.com/classreference/services/AssetsService) and the uploadFile action in [AssetsController](http://buildwithcraft.com/classreference/controllers/AssetsController#actionUploadFile-detail). For the uploading part, you can probably make a simple JS snippet that loops through the file list and [uploads them](https://craftcms.stackexchange.com/questions/2113/does-anyone-have-a-working-example-of-frontend-form-with-multiple-file-upload-d/2163#2163).
  4. After you got that list, write a script that runs through the product list (an CSV or something), and replace the placeholders matching your image filenames (product-condition-xx etc.) with the previous fetched fileId(s).
  5. You will then end up with a comma-separated list of fileIds in your CSV fields, which Craft expects to able to relate the Assets to the imported Entries.
  6. Import the entries with Import.
  7. List the connected assets in your entries template the normal way.
  
  I have not looked into how to save field info for Assets, but you can for sure make fields and then add them to the field layout for your Assets Sources.
  
  (Not sure I understand all the conditions, but I think my outline should work pretty well for your case. Not able to comment yet, so I could not ask any questions beforehand. I'll update my answer if you add some follow-up information).
  
  > **Comments:**
  > **username_0**: 1. Yes I have a CSV containing image names in one cell and has several other cells with product information.  Woops hit enter by mistake, still replying!                        2. The product image filenames do not, in all circumstances, yet have a consistent naming scheme, but a quick trip through a Photoshop action can fix that  3. I am not sure I follow this. Can I not simply upload the images into an asset folder and then use the.....Ah wait, I just went back and looked at the import plugin documentation, different than what was reported to me by an employee.  I have to dig deeper. Thanks!  
  
  ---
  
  