How to Batch Import Book Pages / Multipage Documents (MPDs)
In addition to creating book pages (also called multi-page documents - MPDs) through the web interface, these items can be imported through Mukurtu's Roundtrip tools.
The first thing to note is that book pages that are part of a digital heritage item are actually (on a structural level) fully independent digital heritage items that are then grouped together – that’s how each page can have completely unique metadata. What that means in practice is that each page of the book needs to be entered on its own line in the batch import spreadsheet, and then grouped together in a specific way.
A sample spreadsheet is attached at the end of this article. It has no metadata beyond what is required to create a MPD. You can refer to this as a template for structuring your own sheets. Refer to our other Roundtrip articles for direction on populating the rest of this spreadsheet.
Look at the GUID and Book Pages fields in the attached spreadsheet:
- There are 4 “digital heritage item” entries on this sheet, one for each book page. Each page can have its own metadata (including media assets), but you can also copy/paste or otherwise auto-populate fields if you do want to duplicate metadata across pages.
- I used a basic manually created GUID structure, for ease of viewing here. Again, see the other Roundtrip articles for more information on GUIDs.
- The first page of the book has to be the LAST line of the sheet. The database builds all the pages as digital heritage items starting with the first line of the sheet, and then when it gets to the line that has the Book Pages field populated, it looks for the GUIDs referenced there, so they have to already exist.
- The GUIDs in the Book Pages field on the first page should be in the order you want them to display. The order does not have to correspond to the order they are on the sheet. Do not include the first page there – no self-referencing needed.
- All book pages should share the same Cultural Protocols (Sharing Settings and Sharing Protocols). But note that each page can have distinct community records, the same as any digital heritage item.