Creating Content Objects

From FIG

Jump to: navigation, search
Navigation
NewFig1201.png
FL-Islandora Guides (FIG)
FL-Islandora Overview
User Interface
Permissions and users
Collection Creation and Management
Content models
Creating Content Objects
Metadata
Suppressing Objects From View
PALMM guidelines
Fl-Islandora and Mango
Site Administration
Workflow: From Spreadsheet to Islandora
Using Google Analytics with FL-Islandora
Collection Information Menu
A-I. FL-Islandora Glossary
A-II. Field Inventory

Contents

Creating Content Objects

A content object is any object that is not a collection, for example, a book, image or document.

There are three ways to create a new content object --

  1. online ingest,
  2. batch import (also called the “zip file importer”), and
  3. offline ingest.

Online Ingest

Basic workflow

1) Make sure that the collection you are uploading to can hold the kind of content you are uploading. To do this, look at Chapter 5 on Content models. At the beginning of each description of a content model, some content model names will be in bold. Those content models need to be enabled for the collection. To check that they are enabled, browse to the collection that you will upload to, and click "Manage". Look along the left hand side of the screen for a link to "Manage collection policy", click to that and ensure that the check boxes are checked off for the content models you will need to use.

2) Browse to the collection that the object will be in, and click "Manage". You will be on the Overview screen by default. Click “+ Add an object to this collection”.

3) You will be prompted to select the content model for the new object from a pull-down list of all content models allowed in that collection. Select one content model, then click “Next”.

4) You will be presented with radio buttons for the metadata forms to choose from. Generally, either "MODS Simple Entry" which is a shorter form, or "Full MODS Form" which is a longer form. Select one form, then click “Next”.

5) You will be presented with the option to upload an existing MARCXML record. If you have an existing MARCXML record (filetype “.xml”) for the object in a file on your hard drive or local network, you can find it and upload it here. It will be used to pre-populate the metadata form you selected in the previous step. If you don't have a MARCXML, just click “Next”, and you will be taken to a blank metadata form. This can be helpful if you have existing metadata, for example, a MARC XML file exported from a catalog record or another digital library platform. Note: You should validate the MARCXML file prior to loading, as Islandora does not perform MARCXML validation.

LoadMARCXML.png

6) Your selected metadata form will appear. It may be pre-populated with data from a MARCXML record or from a template used by your institution. Enter metadata for your new object and click “Ingest”.

7) What happens next depends upon the type of object you are creating. Instructions are given below for:

  • unitary Content Objects (PDF files and single images)
  • compound Content Objects
  • paged Content Objects (Books and Newspapers)

Unitary content objects

Unitary objects are complete in one datastream / one file. There may also be associated derivative files stored as datastreams, but there is only one primary file. Content models that support unitary objects are Basic Image, Large Image, PDF, Audio, Video and Binary Object. However, the Binary Object content model cannot be created through the .zip loader. Although the ingest process may vary slightly, all of these content types have essentially the same ingest workflow.

First, select the content model and create metadata as described above. You will then be provided with an upload form.

UploadImage.png

Click "Upload File", browse to the select the file on your desktop, and click the “Upload” button. When the file is uploaded, the “Upload” button changes to a “Remove” button you can click to delete the file if you made a mistake. Once the file is uploaded, click the “Ingest” button. The successfully ingested object will be displayed to you.

The Audio and Binary Object upload processes allow an extra step -- there is a prompt to optionally provide a thumbnail to be used in the search results, Summary and Full Description displays of the object. If a thumbnail is not uploaded, a default icon will display.

The PDF upload process allows an extra step -- there is an option to optionally provide a file of full text for indexing. Full text is extracted from PDF files and stored as a datastream by the system during the upload process by default. However, in some cases an institution may have already created better full text than what can be automatically extracted, for example, by off-shore keying. If the operator uploads a file of full text (which must have the “.txt” file extension) that will be stored as a datastream instead of automatically extracted text.

Compound content objects

Compound objects are sets of two or more related objects of any type that always display together. They are implemented as a parent object following the Compound Object content model consisting of metadata only, and associated child objects following any content model(s). Creating a compound object is a two-step process.

First, ingest the child objects as they would normally be ingested. Second, create a parent object using the Islandora Compound Object Content Model, and associate the children with the parent from within the parent record.
Although it’s possible to associate a child record with a parent from within the child object it is not recommended and can cause problems.

To create the parent compound object, navigate to the collection the object will belong to and click the "Manage" tab. The Overview screen will appear by default. Click “+ Add an object to this collection”.

Select the Compound Object content model, and click “Next”. Provide complete metadata describing the compound object and click “Ingest”. When ingest is complete the metadata will display.

Click the "Manage" tab then click “Compound”. The form for associating child objects appears.

AssociateCompoundForm.png

Child Object Pid/Label: Type the title or PID of the first child object to be part of the compound object. The data entry field will autocomplete, so you should be able to select the desired object after entering just a few characters. Click “Submit”. Repeat for every child object.

After creating a compound object, you may want to reorder the children so that they display in the order you want. To do this, navigate to the compound object parent, click the "Manage" tab, then click “Compound”. The compound object form will now include a block allowing you to remove child objects, and a link to reorder the child objects.

ReorderCompoundCollapsed.png

Click the “REORDER” link and a list of child objects will display.

ReorderCompoundOpened.png

Drag the crosses in front of the object titles to put them in the order you want, then click “Save Changes”.

Paged content objects

Paged objects are hierarchically organized content that consists of individual pages at the lowest level, like books and newspapers. These objects make use of multiple content models. At the highest level, the Islandora Internet Archive Book Content Model and Islandora Newspaper Content Model are, like the Islandora Compound Object Content Model, parent objects consisting of metadata only. Books are created by adding pages to the parent. Newspapers are created by adding issues (metadata only) to the parent and then adding pages to the issues. With release 7.x-1.6 of Islandora there is the new ability to upload PDF objects to book parents or newspaper issues from which individual page image files can be extracted. In both cases the end result is a book or newspaper issue with individual page images. For more details, see Extracting page images from PDFs

Books

To create a book, navigate to the collection that the book will be part of. Click the "Manage" tab. The Overview screen will appear by default. Click “+ Add an object to this collection”. Select the Islandora Internet Archive Book Content Model.

Complete the metadata for the book and click “Ingest”. When ingest is complete, the Internet Archive BookReader view will appear, showing a book with a title but no content.

BookReaderNoPages.png


To add pages, click the "Manage" tab, then click “Book”. The resulting screen will offer two options, “+ Add page” and “+ Add zipped pages”.

ManageBook.png

To add pages one at a time, click “+Add Page”. Find the page file (TIFF or JP2) and upload it. Click the “Ingest” button. When ingest is complete, you will see the single page display.

SinglePageDisplay.png


Note that the page view has a "Manage" tab, but adding pages is a function of the Book, not the Page. To add another page you must return to the book level by clicking “Return to Book View”. On the Book View click the "Manage" tab, then click “Book”. Now you can repeat the steps from clicking “+ Add Page” to add another page.

Uploading pages one by one can be tedious, so there is also a function to add a number of pages bundled together in a single zip file. To use this, at the Book level, click the "Manage" tab, then click “Book”, then click “+ Add Zipped Pages”.

Note: As of April 2019, there is a new, optional, feature that sends uploaded .zip files of Book pages and Newspaper Issue pages to Offline Batch Ingest. This allows users to continue working in the GUI after the .zip file is uploaded, and queues the pages for loading. Loads can then be tracked via your institution's Offline Batch Ingest admin GUI.

AddZippedPages.png

Language: Select the language the text is written in from the pull-down.

Last sequence number: If there are no pages already ingested into the book, this number will default to “0”, otherwise it defaults to the count of pages already ingested into the book. Page numbering will start after the page number entered here. In this example, the first page ingested from the zipped page file will be numbered “2”.

Compressed images file: Locate the zip file of pages and upload it. Click “Add files to book”.

When the ingest is complete, you will get an updated version of the same screen. Any errors encountered while loading the pages will appear at the top. The “Last sequence number” field will be set to the count of the number of pages ingested into the book.

Newspapers

Newspapers make use of three Content Models: Newspaper (title), Issue, and Page. Title-level newspaper objects must be created manually via the User Interface. After title-level objects are created issues and pages can be loaded

Creating a newspaper title record

To create a new newspaper, navigate to the collection the newspaper will be part of and click the "Manage" tab. The Overview screen will appear by default. Click “+ Add an object to this collection”. Select the Newspaper Content Model. Select a metadata edit form and create metadata at the title level. Note that “Type of resource” should be “text”, and “Issuance” should be “serial”.

Creating an issue record

Newspaper issue records can be created either manually via the User Interface, or by loading an issue package via Offline Batch Ingest.

Creating an issue via the User Interface

To add an issue, go to the newspaper title record. (This will be your default location after creating a newspaper object. Click the "Manage" tab and click “Add issue”. Select a metadata form and fill it out.

Title: Include the date or enumeration of the issue. E.g. if the newspaper title is “The Globe” the issue title should be “The Globe, January 1, 1882” or “The Globe, v.1 no.2”.

Type of resource: text

Issuance: single unit

Date Issued: yyyy-mm-dd. It is critical to enter Date Issued in this format to get the correct newspaper tree display.

Adding pages to a newspaper issue

Pages can be added to an issue either one page at a time, or by loading a .zip file containing page images for an entire issue.

Note: As of April 2019, there is a new, optional, feature that sends uploaded .zip files of Book pages and Newspaper Issue pages to Offline Batch Ingest. This allows users to continue working in the GUI after the .zip file is uploaded, and queues the pages for loading. Loads can then be tracked via your institution's Offline Batch Ingest admin GUI.
  • To add a single page, go to the issue level object.
    • Click the "Manage" tab and “Add page”.
    • Upload the JPG, TIFF or JP2 page image and click “Submit”.
  • To add a .zip file of all pages for a single issue, go to the issue level object.
    • Click the "Manage" tab and then click the "Issue" button.
    • Click "+ Add Zipped Pages" and "Choose a file" to select a .zip file of page images for that issue.
    • Click "Add files".

Serial Content Objects

Batch Import (Zip File Importer)

The zip file importer can be used to ingest a batch of objects at once. It can be used to load:

  • MODS metadata and content files
  • Content files without metadata
  • MODS metadata without content files

Objects ingested via the zip file importer have the operator name of the submitting operator as the owning user, and will default to “Active” or “Inactive” state accordingly.

NOTE: For loading content into the Binary Object Content Model you must use the Binary Object Zip Importer instead of the ZIP File Importer.

Preparing the zip file

NOTE: We recommend that you use open source software such as 7-zip to create your Zip files for Islandora instead of the proprietary Microsoft NTFS compression available from a Windows context menu/right click.

The objects to be loaded must be zipped together into a single file of filetype .zip. All objects in the zip file must use the same content model and be intended for the same collection.

Files to be associated with each other (e.g. MODS metadata with content files) are matched by filename, so they must have the same filename and different filetype extensions. The filetype extension for MODS files must be .xml and the filetype extension for full text to be indexed must be .txt.

For example, Large Image objects with metadata might be named:
   file1.jp2
   file1.xml
   file2.jp2
   file2.xml 

PDF files with metadata and full text for indexing might be named:

   1443587.pdf
   1443587.xml
   1443587.txt
   1439_2.pdf
   1439_2.xml
   1439_2.txt


A single zip file can contain pairs of metadata and content files, as well as standalone metadata and/or standalone content files. A zip file containing:

   program_1.pdf
   program_1.xml
   4433256.pdf
   solo.xml

will create 3 objects: one PDF with metadata, one standalone PDF, and one standalone MODS file.

Because the Zip Importer will ingest metadata without content and content without metadata, you should take care that metadata and corresponding content files have matching names -- a typo in the filename can cause the two files to be ingested separately.

Metadata Requirements

  • The MODS file provided should be valid MODS. FLVC strongly recommends validation of MODS files prior to loading with the Zip Importer, as the Zip Importer does not perform validation against the MODS schema during loading. (The FLVC ExceltoMODS Transformer, http://exceltomods.flvc.org, validates against the MODS schema during transformation of Excel spreadsheets into MODS, and so MODS prepared in this way has been validated.)
  • Minimum requirements are that it must include:
    • a unique IID in the element <identifier type="IID">
    • a valid owning institution code in the element <extension> <flvc:flvc> <flvc:owningInstitution>
    • a title in the element <titleInfo><title>
  • Submitting Institution (<submittingInstitution>) and Other Logo (<otherLogo>) can also be put in the <flvc> extension.
  • The namespace for the <flvc> extension must be included in the MODS header information:
    • xmlns:flvc="info:flvc/manifest/v1"
  • The example below shows a valid minimal MODS record for the Zip File Importer:
<?xml version="1.0" encoding="UTF-8"?>
<mods xmlns="http://www.loc.gov/mods/v3"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xmlns:flvc="info:flvc/manifest/v1"   
     xmlns:xlink="http://www.w3.org/1999/xlink”
     xsi:schemaLocation="http://www.loc.gov/mods/v3
     http://www.loc.gov/standards/mods/v3/mods-3-4.xsd”    
     version="3.4">
    <extension>
         <flvc:flvc>
              <flvc:owningInstitution>FSU</flvc:owningInstitution>
         </flvc:flvc>
    </extension>
    <titleInfo>     
         <title>Strawberries</title>
    </titleInfo>  
    <identifier type="IID">FS3518756</identifier>
</mods>

  • NOTE the supplied MODS record must NOT use namespace prefixes on the MODS elements. I.e., do NOT use the namespace definition mods:xmlns=”....” and do NOT create a record like the below:
<mods xmlns="http://www.loc.gov/mods/v3" mods:xmlns=”http://www.loc.gov/mods/v3”>
 <mods:titleInfo>
   <mods:title>This is an example of a bad MODS record.</mods:title>
 </mods:titleInfo>

etc.

If any of these requirements are not met, the supplied metadata will be ignored, and the Zip File Importer will create a skeleton MODS record that contains only the filename as title:

<mods xmlns="http://www.loc.gov/mods/v3">
 <titleInfo>
   <title>[filename]</title>
 </titleInfo>
</mods>

The skeleton record will not be sent to Mango but it will display in Islandora. The first time an operator tries to update the skeleton record online, the MODS Forms will force the creation of required fields.

Doing the import

Navigate to the collection to which the objects should be added. Click "Manage". This should default to the “Overview” screen.

Click "Collection" to get the collection management screen. Click "+ Batch import objects".

Take the default importer, “ZIP File Importer”. Click "Next".

NOTE: Although the Binary Object Content Model appears when you select the ZIP File Importer, to batch load Binary Objects you must use the Binary Object Zip Importer to batch load Binary Objects (the ZIP File Importer will not load the content files).

Fill out the form. Find the zip file to import. Click the content model the import should use.

Select the default namespace, which should be correct. Click "Import".

Importing content without metadata

Content files can be imported without metadata. Any content file in a zip file that has no matching metadata file will be ingested and a minimal MODS record will be created with only the <titleInfo><title> element supplied from the filename of the file.

E.g. if a standalone file named “Flavorcrest.jpg” is imported, this MODS record will be created:

<mods xmlns="http://www.loc.gov/mods/v3">
  <titleInfo>
    <title>Flavorcrest</title>
  </titleInfo>
</mods>

Because the metadata has no IID identifier or owning institution code, these required fields will have to be added the first time the record is edited online.

This is a useful feature for institutions that want to load quantities of objects and then add metadata interactively online.

Importing metadata without content

Metadata files can be imported without corresponding content files. The importer will generate warning messages that derivative files could not be created, according to the content model associated with the import. These messages can be ignored.

Viewing results

After the content of a zip file has been successfully imported, the operator will get a response screen with the message:

   Batch complete!  View/download simple results or see the watchdog log for details.

The “simple results” link provides a list of all objects ingested with their title and PID, and a link to the content in Islandora.

info: Ingested "Viking Motel Acquisition, June 1988" as islandora:1858. Link: islandora:1858. info: Ingested "Naésa zemlja" as islandora:1859. Link: islandora:1859. info: Ingested "Flavorcrest" as islandora:1860. Link: islandora:1860. info: Ingested "Peaches" as islandora:1861. Link: islandora:1861.

The “watchdog log” link provides a view of log messages associated with the import. The entire log can be also be viewed from the Administrative menu / Reports / Recent log messages.

Offline batch ingest

last updated 10/12/2018

Offline batch ingest provides an offline alternative to online ingest and online batch import via the FL-Islandora user interface. At this time six content models are supported by offline ingest: Basic Image, Large Image, PDF, Book, Newspaper Issues, and Video. This frees up your online connections to FL-Islandora via the user interface for other work, and extends FL-Islandora loading and processing capabilities by performing many load operations on the separate FL-Islandora load server.

  • With offline ingest, the content to be ingested into the system is FTP-ed to the FL-Islandora load server.
  • Each object submitted to offline batch ingest must be contained within a single package (directory) which must adhere to certain requirements. (See details below.)
  • A program on the FL-Islandora load server watches for new content and automatically moves it to an ingest queue when found. (Note that the ingest queue is shared by all FL-Islandora users.)
  • Then the offline ingest program loads content in the order in which it was submitted to the shared ingest queue.
  • Results from the load are posted to an offline batch ingest reporting interface that is unique to each FL-Islandora site, where load results for all submitted packages are recorded.


Basic Workflow

Prerequisites: a new user must request an FTP account to the FL-Islandora load servers (test and production). Accounts are issued to individual users from an institution, and are IP restricted. Please provide FLVC with a list of individuals who will be using offline batch ingest at your institution, along with their IP addresses. FLVC will create user accounts and also set up an offline batch ingest reporting user interface for your institution. The individual accounts/logins will provide you with access to only your institution's FTP directory on the FL-Islandora load server.

The offline batch ingest workflow is as follows:

  1. Create an Islandora package per the package requirements detailed below.
  2. Log into the offline ingest FTP/load server using your individual login. (The test server's hostname is “ftpes://tlhlxftp01-tst.flvc.org”. The production server's hostname is “ftpes://tlhlxftp01-prd.flvc.org”.) Note: we recommend that you use the FileZilla client, using port 21.
  3. Upload your packages into your institution's /incoming/ directory. All individual logins from your institution will share this /incoming directory.
  4. The offline batch ingest process checks all /incoming/ directories every 5 minutes and moves new packages into the /processing directory and queues them for loading.
  5. Packages are moved from your institution's /processing directory after they are processed for loading.
  6. Packages that load but encounter load warnings are moved into the /warnings/ directory for your review. (This step may be eliminated in future if users don’t find it to be useful, but during beta testing this could be very useful for FLVC troubleshooting.)
  7. Packages that fail to load will be moved to the /errors/ directory. You can retrieve your package from that directory and make corrections and then resubmit the package.
  8. Load results are recorded in a load database and made available for viewing in your site’s Ingest Reports interface. The URL to that interface is http://[your site root/code].admin.digital.flvc.org, for example: http://islandora-test.admin.digital.flvc.org is the URL to the Ingest Reports interface for the https://islandora-test.digital.flvc.org site, and http://fsu.admin.digital.flvc.org is the URL to the Ingest Reports interface for the FSU FL-Islandora production site. See details below.

Package requirements

Rules for creating packages for offline batch ingest:

  1. Each package (directory) must have the same name as the IID (item identifier) of the object. Allowable characters in the IID are: alphanumeric characters, hyphens, underscores. Note that spaces are not allowed.
  2. The package must contain a) metadata (a valid MODS file), b) a manifest file, and c) content file(s). The name of the MODS file must match the directory/folder name of the package. See examples below.
  3. If the package is for a Book, a METS file containing a structMap and fileSec must be supplied. A Table of Contents will be created from the METS structMap and fileSec information.
  4. If the package if for a Newspaper Issue, a METS file is optional. Without a METS file the load program will assemble pages in ASCII sort order, case sensitive.
  5. The MODS record file must have the same filename as the package and the filetype .xml. E.g. if the package name is “UF12345678” the MODS file must be named “UF12345678.xml”.
  6. The manifest must be named “manifest.xml”. (See below for manifest requirements.)

Creating a METS file

The METS Editor (SobekCM) can be downloaded and installed and used to create a METS file for your Book and Newspaper Issue packages.

Examples of Packages

The following examples of package structures would all be valid packages (assuming of course that all files within them are valid). Note that there is no naming requirements for content filenames, but pages of newspaper issues without METS files will load in ASCII sort order so that they load in correct page order, e.g., p001.jpg through p234.jpg, etc.:

A PDF

  • /UF12345678_00001/ (UF12345678_00001 is the directory or folder name)
    • manifest.xml
    • UF12345678_00001.xml (the MODS metadata file)
    • happy_trails.pdf

A Large Image

  • /GC_accession_1322/ (GC_accession_1322 is the directory name)
    • manifest.xml
    • GC_accession_1322.xml (the MODS metadata file)
    • fits_1322_1.jp2

A Book

  • /FA00000032/ (FA00000032 is the directory name)
    • manifest.xml
    • FA00000032.xml (the MODS metadata file)
    • mets.xml
    • cover1.jp2
    • cover2.jp2
    • p001.jp2
    • etc. (more pages)

A Newspaper Issue

  • /CF00004312_0001/ (CF00004312_0001 is the directory name)
    • manifest.xml
    • CF00004312_0001.xml (the MODS metadata file)
    • mets.xml <- Note that the METS file for a newspaper issue is optional
    • page01.jpg
    • page02.jpg
    • page40.jpg
    • etc. (more pages)

MODS requirements

  • The MODS record must validate against the MODS schema. Packages containing invalid MODS files will fail loading and will record validation errors.
  • The MODS record must NOT use namespace prefixes on the MODS elements.
    • Do NOT use the namespace definition mods:xmlns=”....” and do NOT create a record like the one below:
<mods xmlns="http://www.loc.gov/mods/v3" mods:xmlns=”http://www.loc.gov/mods/v3”>
    <mods:titleInfo>
   <mods:title>This is an example of a bad MODS record.</mods:title>
    </mods:titleInfo>
etc.
    • A correct MODS record will look like this:
<mods xmlns=”http://www.loc.gov/mods/v3”>
   <titleInfo>
     <title>This is an example of a good MODS record.</title>
   </titleInfo>
etc.
  • The MODS record should not include an <flvc> extension. Any sub-elements of the <flvc:flvc> tag will be ignored, removed from the MODS record, and replaced with an <flvc> extension block created by Offline Ingest.
  • The MODS record must contain exactly one identifier of type “IID”, and the identifier value must match the name of the package.
  • For newspaper issue packages the MODS must contain an <originInfo><dateIssued> element, with an encoding attribute of “w3cdtf” and the date expressed in the format YYYY-MM-DD. For example:
<originInfo>
  <dateIssued encoding=”w3cdtf”>1881-05-07</dateIssued>
 </originInfo>
  • Newspaper issue packages that do not contain this element and attribute will not be loaded.

Manifest requirements

The manifest is an XML file containing instructions to the batch ingest process.

An example of a valid manifest file for a Large Image:

<?xml version="1.0" encoding="UTF-8"?>
<manifest xmlns="info:flvc/manifest">
    <contentModel>islandora:sp_large_image_cmodel</contentModel>
    <owningUser>Sally Staff</owningUser>
    <collection>fau:photos</collection>
    <owningInstitution>FAU</owningInstitution>
</manifest>

Example of a Book object's manifest:

 <?xml version="1.0" encoding="UTF-8"?>
 <manifest xmlns="info:flvc/manifest">
    <contentModel>islandora:bookCModel</contentModel>
    <owningUser>Sally Staff</owningUser>
    <collection>ucf:floridabooks</collection>
    <owningInstitution>UCF</owningInstitution>
 </manifest>
 

Example of a Newspaper Issue object's manifest. Note that the collection element must contain the PID of the newspaper title object so that the loader can identify the newspaper title to which the issue is to be attached:

 <?xml version="1.0" encoding="UTF-8"?>
 <manifest xmlns="info:flvc/manifest">
    <contentModel>islandora:newspaperIssueCModel</contentModel>
    <owningUser>Jane Jones</owningUser>
    <collection>fscj:1234</collection>
    <owningInstitution>FSCJ</owningInstitution>
 </manifest>

The following elements are required in the manifest file:

  • collection (required, repeatable)
    • A collection which the object will be a member of. Multiple collections can be specified, but only one per <collection> element.
      • Collection names must be in PID format [namespace]:[name], e.g. fsu:football50
    • For newspaper issue packages, the collection element must contain the PID of the parent newspaper title object, e.g., usf:445, instead of the PID of an Islandora collection object. For example:
      • <collection>usf:445</collection>
  • contentModel (required, not repeatable)
    • The content model to be used for this object. Allowable content model names are:
      • islandora:bookCModel (for Books)
      • islandora:sp_basic_image (for Basic Images)
      • islandora:sp_large_image_cmodel (for Large Images)
      • islandora:sp_pdf (for PDFs)
      • islandora:newspaperIssueCModel (for newspaper issues)
      • islandora:sp_videoCModel (for videos)
  • owningInstitution (required, not repeatable)
    • The institution code of the institution owning the object. This will be validated against a list of institution codes known to the system, and inserted into the local FLVC extension of the MODS record.
  • owningUser (required, not repeatable)
    • The Islandora userid of the operator submitting the package for offline ingest. This will be validated against userids known to the system, and inserted into the local FLVC extension of the MODS record.


The following is a complete list of elements permitted in the manifest.xml file:

  • collection (required, repeatable)
    • A collection which the object will be a member of. Multiple collections can be specified, but only one per <collection> element.
      • Collection names must be in PID format [namespace]:[name], e.g. fsu:football50
    • For newspaper issue packages, the collection element must contain the PID of the parent newspaper title object, e.g., usf:445, instead of the PID of an Islandora collection object. For example:
      • <collection>usf:445</collection>
  • contentModel (required, not repeatable)
    • The content model to be used for this object. Allowable content model names are:
      • islandora:bookCModel (for Books)
      • islandora:sp_basic_image (for Basic Images)
      • islandora:sp_large_image_cmodel (for Large Images)
      • islandora:sp_pdf (for PDFs)
      • islandora:newspaperIssueCModel (for newspaper issues)
      • islandora:sp_videoCModel (for videos)
  • embargo (not required, not repeatable)
    • Information about an embargo to place on the ingested object, supplied in the attributes rangeName and endDate. For example:
      • <embargo rangeName=”FSU campus” endDate=”2014-07-01”>
    • If the embargo is indefinite (no end date) omit the endDate attribute.
  • identifier (not required, repeatable)
    • An identifier to be supplied to the metadata for the object. This function is not fully implemented at this time and the <identifier> element should not be used.
  • label (not required, not repeatable)
    • A label to be supplied to the object. This function is not fully implemented at this time and the <label> element should not be used.
  • otherLogo (not required, repeatable)
    • A logo to be displayed in addition to the owning institution’s logo, which displays by default. This will be inserted into the local FLVC extension of the MODS record.
  • owningInstitution (required, not repeatable)
    • The institution code of the institution owning the object. This will be validated against a list of institution codes known to the system, and inserted into the local FLVC extension of the MODS record.
  • owningUser (required, not repeatable)
    • The Islandora userid of the operator submitting the package for offline ingest. This will be validated against userids known to the system, and inserted into the local FLVC extension of the MODS record.
  • pageProgression (not required, not repeatable)
    • Use <pageProgression>rl</pageProgression> if the pages in a book are read right to left, as with Hebrew. Omit otherwise.
  • submittingInstitution (not required, not repeatable)
    • The institution code of the institution submitting the object for offline ingest. If not provided in the manifest, this will default to the same as the owning institution.

Package submission

To submit packages for loading via the offline batch ingest process:

  • Log into the test FTP server using your individual FTP server login. (The test FTP server’s IP address is islandload-tst.flvc.org, and all packages submitted there will load into your institution’s test site.)
  • Upload your packages into the /incoming directory for your site. (Your login will take you directly to your institution’s FTP directory.)

Viewing results

To view the results of your load, point a browser at your site’s Ingest Reports interface. The URL will be: [institution’s islandora site code].admin.digital.flvc.org, e.g., https://islandora-test.admin.digital.flvc.org.

You will see a page that lists all materials loaded into your site by offline batch ingest or the DigiTool migration loader program.

An example of a display:

IngestReport.png

You can filter the results list by date, load status, package name/ID, title, collection, or content type (content model).

By clicking on the Status link you’ll see the full load report that includes a direct link to the Islandora object, if the object was loaded. Otherwise you’ll see an error report and can expect that the referenced package has been moved to the /errors directory in your site’s FTP space.

In the upper right-hand corner of the Ingest Report page is a CSV download button that will download the search results.

Interpreting results

  • The green "success" status means that your package was successfully loaded. Click on the "success" status link for details of the load and links to the loaded object.
  • The red "error" status means that your package was not loaded. Click on the "error" status link for details about the problem. To resolve errors you must correct the problem and re-upload the package to the /incoming directory for re-processing. The two most common errors are:
    • That the package name, MODS file name and <IID> element in the MODS file are not identical.
    • That an IID is not unique. (In FL-Islandora the MODS <IID> element must be unique.) This means that there is an object on your site that has the same IID as the object you have submitted for loading. You must determine which IID is correct and should be retained.
  • The yellow "warning" status means that your package was loaded, but there were anomalies in the package that you might want to be aware of. It is up to you to determine if you want to delete the loaded package and reload after correcting the anomalies.


During the beta testing phase we encourage your feedback on the Ingest Reports interface.

Dealing with Errors

All packages that fail to load will be moved to your site’s /errors directory, in alphabetically coded sub-directories. You can download the package from there, correct it locally, and can resubmit it, or you can delete the problem package.


  • If you get the following error: RestClient::RequestTimeout Request Timeout
  • That means the server was restarted while the package was processing. This error is caused by the server restart, and the package may be perfectly fine. Move the package back to /incoming/ using your FTP server login and client.

FL-Islandora GUI to Offline Batch Ingest (book and newspaper issue pages, videos)

added 4/8/2019 LTM

As of April 8, 2019, FL-Islandora has added three new "GUI to Offline Batch Ingest" features that allow users to upload content via the FL-Islandora GUI for loading via Offline Batch Ingest. These features are:

  • Loading of .zip files of Book pages and loading of .zip files of Newspaper pages
  • Using the ZIP Loader to load one or more Video .zip files containing a Video file and its associated MODS metadata file.

These features are configurable, i.e., the can be enabled by individual FL-Islandora site.

Overview

How does GUI to Offline Batch Ingest work?

To a large extent these new features are transparent to users, because the initial steps to either add a .zip file of Book pages or a .zip file of Newspaper Issue pages, or a .zip file containing one or more video files and their associated MODS files remain the same. The differences appear after the .zip files are uploaded:

  • After uploading the .zip file using one of the current methods, the new code (if enabled for your site) creates an Offline Batch Ingest package from the .zip file and
  • moves the package to your site's Offline Batch Ingest load queue for batch loading.
  • The GUI provides a link to your site's Offline Batch Ingest administrative interface (http://site code.admin.flvc.org) where you can track the progress of the load.
  • Packages that have been successfully transferred are noted as Status "queued". After processing you will see the regular "success", "warning" or "error" status.

An example of loading a .zip file of Book pages via the GUI to Offline Batch Ingest process

1. As usual, first create a book title object and edit its metadata.

2. To add a .zip file of pages, click Manage -> Book -> +Add zipped pages from within the parent Book object. You can load a .zip file of pages to a newly created Book parent object, or you can add pages to an existing Book parent object with existing book pages. Pages will be added to the end of the book.

3. Upload the .zip file of pages, and click "Add files"

Book pages zip.png


4. With the new feature your .zip file will upload and be passed to Offline Batch Ingest, and you'll receive a message that indicates that your pages will be loaded via offline batch ingest: Sent to offline batch ingest.png


5. You'll see in the Offline Batch Ingest admin GUI that your package of pages is queued for loading. Note that the "title" of the load will be the IID of the book object to which pages are being added, along with the date and timestamp of the load (not the title of the book):

Admin queued.png


6. Once the pages load you'll see a "success" status and details about the load, including a link to the book parent object and a list of page PIDs and links:

Success.png


Loading .zip files of video objects

Please see ZIP loading Video Content Model Objectsfor instructions on requirements for creating video objects. Once the .zip file of video objects is uploaded you will see the same messages and links to your site's Offline Batch Ingest admin GUI as displayed above.

Step-by-step Instructions

Collection content model: Step-by-step

Creating a Collection through the web

1) Make sure the collection you are creating a new Collection in can hold the "Islandora Collection Content Model (islandora:collectionCModel)". (To check this, browse to the collection you will create a collection in, then click "Manage", then click "Collection", then on the left it will say "Manage collection policy" and if the box for "Islandora Collection Content Model (islandora:collectionCModel)" is checked then you are good to go.)

2) Browse to the collection you will create your new Collection in. Click the "Manage" tab, then click "Add an object to this Collection".

3) Under "Collection PID", enter a PID for your new collection. The Collection's PID has to start with your institution's namespace. The namespace is the part of your site's URL that comes before ".digital.flvc.org". (For example, https://fsu.digital.flvc.org has the namespace fsu . For example, https://ucf.digital.flvc.org has the namespace ucf .) The namespace has to be lowercase. If you enter a wrong namespace, then you get an error message on the very last screen. If you don't enter a "Collection PID" then Islandora will automatically assign one, but Islandora will assign a random number, and that's bad for search engine optimization.

4) Uncheck the box for "Inherit collection policy". This opens up a bunch of check box options. Pick the ones for the content that you plan to upload into this new collection. (You can go back and change this setting later.)

5) Click "Next".

6) You can ignore MARCXML file. Click "Next" without doing anything on the MARCXML screen.

7) Enter a "Collection Title". This will show up to people browsing the site. You can change it later.

8) Click "Ingest".

PDF and Book

PDF vs Book comparison

Use this comparison tearsheet to help choose which to use: PDF content model vs 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 pages, 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 pics 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. This was resource intensive, and for that reason the ability to upload PDFs is disabled on all FL-Islandora sites.
  • Stores the original pic that you uploaded for each page. It shows a smaller file web file in the page-flipper display, but the original pic is in Islandora.
  • Example Books:
  • To upload like this, you start with a set of .tiff / .tif / .jpeg / .jpg / .jp2 pics. Islandora runs OCR, and so the text will be searchable. The quality varies from book to book, and sometimes the text is almost perfect, sometimes it's gobbledygook.

PDF content model:

  • When users look at the PDF object, then they see an in-browser display of the PDF. This is something that's part of the browser, and not part of Islandora, so might not work on some browsers - for example, if the browser is pretty old or maybe it's a phone or tablet or doesn't have Adobe Acrobat Reader built in.
  • 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.

PDF content model: Step-by-step

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 you will upload the pic into. 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", but definitely not short.)

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) 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://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). 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. To see what's coming in Encore, you can run searches at http://discover.falsc.org/ and then click to the "Images" tab to see digital collections. The way those look is extremely likely to change between now and go-live for Encore.

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 ( 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 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.

4) Browse to the collection you will upload the pdfs into. 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 pics. Under "Content Model", select "Islandora PDF Content Model (islandora:sp_pdf)". Then click "Import".

7) 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. For instructions, see https://fig.wiki.flvc.org/wiki/index.php/Creating_Content_Objects#Offline_batch_ingest .

Book content model: Step-by-step

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

  • Secret step 1 is always to pick a content model. Before you begin, look over the notes for the Book content model posted at https://fig.wiki.flvc.org/wiki/index.php/Content_models#Books , and look at the example Book content model at http://fsu.digital.flvc.org/islandora/object/fsu:20702 to make sure that's what you want your material to look like.
  • For Book content model objects, you need a pic of each page to upload. Each page pic 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 you will upload the book into. 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", but definitely not short.)

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) 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. extra info). Regarding what fields to fill out, it's good to make a checklist of fields and then fill those out for each Book. So, maybe... Look at other Islandora sites 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). 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. To see what's coming in Encore, you can run searches at http://discover.falsc.org/ and then click to the "Images" tab to see digital collections. The way those look is extremely likely to change between now and go-live for Encore.

6) After you click "Ingest", you have created the Book. Now you have to add the Pages.

7) Prep the pics of pages on your computer. (Each pic 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 you will upload the Books into. 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.

7) For each Book:

a) Click to the Book, then click to the "Manage" tab, click to the "Manage" tab, then to "Book", then to "Add Zipped Pages".

b) Click "Browse" and find your .zip file of pages, then click to "Upload" it, and click to "Add files".

c) 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. For instructions, see https://fig.wiki.flvc.org/wiki/index.php/Creating_Content_Objects#Offline_batch_ingest .

FLVC prefers you 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 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.

Newspaper and Serial

Newspaper vs Serial Comparison

Use this comparison tearsheet to help choose which to use: Newspaper content model vs Serial content model

Newspaper content model:

  • Newspaper Issues have to have a date issued.
  • 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, then displays all newspaper issues for the selected month.
  • Newspaper issues are stored as pics 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 Newspaper Issue, and Islandora will extract the images from the PDF. This was resource intensive, and for that reason FLVC has the ability to upload PDFs disabled on all FL-Islandora sites.
  • Supports metadata at the Newspaper Issue or top level Newspaper parent object only. Does not support article level metadata.
  • Example Newspapers:
  • To upload like this, you start with a set of .tif / .jpeg / .jp2 pics. Islandora runs OCR, and so the text will be searchable. The quality varies from newspaper to newspaper, and sometimes the text is almost perfect, 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 metadata, and issue level metadata, 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.

Newspaper content model: Step-by-step

Uploading Newspapers through the web

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 you will upload the newspaper into. 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", but definitely not short.)

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) 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. extra info). Regarding what fields to fill out, it's good to make a checklist of fields and then fill those out for the Newspaper. So, maybe... Look at other Islandora sites 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). 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. To see what's coming in Encore, you can run searches at http://discover.falsc.org/ and then click to the "Images" tab to see digital collections. The way those look is extremely likely to change between now and go-live for Encore.

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”.
  • For Upload document: Find the thumbnail you want to use and upload it. (Recommended size is 200 x 200.)

Create the Newspaper Issue

7) Click to the Newspaper parent object that you want to create a Newspaper Issue inside of.

8) Click the "Manage" tab, then click to "Add Issue".

9) 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.

10) 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

11) After you click "Ingest", you have created the Newspaper Issue. Now you have to add the Pages.

12) Prep the pics 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.

13) Browse to the Newspaper Issue that you want to add pages to, click to the "Manage" tab, then click to the "Issue" tab.

14) Click to "Add Zipped Pages".

15) Click "Browse" and find your .zip file of pages, then click to "Upload" it, and click to "Add files".

16) 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 is NOT available for 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. For instructions, see https://fig.wiki.flvc.org/wiki/index.php/Creating_Content_Objects#Offline_batch_ingest .

1 - 5) Create the Newspaper parent object through the GUI.

6) 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.

Serial content model: Step-by-step

Create the Serial parent object

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 FLVC to go on screensharing 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 you will upload the book into. Click the "Manage" tab, then click "Add an object to this Collection".

4) Choose the MODS Simple Entry form. (It's shorter than "Full MODS Form", but definitely not short.)

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) Fill out the MODS form and way at the bottom click "Next". For this particular item (the top level Serial), consider filling out only the Title and IID. You can go back and edit metadata, but you have to build out the structure of the Serial on the next step and you cannot edit that later. So, spend the time on building that out, and then come back to the metadata later. The MODS Simple Entry Form is pretty long, and the Full MODS Form is even longer. extra info). Regarding what fields to fill out, it's good to make a checklist of fields and then fill those out for the Newspaper. So, maybe... Look at other Islandora sites 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). 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. To see what's coming in Encore, you can run searches at http://discover.falsc.org/ and then click to the "Images" tab to see digital collections. The way those look is extremely likely to change between now and go-live for Encore.

7) After you click through the MODS and click "Next", you will see a menu reading "Serial Level Configuration".

Serial can hold levels of something 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.

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.

You cannot go back and edit these hierarchical levels later. Refer to your pen and paper sketch of what the serial should look like, and verify that the accordion levels you want are the same as the accordion levels you entered in Islandora.

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

8) This takes you to a "Create Intermediate Objects" screen. Create only 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. You can go back and edit this later. Click "Ingest".

Create the Serial issues/numbers/volumes

Now you need to upload an issue to the Serial. (These instructions use the word "issue" to mean basically one thing - ie. one publication within the bigger serial.) You can have one big pdf with the whole issue. Or you can have one pdf for each article.

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 through the web

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) Choose the MODS Simple Entry form. (It's shorter than "Full MODS Form", but definitely not short.)

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://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). 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. To see what's coming in Encore, you can run searches at http://discover.falsc.org/ and then click to the "Images" tab to see digital collections. The way those look is extremely likely to change between now and go-live for Encore.

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.

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. So, if you have article level PDFs for a Serial, then zip loading makes sense. But, 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 ( 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.

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 is NOT available for the Serial content model

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

Basic Image content model: Step-by-step

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

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 you will upload the pic into. 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", but definitely not short.)

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) 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. extra info). Regarding what fields to fill out, it's good to make a checklist of fields and then fill those out for each pic. So, maybe... Look at other Islandora sites 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). 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. To see what's coming in Encore, you can run searches at http://discover.falsc.org/ and then click to the "Images" tab to see digital collections. The way those look is extremely likely to change between now and go-live for Encore.

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 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://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 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 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). Zip that folder to make a .zip file.

4) 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".

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 pics. Under "Content Model", select "Islandora Basic Image Content Model (islandora:sp_basic_image)". Then click "Import".

7) This will load metadata and files for each Basic Image object.

Offline Batch Ingest for Basic Image objects

Offline batch ingest is available for the Basic Image content model. For instructions, see https://fig.wiki.flvc.org/wiki/index.php/Creating_Content_Objects#Offline_batch_ingest .

Large Image content model: Step-by-step

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

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 you will upload the pic into. 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", but definitely not short.)

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) 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 pic. So, maybe... Look at other Islandora sites 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). 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. To see what's coming in Encore, you can run searches at http://discover.falsc.org/ and then click to the "Images" tab to see digital collections. The way those look is extremely likely to change between now and go-live for Encore.

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 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://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 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 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). Zip that folder to make a .zip file.

4) 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".

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 pics. Under "Content Model", select "Islandora Large Image Content Model (islandora:sp_large_image_cmodel)". Then click "Import".

7) 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. For instructions, see https://fig.wiki.flvc.org/wiki/index.php/Creating_Content_Objects#Offline_batch_ingest .

Audio content model: Step-by-step

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

  • Secret step 1 is always to pick a content model. Before you begin, look over the notes for the Audio content model posted at https://fig.wiki.flvc.org/wiki/index.php/Content_models#Audio , and look at the example Audio content model objects at https://fau.digital.flvc.org/islandora/object/fau:pearlcity to make sure that's what you want your material to look like.
  • To make the Audio content model, you have to have a .wav or .mp3 file to start with. 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, Audacity to create an .mp3 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 you will upload the audio into. 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", but definitely not short.)

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) 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. extra info). Regarding what fields to fill out, it's good to make a checklist of fields and then fill those out for each Audio object. So, maybe... Look at other Islandora sites 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). 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. To see what's coming in Encore, you can run searches at http://discover.falsc.org/ and then click to the "Images" tab to see digital collections. The way those look is extremely likely to change between now and go-live for Encore.

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 a pic 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 pic 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:

View.jpg

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

  • Secret step 1 is always to pick a content model. Before you begin, look over the notes for the Audio content model posted at https://fig.wiki.flvc.org/wiki/index.php/Content_models#Audio , and look at the example Audio content model objects at https://fau.digital.flvc.org/islandora/object/fau:pearlcity to make sure that's what you want your material to look like.
  • To make the Audio content model, you have to have a .wav or .mp3 file to start with. 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, Audacity to create an .mp3 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) 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 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 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). Zip that folder to make a .zip file.

4) Browse to the collection you will upload the Audio files into. 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 audio files. Under "Content Model", select "Islandora Audio Content Model (islandora:sp-audioCModel)". Then click "Import".

7) This will load metadata and files for each Audio object.

8) Optional extra step: Batch load thumbnail images for audio recordings

The default thumbnail will look like this:

View.jpg

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

  • 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 . Recommended size of each thumbnail is 200 x 200.

Offline Batch Ingest is NOT available for Audio objects

Offline Batch Ingest is not available for Audio objects

Video content model: Step-by-step

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

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 you will upload the video into. 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", but definitely not short.)

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) 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. extra info). Regarding what fields to fill out, it's good to make a checklist of fields and then fill those out for each pic. So, maybe... Look at other Islandora sites 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). 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. To see what's coming in Encore, you can run searches at http://discover.falsc.org/ and then click to the "Images" tab to see digital collections. The way those look is extremely likely to change between now and go-live for Encore.

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 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 ( 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 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 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). Zip that folder to make a .zip file.

4) 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".

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 pics. Under "Content Model", select "Islandora Video Content Model (islandora:sp_videoCModel)". Then click "Import".

7) 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 is for Video content model objects

Offline batch ingest is available for the Large Image content model. For instructions, see https://fig.wiki.flvc.org/wiki/index.php/Creating_Content_Objects#Offline_batch_ingest .

Binary Object content model: Step-by-step

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

  • Secret step 1 is always to pick a content model. Before you begin, look over the notes for the Binary Object content model posted at https://fig.wiki.flvc.org/wiki/index.php/Content_models#Binary_Object , and upload a sample Binary Object content model object to your test site to make sure that's what you want your material to look like.
  • 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 you will upload the pic into. 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", but definitely not short.)

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) 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 item. So, maybe... Look at other Islandora sites 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). 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. To see what's coming in Encore, you can run searches at http://discover.falsc.org/ and then click to the "Images" tab to see digital collections. The way those look is extremely likely to change between now and go-live for Encore.

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 Binary Object content model object.

Zip loading is NOT available for Binary Object content model objects

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

Offline Batch Ingest is NOT available for Binary Object content model objects

Compound Object content model: Step-by-step

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

  • Secret step 1 is always to pick a content model. Before you begin, look over the notes for the Compound Object content model posted at https://fig.wiki.flvc.org/wiki/index.php/Content_models#Compound_object , and some sample Compound Object content model objects to your test site to make sure that's what you want your materials to look like.
  • 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 you will upload the Compound Object into. 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", but definitely not short.)

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) 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 item. So, maybe... Look at other Islandora sites 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). 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. To see what's coming in Encore, you can run searches at http://discover.falsc.org/ and then click to the "Images" tab to see digital collections. The way those look is extremely likely to change between now and go-live for Encore.

9) After you click "Ingest", you have created the Compound Object content model object. Now you have 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. After you link up child objects, the Compound Object will look like examples linked in <a href="https://fig.wiki.flvc.org/wiki/index.php/Content_models#Compound_object">Chapter 5e</a> of this FIG wiki. * note *

Linking the child objects

10) Browse to the collection holding your child objects and your Compound Object parent.

11) 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.

12) Browse to the collection holding your child objects and your Compound Object parent.

13) Click to the Compound Object parent. Click the "Manage" tab on the Compound Object parent, then click to the "Compound" tab.

14) 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.

15) Continue through filling out "Child Object Pid/Label" and adding each child object. Use the spreadsheet you downloaded in step 11 as a check list.

16) 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.)

17) 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

  • Secret step 1 is always to pick a content model. Before you begin, look over the notes for the Compound Object content model posted at https://fig.wiki.flvc.org/wiki/index.php/Content_models#Compound_object , and some sample Compound Object content model objects to your test site to make sure that's what you want your materials to look like.
  • 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) Prepare all MODS metadata for your Compound Objects. 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. 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 MODS XML in a single folder. The name of this file should match the name of the corresponding XML. Zip that folder to make a .zip file.

6) Browse to the collection you will upload the Compound Objects into. Click the "Manage" tab, then click to the "Collection" tab, then click to "Batch Import Objects".

7) Under the "Importer" drop down, you should see "Zip File Importer" selected. If not, then choose "Zip File Importer".

8) 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".

9) This will load metadata for each Compound Object parent.

Linking the Compound Object parents and child objects

10) 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:" steps 10-17. 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 is NOT available for Compound Object content model objects

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

Personal tools