importing jpegs via csv

I have multiple jpeg files for one item. I have created a spreadsheet that includes Dublin Core metadata for each jpeg. Are they all now separate items? How do I use the csv plugin to upload the jpegs? (They are images of pages from one book.)

For all the images for a single item, it is usually easiest to put them all in one column for files, surrounded by quotation marks and comma-separated in the column:

| files |
| "," |

I do not understand your instructions. In putting them all in one column, does each image get its own cell, which is what I've done? Should each image identifier, e.g. ABC123.jpg,be surrounded by quotation marks and followed by a comma? Must they be stored somewhere, like Dropbox?

How do I create the page view/page turning feature as shown here:
the page view/turning feature,

All of the references to images will be in one cell, surrounded by quotation marks, with commas inside that separating the values.

The references will have to be URLs to files available somewhere on the web. It doesn't really matter where, as long as they have URLs in the CSV files that point to where they are publicly available on the web.

For displaying the files, you might try the Docs Viewer plugin, though we've seen results vary with it.

For what it's worth, I find it easier to use a separator in my CSVs that will almost never appear in the text, to avoid having to use quotes. For columns, I use a pipe (|) and for multiple values in a field/cell I use a caret(^).

Dublin Core:Title|files
This is an item title|http://url1/^http://url2/^http://url3

I have downloaded the Internet Archive Bookreader source code. Can you give me step by step instructions on how to modify BookReaderJSSimple.js to connect the BookReader with my page images and metadata?

Will the docs viewer plugin do this as well?

Generally, it'll help us keep track of where questions stand to open a new thread for a new question.

In this case, I suspect you might have better luck on any forum or message list that they have for developers, since this sounds more about understanding their code rather than Omeka's.