Question / musings about building book objects w/ multiple files

[Derek Merleaux]

Good morning all,

Very excited to have time and opportunity to be playing w/ the new Archipelago release. I'm working my way through all the updated documentation and trying to establish a test/example set of collections and objects on my test server.

I'm looking at a specific use-case - that of creating a book object from a set of files. So I've got a 20 page book that was scanned to 20 TIF image files. 

I understand that I can load this via AMI as a single line in the CSV with all 20 image files referenced in the "images" column - that works as expected. (Is this the recommended way to make a book from files?) 

Often when I'm working w/ digitized books like this, there is (at minimum) a page-level title that has useful/meaningful information (like "title page" or "plate 1" or "acknowledgments")  My question is about how to best display this information to users while still making use of the IAB book viewer.

Archipelago does this amazing job of bringing all the image file's exif data into the object JSON so I can see how adding the page-image title to the exif will automatically bring that data into the ADO. Is there an already existing mechanism to display that? 

An idea scenario would be allowing the IAB to display the image exif title - maybe as hover text? I can imagine using a custom display template to make a table of contents that has all the page titles and links that flip the IAB to that page. I guess it's also possible to make a custom display for books akin to the "pages" tab on the Islandora7 book cmodel that displays all the page images as a collection w/ their titles.

Any thoughts, ideas, corrections to my assumptions are welcome!

Best,

Derek

Derek Merleaux

Senior Consultant and Project Manager

Pronouns: he/him/his. 

Born-Digital | 84 Russell St, Hadley MA | (413) 259-8787 ext.113 | born-digital.com

[Josh Hadro]

Hi Derek --

This is probably not the precise answer you're looking for since it does not explain how to show the canvas labels in the IA book reader, but one the amazing things about the deep integration of IIIF into Archipelago is that all the digital objects should be portable to other IIIF viewers, many of which are designed to display more granular detail about books and manuscripts in IIIF than the IA reader is designed to do.

At a really high level, this IIIF Cookbook recipe describes your use case, I believe, including canvas labels for each page:

https://iiif.io/api/cookbook/recipe/0009-book-1/

Just above the example JSON there, you can see examples of that manifest in different viewers, including Mirador and the Universal Viewer, which both by default show those page labels for each image, when present.

I know Archipelago already has Mirador integration options, and I'm not sure if anyone has attempted integrating Universal Viewer yet.

In any event, the reason I mention all of that is that if you're considering adjusting the IA book reader,  it may also be worth exploring if another IIIF viewer might already have the functionality you need out of the box, including page labels and table of contents displays, and would already work with the IIIF manifests that Archipelago generates natively.

Hope that's helpful, but I'm happy to offer more info on the IIIF front if that's helpful.

Thanks --

Josh

--
You received this message because you are subscribed to the Google Groups "archipelago commons" group.
To unsubscribe from this group and stop receiving emails from it, send an email to archipelago-com...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/archipelago-commons/bb3f2e55-ffd8-4b76-9e72-74ab4394f6afn%40googlegroups.com.

[Derek Merleaux]

Thanks Josh! That's exactly the kind of idea(s) I was hoping for - I've experimented a bit w/ Mirador in Archipelago and I can see how that makes a lot of sense for the use case I was describing. 

I'm still getting used to the flexibility of this software - one thing I know from experience is that people really like the look and feel of IAB (page flipping goodness!) but there's no reason I can't have two view modes and give users the ability to change from the more detailed - exif displaying Mirador and the simple clean IAB.

I'm expecting to be neck deep in the IIF part of this soon so I will definitely reach out on this list for help and ideas!

Thanks,

Derek

[Derek Merleaux]

following up on my own questions - I had not yet fully explored the Creative Works Series type which is using Mirador and basically does what I want already - see this excellent description of that piece from Diego https://groups.google.com/g/archipelago-commons/c/qh7Cd7fGyco/m/DL7CHSNzAAAJ

[dp...@metro.org]

Hi Derek, glad you found the creative Work Series (similar to a compound but IIIF Presentation API V3 driven) explanation and I hope you saw the built in implementation in RC3. All the Templates built for that were improved in the last release but can also be expanded to add (or use) techMD as part of the metadata key of the manifest and of each canvases (e.g the page). IIIF also allows a TOC (ranges) structure but I see in current release Mirador is not really using it. Maybe we can explore that too. Pages (or any child object) also now allow a sort key (sequence_id, top level metadata key) that is being indexed in Solr by default as an Integer, Which allows you as the name implies, define different progressions.

But, since we have full control on how to extend IA Book reader and its already using a IIIF Manifest V2, I could also allow book reader to expose metadata per page and maybe even add support on our side for that TOC. If you could give us some detailed UI/UX expectations about that in a GitHub issue inside GitHub.com/esmero/format_strawberryfield that would help us be more concrete on the additional code to make that happen.

Thanks a lot!

Diego

[Giancarlo Birello]

Hi Diego and all,

About using TOC with IAB, I implemented TOC with IAB on I7, here a sample: https://www.byterfly.eu/islandora/object/librib:83318 (see markers in page bar).

That was really custom: from DC I extract TOC entries by a Views then rewrited IAB js to populate chapter markers.

With IAB 4 (also 5 I think) we can solve that using included plugin chapters (see https://github.com/internetarchive/bookreader/blob/master-v4/src/js/plugins/plugin.chapters.js) and exposing an end-point to return TOC elements (probably extracted from STBF-JSON).

Just an idea: if Derek needs a title per page, that is a TOC with an element for each page, right?

Best

Giancarlo

To view this discussion on the web visit https://groups.google.com/d/msgid/archipelago-commons/12870584-7acc-4e33-bab2-e88a20c3d8d5n%40googlegroups.com.