how to contain multiple images in one item?

[chrkibo]

Hi

I wanted to put several images in one item (see: https://www.lib.uidaho.edu/digital/hjccc/data/hjccc-163.html). I read the documentation and it wasn't mentioned how to do it.

Thanks,
Apple

[evanwill]

@chrkibo thanks for the question! And yes, sorry that isn't a feature that is documented or built in right now.

We typically call item pages with multiple images or other files "compound objects". We have implemented them in many different ways in different collections--but don't have a method directly built into any of the templates right now. We are likely to roll out a built in method this summer.

In the meantime, if you are familiar with Jekyll, it is not many steps to customize your project to support compound objects.
There is a few approaches:

• A new column: the simplest approach if you just have images and don't need additional metadata, is to add a new column to your main metadata CSV called "compound" that lists all the additional filenames. Then modify the item page layout to look at that column to add the additional images. There is an example implemented in cb-gh-postcards.
• Two CSVs: In the example you mention, if you look at HJCCC source code there is two CSVs: one for the "objects" describing the full items (each record in this CSV will become an item page) and one for all "images" (each image is one row in the CSV with minimal metadata, plus a "objectid" that matches one of the item in the "objects" CSV). Item pages are generated from the "objects" CSV, and the item page layout checks the "images" CSV to pull in any related images. This is a flexible approach because each object can have any number of images associated, and the images can have additional metadata applied.
• One CSV: another approach is to add the additional images as rows in your main metadata csv, leaving the "objectid" column blank. Any row with an "objectid" value will be a full "object" record and generate an item page. The rows without "objectid" will be additional images, and use a key value to be associated with one of the "object" records. This approach is likely to be built into the templates eventually, but is a bit more complicated to get set up right now.

If you are working on a specific project right now, please let us know and we would be happy to help get it set up!

[chrkibo]

Hi Evan, Thanks for this guide. My colleagues and I were able to customise it using the second approach. Attached is the screenshot of the page. Collection Builder is awesome! Thank you for making it accessible for everyone :) Apple/KIBO

…

On Fri, 25 Jun 2021 at 00:51, EvanWill ***@***.***> wrote: @chrkibo <https://github.com/chrkibo> thanks for the question! And yes, sorry that isn't a feature that is documented or built in right now. We typically call item pages with multiple images or other files "compound objects". We have implemented them in many different ways in different collections--but don't have a method directly built into any of the templates right now. We are likely to roll out a built in method this summer. In the meantime, if you are familiar with Jekyll, it is not many steps to customize your project to support compound objects. There is a few approaches: - *A new column:* the simplest approach if you just have images and don't need additional metadata, is to add a new column to your main metadata CSV called "compound" that lists all the additional filenames. Then modify the item page layout to look at that column to add the additional images. There is an example implemented in cb-gh-postcards <https://github.com/evanwill/cb-gh-postcards>. - *Two CSVs:* In the example you mention, if you look at HJCCC source code <https://github.com/uidaholib/HJCCC_source> there is two CSVs: one for the "objects" describing the full items (each record in this CSV will become an item page) and one for all "images" (each image is one row in the CSV with minimal metadata, plus a "objectid" that matches one of the item in the "objects" CSV). Item pages are generated from the "objects" CSV, and the item page layout checks the "images" CSV to pull in any related images. This is a flexible approach because each object can have any number of images associated, and the images can have additional metadata applied. - *One CSV:* another approach is to add the additional images as rows in your main metadata csv, leaving the "objectid" column blank. Any row with an "objectid" value will be a full "object" record and generate an item page. The rows without "objectid" will be additional images, and use a key value to be associated with one of the "object" records. This approach is likely to be built into the templates eventually, but is a bit more complicated to get set up right now. If you are working on a specific project right now, please let us know and we would be happy to help get it set up! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#28 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AURNKHAIB7O36E4C73CY333TUNPA3ANCNFSM47IGQXPQ> .