Content models

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
NOTE: In Islandora, format support is provided by a combination of Fedora Content Models and Islandora Solution Packs (code modules). For the sake of simplicity, Content Model and Solution Pack are used to mean the same thing in this wiki page.

This chapter does not include the Islandora Collection Content Model (islandora:collectionCModel).

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


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

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

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

For additional information on ingesting files, see Creating Content Objects.


Contents

Audio

Prepping the collection:

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

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

Files for Upload:

The Audio Content Model is used for single audio files.

The Audio content model accepts these filetypes:

   WAVE (.wav)
   MP3 (.mp3)

How it looks:

It optionally allows the operator to upload a thumbnail image when you first upload (or you can add a thumbnail anytime later).

Plays audio in the browser using JWPlayer. The thumbnail shows up in the background of the player window in the browser, in addition to its normal locations. In the pic below the image of a microphone is the thumbnail.

AudioCMDisplay.png


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

Examples:

Technical info / Datastreams:

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

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

Basic Image

Prepping the collection:

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

  • Islandora Basic Image Content Model (islandora:sp_basic_image)

Files for Upload:

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

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

   JPEG (.jpg, .jpeg)
   PNG (.png)
   GIF (.gif)
   TIFF (.tif, .tiff) (Note: .tif and .tiff can only be loaded to Basic Image by GUI;  they cannot be loaded to Basic Image by zip; they cannot be loaded by offline batch ingest)

How it Looks:

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

BasicImageCM.png

Examples:

Technical info / Datastreams:

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

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

If a TIFF is supplied, islandora:sp_basic_image will create these datastreams:

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

Binary Object

The Binary Object Content Model is designed to hold any type of file. Files loaded using this Content Model are not rendered by Islandora but rather are available to users to download. This Content Model is ideal for sharing 3D files (e.g., STL, OBJ, AMF, 3MF) that can be downloaded and printed or used by a variety of applications, or for any file format where the objective is to provide a file for download by users. Binary objects can be components of a Compound Object as well, perhaps combining a rendered version of an object as well as a downloadable version.

Prepping the collection:

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

  • Islandora Binary Object Content Model (islandora:binaryObjectCModel)

Files for Upload:

The Binary Object content model can hold any kind of file at all!

The Binary Object content model is used to ingest a single content object of a file type not supported by the other Islandora content models, or any file in which the desired presentation is a link for download. Since Islandora is not instructed in a method to render the ingested file (datastream), it will provide only a link for the user to download the file. Binary Object is appropriate for common office formats such as spreadsheets, 3D files, slides, and word processing documents, among other things.

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

The Binary Object content model accepts a single file of any type as the primary datastream, and optionally allows the user to upload a thumbnail image to use for the file. If no thumbnail is uploaded, a default thumbnail is provided. Each site can associate thumbnail icons to be used as the default for particular MIME types (ie. you can set up Islandora to always load an Excel icon as the thumbnail for .xls files). Instructions for associating thumbnail icons with MIME types can be found in Site Administration: Binary Object Thumbnail Association .

How it looks:

BinaryCMDisplay.png

Examples:

  • None available at this time.

Technical info / Datastreams:

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

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

Books

Prepping the collection:

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

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


Books can be created in FL-Islandora through the User Interface, or they can be loaded using Offline Batch Ingest. Documentation on creating book objects via the User Interface can be found at Creating Content Objects: Books. Documentation on creating book packages for loading via Offline Batch Ingest can be found at Package requirements.

Internet Archive Book Content Model

Islandora Internet Archive Book Content Model (islandora:bookCModel)

Files to upload:

No files. Just metadata.

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

BookReaderNoPages.png

Examples (of the Book):

Technical info / Datastreams (for the Book, not the page):

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

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

Page Content Model

Prepping the collection:

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

Files for upload:

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

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

How pages look:

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

IAbookReader.png

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

PageObjectDisplay.png

Examples (of the pages):

Technical info / Datastreams (for each Page):

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

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

Compound object

Prepping the collection:

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

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

Files for upload:

The Compound Object content model is metadata only. It holds together multiple objects, and those objects can have different formats.

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

Normally the child objects will already be in the repository. The Parent Object is then created using the Compound Object content model, and the children are then associated with the parent.

How it looks:

CompoundObjectCM.png

Examples:

Technical info / Datastreams:

For the parent, the following datastreams are created:

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

Large Image

Prepping the collection:

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

Islandora Large Image Content Model (islandora:sp_large_image_cmodel)

Files for upload:

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

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

How it looks:

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

LargeImagecm.png

Examples:

Technical info / Datastreams:

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

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

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

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

Newspaper

Prepping the collection:

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

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

Documentation on creating newspaper objects can be found at Creating Content Objects: Newspapers as well as in the Offline batch ingest section of this Guide.

Newspaper Content Model

Islandora Newspaper Content Model (islandora:newspaperCModel)

Files to upload:

No files. Just metadata.

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

How it looks:

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

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

NewspaperCM.png

Examples (of top level newspaper objects):

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

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

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

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

Newspaper Issue Content Model

Islandora Newspaper Issue Content Model (islandora:newspaperIssueCModel)

Files for upload:

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

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

How it looks:

NewspaperIssueCM.png

Examples:

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

The following datastreams are created:

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

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

Newspaper Page Content Model

Islandora Newspaper Page Content Model (islandora:newspaperPageCModel)

Prepping the collection:

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

Files for upload:

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

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

How pages look:

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

NewspaperPageCM.png

Examples:

Technical info / Datastreams (for each Page):

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

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

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

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

PDF

Prepping the collection:

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

  • Islandora PDF Content Model (islandora:sp_pdf)

Files for upload:

The PDF content model is used for single PDF files.

It accepts files of the following filetypes as input:

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

How it looks:

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

PdfCM.png

Examples:

Technical info / Datastreams:

The following datastreams will be created:

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

Serial

For usage details please see FL-Islandora Serials Module

Prepping the Collection:

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

  • Islandora Serial Object Content Model (islandora:rootSerialCModel)
Note: Do not enable the following Content Models:
  • Islandora Serial Object Intermediate Content Model (islandora:intermediateCModel)
  • Islandora Serial Object Intermediate Category Content Model (islandora:intermediateSerialCModelStub)
Even though it seems counter-intuitive, enabling/checking the above options will cause problems.

Files for upload:

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

SerialPDFtoc.png

The table of contents as a whole and Description tab represent a single Serial Object Intermediate. Sections defined in the left most column of the table of contents are Serial Object Intermediate Category objects. The article titles represent PDF objects that are children of the Serial Object Intermediate.

Serial Object Content Model

Islandora Serial Object Content Model (islandora:rootSerialCModel)

Files to upload:

Metadata only. No files.

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

How it looks:

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

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

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

SerialTreeHierarchy.png

Examples:

Technical info / Datastreams:

Created Datastreams:

RELS-EXT Default Fedora relationship metadata
MODS MODS record
DC Dublin Core record
TN Thumbnail image. Not created on ingest, must be added
SERIAL-LEVELS Hierarchical Information for the Serial Object

Serial Object Intermediate Content Model

Islandora Serial Object Intermediate Content Model (islandora:intermediateCModel)

Files to upload:

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

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

Technical info / Datastreams:

Created datastreams:

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

Serial Object Intermediate Category Content Model

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

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

How these look:

Examples:

Technical info / Datastreams:

Created datastreams:

RELS-EXT Default Fedora relationship metadata
DC Dublin Core record

Video

Prepping the collection:

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

  • Islandora Video Content Model (islandora:sp_videoCModel)

Files for upload:

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

It accepts the following filetypes:

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

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

How these look:

Videos are currently displayed in FL-Islandora by JWPlayer.

VideoCM.png

Examples:

  • None available at this time.

Technical info / Datastreams:

The following datastreams will be created:

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