Skip to Main Content
It looks like you're using Internet Explorer 11 or older. This website works best with modern browsers such as the latest versions of Chrome, Firefox, Safari, and Edge. If you continue with this browser, you may see unexpected results.

FL-Islandora Guide

A guide for FL-Islandora users.

Introduction to Accepted Content Types

The sections below provide a reference for the types of content that can be ingested into Islandora and the presentation of the content ingested into Islandora, as provided by Islandora Solution Packs. To ingest files into an Islandora collection the content type, Content Model(s), must be defined in the collection policy.

When selecting a Content Model to use for ingesting a file there are a number of things to consider:

  • What is the primary method of display desired for this file?
  • Is this file part of a larger item?
  • What is the file/mime type of the file?
  • Are there files in multiple formats representing the same item?

Some types of files may be ingested into more than one Content Model, while others may not be accepted by any Content Model. The access file (the file as presented to the end user) may be a derivative and not the original file ingested into FL-Islandora.

PDF vs Book Comparison

Use this comparison to help choose between the PDF content model and Book content model.

Book content model:
  • When users look at the Book object, then they see a page flipper display.
  • There is no download button. It is possible to click over to the Pages tab and download one page at a time, but for someone who wants to download a Book fast, there's no easy "download" button.
  • Books are stored as pictures of each page, and show up in the Internet Archive Book Reader page-turning display. Since Islandora version 7.x-1.6, Islandora lets you upload a PDF when you create the Book, and Islandora will extract the images from the PDF. However, since this was resource-intensive, the ability to upload PDFs is disabled on all FL-Islandora sites.
  • Stores the original picture that you uploaded for each page. It shows a smaller web file in the page-flipper display, but the original file is stored in Islandora.
  • Example Books:
  • To upload like this, you start with a set of .tiff / .tif / .jpeg / .jpg / .jp2 files. Islandora runs OCR, so the text will be searchable. The quality varies from book to book, and sometimes the text is almost perfect and sometimes it's gobbledygook.
PDF content model:
  • When users look at the PDF object, they see an in-browser display of the PDF. This is something that's part of the browser, and not part of Islandora, so it might not work on some browsers. For example, if the browser is an old version or maybe it's a phone or tablet or doesn't have Adobe Acrobat Reader built in to the browser. You will also see different functionality in the PDF viewer based on the browser and its in-built PDF viewer.
  • Example PDF content model objects:
  • To upload like this, you start with a .pdf. If you have run OCR on the PDF before you upload, then Islandora will extract and store the text layer from the PDF. But, if you haven't run OCR on the PDF before uploading, then Islandora will not run OCR and the PDF will not be full-text searchable.

Newspaper vs Serial Comparison

Use this comparison to help choose which content type to use: Newspaper content model or Serial content model

Newspaper content model:
  • Newspaper Issues have to have a date issued MODS field in valid format (YYYY-MM-DD).
  • Users browse from the collection to a Newspaper object, then from the Newspaper object there is an accordion-style menu that opens up by year, then month, which then displays all newspaper issues for the selected month.
  • Newspaper issues are stored as pictures of each page, and show up in the Internet Archive Book Reader page-turning display. Since Islandora version 7.x-1.6, Islandora lets you upload a PDF when you create the Book, and Islandora will extract the images from the PDF. However, since this was resource-intensive, the ability to upload PDFs is disabled on all FL-Islandora sites.
  • Supports metadata at the Newspaper Issue or top-level Newspaper parent object only. This module does not support article-level metadata.
  • Example Newspaper:
  • To upload like this, you start with a set of .tif / .jpeg / .jp2 files. Islandora runs OCR, so the text will be searchable. The quality varies from newspaper to newspaper, and sometimes the text is almost perfect and sometimes it's gobbledygook.
Serials content model:
  • When the library creates the top-level object, the library specifics levels for the serial. For example, the library can specific "Volume, Number" for one serial, and "Volume, Issue" for another, and "Year, Month" for another. There's no limit to levels - so it's even possible to do "Volume, Number, Issue".
  • Users browse from the collection to a Serial object, then from the Serial object, there is an accordion-style menu that opens up by whatever levels the library specified for that serial. For example, if a Serial were set up to have "Volume" and "Issue" as levels, then the user would click to the Volume they wanted, then to the Issue they wanted, then see all PDFs in that Issue.
  • Serials supports article-level, issue-level, and top-level serial metadata
  • Example Serials:
  • To upload like this, you start with a .pdf. If you have run OCR on the PDF before you upload, then Islandora will extract and store the text layer from the PDF. But, if you haven't run OCR on the PDF before uploading, then Islandora will not run OCR and the files will not be full-text searchable.

PDF (Most Common)

In order to upload a PDF Object content model, you need to enable the collection to hold:

  • Islandora PDF Content Model (islandora:sp_pdf)

Files for upload

The PDF content model is used for single PDF files.  It accepts files of the following file types as input:

   PDF (.pdf) required
   TEXT (.txt) optional

How it looks

At this time, there are no PDF viewers installed in FL-Islandora. Viewing a PDF object in-browser is dependent on what browser (and browser plugins) you are using to access the page. There is no single recommended browser. Any popular, modern, up-to-date browser should be sufficient to view FL-Islandora PDF objects in-browser along with the remainder of a site. However, some users may not be able to see the PDF in their browser window or will have varying functionality to interact with the PDF depending on their browser's built-in PDF viewer.

Examples:

Technical Information/Datastreams

The following datastreams will be created:

RELS-EXT Default Fedora relationship metadata
MODS MODS record
DC Dublin Core record
TN Thumbnail image, created from the first page of the PDF at time of ingest
OBJ The source PDF
FULL_TEXT      Full text of the PDF, either provided as a source file or derived from the PDF at the time of ingest
PREVIEW

A JPEG image derived from the PDF, used for the initial view of the PDF.

Uploading PDF content model objects one-at-a-time through the web

  1. Make sure the collection you are loading into can hold the "Islandora PDF Content Model (islandora:sp_pdf)". (To check this, browse to the collection you will upload to, then click "Manage", then click "Collection", then on the left it will say "Manage collection policy" and if the box for "Islandora PDF Content Model (islandora:sp_pdf)" is checked then you are good to go.)
  2. Browse to the collection into which you will upload the PDF. Click the "Manage" tab, then click "Add an object to this Collection".
  3. Choose the MODS Simple Entry form. (It's shorter than "Full MODS Form.")
  4. MARCXML lets you upload a MARCXML file and that will populate the MODS forms. A library might have these if they are digitizing older public domain materials, where they look for rare items in the catalog, digitize, then export the MARC record from the catalog. You also could make a template MARC file to use if you are uploading a large set of material with many repeated fields that are identical for the whole set of items. MarcEdit will allow easy conversion of a MODS XML file to a MARC XML file. So, to make the MARC XML template, you could use Islandora to fill out repetitive MODS fields, then click to "Manage" then "Datastreams" then "download" MODS, then on your desktop use Notepad to remove fields specific to that item, then use MarcEdit to convert MODS XML to MARC XML, then use the MARC XML template to autofill the repeated fields.
  5. If not using MARCXML, fill out the MODS form and click "Ingest". The MODS Simple Entry Form is long, and the Full MODS Form is even longer. Regarding what fields to fill out, it's good to make a checklist of fields and then fill those out for each PDF. You may look at other Islandora sites (ex. https://falsc.libguides.com/FL-Islandora/Sites) and see what fields show up in search results for a site and think that those are more important for someone using the site (FLVC can change these for your site if you want to show or not show certain fields).
  6. Click "Next".
  7. Click "Choose File" and find the pic you would like to upload.
  8. After you click "Ingest", you have created the PDF content model object.

Zip loading PDF content model objects

  1. Make sure the collection you are loading into can hold the "Islandora PDF Content Model (islandora:sp_pdf)". (To check this, browse to the collection you will upload to, then click "Manage", then click "Collection", then on the left it will say "Manage collection policy" and if the box for "Islandora PDF Content Model (islandora:sp_pdf)" is checked then you are good to go.)
  2. Prepare all MODS metadata for your object. It is recommended to use the Excel to MODS Transformer to prepare the metadata since this will ensure that metadata validates against the MODS schema and meets FL-Islandora requirements.
  3. Put all the MODS XML and all PDF files in a single folder that you wish to upload. The name of each PDF file should match the name of the corresponding XML. For example, the folder should hold document1.xml, document1.pdf, document2.xml, document2.pdf, etc. and no other files (ie. no XML without a pdf and no pdf without an XML file).
  4. Zip that folder to make a .zip file.
  5. Browse to the collection into which you will upload the PDFs. Click the "Manage" tab, then click to the "Collection" tab, then click to "Batch Import Objects".
  6. Under the "Importer" drop-down, you should see "Zip File Importer" selected. If not, then choose "Zip File Importer".
  7. Under Zip Batch Importer, click to "Choose File" and upload the .zip file you created with your PDF and MODS XML files. Under "Content Model", select "Islandora PDF Content Model (islandora:sp_pdf)". Then click "Import".
  8. This will load metadata and files for each PDF content model object.

Offline Batch Ingest for PDF content model objects

Offline batch ingest is available for the PDF content model.

 

Audio

In order to upload the Audio content model, you need to enable the collection to hold:

  • Islandora Audio Content Model (islandora:sp-audioCModel)

Files for Upload

The Audio Content Model is used for single audio files.

The Audio content model accepts these file types:

   WAVE (.wav)
   MP3 (.mp3)

How it looks

This module plays audio in the browser using JWPlayer. The thumbnail shows up in the background of the player window in the browser, in addition to its normal locations. In the picture below, the default image of a microphone is shown as the thumbnail.  Optionally, the operator may upload a thumbnail image during the initial upload (or you can add a different thumbnail anytime later) to replace the default image.


Selecting Full Screen View will render the file in a user's browser default.

Example:

Technical Information/Datastreams

Ingested islandora:sp-audioCModel objects create the following datastreams:

RELS-EXT Default Fedora relationship metadata
MODS MODS record, created at time of ingest
DC Dublin Core record, derived from MODS
OBJ The original WAVE or MP3 file uploaded.
TN The uploaded thumbnail image, or a default thumbnail icon.
PROXY_MP3      An MP3 file for playback derived from the original WAVE or MP3 file uploaded.

Uploading Audio objects one-at-a-time through the web

To make the Audio content model, you have to have a .wav or .mp3 file.  If your audio files are in a different format, consider uploading as a Compound Object with two parts, the original file as a Binary Object and a .mp3 derivative as an Audio file. Keeping the original in Islandora helps keep it easy to find over time. You can use the open-source software, like Audacity, to create a .mp3 file from almost any other source format.

  1. Make sure the collection you are loading into can hold the "Islandora Audio Content Model (islandora:sp-audioCModel)". (To check this, browse to the collection you will upload to, then click "Manage", then click "Collection", then on the left it will say "Manage collection policy" and if the box for "Islandora Audio Content Model (islandora:sp-audioCModel)" is checked then you are good to go.)
  2. Browse to the collection into which you will upload the audio. Click the "Manage" tab, then click "Add an object to this Collection".
  3. Choose the MODS Simple Entry form. (It's shorter than "Full MODS Form")
  4. You can ignore MARCXML file. MARCXML lets you upload a MARCXML file and that will prepopulate the MODS forms. A library might have these if they are digitizing older public domain materials, where they look for rare items in the catalog, digitize, then export the MARC record from the catalog. You also could make a template MARC file to use if you are uploading a large set of material with many repeated fields that are identical for the whole set of items. MarcEdit will allow easy conversion of a MODS XML file to a MARC XML file. So, to make the MARC XML template, you could use Islandora to fill out repetitive MODS fields, then click to "Manage" then "Datastreams" then "download" MODS, then on your desktop use Notepad to remove fields specific to that item, then use MarcEdit to convert MODS XML to MARC XML, then use the MARC XML template to autofill the repeated fields.
  5. If not using MARCXML, fill out the MODS form and click "Ingest". The MODS Simple Entry Form is long, and the Full MODS Form is even longer. Regarding what fields to fill out, it's good to make a checklist of fields and then fill those out for each Audio file. You may look at other Islandora sites (ex. https://falsc.libguides.com/FL-Islandora/Siteshttps://falsc.libguides.com/FL-Islandora/Sites) and see what fields show up in search results for a site and think that those are more important for someone using the site (FLVC can change these for your site if you want to show or not show certain fields). 
  6. Click "Next".
  7. Click "Choose File" and find the .wav or .mp3 you would like to upload.
  8. If you have a thumbnail that you would like to use, then you can check the box to "Upload Thumbnail" and upload an image from your computer. (There are no plans to keep this thumbnail in a high resolution going forward, so if you have a project to digitize album covers or something where the image has value by itself, then upload the album covers separately.)
  9. After you click "Ingest", you have created the Audio object.
  10. Optional extra step: Adding a thumbnail image for an audio recording

The default thumbnail will look like this:

To add a different thumbnail image (for example, an album cover):

  • Click to the item in Islandora while logged in.
  • Click the “Manage” tab.
  • Click to “Datastreams”.
  • Click to “Add a datastream”.
    • For “Datastream ID”: type “TN”.
    • For “Datastream Label”: type “Thumbnail”.
    • For Upload document: Find the thumbnail you want to use and upload it. (Recommended size is 200 x 200.)

Zip loading Audio

  1. Make sure the collection you are loading into can hold the "Islandora Audio Content Model (islandora:sp-audioCModel)". (To check this, browse to the collection you will upload to, then click "Manage", then click "Collection", then on the left it will say "Manage collection policy" and if the box for "Islandora Audio Content Model (islandora:sp-audioCModel)" is checked then you are good to go.)
  2. Prepare all MODS metadata for your object(s). It is recommended to use the Excel to MODS Transformer ( https://falsc.libguides.com/FL-Islandora/Metadata ) to prepare the metadata since this will ensure that metadata validates against the MODS schema and meets FLVC's local requirements.
  3. Put all the MODS XML and all files, in a single folder. The name of the audio file(s) should match the name of the corresponding XML. For example, the folder should hold music1.xml, music1.mp3, music2.xml, music2.wav, etc. and no other files (ie. no XML without a file and no .mp3 or .wav without an XML).
  4. Zip that folder to make a .zip file.
  5. Browse to the collection into which you will upload the Audio files. Click the "Manage" tab, then click to the "Collection" tab, then click to "Batch Import Objects".
  6. Under the "Importer" drop-down, you should see "Zip File Importer" selected. If not, then choose "Zip File Importer".
  7. Under Zip Batch Importer, click to "Choose File" and upload the .zip file of MODS XML for your audio files. Under "Content Model", select "Islandora Audio Content Model (islandora:sp-audioCModel)". Then click "Import".
  8. This will load metadata and files for each Audio object.
  9. Optional extra step: Batch load thumbnail images for audio recordings

To add a different thumbnail image (for example, an album cover) via batch loading:

  • Put the thumbnails in the .zip folder, and make the name of the thumbnail match the name of the audio file and XML MODS. (ie. audiofile1.mp3, audiofile1.xml, audiofile1.jpg )
  • The thumbnail images should be .jpg , .jpeg, .png, or .gif. The recommended size of each thumbnail is 200 x 200.

Offline Batch Ingest for Audio objects

Offline Batch Ingest is not available for Audio objects

Basic Image

In order to upload the Basic Image content model, you need to enable the collection to hold:

  • Islandora Basic Image Content Model (islandora:sp_basic_image)

Files for Upload

Basic Image is meant primarily for JPEG images, but can be used for some other image formats.

The Basic Image content model accepts a single file of the following file types:

   JPEG (.jpg, .jpeg)
   PNG (.png)
   GIF (.gif)
   TIFF (.tif, .tiff) 


NOTE: .tif and .tiff can only be loaded to Basic Image by GUI;  
They cannot be loaded to Basic Image by zip or offline batch ingest

How it Looks

The picture shows up in the browser. There's no way to zoom in or out. If you click on the picture, you go right to the file and can save it to your desktop.

Examples:

Technical Information/Datastreams

If a JPEG, PNG or GIF is supplied, islandora:sp_basic_image will create the following datastreams:

RELS-EXT Default Fedora relationship metadata
MODS MODS record, created at time of ingest
DC Dublin Core record
OBJ The original image file uploaded
TN Thumbnail image, created at time of ingest
MEDIUM_SIZE      A compressed version of the image, used on the object's View page

 

If a TIFF is supplied, islandora:sp_basic_image will create these datastreams (Large Image Module is the recommended module for TIFF files):

RELS-EXT Default Fedora relationship metadata
MODS MODS record, created at time of ingest
DC Dublin Core record
OBJ A full-size JPEG created from the source TIFF image
ARCHIVE The source TIFF image
TN Thumbnail image, created at time of ingest
MEDIUM_SIZE      A compressed version of the image, used on the object's View page

 

Uploading Basic Image objects one-at-a-time through the web

To make the Basic Image content model, you have to have a .jpg, .jpeg, .png, or .gif file to start with.

  1. Make sure the collection you are loading into can hold the "Islandora Basic Image Content Model (islandora:sp_basic_image)". (To check this, browse to the collection you will upload to, then click "Manage", then click "Collection", then on the left it will say "Manage collection policy" and if the box for "Islandora Basic Image Content Model (islandora:sp_basic_image)" is checked then you are good to go.)
  2. Browse to the collection into which you will upload the image. Click the "Manage" tab, then click "Add an object to this Collection".
  3. Choose the MODS Simple Entry form. (It's shorter than "Full MODS Form")
  4. You can ignore MARCXML file. MARCXML lets you upload a MARCXML file and that will prepopulate the MODS forms. A library might have these if they are digitizing older public domain materials, where they look for rare items in the catalog, digitize, then export the MARC record from the catalog. You also could make a template MARC file to use if you are uploading a large set of material with many repeated fields that are identical on the whole set of items. MarcEdit will allow easy conversion of a MODS XML file to a MARC XML file. So, to make the MARC XML template, you could use Islandora to fill out repetitive MODS fields, then click to "Manage" then "Datastreams" then "download" MODS, then on your desktop use Notepad to remove fields specific to that item, then use MarcEdit to convert MODS XML to MARC XML, then use the MARC XML template to autofill the repeated fields.
  5. If not using MARCXML, fill out the MODS form and click "Ingest". The MODS Simple Entry Form is long, and the Full MODS Form is even longer. Regarding what fields to fill out, it's good to make a checklist of fields and then fill those out for each image. You may look at other Islandora sites (ex. https://falsc.libguides.com/FL-Islandora/Siteshttps://falsc.libguides.com/FL-Islandora/Sites) and see what fields show up in search results for a site and think that those are more important for someone using the site (FLVC can change these for your site if you want to show or not show certain fields).
  6. Click "Next".
  7. Click "Choose File" and find the image file you would like to upload.
  8. After you click "Ingest", you have created the Basic Image object.

Zip loading Basic Image objects

  1. Make sure the collection you are loading into can hold the "Islandora Basic Image Content Model (islandora:sp_basic_image)". (To check this, browse to the collection you will upload to, then click "Manage", then click "Collection", then on the left it will say "Manage collection policy" and if the box for "Islandora Basic Image Content Model (islandora:sp_basic_image)" is checked then you are good to go.)
  2. Prepare all MODS metadata for your object. It is recommended to use the Excel to MODS Transformer ( https://falsc.libguides.com/FL-Islandora/Metadata ) to prepare the metadata since this will ensure that metadata validates against the MODS schema and meets FLVC's local requirements.
  3. Put all the MODS XML and all image files in a single folder. The name of the image file should match exactly the name of the corresponding XML. For example, the folder should hold pic1.xml, pic1.gif, pic2.xml, pic2.jpeg, etc. and no other files (ie. no XML without a file and no jpg/jpeg/png/gif without an XML file).
  4. Zip that folder to make a .zip file.
  5. Browse to the collection you will upload the pics into. Click the "Manage" tab, then click to the "Collection" tab, then click to "Batch Import Objects".
  6. Under the "Importer" drop-down, you should see "Zip File Importer" selected. If not, then choose "Zip File Importer".
  7. Under Zip Batch Importer, click to "Choose File" and upload the .zip file of MODS XML for your pics. Under "Content Model", select "Islandora Basic Image Content Model (islandora:sp_basic_image)". Then click "Import".
  8. This will load metadata and image files for each Basic Image object.

Offline Batch Ingest for Basic Image objects

Offline batch ingest is available for the Basic Image content model.

Binary

The Binary Object Content Model is designed to enable users to load and display “download only” files of any type. The Binary Object Content Model does not render the content file object itself but enables users to view the object’s metadata and download the object.  This Content Model is ideal for sharing 3D files (e.g., STL, OBJ, AMF, 3MF) that can be downloaded and printed or used by a variety of applications, or for any file format where the objective is to provide a file for download by users. Binary objects can be components of a Compound Object as well, perhaps combining a rendered version of an object as well as a downloadable version.

In order to upload the Binary content model, you need to enable the collection to hold:

  • Islandora Binary Object Content Model (islandora:binaryObjectCModel)

Files for Upload

Any Kind of File

The Binary Object content model is used to ingest a single content object of a file type not supported by the other Islandora content models, or any file in which the desired presentation is a link for download. Since Islandora is not instructed in a method to render the ingested file (datastream), it will provide only a link for the user to download the file. Binary Object is appropriate for common office formats such as spreadsheets, 3D files, slides, and word processing documents, among other things. The Binary Object content model accepts a single file of any type as the primary datastream, and optionally allows the user to upload a thumbnail image to use for the file. If no thumbnail is uploaded, a default thumbnail is provided. Each site can associate default thumbnail icons to be used for particular file Multipurpose Internet Mail Extensions (MIME) types (ie. you can set up Islandora to always load an Excel icon as the thumbnail for .xls files).  Determining the correct MIME type for a specific file can be challenging, because several MIME types may apply to files with the same extension. The following tips may help:

  • Use a site such as http://mime.ritey.com/ to upload your file and determine its MIME type.
  • When all else fails, load the object into Islandora and check its MIME type in the datastreams tab.

NOTE:  This content model will accept any file type as long as the individual file is under 2GB, which is the current (Sept 2018) size limitation on any individual content files in FL-Islandora.

How it looks

OR

NOTE: there is no “Summary” tab to view the object (in this case, a PowerPoint file) and that the display includes the following text and a link to download the object: “This is a downloadable object of filetype ppt and size 536 KB. -> Download”

 

Technical Information/Datastreams

 

The following datastreams will be created for the islandora:binaryObjectCModel:

RELS-EXT      Default Fedora relationship metadata
OBJ The uploaded primary datastream.
MODS MODS record
DC Dublin Core record derived from the MODS record.
TN Thumbnail image, uploaded with the Binary Object or provided as a default by the system.

Uploading Binary Object content model objects through the web

To make the Binary Object content model, you can start with any file at all. This is the only way to hold files like Excel files, Powerpoint files, or datasets. A common way to use the Binary Object content model might be as part of a Compound Object. For example, a Compound Object might have two child objects, one being a PDF of a paper and the other being a Binary Object of a dataset.

  1. Make sure the collection you are loading into can hold the "Islandora Binary Object Content Model (islandora:binaryObjectCModel)". (To check this, browse to the collection you will upload to, then click "Manage", then click "Collection", then on the left it will say "Manage collection policy" and if the box for "Islandora Binary Object Content Model (islandora:binaryObjectCModel)" is checked then you are good to go.)
  2. Browse to the collection into which you will upload the file. Click the "Manage" tab, then click "Add an object to this Collection".
  3. Choose the MODS Simple Entry form. (It's shorter than "Full MODS Form")
  4. You can ignore MARCXML file. MARCXML lets you upload a MARCXML file and that will pre-populate the MODS forms. A library might have these if they are digitizing older public domain materials, where they look for rare items in the catalog, digitize, then export the MARC record from the catalog. You also could make a template MARC file to use if you are uploading a large set of material with many repeated fields that are identical on the whole set of items. MarcEdit will allow easy conversion of a MODS XML file to a MARC XML file. So, to make the MARC XML template, you could use Islandora to fill out repetitive MODS fields, then click to "Manage" then "Datastreams" then "download" MODS, then on your desktop use Notepad to remove fields specific to that item, then use MarcEdit to convert MODS XML to MARC XML, then use the MARC XML template to autofill the repeated fields.
  5. If not using MARCXML, fill out the MODS form and click "Ingest". The MODS Simple Entry Form is long, and the Full MODS Form is even longer. Regarding what fields to fill out, it's good to make a checklist of fields and then fill those out for each Binary Object. You may look at other Islandora sites (ex. https://falsc.libguides.com/FL-Islandora/Sites) and see what fields show up in search results for a site and think that those are more important for someone using the site (FLVC can change these for your site if you want to show or not show certain fields).
  6. Click "Next".
  7. Click "Choose File" and find the file you would like to upload.
  8. After you click "Ingest", you have created the Binary Object content model object.
  9. Go into the collection that the Binary Object is located in.  Look at the thumbnail image on the incoming link, and check that it looks OK.  For common file formats, such as Powerpoint or Excel, FLVC has set up a default thumbnail association.  For less common filetypes, the thumbnail may look like a gray folder icon.  If that is the case, consider adding a thumbnail image (click to the item, click to "Manage", click to "Datastreams", click to "add a datastream", and create a datastream with Datastream ID = "TN" and Datastream Label = "Thumbnail).  That will ensure that incoming links to the item have the desired look and feel.

Zip loading for Binary Object content model objects

Zip loading is not available for the binary object content model.

Offline Batch Ingest for Binary Object content model objects

Offline Batch Ingest is not available for Binary Object content model objects.

Creating Thumbnails for Binary Objects

Before configuring default thumbnails you must create thumbnail files/images. The requirements for these files are:

  • They must be .jpg or .png files

  • Size does not matter, they will always render the default size for Islandora

  • Use a naming convention that will make it easy for you to identify the file. We recommend TN for thumbnail: TN_[file format], for example: TN_audio.jpg.

To upload default thumbnails and associate them with file MIMETYPEs

1. Log in as a user associated with the Islandora Site Administrator role.

2. Click on the “Binary Object” link in the toolbar:

You’ll be presented with a screen that enables you to begin uploading thumbnails and then associating them with MIME types.

Click on the “Upload” link to upload your first thumbnail, browse for your file, then click “Submit” to save it. (Note that the uploaded file won’t be saved until you click “Submit”.) You can continue to upload thumbnails at this point, or you can associate uploaded thumbnails with MIME types.

To associate an uploaded thumbnail with one or more MIME types 
  1. Type in the MIME type in the space provided and click “Add”.
  2. Repeat this for as many MIME types you wish to associate with a thumbnail and click the “Submit” button to save. (Your associations will not be saved until you click “Submit”!)
  3. It’s best to test the new associations by uploading a test object. If you find that it’s not displaying the desired thumbnail, check the object’s MIME type in the Manage -> Datastreams tab to determine if it matches the associations for that thumbnail. Note that MIME types of files produced by the same method or application should be consistent, so it may be helpful to upload one object from each expected source into Islandora to test your associations.

NOTE:

  • The “Remove Selected” button allows you to check any MIME types already associated with a thumbnail and remove them. 
  • The “Delete Association” button removes the selected thumbnail and all of its MIME type associations.

Book

In order to upload the Book content model, you need to enable the collection to hold:

  • The Internet Archive Book Content Model, which contains metadata about the book object.
NOTE: Do not enable/check the Page Content Model, which contains actual page objects (an image for each page). Although it seems counter-intuitive, checking that Content Model will cause problems and is unnecessary.


Books can be created in FL-Islandora through the User Interface, or they can be loaded using Offline Batch Ingest. 

Internet Archive Book Content Model

Files to upload

No files. Just metadata.

The Book content model does not allow any file upload, only metadata creation. You make the book, then you later make pages and each page holds a file.

Examples (of the Book):

Technical Information/Datastreams (for the Book, not the page)

When a book is created online through the interactive online interface, the following datastreams are created at the Book level:

RELS-EXT      Default Fedora relationship metadata
MODS MODS record
DC Dublin Core record
TN Thumbnail image, created from the first page at time of ingest

Page Content Model

  • You upload pages to a Book, not to a collection.
  • The collection that the Book is in has to be able to hold Islandora Page Content Model (islandora:pageCModel)
Files for upload

The Page Content Model is used for each page of a book. If the page is ingested online, it accepts the following files as input:

   TIFF (.tiff, .tif)
   JPEG (.jpeg, .jpg)
   JPEG2000 (.jp2)
How it looks

In FL-Islandora page objects are primarily displayed as jpegs within the Internet Archive Bookreader. The jpegs that a person sees when flipping pages are created by the Islandora software for use as display images. (Original uploaded image files are stored in Islandora, and you can get to the original images by clicking to the page object and viewing Datastreams.)

Page objects viewed alone will display using the OpenSeadragon viewer. This is the same viewer used to display the Large Image Content Model.

Examples (of the pages):

Technical Information/Datastreams (for each Page)

If the pages are ingested through the GUI, the following datastreams are created for each page:

RELS-EXT      Default Fedora relationship metadata
MODS A minimal MODS record created by program
DC Dublin Core record derived from the MODS
OBJ The uploaded TIFF file
JP2 A derivative JPEG2000 image created from the TIFF
JPG A smaller JPEG derivative
TN A thumbnail image of the page created from the JP2
PDF A derivative PDF version of the page, stored for future use in printing
RELS-INT Fedora internal relationship data, giving height and width information about the JP2 page image
OCR Text extracted from the page image by optical character recognition
HOCR A marked up version of the OCR text, indicating word position on the page

Uploading Books one-at-a-time through the web

For Book content model objects, you need a picture of each page to upload. Each page picture needs to be tiff/tif/jpeg/jpg/jp2 . The pages in the book don't all have to be the same file extension as one another, so you can mix .tiff and .jpg or other format into the same Book. If you are starting from a PDF, then use Adobe Acrobat Professional (Adobe Acrobat Reader will not work) to extract an image for each page.

  1. Make sure the collection you are loading into can hold the "Islandora Internet Archive Book Content Model (islandora:bookCModel)". (To check this, browse to the collection you will upload to, then click "Manage", then click "Collection", then on the left it will say "Manage collection policy" and if the box for "Islandora Internet Archive Book Content Model (islandora:bookCModel)" is checked then you are good to go.)
  2. Browse to the collection into which you will upload the book. Click the "Manage" tab, then click "Add an object to this Collection".
  3. Choose the MODS Simple Entry form. (It's shorter than "Full MODS Form")
  4. You can ignore MARCXML file. MARCXML lets you upload a MARCXML file and that will prepopulate the MODS forms. A library might have these if they are digitizing older public domain books, where they look for rare items in the catalog, digitize, then export the MARC record from the catalog. You also could make a template MARC file to use if you are uploading a large set of material with many repeated fields that are identical on the whole set of items. MarcEdit will allow easy conversion of a MODS XML file to a MARC XML file. So, to make the MARC XML template, you could use Islandora to fill out repetitive MODS fields, then click to "Manage" then "Datastreams" then "download" MODS, then on your desktop use Notepad to remove fields specific to that item, then use MarcEdit to convert MODS XML to MARC XML, then use the MARC XML template to autofill the repeated fields.
  5. If not using MARCXML, fill out the MODS form and click "Ingest". The MODS Simple Entry Form is long, and the Full MODS Form is even longer. Regarding what fields to fill out, it's good to make a checklist of fields and then fill those out for each PDF. You may look at other Islandora sites (ex. https://libraries.flvc.org/ca/digital-library-platform-palmm-) and see what fields show up in search results for a site and think that those are more important for someone using the site (FLVC can change these for your site if you want to show or not show certain fields). You can also look at search results in Mango (https://union.discover.flvc.org/ux.jsp). In Mango, you can run a search, then on the left-hand facets, look under "Subcollection", and click to the facet for "Digital Collections". Some of those are coming from Islandora sites, some are coming from UF's Digital Collections, and some are coming from FIU's dPanther. You can look at what fields show up in search results. 
  6. After you click "Ingest", you have created the Book. Now you have to add the Pages.
  7. Prep the images of pages on your computer. (Each image has to be tiff/tif/jpeg/jpg/jp2 . The pages do not have to be the same kind of file as one another, so you can mix it up if you have some .tiff and some .jpg . You will upload them as a zipped file of pages. To do this, put all the pages in the same folder, check that they are sorted in the correct order that you want them in, and then zip that folder up.
  8. From the Book, click to the "Manage" tab, then to "Book", then to "Add Zipped Pages".
  9. Click "Browse" and find your .zip file of pages, then click to "Upload" it, and click to "Add files".
  10. There will be a long wait while Islandora processes the pages. It will run optical character recognition (OCR) on them and make them searchable. While you wait, you can edit metadata for other items on the site, but don't start another upload of zipped pages until the other one is finished.

Zip loading Books

  1. Make sure the collection you are loading into can hold the "Islandora Internet Archive Book Content Model (islandora:bookCModel)". (To check this, browse to the collection you will upload to, then click "Manage", then click "Collection", then on the left it will say "Manage collection policy" and if the box for "Islandora Internet Archive Book Content Model (islandora:bookCModel)" is checked then you are good to go.)
  2. Prepare all MODS metadata for your object. It is recommended to use the Excel to MODS Transformer ( https://fig.wiki.flvc.org/wiki/index.php/Workflow:_From_Spreadsheet_to_Islandora ) to prepare the metadata, since this will ensure that metadata validates against the MODS schema and meets FLVC's local requirements.
  3. Put all the MODS XML, but no files, in a single folder and zip that folder to make a .zip file.
  4. Browse to the collection into which you will upload the Books. Click the "Manage" tab, then click to the "Collection" tab, then click to "Batch Import Objects".
  5. Under the "Importer" drop down, you should see "Zip File Importer" selected. If not, then choose "Zip File Importer".
  6. Under Zip Batch Importer, click to "Choose File" and upload the .zip file of MODS XML for your books. Under "Content Model", select "Islandora Internet Archive Book Content Model". Then click "Import".

This will load metadata records for each book. Now, you will load the pages. For each Book:

  1. Click to the Book, then click to the "Manage" tab, click to the "Manage" tab, then to "Book", then to "Add Zipped Pages".
  2. Click "Browse" and find your .zip file of pages, then click to "Upload" it, and click to "Add files".
  3. There will be a long wait while Islandora processes the pages. It will run optical character recognition (OCR) on them and make them searchable. While you wait, you can edit metadata for other items on the site, but don't start another upload of zipped pages until the other one is finished.

Offline batch ingest for Books

Offline batch ingest is available for the Book content model. In fact, it is preferred that members use offline batch ingest for Books and Newspaper Issues. This is because running OCR takes a lot of server resources when you upload pages through the web interface. Feel free to contact help@flvc.org for assistance in getting started with offline batch ingest.

  1. Make sure the collection you are loading into can hold the "Islandora Internet Archive Book Content Model (islandora:bookCModel)". (To check this, browse to the collection you will upload to, then click "Manage", then click "Collection", then on the left it will say "Manage collection policy" and if the box for "Islandora Internet Archive Book Content Model (islandora:bookCModel)" is checked then you are good to go.)
  2. Make sure you are set up with access to upload via FTP for offline batch ingest. You can email help@flvc.org to get set up with an account.

Book step-by-step Training Exercise.

Compound

In order to upload a Compound Object content model, you need to enable the collection to hold:

  • Islandora Compound Object Content Model (islandora:compoundCModel)
  • All content models used in any component parts.

Files for upload

The Compound Object content model is metadata only. It holds together multiple objects, and those objects can have different formats.  Normally, the child objects will already be in the repository. The Parent Object is then created using the Compound Object content model, and the children are then associated with the parent.

The Compound Object content model can be used when two or more objects are related to each other. For example, two images that represent the front and back of a postcard, or a spoken-word audio file and corresponding PDF transcript. In a Compound Object, there is a parent object, loaded using the Compound Object Content Model. The parent object consists of metadata only. (Note that the parent object metadata display will be a default display of the DC datastream until child objects are attached. Replacing a MODS datastream in this situation doesn't update the DC datastream.) It has two or more child objects associated with it that adhere to other content models. The child objects are loaded using the Content Model appropriate to their file types and are associated with the "parent" object. In search results, only the parent object is displayed, and clicking on the parent object displays all "child" objects associated with that parent. Relationships between parent and child objects should be managed from the parent object.

How it looks

Examples:

Technical Information/Datastreams

For the parent, the following datastreams are created:

RELS-EXT      Default Fedora relationship metadata
MODS MODS record
DC Dublin Core record
TN Thumbnail image, created from the first page at time of ingest

Uploading Compound Object content model objects one-at-a-time through the web

To make the Compound Object content model, you don't use a file. Instead, the Compound Object is metadata for holding other content models. A single Compound Object can hold an unlimited number of other items as child objects.

  1. Visualize what you want your Compound Objects to look like and what you want to do with them (ie. show front and back of a postcard, show a sculpture from different angles, present all together audio from a speech and video from a speech and the program handed out at the speech, published paper and dataset). Draw a sketch on paper of a sample Compound Object with the children.
  2. Decide what content model you will use for each child object. Upload your child objects to the collection you will create the Compound Objects in. For example, if you are working with front and back of postcards, then you might upload Basic Image or Large Image objects to the collection.
  3. Upload the Compound Object parent objects. Make sure the collection you are loading into can hold the "Islandora Compound Object Content Model (islandora:compoundCModel)". (To check this, browse to the collection you will upload to, then click "Manage", then click "Collection", then on the left it will say "Manage collection policy" and if the box for "Islandora Compound Object Content Model (islandora:compoundCModel)" is checked then you are good to go.) (You should leave the content models enabled for all the child objects.)
  4. Browse to the collection in which you will upload the Compound Object. Click the "Manage" tab, then click "Add an object to this Collection".
  5. For "Select a Content Model to Ingest", choose the "Islandora Compound Object Content Model".
  6. Choose the MODS Simple Entry form. (It's shorter than "Full MODS Form")
  7. You can ignore MARCXML file. MARCXML lets you upload a MARCXML file and that will prepopulate the MODS forms. A library might have these if they are digitizing older public domain materials, where they look for rare items in the catalog, digitize, then export the MARC record from the catalog. You also could make a template MARC file to use if you are uploading a large set of material with many repeated fields that are identical on the whole set of items. MarcEdit will allow easy conversion of a MODS XML file to a MARC XML file. So, to make the MARC XML template, you could use Islandora to fill out repetitive MODS fields, then click to "Manage" then "Datastreams" then "download" MODS, then on your desktop use Notepad to remove fields specific to that item, then use MarcEdit to convert MODS XML to MARC XML, then use the MARC XML template to autofill the repeated fields.
  8. If not using MARCXML, fill out the MODS form and click "Ingest". The MODS Simple Entry Form is long, and the Full MODS Form is even longer. Regarding what fields to fill out, it's good to make a checklist of fields and then fill those out for each PDF. You may look at other Islandora sites (ex. https://falsc.libguides.com/FL-Islandora/Sites) and see what fields show up in search results for a site and think that those are more important for someone using the site (FLVC can change these for your site if you want to show or not show certain fields).
  9. After you click "Ingest", you have created the Compound Object content model object. Now you have to link up the child objects. NOTE: Before you link up the child objects, the display of the Compound Object will look odd, and you will not be able to see MODS information from the public interface. 
Linking the child objects
  1. Browse to the collection holding your child objects and your Compound Object parent.
  2. Click to "View All Items in this Collection" in the top right corner. Look under the label "Collection home" in the top right corner and click the Excel icon (looks like a small bow with a green grid and a color wheel on it). When you click the Excel icon, Islandora will make a spreadsheet of all the items in the collection. Click to download along the top of the screen where it says, "The exported results CSV is available for download here." Use this spreadsheet as a checklist and mark off each child object as you add it to the Compound Object.
  3. Browse to the collection holding your child objects and your Compound Object parent.
  4. Click to the Compound Object parent. Click the "Manage" tab on the Compound Object parent, then click to the "Compound" tab.
  5. Under the heading for "ADD CHILD OBJECTS" under "Child Object Pid/Label" fill in the PID for a child object, then click "Add". It's best to type the PID, with all but the last number, and then when Islandora suggests some PIDS, click the correct one. This means each character is formatted perfectly with no extra spaces at the end or anything like that.
  6. Continue through filling out "Child Object Pid/Label" and adding each child object. Use the spreadsheet you downloaded in step 11 as a checklist.
  7. Check the Compound Object and make sure it looks like you want it to: Browse to the collection holding the Compound Object. You should now see only the parent Compound Object, but not see the children. Once an object becomes a child of a Compound Object, that child object is hidden from view. (The child objects will show up in search results. Search results will show the thumbnail for the parent object but will link to the child object in the context of the parent object. Try this out to see how it works.)
  8. If you need to make any changes to the Compound Object: Click into the Compound Object, then click the "Manage" tab, then click to "Compound". Using "REMOVE CHILD OBJECTS" and "REORDER" you can change how the Compound Object looks. "REMOVE CHILD OBJECTS" will remove them from the parent compound object, but won't delete them, so you can't break anything from here.

Zip loading Compound Object content model objects

  1. Visualize what you want your Compound Objects to look like and what you want to do with them (ie. show front and back of a postcard, show a sculpture from different angles, present all together audio from a speech and video from a speech and the program handed out at the speech, published paper and dataset). Draw a sketch on paper of a sample Compound Object with the children.
  2. Decide what content model you will use for each child object. Upload your child objects to the collection you will create the Compound Objects in. For example, if you are working with front and back of postcards, then you might upload Basic Image or Large Image objects to the collection.
  3. Upload the Compound Object parent objects. Make sure the collection you are loading into can hold the "Islandora Compound Object Content Model (islandora:compoundCModel)". (To check this, browse to the collection you will upload to, then click "Manage", then click "Collection", then on the left it will say "Manage collection policy" and if the box for "Islandora Compound Object Content Model (islandora:compoundCModel)" is checked then you are good to go.) (You should leave the content models enabled for all the child objects.)
  4. Prepare all MODS metadata for your Compound Objects. It is recommended to use the Excel to MODS Transformer ( https://falsc.libguides.com/FL-Islandora/Metadata ) to prepare the metadata, since this will ensure that metadata validates against the MODS schema and meets FLVC's local requirements. Hint: If you used the Excel to MODS Transformer to prep your child objects, then you can reuse the older spreadsheet, by changing the IIDs and changing any fields that describe the physical object (ie. fields about format or media that the object is in). Usually, the metadata for the parent object and its children are very similar.
  5. Put all the compound object parent MODS XML in a single folder.
  6. Zip that folder to make a .zip file.
  7. Browse to the collection into which you will upload the Compound Objects. Click the "Manage" tab, then click to the "Collection" tab, then click to "Batch Import Objects".
  8. Under the "Importer" drop-down, you should see "Zip File Importer" selected. If not, then choose "Zip File Importer".
  9. Under Zip Batch Importer, click to "Choose File" and upload the .zip file of MODS XML for your Compound Object parents. Under "Content Model", select "Islandora Compound Object Content Model (islandora:compoundCModel)". Then click "Import".
  10. This will load metadata for each Compound Object parent.
Linking the Compound Object parents and child objects

For each Compound Object, you have to manually add the children. Refer to the instructions above for "Uploading Compound Object content model objects one-at-a-time through the web." Especially, use the downloaded spreadsheet as a checklist and to keep organized in matching the correct parent objects with the correct child objects.

Offline Batch Ingest for Compound Object content model objects

Offline Batch Ingest is not available for Compound Object content model objects.

Large Image

In order to upload the Large Image content model, you need to enable the collection to hold:

  • Islandora Large Image Content Model (islandora:sp_large_image_cmodel)

Files for upload

The Islandora Large Image Content Model accepts a single image of the following file types as input:

   JPEG2000 (.jp2, .jpg2)
   TIFF (.tiff, .tif)

How it looks

Large Image objects are displayed as JP2s in an interactive viewfinder (OpenSeadragon).

Examples:

Technical Information/Datastreams

When a JPEG2000 is provided as the source image, the following datastreams are created:

RELS-EXT      Default Fedora relationship metadata
MODS MODS record
DC Dublin Core record
TN Derived thumbnail image
OBJ A TIFF file created from the source JPEG2000
JP2 The source JPEG2000 image
JPG A medium sized JPEG derivative.

 

When a TIFF image is provided as the source, the OBJ and JP2 datastreams are created differently:

OBJ      The source TIFF file.
JP2 A JPEG2000 image derived from the TIFF source.

 

Uploading Large Image objects one-at-a-time through the web

To make the Large Image content model, you have to have a .jp2, jpg2, or .tiff file.

  1. Make sure the collection you are loading into can hold the "Islandora Large Image Content Model (islandora:sp_large_image_cmodel)". (To check this, browse to the collection you will upload to, then click "Manage", then click "Collection", then on the left it will say "Manage collection policy" and if the box for "Islandora Large Image Content Model (islandora:sp_large_image_cmodel)" is checked then you are good to go.)
  2. Browse to the collection into which you will upload the image file. Click the "Manage" tab, then click "Add an object to this Collection".
  3. Choose the MODS Simple Entry form. (It's shorter than "Full MODS Form")
  4. You can ignore MARCXML file. MARCXML lets you upload a MARCXML file and that will prepopulate the MODS forms. A library might have these if they are digitizing older public domain materials, where they look for rare items in the catalog, digitize, then export the MARC record from the catalog. You also could make a template MARC file to use if you are uploading a large set of material with many repeated fields that are identical for the whole set of items. MarcEdit will allow easy conversion of a MODS XML file to a MARC XML file. So, to make the MARC XML template, you could use Islandora to fill out repetitive MODS fields, then click to "Manage" then "Datastreams" then "download" MODS, then on your desktop use Notepad to remove fields specific to that item, then use MarcEdit to convert MODS XML to MARC XML, then use the MARC XML template to autofill the repeated fields.
  5. If not using MARCXML, fill out the MODS form and click "Ingest". The MODS Simple Entry Form is long, and the Full MODS Form is even longer. Regarding what fields to fill out, it's good to make a checklist of fields and then fill those out for each PDF. You may look at other Islandora sites (ex. https://falsc.libguides.com/FL-Islandora/Sites) and see what fields show up in search results for a site and think that those are more important for someone using the site (FLVC can change these for your site if you want to show or not show certain fields).
  6. Click "Next".
  7. Click "Choose File" and find the image file you would like to upload.
  8. After you click "Ingest", you have created the Large Image object.

Zip loading Large Image objects

  1. Make sure the collection you are loading into can hold the "Islandora Large Image Content Model (islandora:sp_large_image_cmodel)". (To check this, browse to the collection you will upload to, then click "Manage", then click "Collection", then on the left it will say "Manage collection policy" and if the box for "Islandora Large Image Content Model (islandora:sp_large_image_cmodel)" is checked then you are good to go.)
  2. Prepare all MODS metadata for your object. It is recommended to use the Excel to MODS Transformer ( https://falsc.libguides.com/FL-Islandora/Metadata ) to prepare the metadata since this will ensure that metadata validates against the MODS schema and meets FLVC's local requirements.
  3. Put all the MODS XML and all files, in a single folder. The name of the content file should match the name of the corresponding XML. For example, the folder should hold pic1.xml, pic1.jp2, pic2.xml, pic2.tiff, etc. and no other files (ie. no XML without a file and no jp2/jpg2/tiff without an XML file).
  4. Zip that folder to make a .zip file.
  5. Browse to the collection you will upload the pics into. Click the "Manage" tab, then click to the "Collection" tab, then click to "Batch Import Objects".
  6. Under the "Importer" drop-down, you should see "Zip File Importer" selected. If not, then choose "Zip File Importer".
  7. Under Zip Batch Importer, click to "Choose File" and upload the .zip file of MODS XML for your pics. Under "Content Model", select "Islandora Large Image Content Model (islandora:sp_large_image_cmodel)". Then click "Import".
  8. This will load metadata and files for each Large Image object.

Offline Batch Ingest for Large Image objects

Offline batch ingest is available for the Large Image content model.

Newspaper

In order to upload the Islandora Newspaper content model, you need to enable the collection to hold:

  • Islandora Newspaper Content Model (islandora:newspaperCModel)
Note: Even though the Page and Issue Content Model options appear in the list, do not enable/check the following options:
  • Islandora Newspaper Issue Content Model (islandora:newspaperIssueCModel)
  • Islandora Newspaper Page Content Model (islandora:newspaperPageCModel)

Newspaper Content Model

Islandora Newspaper Content Model (islandora:newspaperCModel)

Files to upload

No files. Just metadata.

The Islandora Newspaper Content Model does not allow any file upload, and instead only holds metadata for the top-level newspaper - the run of the newspaper, not any issues. It is the top-level container into which issues of the newspaper are loaded. For understanding terminology, the container or root is "The New York Times", and an issue is "VOL. CLXV...No. 57,081/Dec 15, 2015".

How it looks

A newspaper is displayed as a tree of years and months containing issues.

Islandora automatically creates a browse by date interface. You click to the year, then a month, then the day to get to the issue you want. You are able to upload multiple issues for a single day, for example, if a newspaper had a morning and an evening edition.

Examples (of top level newspaper objects):

Technical Information/Datastreams (for the Newspaper, not the issue, not the pages)

When a newspaper is created online through the interactive online interface the following datastreams are created at the Newspaper level:

RELS-EXT      Default Fedora relationship metadata
MODS MODS record
DC Dublin Core record

 

NOTE: No TN (Thumbnail) datastream is created, although the default folder icon will display for a newspaper title. After a newspaper title object is created you can replace the thumbnail (TN) datastream with another thumbnail at any time. Many users use a thumbnail from an attractive newspaper issue as the thumbnail for the newspaper title.

Newspaper Issue Content Model

Islandora Newspaper Issue Content Model (islandora:newspaperIssueCModel)

Files for upload

The Islandora Newspaper Issue content model is metadata only, not files. Pages within the Newspaper Issue will hold the files.

Issues are created through an object with the Islandora Newspaper Content Model. Issues are displayed in the Internet Archive Bookreader and are similar to the Islandora Internet Archive Book content model objects.

How it looks

Examples:

Technical Information/Datastreams (for each Issue, not the top level newspaper, not the pages)

The following datastreams are created:

RELS-EXT      Default Fedora relationship metadata
MODS MODS record
DC Dublin Core record
TN Thumbnail image, created from the first page at time of ingest

The first three datastreams are created by online ingest at the time the issue is created. The TN (Thumbnail) datastream is created when the first page is added to the issue.

Newspaper Page Content Model

Islandora Newspaper Page Content Model (islandora:newspaperPageCModel)

  • You upload pages to a Newspaper Issue, not to a collection.
  • The collection that the top level Newspaper is in has to be able to hold Islandora Newspaper Page Content Model (islandora:newspaperPageCModel)

Files for upload

The Newspaper Page Content Model can take TIFF, JP2, or JPG images as source files.

  TIFF (.tiff, .tif)
  JPEG2000 (.jp2, .jpg2)
  JPEG (.jpg, .jpeg)

How pages look

Newspaper Page objects are added to a Newspaper Issue object in the same way Page Objects are added to Book Objects. Newspaper Page objects are also displayed in the IA Bookreader as jpeg and as jp2 in the OpenSeadragon viewfinder as individual newspaper pages.

Technical Information/Datastreams (for each Page)

If a TIFF file is provided the following datastreams are created.

RELS-EXT      Default Fedora relationship metadata
DC A minimal Dublin Core record with only title (filename of page image) and Fedora PID
TN Thumbnail image, created from the first page at time of ingest
OBJ The uploaded TIFF file
JP2 A derivative JPEG2000 image created from the TIFF
TN A thumbnail image of the page created from the JP2
JPEG A derivative medium-sized JPEG image of the page
PDF A derivative PDF version of the page
RELS-INT Fedora internal relationship data, giving height and width information about the JP2 page image
OCR Text extracted from the page image by optical character recognition
HOCR A marked up version of the OCR text, indicating word position on the page

If a JP2 source file is provided, the OBJ datastream contains the original JP2, and the JP2 datastream contains a derivative JP2.

If a JPG source file is provided, the OBJ datastream contains the original JPG, the JPG datastream contains a medium-sized derivative JPG, and a JP2 derivative is created.

Uploading Newspapers through the web

For Newspapers, you need a picture of each page to upload. If you are starting from a PDF, then use Adobe Acrobat Professional (Adobe Acrobat Reader will not work) to extract an image for each page.

Create the Newspaper parent object
  1. Make sure the collection you are loading into can hold the "Islandora Newspaper Content Model (islandora:newspaperCModel)". (To check this, browse to the collection you will upload to, then click "Manage", then click "Collection", then on the left it will say "Manage collection policy" and if the box is checked for "Islandora Newspaper Content Model (islandora:newspaperCModel)" then you are good to go.)
  2. Browse to the collection into which you will upload the newspaper. Click the "Manage" tab, then click "Add an object to this Collection".
  3. Choose the MODS Simple Entry form. (It's shorter than "Full MODS Form")
  4. You can ignore MARCXML file. MARCXML lets you upload a MARCXML file and that will prepopulate the MODS forms. A library might have these if they are digitizing older public domain materials, where they look for rare items in the catalog, digitize, then export the MARC record from the catalog. You also could make a template MARC file to use if you are uploading a large set of material with many repeated fields that are identical on the whole set of items. MarcEdit will allow easy conversion of a MODS XML file to a MARC XML file. So, to make the MARC XML template, you could use Islandora to fill out repetitive MODS fields, then click to "Manage" then "Datastreams" then "download" MODS, then on your desktop use Notepad to remove fields specific to that item, then use MarcEdit to convert MODS XML to MARC XML, then use the MARC XML template to autofill the repeated fields.
  5. If not using MARCXML, fill out the MODS form and click "Ingest". The MODS Simple Entry Form is long, and the Full MODS Form is even longer. Regarding what fields to fill out, it's good to make a checklist of fields and then fill those out for each PDF. You may look at other Islandora sites (ex. https://falsc.libguides.com/FL-Islandora/Sites) and see what fields show up in search results for a site and think that those are more important for someone using the site (FLVC can change these for your site if you want to show or not show certain fields).
  6. Add a thumbnail to the parent newspaper object. Click "Manage", then click "Datastreams", then click "Add a datastream". Upload a thumbnail for the newspaper. For “Datastream ID”: type “TN”, For “Datastream Label”: type “Thumbnail" and for Upload document: Find the thumbnail you want to use and upload it. (Recommended size is 200 x 200.)
Create the Newspaper Issue
  1. Click to the Newspaper parent object in which you want to create a Newspaper Issue.
  2. Click the "Manage" tab, then click to "Add Issue".
  3. You can ignore MARCXML file. MARCXML lets you upload a MARCXML file and that will prepopulate the MODS forms. A library might have these if they are digitizing older public domain materials, where they look for rare items in the catalog, digitize, then export the MARC record from the catalog. You also could make a template MARC file to use if you are uploading a large set of material with many repeated fields that are identical on the whole set of items. MarcEdit will allow easy conversion of a MODS XML file to a MARC XML file. So, to make the MARC XML template, you could use Islandora to fill out repetitive MODS fields, then click to "Manage" then "Datastreams" then "download" MODS, then on your desktop use Notepad to remove fields specific to that item, then use MarcEdit to convert MODS XML to MARC XML, then use the MARC XML template to autofill the repeated fields.
  4. Fill out the MODS form and way at the bottom click "Ingest". For Newspaper Issues, most of the MODS record will be similar across all issues. As you are getting started, consider working with FLVC explore ways to get the metadata prepped in batches.
Load the pages to the Newspaper Issue
  1. After you click "Ingest", you have created the Newspaper Issue. Now you have to add the Pages.
  2. Prep the image files pf pages on your computer. Each page pic should be a tiff/tif/jp2/jpg2/jpg/jpeg file. You can mix file types in the same load, so you can have .jpeg and .tif files zipped together and loaded to the same issue. You will upload them as a zipped file of pages. To do this, put all the pages in the same folder, check that they are sorted in the correct order that you want them in, and then zip that folder up.
  3. Browse to the Newspaper Issue that you want to add pages to, click to the "Manage" tab, then click to the "Issue" tab.
  4. Click to "Add Zipped Pages".
  5. Click "Browse" and find your .zip file of pages, then click to "Upload" it, and click to "Add files".
  6. There will be a long wait while Islandora processes the pages. It will run optical character recognition (OCR) on them and make them searchable. While you wait, you can edit metadata for other items on the site, but don't start another upload of zipped pages until the other one is finished.

Zip loading Newspapers

There is no way to zip load Newspaper Issues.

Offline batch ingest for Newspapers

Offline batch ingest is available for the Newspaper Issue content model. 

  1. Create the Newspaper parent object through the GUI.
  2. Prepare all MODS metadata for your object. It is recommended to use the Excel to MODS Transformer to prepare the metadata, since this will ensure that metadata validates against the MODS schema and meets FLVC's local requirements.

Newspaper step-by-step Training Exercise.

Serial

The serials module enables users to create a top-level metadata record that represents a serial title and from that record, you can create a hierarchical tree view with links to individual serial issues. Serial issues are either a single PDF that represents an entire issue, or a set of PDFs that represent individual articles or sections of an issue.

The FL-Islandora serials module contains three different types of objects:

  • A Serial title object:
    • represents the serial title and contains MODS metadata and a thumbnail, a hierarchical tree, and links to other objects.
    • is the top-level object displayed in the “View all items” function or collection browse.
    • displays a hierarchical tree of one or more levels of hierarchy, with links to issues at the lowest level of the hierarchy
    • is parent to “intermediate objects” that represent nodes in the hierarchical tree display
  • An intermediate object:
    • simply represents a node or branch in the hierarchical tree display of the serial and contains no thumbnail or other content file/datastream
    • at the lowest level of the tree hierarchy, the intermediate object is the “parent” of a serial issue (one or more PDFs)
    • is created from within the serial title object using the “intermediate management” function
    • contains only a MODS metadata datastream (and the Dublin Core datastream derived from the MODS and required by Islandora).
    • the intermediate object’s MODS datastream is created when the user creates the hierarchical tree. The MODS metadata can be edited either via an “intermediate management” form or directly from the intermediate object.
  • A PDF object:
    • represents either an entire serial issue or a section or article of a serial issue
    • is linked to a “parent” intermediate object and loaded into Islandora from the Manage tab of the “parent” intermediate object
    • each PDF object contains its own MODS datastream.
    • if the PDF object represents an entire serial issue, its MODS datastream should contain issue-level metadata
    • if the PDF object represents a section or article of a serial issue, its MODS datastream should contain metadata describing the specific section or article

An example of an FL-Islandora serial title and relationships with intermediate objects and PDF objects. In this example, the tree hierarchy has two levels, Volume, and Issue:

To configure a collection to contain Serial Content Model objects, enable/check the

  • Islandora Serial Object Content Model (islandora:rootSerialCModel)

NOTE: Do not enable the following Content Models:

  • Islandora Serial Object Intermediate Content Model (islandora:intermediateCModel)

  • Islandora Serial Object Intermediate Category Content Model (islandora:intermediateSerialCModelStub)

Even though it seems counter-intuitive, enabling/checking the above options will cause problems.

Files for upload

For serials, you will upload using PDF. Each PDF has its own metadata. You can upload one PDF for a whole issue, or you can upload several PDFs of articles together in the same issue and the software will display as a table of contents:

The table of contents as a whole and Description tab represents a single Serial Object Intermediate. Sections defined in the left-most column of the table of contents are Serial Object Intermediate Category objects. The article titles represent PDF objects that are children of the Serial Object Intermediate.  The "Full Description" tab displays the descriptive metadata for the serial issue intermediate object (No. 4), and the "Serial Details" tab displays the descriptive metadata for the serial title object (Journal of Coastal Research).  The “Section” headings are manually created from the “PDF Management” screen found by clicking on the Manage tab. Authorized users can edit and view single PDF objects from this display by clicking on the title link.

Serial Object Content Model

Islandora Serial Object Content Model (islandora:rootSerialCModel)

Files to upload

Metadata only. No files.

Similar to the Newspaper Content Model, Serial Objects are the primary parent, container, or "root" object of a serial. For example, the publication Time Magazine would be represented in its entirety by a single Serial Object.

How it looks

The tree as a whole and Details tab represent the Serial Object.

The Serial Object shows a tree browse of the Serial Object Intermediates. You can specify what these are called. For example, you can have "Volumes" and "Issues". You can have "Years" and "Months". You can have "Volumes" and "Numbers". You can have "Volumes" and "Issues" and "Numbers". You can go as many levels deep as you'd like.

Below, the individual nodes defined by the user are Volume and Issue. Each of those (Volume and Issue) a Serial Object Intermediate object. And below is how the Serial Object looks.

The “Serial Details” tab displays descriptive metadata and a thumbnail of the serial title:

Examples:

Technical Information/Datastreams

The following datastreams will be created:

RELS-EXT

Default Fedora relationship metadata

MODS

MODS record

DC

Dublin Core record

TN

Thumbnail image. Not created on ingest, must be added

SERIAL-LEVELS     

Hierarchical Information for the Serial Object

Serial Object Intermediate Content Model

Islandora Serial Object Intermediate Content Model (islandora:intermediateCModel)

Files to upload

These are metadata only objects. They have a name specified when you create them, for example, "Volume" or "Issue" or "Month". They allow other content to be structured.

Metadata-only objects that serve as layers of separation between the serial "root" object and the PDF objects. Intermediate objects without intermediate children may have one or more PDF children added through PDF Management. Examples of intermediate objects are year, volume, issue, etc. - as in Time magazines published in 2010. Time vol 81. Time No. 3. No. 3 may have a single PDF of this issue of Time or it may have many in the form of articles. In this example, Time Vol.81 No 3. 2010, is three stacked intermediate objects and is the path down from Serial Object root to a PDF.

Technical Information/Datastreams

The following datastreams will be created:

RELS-EXT     

Default Fedora relationship metadata

MODS

MODS record

DC

Dublin Core record

Serial Object Intermediate Category Content Model

Islandora Serial Object Intermediate Category Content Model (islandora:intermediateSerialCModelStub)

Serial Object Intermediate Category Content Model objects are the rarest and most beautiful content model in islandora. Their only purpose is to serve as section headings within the table of contents of a single intermediate object. Example: Editorials in an issue of Time magazine. They may be added as children of intermediates that also have PDF children. They may have no child objects.

The following datastreams will be created:

RELS-EXT     

Default Fedora relationship metadata

DC

Dublin Core record

Uploading Serials through the web

For Serial content model objects, you need a .pdf of each article or of each issue to upload. If you are starting from a series of scanned pictures rather than starting with a .pdf, then use Adobe Acrobat Professional (Adobe Acrobat Reader will not work) to combine the images into a .pdf.

Create the Serial parent object

Setting up the Serial parent object is one of the trickier things in Islandora. You only do it once for a serial, and the rest of what you do is upload PDFs inside it. Feel free to email help@flvc.org with "Islandora" in the subject line, and ask for someone from FL Library Services to go on screen-sharing with you and set up the serial.

  1. Look at the material you will upload, then look at the accordion views for the example Serial objects ( https://palmm.digital.flvc.org/islandora/object/uf:147 , http://fau.digital.flvc.org/islandora/object/fau:13741 , https://palmm.digital.flvc.org/islandora/object/ucf:9622 ). Use a pen and paper to draw out a few accordion views for your serial that you plan to upload. This way you nail down part/volume/issue/chapter/section/paragraph/track/etc. Keep your sketch handy when you go to create the Serial Object content model (ie. parent serial).
  2. Make sure the collection you are loading into can hold the "Islandora Serial Object Content Model (islandora:rootSerialCModel)". (To check this, browse to the collection you will upload to, then click "Manage", then click "Collection", then on the left it will say "Manage collection policy" and if the box is checked for "Islandora Serial Object Content Model (islandora:rootSerialCModel)" then you are good to go.)
  3. Browse to the collection into which you will upload the serial. Click the "Manage" tab, then click "+ Add an object to this Collection".
  4. Select a MODS edit form and created metadata as appropriate for the serial title. FL Library Services recommends the MODS Simple Entry form.
  5. You can ignore MARCXML file. MARCXML lets you upload a MARCXML file and that will prepopulate the MODS forms. A library might have these if they are digitizing older public domain materials, where they look for rare items in the catalog, digitize, then export the MARC record from the catalog. You also could make a template MARC file to use if you are uploading a large set of material with many repeated fields that are identical on the whole set of items. MarcEdit will allow easy conversion of a MODS XML file to a MARC XML file. So, to make the MARC XML template, you could use Islandora to fill out repetitive MODS fields, then click to "Manage" then "Datastreams" then "download" MODS, then on your desktop use Notepad to remove fields specific to that item, then use MarcEdit to convert MODS XML to MARC XML, then use the MARC XML template to autofill the repeated fields.
  6. If not using MARCXML, fill out the MODS form and click "Ingest". The MODS Simple Entry Form is long, and the Full MODS Form is even longer. Regarding what fields to fill out, it's good to make a checklist of fields and then fill those out for each PDF. You may look at other Islandora sites (ex. https://falsc.libguides.com/FL-Islandora/Sites) and see what fields show up in search results for a site and think that those are more important for someone using the site (FLVC can change these for your site if you want to show or not show certain fields).
  7. After you click through the MODS and click "Next", you will see a menu reading "Serial Level Configuration".  On this screen you’ll be presented with the option to define levels of hierarchy for your serial title, but if you do not wish to do so click “Ingest” to save your MODS metadata. If you do not define your hierarchy now you may be able to define levels of hierarchy at a later time, but it is best to do define now. To return to the Serial Level Configuration:  Click on the serial title object’s Manage tab, then on the “Intermediate Management” link.

Serials can hold levels and these can be nested any amount deep. For example, you can have "Series" then "Volume" then "Issue". You can have "Volume" then "Number" then "Issue". You can have "Year" then "Month" then "Day". You can have "Volume" then "Quarter" (ie. spring, summer, fall). Look back at the examples, and see how these will look in an accordion display.

The serials module requires you to define the number of levels of hierarchy for each serial title’s hierarchical tree display. Each serial title has its own definition of levels of hierarchy and default metadata that will be used to create the hierarchical tree display.

Next to "Hierarchical Level"

  • under "MODS DETAIL[@TYPE] VALUE" put a one word label for what you'd like. This will be recorded in the metadata.
  • under "DEFAULT CAPTION VALUE" fill in the label that you want to show up to someone browsing the site. This will show up to the public.
  • For "Level 1", enter your top level. For example, on Spanish River Papers http://fau.digital.flvc.org/islandora/object/fau:13741 , "Level 1" is "Volume".
  • For "Level 2", enter your second level down. For example, on Spanish River Papers http://fau.digital.flvc.org/islandora/object/fau:13741 , "Level 2" is "Number".

When you've filled out the "Serial Level Configuration" and entered all you levels you'd like to have, click "Next".

To define levels of hierarchy for your serial title’s tree display

Select “Add a level”. You can now define the number of levels of hierarchy in your tree display and the default labels that will appear in the tree display. These labels also populate the MODS datastream for the intermediate objects in the tree. An example of perhaps the most common setup of two levels of hierarchy, volume and issue. (Note that the “default caption value” is the text that will display to the public in the tree, and the MODS)

The Serial Level Configuration is saved to the serial title object as a “SERIALS-LEVELS” datastream. You will be able to modify and delete the SERIALS-LEVELS file as long as you have not created the tree display.

Creating the nodes/branches of the hierarchical tree display

Once your levels of hierarchy are defined you’ll be ready to create the actual hierarchical tree display. That process will use the defaults defined in your SERIALS-LEVELS file.  To return to the hierarchical tree display:  from a serial title object record click on the Manage tab and then on the Intermediate Management link.  You may be presented with the Serial Level Configuration screen (SERIALS-LEVELS) for a last opportunity to modify the hierarchy. If you’re satisfied with your hierarchy, click “Next”.

8) This takes you to a "Create Intermediate Objects" screen. This is a screen that creates a “drag and drop” table. Click “Add another” to start building nodes/branches/intermediate objects of your tree. Create at least one intermediate by typing something into the blank for "Number". For example, if your top level is Volume, then fill in "Number" with 1 to create a Volume 1. To go back and edit this later, click "Ingest".

The table will be populated with an intermediate object at the highest level of your hierarchy, and the Caption field will default to the caption you input in your Serial Level Configuration file. File in the Number field with the value to display in your tree and click “Update” to save.

In the above example, the caption is “Vol.” and the number is “1”. The display label for that node/branch of the hierarchical tree display will be “Vol. 1”.

To create intermediate objects at the lower level of hierarchy, click “Add another”, then drag the new object to the right with your cursor. Islandora will indent the object and the caption will then default to the caption defined for Level 2 of your hierarchy:

You can continue to create additional intermediate objects/nodes/branches using the above steps. Each row in the table will create an serials intermediate object.  NOTE: updating/saving the table will cause the public display of the tree to be updated. At this point those nodes will not yet link to PDF objects.

9) Browse to the Serial Object content model object you'd like to add an issue to. Click the "Manage" tab, then click to the "Intermediate Management" tab and check what volumes, issues, numbers, etc. already exist for this Serial.

10) Click "Add another", then drag and drop the new intermediate to where you want it. If you drag it to the right, it will convert from top level in the accordion view to a lower level. Build out a tree to hold your PDFs, by clicking "Add another", dragging and dropping where you want it, and filling in the blank for "Number". (Even though this blank is labeled "Number" it can hold letters or anything you want. For example, if you have something where the issues are named Fall, Winter, Spring, then you can type out "Fall" or "Winter" or "Spring" under the heading "Number".) When you are done or at a stopping point, click "Update". This will save your changes. You can go back at any time to this "Intermediate Management" and building the tree view.

Uploading PDFs to Serial content model objects

The PDF management function and the ability to load PDFs is available only at the lowest level of the tree hierarchy. You cannot load PDFs at any other level of the hierarchical tree. For example, if your hierarchical tree contains two levels of hierarchy, volumes and issues, you will only be able to add PDFs at the issue level and will not be able to add/link PDFs at the volume level.

Serials PDF objects are virtually identical to PDF objects created using the PDF Content Model, however, you cannot modify/transform a PDF object loaded using the PDF Content Model into a serials PDF object. In other words, if you have already loaded a PDF representing a serials issue using the PDF Content Model that object will need to be reloaded from within the serials module if you want it to link to a node in the hierarchical tree display. 

1-10) Create the Serial parent object: Follow steps 1 through 10 above.

11) Click to the Serial, then click to the lowest level of the serial tree. For example, if you have Volume, Issue, Number, then you would click to the Number where you want to load the .pdf(s).

12) Click the "Manage" tab, then click the tab for "PDF Management".

13) Click "Add a PDF".

14) If you choose to use the “Add a PDF” option, we recommend that you use the Full MODS edit form and within that form specifically the Related Item Part section of the form to describe the issue. The top-level Title element should be used for the serial title.

Note that the Title in this section of the form refers to the title of an issue and not the serial title. All of the elements in the section of this form will display in the Full Description of the issue with the label “Issue”, in the following order Title, Number, Caption.  The MODS detail@type value does not display to the public.

15) You can ignore MARCXML file. MARCXML lets you upload a MARCXML file and that will prepopulate the MODS forms. A library might have these if they are digitizing older public domain materials, where they look for rare items in the catalog, digitize, then export the MARC record from the catalog. You also could make a template MARC file to use if you are uploading a large set of material with many repeated fields that are identical on the whole set of items. MarcEdit will allow easy conversion of a MODS XML file to a MARC XML file. So, to make the MARC XML template, you could use Islandora to fill out repetitive MODS fields, then click to "Manage" then "Datastreams" then "download" MODS, then on your desktop use Notepad to remove fields specific to that item, then use MarcEdit to convert MODS XML to MARC XML, then use the MARC XML template to autofill the repeated fields.

16) Fill out the MODS form and way at the bottom click "Ingest". The MODS Simple Entry Form is pretty long, and the Full MODS Form is even longer. Regarding what fields to fill out, it's good to make a checklist of fields and then fill those out for each pdf. So, maybe... Look at other Islandora sites https://falsc.libguides.com/FL-Islandora/Sites and see what fields show up in search results for a site and think that those are more important for someone using the site (FLVC can change these for your site, if you want to show or not show certain fields).

17) Click "Next".

18) Click "Choose File" and find the pic you would like to upload.

19) After you click "Ingest", you have created the PDF content model object.

Creation of a serial issue containing one PDF per article is similar to the above procedure, with the following exceptions:

  • The Full Description tab of the multi-PDF issue is generated from the parent intermediate object’s MODS file. (The Full Description tab of the single PDF issue is generated from the PDF object’s MODS file.
  • A table of contents derived from a combination of article-level metadata and sections created using the PDF Management table is displayed in the summary tab.
  • The PDF Management function allows you rearrange the order of PDFs and to create and edit table of contents sections.

1. From the serial title object, click on the node in the hierarchical tree display to which you want to attach the PDF. You will see a “No PDFs are currently associated” message.

2. Click on the Manage tab, and then on the PDF Management link.

3. At this point you can either click on “Add a PDF” to manually create MODS metadata or upload a MARCXML metadata file, or you can click on “Batch Import” to upload a .zip file containing one or more pairs of metadata and PDF files. You can load all articles for the entire issue in one batch.

Zip loading PDFs to Serial content model objects

  • Zip loading is only available for Serials in the context of zip loading several article PDFs into whatever the bottom most level of the Serial is. If you have article level PDFs for a Serial, then zip loading makes sense. However, if you have one big PDF with lots of articles all stuck together (ie. you have the entire issue as a single PDF), then you will have to load one at a time.

1-10) Create the Serial parent object: Follow steps 1 through 10 above.

11) Prepare all MODS metadata for your object. It is recommended to use the Excel to MODS Transformer to prepare the metadata, since this will ensure that metadata validates against the MODS schema and meets FLVC's local requirements.

12) Put all the MODS XML and all files, in a single folder. The name of this file should match the name of the corresponding XML. For example, the folder should hold document1.xml, document1.pdf, document2.xml, document2.pdf, etc. and no other files (ie. no XML without a pdf and no pdf without an XML file). Zip that folder to make a .zip file.

13) Click to the Serial, then click to the lowest level of the serial tree. For example, if you have Volume, Issue, Number, then you would click to the Number where you want to load the .pdf(s).

14) Click the "Manage" tab, then click the tab for "PDF Management".

15) This will take you to a "PDF Zip Batch Importer" screen. Upload your .zip file here and click "Import".

Offline batch ingest for the Serial content model

Offline batch ingest is not available for the Serial content model.

The quick "Add Intermediate" function

The "Add Intermediate" button allows you to quickly add nodes to your serials tree, especially if your serial has many nodes.

1. From the place in the hierarchy tree to which you'd like to add another node. For example, if your 1st level of hierarchy is "Year" you must be at the serial title level. If you wish to add a second level of hierarchy node, e.g., month, you must first click on the year to which you'd like to add a month.

2. Then click "Manage" and "Add Intermediate". You'll see a screen with a brief display in which the node type has been provided by Islandora. (Hint, if you see the wrong node Type being displayed you are in the wrong node.):

3. Fill in the appropriate Caption and Number for the node.

4. Click "Add". You'll remain in the "Add Intermediate" screen and will be able to create additional nodes at the same level (e.g., all months in a given year).

5. When you're finished adding new nodes simple close the pop-up.

You can then return to the tree and add PDFs to your new node(s).

Modifying the nodes/branches of the hierarchical tree display

The hierarchical tree display can be modified at any time after it has been created. You can “drag and drop” nodes/branches of the tree at any level from the “Intermediate Management” function. Any PDFs linked to the intermediate objects will move with them.

You can also modify the caption and number values at any time from this table, and the changes will be reflected both in the hierarchical tree display as well as in the MODS of the intermediate objects.

Editing a single PDF issue

Because the serials module accommodates both single PDF and multiple PDF issues, staff users need to do the following in order to edit a single PDF issue:

1. From the serial title hierarchical tree display, click on the intermediate object to which the PDF issue is linked. For staff users only (public users are taken directly to the PDF display) the intermediate object will be displayed, along with a title link to the PDF issue:

2. Click on the title link to view and edit the PDF object from the Manage tab:

Editing a Multi-PDF Issue

Table of contents viewed from the “PDF Management” link found under the Manage tab:

The PDF Management function displays a “drag and drop” table allows you to use the  symbol to drag articles and sections to reorder them.

  • The “Add a Section” link allows you to create section headings to better organize the table of contents. Section headings can be edited or deleted at any time.
  • The “Add a PDF” function allows you to manually create/upload additional article-level PDFs and their metadata.
  • The “Batch Import” function allows to upload a .zip file containing metadata and/or PDFs for one or more articles. You can package all metadata and PDFs for all articles in an entire issue into one .zip file and load them using this function.
  • To view/edit individual article PDF objects, click on the View tab, then on the title of the desired article.

Serial step-by-step Training Exercise.

Video

In order to upload the Video content model, you need to enable the collection to hold:

  • Islandora Video Content Model (islandora:sp_videoCModel)

Files for upload

The Islandora Video Content Model is used for single video files.

It accepts the following file types:

  MPEG-4 (.mp4) 
  QuickTime (.mov, .qt)
  M4V(Apple) (.m4v) 
  Audio Video Interleaved (.avi)
  Matroska Multimedia Container (.mkv)

Files must be less than 2048 MB (2 GB) if you upload them through the GUI. If you have a file larger than 2GB, contact help@flvc.org with "Islandora" in the subject line of your email.

How these look

Videos are currently displayed in FL-Islandora by JWPlayer.

Examples:

Technical Information/Datastreams

The following datastreams will be created:

RELS-EXT      Default Fedora relationship metadata
MODS MODS metadata record created during ingest
DC Dublin Core record
OBJ The original video file ingested
MP4 MP4 derivative created during ingest by ffmpeg and used by JWPlayer if no suitable video exists
MKV MKV derivative created during ingest by ffmpeg (disabled by default)
TN Thumbnail image pulled from a frame of the video by ffmpeg2theora

 

Uploading Video content model objects one-at-a-time through the web

To make the Video content model, you have to have a .mp4, .mov, .qt, .m4v, .avi, and .mkv file.

  1. Make sure the collection you are loading into can hold the "Islandora Video Content Model (islandora:sp_videoCModel)". (To check this, browse to the collection you will upload to, then click "Manage", then click "Collection", then on the left it will say "Manage collection policy" and if the box for "Islandora Video Content Model (islandora:sp_videoCModel)" is checked then you are good to go.)
  2. Browse to the collection into which you will upload the video. Click the "Manage" tab, then click "Add an object to this Collection".
  3. Choose the MODS Simple Entry form. (It's shorter than "Full MODS Form")
  4. You can ignore MARCXML file. MARCXML lets you upload a MARCXML file and that will prepopulate the MODS forms. A library might have these if they are digitizing older public domain materials, where they look for rare items in the catalog, digitize, then export the MARC record from the catalog. You also could make a template MARC file to use if you are uploading a large set of material with many repeated fields that are identical on the whole set of items. MarcEdit will allow easy conversion of a MODS XML file to a MARC XML file. So, to make the MARC XML template, you could use Islandora to fill out repetitive MODS fields, then click to "Manage" then "Datastreams" then "download" MODS, then on your desktop use Notepad to remove fields specific to that item, then use MarcEdit to convert MODS XML to MARC XML, then use the MARC XML template to autofill the repeated fields.
  5. If not using MARCXML, fill out the MODS form and click "Ingest". The MODS Simple Entry Form is long, and the Full MODS Form is even longer. Regarding what fields to fill out, it's good to make a checklist of fields and then fill those out for each PDF. You may look at other Islandora sites (ex. https://falsc.libguides.com/FL-Islandora/Sites) and see what fields show up in search results for a site and think that those are more important for someone using the site (FLVC can change these for your site if you want to show or not show certain fields).
  6. Click "Next".
  7. Click "Choose File" and find the video file you would like to upload.
  8. After you click "Ingest", you have created the Video content model object.

Zip loading Video content model objects

Note: As of April 2019, there is a new, optional, feature that sends uploaded .zip files of Video objects to Offline Batch Ingest. This allows users to continue working in the GUI after the .zip file is uploaded, and queues the videos for loading. Loads can then be tracked via your institution's Offline Batch Ingest admin GUI.
  1. Make sure the collection you are loading into can hold the "Islandora Video Content Model (islandora:sp_videoCModel)". (To check this, browse to the collection you will upload to, then click "Manage", then click "Collection", then on the left it will say "Manage collection policy" and if the box for "Islandora Video Content Model (islandora:sp_videoCModel)" is checked then you are good to go.)
  2. Prepare all MODS metadata for your videos. It is recommended to use the Excel to MODS Transformer to prepare the metadata, since this will ensure that metadata validates against the MODS schema and meets FLVC's local requirements.
  3. Put all the MODS XML and all files, in a single folder. The name of the video file should match the name of the corresponding XML. For example, the folder should hold video1.xml, video1.mp4, video2.xml, video2.avi, etc. and no other files (ie. no XML without a file and no mp4/mov/qt/m4v/avi/mkv without an XML file).
  4. Zip that folder to make a .zip file.
  5. Browse to the collection into which you will upload the videos. Click the "Manage" tab, then click to the "Collection" tab, then click to "Batch Import Objects".
  6. Under the "Importer" drop-down, you should see "Zip File Importer" selected. If not, then choose "Zip File Importer".
  7. Under Zip Batch Importer, click to "Choose File" and upload the .zip file of MODS XML for your pics. Under "Content Model", select "Islandora Video Content Model (islandora:sp_videoCModel)". Then click "Import".
  8. This will load metadata and files for each Video content model object. Note: if your site is configured to send video .zip files to Offline Batch Ingest you will be able to track the progress of your video loads via your site's Offline Batch Ingest admin interface. Offline Batch Ingest validates the MODS file, so videos with invalid MODS files will not load.

Offline Batch Ingest for Video content model objects

Offline batch ingest is available for the Large Image content model.