ISLANDORA BASIC TRAINING MANUAL

Transcription

1 ISLANDORA BASIC TRAINING MANUAL September 2013 PALS This documentation will introduce Islandora and provide an overview of its features, and show how PALS can support Islandora. No previous experience with Islandora is needed. Included in this documentation is a how to guide for adding books (objects) to a repository, links to Islandora sites that PALS supports, scanning and file naming recommendations, information on digitization standards, an introduction to the MODS metadata schema (which is our recommended schema to use with Islandora), and notes on global changes in Islandora. This documentation refers to Islandora version 7.x-1.2. The purpose of this manual is to provide an interested user with an overview of how Islandora works and what it can do. Page 1

2 Table of Contents Chapter 1: Introducing Islandora Page 4 What is Islandora?...Page 4 Key terms..page 4-5 Resources.Page 5 Solution Packs...Page 6 Islandora Core Technologies..Page 6 How Islandora Understands Content..Page 7 Chapter 2: Scanning and file naming conventions for ingest.page 9 Chapter 3: Customized Ingest Forms and Solution Packs.Page 12 Chapter 4: How to use the Book Solution Pack Page 13 Saving images as uncompressed TIFFs..Page 13 Creating a zip file Page 15 Creating a book object..page 17 Adding zipped pages (files) Page 22 Completed book interface overview.page 27 Datastreams.Page 28 How to edit the metadata.page 29 Metadata mapping (MODS to DC) Page 31 Chapter 5: Audio Solution Pack Page 33 Chapter 6: Basic Image Solution Pack.Page 35 Chapter 7: Compound Solution Pack..Page 36 Chapter 8: Core Collection Solution Pack.Page 37 Chapter 9: Islandora Paged Content Solution Pack....Page 39 Chapter 10: Large Image Solution Pack.Page 42 Page 2

3 Chapter 11: Newspaper Solution Pack Page 44 Chapter 12: PDF Solution Pack.Page 47 Chapter 13: Video Solution Pack.Page 49 Searching.Page 51 PALS Islandora Services Page 53 Islandora Site Examples by PALS Page 54 Appendix A: Digitization Standards Page 55 Appendix B: MODS Introduction..Page 58 Note on global changes/edits.page 61 Contact information Page 62 Page 3

4 CHAPTER 1: Introducing Islandora Documentation derived from and taken from: What is Islandora? From Islandora 7.x-1.2 Documentation: Chapter 1, Introduction Islandora is an open source framework developed by the University of Prince Edward Island's Robertson Library since It leverages both the expertise of PHP/Java/Python developers and of librarians and other information-professionals. Islandora is committed to utilizing open standards for data description and access, as well as high-standards for data stewardship and security over time. Islandora makes it possible to create, edit, discover, view, and manage repository assets. The system strives to strike a balance between extensibility and usability, by providing out-of-the box support for collections, while maintaining an architecture that lends itself to customization to other software and workflows. The heart of Islandora s data stewardship model is Fedora - if you are a Fedora user, you are still capable of accessing and manipulating objects in Islandora s underlying Fedora as you would in any Fedora installation. Special consideration for Fedora users is taken in Chapter 7 - Customizing Islandora. The Islandora project combines and harnesses the power of the Drupal content management system and the FedoraCommons Repository software to create a robust digital asset management system that can be used to meet the short and long-term collaborative requirements of digital data stewardship. More information about Islandora s core technologies is provided in this introductory chapter. A list of current installations of Islandora is available at Islandora also represents a community-based approach to integrating robust open source software projects together. The resulting toolkit empowers users to create bespoke solutions and designs that accommodate the integration of software solutions that you already use. Additional open source applications that provide flexibility and extensibility are added to this core stack to create Solution Packs. Key terms Object (also Fedora Object ) Everything stored in a Fedora repository is treated as an object. Objects are made up of three components: a Persistent Identifier (PID), System Properties, and one or more Datastreams. The generic nature of Fedora s digital object model allows a wide variety of digital content to be stored and delivered to users. Page 4

5 Collection object Content model Everything stored in Fedora is an object, including collections. Collection objects provide a means to organize other objects via an ismemberof element in an RDF statement. Content models describe the characteristics of objects in the Fedora repository. Islandora extends Fedora s content model architecture with a datastream that has the datastream ID (DSID) ISLANDORA_CM. Datastream Datastreams are elements of objects that represent content. They may contain metadata about the object. Each object has a number of default datastreams, notably a Dublin Core Datastream and a RELS-EXT (Fedora Object-to-Object Relationship Data Datastream. Datastreams can also contain other useful information, and different types of objects will have different datastreams; for example a collection object has a collection policy datastream, while an image might contain a thumbnail datastream. There are two kinds of datastreams: A collection of data about an object Different representations of the object itself (MODS/Dublin Core metadata, TIFF, thumbnail, JPG, OCR) Resources If you want to ask questions to the Islandora community, there is a Google Group located at The Islandora website is located at: Discovery Garden focuses on building specialized systems that allow organizations and companies to manage their digital assets in a flexible, robust framework. Islandora s ticketing system: Page 5

6 Solution Packs Solution Packs reflect best-practice workflows emerging as a result of the community s experience dealing with particular types of data, such as large-format images, maps, books, magazines, and individual research articles. Solution packs combine pre-chosen content models, metadata forms, and Viewers based on the experience of the Islandora community. Solution packs may be customized to meet the needs of your collection and institution, or used out of the box to create collections. Solution Packs often require additional applications to be installed and configured. In this implementation of Islandora, we are using the Book Solution Pack, which contains the Internet Archive Viewer. The IA Viewer displays the object as if you are reading a book, and provides robust interactive capabilities. Supported solution packs: Simple Image Solution Pack Large Image Solution Pack PDF Solution Pack Audio Solution Pack Video Solution Pack Books Solution Pack Islandora Core Technologies Taken from documentation: +Introducing+Islandora Islandora s core technologies are FedoraCommons repository software, Drupal, and Solr. FedoraCommons Repository Software lends itself to data stewardship via a unique content and relationship modeling framework that preserves the integrity of collections and can be modified to manage any digital asset. This means that Fedora collections are uniquely persistent, no matter what new software lurks around the corner. In the Islandora system, Drupal acts as an interaction layer atop Fedora, enabling users to discover, view, and manage Fedora objects. Drupal is a very popular, modulebased system that understands Islandora as a suite of modules. Through Drupal, Islandora users can create content together, and use social-networking to enrich Fedora content. Solr represents an emerging, and important third application used in Islandora bringing lightning-fast searching of the Fedora database, including full-text searching of any attached documents. Solr also allows for results to be refined, using faceting techniques to engage users in a process of discovery and exploration. Page 6

7 How Islandora Understands Content Islandora uses Fedora s Digital Object Model, Relationships, and Content Model. In Islandora Everything is an OBJECT: o Objects have PERSISTENT IDENTIFIERS that you will be asked to specify o Objects have RELATIONSHIPS to one another o Objects have DATASTREAMS Two kinds: There are 3 types of Objects o Content Model Objects o Collection Objects o Data Objects A collection of data about an object Different representations of the object itself (MODS/DC metadata, tiff, thumbnail, jpg, OCR) Page 7

8 Content Model Object A content model object is a template for a particular type of content. Defines What will happen to the object when it is ingested into the repository How object will be displayed What object consists of (for example, PDFs, maps, etc..) List of datastreams the associated digital object has, as well as list of binary files Collection object Is the same as the traditional concept of a collection Every instance of Islandora has a root collection object which subscribes to a Collection Content Model Collections are created under the Collection Content Model All Collection objects will be affiliated with the Collection Content Model Object o That affiliation defines types of Data Objects that can belong to a Collection That affiliation defined in one of the Datastreams of the collection object (the COLLECTION_POLICY stream Data Object Refers to the actual assets being stored o One map and its associated datastreams (metadata, alternate image formats/sizes) is a data object o Datastreams tell system where the main file is located, as well as any derivatives that are used for web-display, they will contain the bibliographic (metadata) record associated with that object, and they will indicate which collection (s) the map belongs too Concepts to remember Objects have datastreams each object has a datastream, which are the parts of an object Specialized objects and their specialized datastreams perform a number of different functions, and serve a number of different purposes Examples of datastreams: A reference to the binary file being stored (i.e. PDF, or image) Page 8

9 May declare the Content Model Object affiliations of an object May store relationships that an object has to other objects in the repository Each object has a default DC datastream Objects have relationships Objects in Islandora have relationships to each other. These are stored in a RELS-EXT datastream in an object. Usually labeled Fedora Object-to-Object Relationship. This datastream is written in RDF. RDF statements indicate o what collection an object (s) belongs to, o what content model it subscribes to, o and what its PID is. Objects have unique (persistent) identifiers Each object has a unique (persistent) identifier specified by a user or automatically created. Page 9

10 CHAPTER 2: Scanning and file naming conventions for ingest PPI/DPI (Scanning) Recommendations When saving images it is important to consider the DPI (dots per inch) and/or the PPI (pixels per inch). DPI and PPI each affect how clear the image will appear. DPI refers to output devices (like a printer) and PPI refers to on screen display. It s important to note that different monitors will affect how clear an image appears on a screen. For example if an image is at 300 PPI it may look clearer on one machine; and less so on another monitor. The recommended DPI for display/access images is 300. We recommend between DPI for full color and text documents, saved as uncompressed TIFF. For black and white text documents that include black and white photographs we recommend between DPI. It s also important to note that while technically DPI and PPI mean different things, they are often used interchangeably and can mean the same thing. This can definitely cause confusion. Page 10

11 File naming recommendations Use only lowercase alphanumeric characters in a file name End file names with established three character extension representing file name (i.e. jpg, tif) Do not use spaces: substitute underscore or hyphen characters for spaces Do not use tabs, asterisks, slashes, etc. If appropriate, designate the image role with a letter code (e.g. thumbnail reference: t.gif) General practice indicates using a convention with an eight-character file name with a three character extension to accommodate different systems First 2 or 3 can be alphabetical unit-specific identification and the remaining characters a numeric digital object identifier o am tf (Art Museum, digital object identifier 421, TIFF Could also include a system that uses institutional acronym, collection identifier, part designator and file extension, separated by an underscore o Laramie Historical Society, Accession Number 9800, Box 5, Folder 2, item 26: lhs_9800_b5f2i26.tif o Other protocols may include the collection number and folder number as part of the path name: Lhs/9800/b5/f2/i26.tif Always keep the same number of characters in the filename and do not vary the length Be consistent Examples Photograph 8 in record group 15, series 4: rg15_4/photos/ m.tif (master file) rg15_4/photos/ r.jpg (reference file) rg15_4/photos/ t.gif (thumbnail file) YUAG naming convention includes institutional acronym, collection identifier, part designator and file extension, separated by dash ag-obj bar.tif (six digit number can increase if data records exceed 6 characters) ag=art Gallery ; obj=objects Module of TMS ; number series=object I.D. from TMS, 001=rendition number (which will increase with each saved capture) Page 11

12 CHAPTER 3: Customized Ingest Forms and Solution Packs Derived from documentation: ++Islandora+and+Ingest+Forms Each Islandora Solution Pack comes pre-packaged with an ingest form. This means yours will likely have a different form for each data format. This is the form that you will use when adding (ingesting) new items into a collection. PALS will customize these forms for you. These customized forms are different from the pre-packaged (default) forms that come with each Solution Pack. An example of a customized form: Page 12

13 CHAPTER 4: How to use the Book Solution Pack This section will go through how to use the Book Solution Pack creating a book object, uploading and adding pages (zip or individual), how to fill out a form, how to edit metadata, and how to delete objects. The Book Solution Pack is one of the more popular solution packs. The Book Solution Pack appears to be a popular choice. The important thing to know when using the book solution pack is that it requires uncompressed.tiff or.tif files, or a.zip file of tiff/tif files. There are two possible ways you can save images as uncompressed tiffs: 1. Save when scanning. This depends on the scanner you are using. 2. You can save images as uncompressed TIFFs in Adobe Acrobat Pro. To do so, go to File, Save as Other, Image, then TIFF. Page 13

14 Next, click on Settings: Change all file settings to NONE. The other settings are different kinds of compressions. Click on OK. Before saving check the filename to make sure there it follows recommendations. Then save. Page 14

15 Creating a zip file Before you ingest (add) your tiff images, you will need to create a book object. The pages (tiffs) get added to the book object. So in the book solution pack you are: 1. First, creating the book object 2. Filling out data entry form the metadata here describes the entire book object. 3. Then adding pages to the book object. Also, there are different levels at which you can manage different things: 1. Repository level manage entire repository 2. Collection level manage objects in this collection (add, delete, share, etc.) 3. Object level (edit metadata, add pages, delete pages, etc) Before creating a book object, first create your zip file that you will upload. To create a zip file: 1. Find your set of.tiffs: This is another good chance to change the filenames (Select a file, right click mouse, rename): Page 15

16 2. Select all the TIFFS you want to add to the book object. In this example it is smsu_today_page 3, 2, 1. Right click after selecting them all, and then select Send to from the drop down menu. 3. Click on Compressed (zipped) folder: 4. Progress bar Page 16

17 5. Zip file is created: 6. Rename zip file. Now it is ready for ingest. NOTE: ZIP is file compression, not image compression. There is no loss. Zipping a TIFF file, then un-zipping it, does not degrade it. Zip is a lossless compression. Creating a book object To create a book object, first go to the collection you are using. Then from the collection level click on the Manage tab. Test Book Repository is the name of this collection. Your Manage box will appear: Page 17

18 By default, it opens at Overview. This gives you the type of content model being used for this collection, and the number of objects in the collection. From here you can also add an object, view datastreams (which is important later on), and properties. You can also add an object from the Collection tab: Click on Collection. From here you can add an object, share members (objects), migrate members, or delete members of the collection. To add a book object, click on Add an object to this Collection. Choose your content model. In this case it is Islandora Internet Archive Book Content Model. Then click Next. This brings up the metadata entry form. This is the default out-of-the-box form. PALS will work with you to customize it which will greatly increase the ease of data entry. This customization includes choosing metadata elements, adding text instructions for elements regarding data entry, customizing titles of elements, eliminating elements, adding default text for certain areas (so you won t have to enter them every time), and other aspects. Page 18

19 This is the default metadata entry form: Page 19

20 While highly useful, filling out this out-of-the-box form can be time consuming. Customization is a very appealing feature of Islandora as it can greatly increase efficiency and ease of use. Page 20

21 After filling out your form, click on Ingest: Remember at this point we have only created the book object, so there will be no pages. Therefore the page viewer will be blank: Now you will need to add the pages. To do so, click on Manage. Page 21

22 From the Manage box, click on Book: From here you can add individual book pages (remember, only.tiff or.tif files) or add zipped pages. You can do a number of other things as well, including perform OCR. You could do this if the OCR doesn t work well the first time when you add the page. This is also where you can reorder pages if they get out of order, and perform some other functions. Adding zipped pages (files) We will add zipped pages. Click on Add Zipped Pages: Page 22

23 After clicking on Add Zipped Page, click on 1. Browse find your zip file. 2. Upload Upload zip file. 3. Add files to book Add pages to book. 1. Click Browse, find file: Page 23

24 2. Upload file. 3. Add files to book. 4. Friendly progress bar Page 24

25 5. When it is finished ingesting, this screen appears again. It may appear that nothing was ingested, but it has been. From here you could ingest another zip file if you wanted to. 6. Close this screen (click the x): 7. The viewer will now have pages. The icon for the object has changed to the first page of the book object: Page 25

26 8. This is an example of a repository with several book objects (and pages attached to books) added: 9. Click on any object (title or image) to view. Page 26

27 COMPLETED BOOK INTERFACE OVERVIEW 1. View tab a. Returns you to book display view. 2. Manage tab (only appears when logged in with right permissions) a. From here you can manage the book object, see datastreams, edit the MODS record, add pages to the book, reorder pages, delete pages, and perform similar functions. 3. Pages tab a. Displays all pages of the book. 4. Play 5. i = About this book (metadata) 6. Text view 7. Full screen view Page 27

28 Datastreams Datastreams are generated when you create a book object, and when you add pages to a book object. These are the datastreams generated when a book object is created: Datastreams are different kinds of objects/things that describe the book object. There is relationship data, metadata (MODS and Dublin Core Records), and a thumbnail of the book object. It s important to remember that the datastreams that are generated when you create a book object are different than those that get generated when you add a page to the object. The datastreams are describing different things. These are the datastreams that get generated when you add a page: Page 28

29 So, again, there are the datastreams describing the book: RELS-EXT (relationship information), and the metadata (MODS and Dublin Core). Also there are other datastreams generated when you add a page. These are derivatives of the original page: PDF, JP2, JPG, OCR, and HOCR. Different programs, or MicroServices, are used to create these derivatives. Examples of MicroServices include GhostScript and ImageMagick. The main thing to remember is that the derivatives (JPEG2000, PDF, etc.), are created when you add a page to the book object. How to edit the metadata (MODS record) This section shows how to edit your metadata from the data entry form you used when adding your object. Find the object you want to edit, and click on Manage: Click on Datastreams: Page 29

30 Find the MODS record, click on EDIT to the right: This takes you to the form, where you can make edits: Page 30

31 Metadata mapping This section is an example of how the metadata gets mapped from your data entry form (in MODS) to Dublin Core, which is required by Fedora (the data management layer under Islandora). The Dublin Core record is by default what you search. This is a MODS record from Southwest Minnesota State University: This is the Dublin Core record for the same object: Page 31

32 As you can see, some of the MODS elements are not mapped to DC. It is possible to choose which MODS elements are mapped to Dublin Core. MODS: titleinfo = Dublin Core (DC): title MODS:TypeOfResource = hidden, required attribute, not in template MODS: <origininfo><dateissued> = DC: title MODS: <placeterm><place><publisher> = DC: publisher MODS: <name><namepart> <role><roleterm> = DC: creator MODS: <phsyicaldescription><form> = DC: format MODS: <part><detail > = NOT MAPPED TO DC MODS: <location><physicallocation = NOT MAPPED TO DC MODS: <targetaudience> = NOT MAPPED TO DC MODS: <subject><title><topic><temporal> = DC: coverage MODS: <note> = NOT MAPPED TO DC Page 32

33 Chapter 5: Audio Solution Pack Taken from documentation at: Overview The Audio Solution Pack adds the ability to create audio collections, which can be used to upload WAV and MP3 files as objects. These files can then be downloaded by users, or the JWPlayer library and module can be installed to allow for playing of the file in the View tab. On ingest, the module can also use an installation of the LAME audio encoder to create derivative audio files. Dependencies The LAME Encoder is required for derivative creation JWPlayer and its corresponding Islandora module can be used to play audio files in the View tab Core Collection Solution Pack Downloads Release Notes and Downloads Configuration The Audio Solution Pack configuration options can be accessed at and includes the following options: Path to LAME: Upon installing the LAME Audio Codec, an executable is created on your server. The Audio Solution Pack module requires the path to this executable to run. On Linux-based servers, this path can often be found by running: whereislame Viewers By default, the Audio Solution Pack is unable to play any audio files directly in the browser; however, the JWPlayer library and module can be installed, adding that option to the Viewers section. Check the JWPlayer page for more information. Page 33

34 Content Models, Prescribed Datastreams and Forms The Audio Solution Pack comes with the following objects in Islandora Audio Content Model (islandora:sp-audiocmodel) Audio Collection (islandora:audio_collection) An audio file ingested using the Audio Solution Pack's content model and LAME will have the following datastreams: RELS-EXT MODS DC OBJ PROXY_MP3 Default Fedora relationship metadata MODS record filled out during ingest Dublin Core record Original audio file uploaded MP3 derivative created by the LAME encoder TN Default thumbnail icon for audio objects The Audio Solution Pack comes with the Audio MODS form. Page 34

35 Chapter 6: Basic Image Solution Pack Taken from documentation at: Overview The Basic Image module adds the ability to create Basic Image collections, which are capable of displaying GIF, PNG and JPG/JPEG files. Users can view a compacted version of the image on the object's View tab, or click the image to view it full-size. It also allows for creation of a thumbnail image datastream during the ingest process. Dependencies Core Collection Solution Pack Downloads Release Notes and Downloads Content Models, Prescribed Datastreams and Forms The Basic Image Solution Pack comes with the following objects in Islandora Basic Image Collection (islandora:sp_basic_image) Basic Image Collection (islandora:sp_basic_image_collection) An image object created using the Basic Image Solution Pack's content model will have the following datastreams: RELS-EXT MODS DC OBJ Default Fedora relationship metadata MODS record, created at time of ingest Dublin Core record The original image file uploaded Page 35

36 TN MEDIUM_SIZE Thumbnail image, created at time of ingest A compressed version of the image, used on the object's View page The Basic Image Solution Pack comes with the Basic image MODS form. Chapter 7: Compound Solution Pack Taken from documentation at: Overview The Compound Solution pack module adds the ability to to create compound objects using objects created with any other Islandora solution pack by enabling a generic parent-child relationships between objects. The object view of a compound object is replaced by the view of its first child object. The included "Islandora Compound Object Navigation" block provides a thumbnail navigation of an object's siblings. A "Compound" management tab allows for the addition and removal of parent and child objects for each object. Configuration options are available through the Compound objects administrative menu (admin/islandora/compound_object) Dependencies Core Collection Solution Pack Downloads Release Notes and Downloads Content Models, Prescribed Datastreams and Forms The Compound Solution Pack comes with the following objects in Islandora Compound Object Content Model (islandora:compoundcmodel) Page 36

37 Compound Collection (islandora:compound_collection) An image object created using the Compound Solution Pack's content model will have the following datastreams: RELS-EXT MODS DC TN Default Fedora relationship metadata MODS record, created at time of ingest Dublin Core record Thumbnail image, created at time of ingest The Compound Solution Pack comes with the Compound Object MODS form. Core Collection Solution Pack Taken from documentation at: Overview The Islandora Core Collection Solution Pack module allows Islandora to view and manipulate objects as a collection. Installing the module allows collections to be viewed and created, and adds the 'Collection' button to all collections' management pages. It also adds the Islandora Collection content model to the list of solution packs. Dependencies Islandora Module Downloads Release Notes and Downloads Page 37

38 Usage Information about the links on an object's 'Collection' button (found on its 'Manage' tab) can be found in the various subsections under Chapter 3 - Getting Started with Islandora. Configuration Configuration options for the Core Collection module can be found at and include the following options: The default number of objects to show for a collection: If a collection contains more than the number of objects displayed here, it will split them up into pages. Select the default collection view style: Grid view displays icons with little information, while list view can be used to get more metadata at a glance. Disable deleting the collection policy: Unchecking this box will allow you to delete and then replace any collection's policy datastream. This is an advanced technique and generally should be left checked. Content Models, Prescribed Datastreams and Forms The Core Collection Solution Pack comes with the following objects in Islandora Collection Content Model (islandora:collectioncmodel) A collection created using the Core Collection Solution Pack's content model will have the following datastreams: RELS-EXT COLLECTION_POLICY TN DC Default Fedora relationship metadata The collection's policies regarding applied content models and membership Thumbnail icon Dublin Core record The Core Collection Solution Pack comes with no forms. Page 38

39 Islandora Paged Content Taken from documentation at: Overview The Islandora Paged Content module is shared by the Book Solution Pack and Newspaper Solution Pack modules to provide numbered, individual pages as objects within each type of collection. It takes files in TIFF format, and is able to create several kinds of derivatives depending on the type of collection they are being ingested into. Solution Packs that use the Paged Content module are referred to below as 'Paged Content collections'. Dependencies The Large Image Solution Pack is required to create image derivatives Ghostscript is used to compile PDF derivatives into a single document Core Collection Solution Pack Provisions The Book Solution Pack or Newspaper Solution Pack are examples of Paged Content collections. It is advisable to install one of those solution packs, and check their pages for additional dependencies. Downloads Release Notes and Downloads Usage Adding a collection that uses the Paged Content module (currently the Book and Newspaper Solution Pack are provided as out-of-the-box modules that function with it) adds a new button to the end of the 'Manage' tab - 'Book', for the Book Solution Pack, and 'Newspaper' for the Newspaper Solution Pack, for example. It also adds a 'Page' button to the 'Manage' tab of any page objects added to a Paged Content collection. Clicking on this button will bring up several options, depending on what components of the module are selected and enabled: Page 39

40 Add Page - This brings up a page that uses the TIFF uploader form in conjunction with Tesseract to allow you to choose the file and language of your page, and add it to the parent Paged Content collection. Create PDF - This section includes the ability to create either a single page PDF if selected from a single page's 'Manage' tab, or a PDF of an entire Paged Content collection if selected from the collection's 'Manage' tab. The resolution of the image can also be set here. Creating a PDF will overwrite any existing PDF datastream. Perform OCR - This section includes the ability to create OCR datastreams for a single page if selected from that page's 'Manage' tab, or OCR datastreams for an entire Paged Content collection if selected if selected from the collection's 'Manage' tab. If multiple languages are installed into Tesseract, the option to switch between them will also be given here. Creating new OCR datastreams will overwrite any existing ones. Create Images - This section adds the option to create image derivatives if the Large Image Solution Pack is installed. Any existing image derivatives will be overwritten if this is used. If this option is selected from a Paged Content collection, the option will be given to create a thumbnail image for the collection from the first ordered page, updating and overwriting any existing thumbnail. Reorder Pages - This section allows a user to re-order the pages in a Paged Content collection if they are not in their correct place. Delete Pages - This section allows a user to remove pages from a Paged Content collection. Configuration Very few configuration options exist for the paged content module out-of-the-box; most of the configuration should occur with the solution pack the pages are being ingested into. However, a configuration page does exist at and includes the following options: PDF Derivative Settings The Paged Content module requires the Ghostscript executable to be installed on your server, and the path to the executable to be entered here, on the configuration page, in order for multi-page PDFs to be compiled using each page in the book or newspaper. More information about installing Ghostscript on your server can be found at the official website, Content Models, Prescribed Datastreams and Forms The Paged Content Solution Pack comes with the following objects in Islandora Page Content Model (islandora:pagecmodel) An image ingested into a Paged Content collection using ImageMagick, the Large Image Solution Pack and the Islandora OCR modules, will have the following datastreams: Page 40

41 OBJ Original TIFF file uploaded DC PDF JP2 JPG Dublin Core record PDF derivative created by Ghostscript JPEG 2000 derivative created by ImageMagick Smaller JPEG derivative created by ImageMagick TN Thumbnail icon created from the image during the ingest process RELS-INT Internal Fedora relationship metadata defining the dimensions of the JP2 datastream OCR The raw output from Tesseract HOCR A converted version of the OCR datastream, intended to be more human-readable RELS-EXT Default Fedora relationship metadata The Paged Content Solution Pack does not come with any forms. Page 41

42 Chapter 10: Large Image Solution Pack Overview The Large Image Solution Pack module supports ingesting and viewing TIF/TIFF files, which by nature tend to be extremely large in both filesize and resolution. The module supports creation of derivatives for use when a smaller filesize is necessary, and also supports the installation of image viewers that can accommodate the larger resolution. Dependencies ImageMagick is required to create image derivatives OpenSeadragon can be used as an alternative viewer Core Collection Solution Pack Downloads Release Notes and Downloads Configuration The Large Image Solution Pack module's configuration page can be found at and contains the following settings: Lossless Derivative Creation?: Enabling this will force the Large Image Solution Pack to use no compression when creating derivatives. Use Kakadu for Image Compression?: The Kakadu software suite can be installed on your server to take advantage of its much faster kdu_compress program. Check the official website at for download and installation instructions Viewers If no viewers are installed, the Large Image Solution Pack module will use its standard viewer to display images. For better results, the OpenSeadragon library can be installed; check that page for further instructions. If it is installed, it can be selected here. Page 42

43 Content Models, Prescribed Datastreams and Forms The Large Image Solution Pack comes with the following objects in Islandora Large Image Content Model (islandora:sp_large_image_cmodel) Islandora Large Image Collection (islandora:sp_large_image_collection) An image ingested using the Large Image Solution Pack's content model using ImageMagick will have the following datastreams: RELS-EXT MODS DC OBJ JP2 JPG TN Default Fedora relationship metadata MODS record filled out during ingest Dublin Core record Original TIFF file uploaded JPEG 2000 derivative created by ImageMagick or Kakadu Medium-sized JPEG created by ImageMagick and used in the standard image viewer Thumbnail icon created from the image during the ingest process The Large Image Solution Pack comes with the Large image MODS form. Page 43

44 Chapter 11: Newspaper Solution Pack Taken from documentation at: Overview The Islandora Newspaper Solution Pack is a Paged Content collection that is similar to the Book solution pack, with a few key differences. Unlike a book collection, a newspaper collection is intended to represent a single publication, and each object inside that collection is intended to represent a single issue of that publication. Another level down, each object is intended to represent a page of that particular issue. The Newspaper Solution Pack is designed to make it easier to navigate between issues and pages of a single publication - closer to the nature of a newspaper or magazine - as opposed to a book, which is more commonly read page-by-page. Dependencies Islandora Paged Content Core Collection Solution Pack OpenSeadragon can be used to view pages Islandora OCR is required to create OCR and HOCR derivatives ImageMagick is required to create PDF datastreams Large Image Solution Pack is required to create thumbnails and other image derivatives Ghostscript is required to combine PDF datastreams into one issue-wide PDF Downloads As of release, the Newspaper Solution Pack is incomplete and still considered to be in 'beta'. However, a repository exists on Github's Islandora page at on the branch 7.x-release. For those interested in trying out the module, it can be cloned from Usage Adding a newspaper, issue and page Page 44

45 The Islandora Newspaper Solution Pack comes with several different content models that are intended to be ingested in a particular order: 1. A child collection is set up and given the Islandora newspaper content model. This represents the publication that issues will be added to. 2. Inside that collection, a new object is created; this will automatically be given the Islandora newspaper issue content model. 3. Within that new object, pages are added. These are automatically given the Islandora newspaper page content model. Because you will be ingesting multiple issues of a publication that contains extremely similar MODS records, it is recommended to install the MARCXML Module so that the MARCXML record from one issue can be uploaded into other issues. Check the MARCXML Module page for more information on downloading and ingesting MARCXML files. Creating issue derivatives Once pages are added and sorted in an issue, you can use the 'Collection' section of the issue's 'Manage' tab to create derivatives: Under 'Create PDF', if Ghostscript is installed on your server, you can use it to concatenate individual PDF page datastreams into one ordered PDF datastream that can be appended to the issue itself Under 'Create Images', you can update the issue's thumbnail image if page one has changed. Page controls When looking at an individual page, navigation options will be given above the viewing window, listed below from left to right: A drop-down menu to quickly select a page in the current issue Options to view the entire issue or the entire publication Links to download any created derivatives A link to download the original image Configuration The Islandora Newspaper Solution Pack configuration page is accessible at and includes the following options: Page 45

46 Create Page Derivatives Locally This section allows you to configure the Newspaper Solution Pack module to create derivative datastreams for pages. The following derivative datastreams can be set, with their accompanying dependencies: PDF ImageMagick TN, JPEG, JP2 Large Image Solution Pack OCR, HOCR Islandora OCR Page Viewers This section changes how Islandora handles a request in the 'View' tab of a newspaper's page object. Islandora includes out-of-the-box support for OpenSeadragon; otherwise, no viewer will be available. Check the OpenSeadragon page for more information on installing this component. Content Models, Prescribed Datastreams and Forms The Newspaper Solution Pack comes with the following objects in Islandora newspaper content model (islandora:newspapercmodel) Islandora newspaper issue content model (islandora:newspaperissuecmodel) Islandora newspaper page content model (islandora:newspaperpagecmodel) Newspaper collection (islandora:newspaper_collection) A newspaper issue ingested with all derivative creation options checked will have the following datastreams: RELS-EXT Default Fedora relationship metadata MODS MODS metadata form DC TN Dublin Core record Thumbnail image PDF Concatenated PDF compiled with Ghostscript Page 46

47 Check Islandora Paged Content for information on an individual page's datastreams. The Newspaper Solution Pack comes with the Islandora Newspaper MODS form. Chapter 12: PDF Solution Pack Overview The PDF Solution Pack module adds functionality to Islandora for ingesting and viewing PDF files. It uses the ImageMagick library and module to create derivative thumbnail and preview images. Because of the text-based nature of PDF files, it can also be used to create or append easily searchable text datastreams to the object, which can later be configured through Solr to appear in searches. Dependencies ImageMagick is required to create derivatives pdftotext is required to automatically create a FULL_TEXT datastream. Core Collection Solution Pack Downloads Release Notes and Downloads Configuration The configuration options for the PDF Solution Pack module can be found at and include the following: Text Users can either upload a text file of their own, or allow Islandora to extract one from the PDF. Text accompanying the PDF is stored as the FULL_TEXT datastream. If both options are checked under the Text configuration section, and a valid path to pdftotext is entered, preference will be given to a supplied text file on ingest. Allow users to upload text file with PDF?: This file must be plain text stored in.txt format. Page 47

48 Store extracted (or supplied) text?: Checking this box, will display an option to enter a path to the pdftotext executable. This package is not native to most server setups and will need to be installed manually for this option to be functional. Check the pdftotext dependency page for more information. Thumbnail and Preview These options set the parameters that will be sent to ImageMagick when ingesting a PDF. ImageMagick will attempt to create these using the first page of the document. Changing these will simply change the size of the derivatives being created. Content Models, Prescribed Datastreams and Forms The PDF Solution Pack comes with the following objects in Islandora PDF Content Model (islandora:sp_pdf) PDF Collection (islandora:sp_pdf_collection) A collection created using the PDF Solution Pack's content model will have the following datastreams: RELS-EXT MODS DC OBJ Default Fedora relationship metadata MODS metadata record created during ingest Dublin Core record Original PDF file uploaded TN PREVIEW Thumbnail image created by ImageMagick during ingest Preview image created by ImageMagick during ingest FULL_TEXT Optional datastream either uploaded during ingest, or created by the pdftotext executable The PDF Solution Pack comes with the PDF MODS Form. Page 48

49 Chapter 13: Video Solution Pack Taken from documentation at: Overview The Islandora Video Solution Pack is used to ingest digital videos into Fedora. It supports creation of derivatives in various different video formats, and requires the server-side installation of accompanying codecs to enable this functionality. It can also be configured to stream the video to a player window onsite using JWPlayer. Dependencies Core Collection Solution Pack The Islandora JWPlayer library (and the Libraries API module) are all required to play videos in a video object's 'View' tab ffmpeg is required if MKV and MP4 derivatives are to be created on the same server as Islandora ffmpeg2theora is required if OGG and thumbnail derivatives are to be created on the same server as Islandora Downloads Release Notes and Downloads Configuration The Islandora Video Solution pack can be configured at and includes the following options: Viewers If JWPlayer has been correctly installed on the server, an option to select it as a viewer will appear here. Keep original file after ingest? - Check this option to retain files uploaded to a video collection as a datastream appended to the video object Page 49

50 Paths to ffmpeg/theora executables For derivative creation, the Video Solution Pack needs to know the location of the binaries that perform conversion. On Unix-based systems, this can often be done by running: whereis ffmpeg ffmpeg2theora and checking for binary package files located in folders called 'bin' (such as /usr/bin, /usr/local/bin, etc.) Video conversion in any context is an extremely resource-heavy task that can be very taxing on the computer performing it. In the case of Islandora, when using these derivative creation options, the task is called upon and performed by the 'apache' user on the same server Islandora is running on and that users are performing other tasks with. When creating video derivatives on ingest, please consider either delaying ingest to a low-traffic period of time, or performing derivative creation on another machine altogether. Content Models, Prescribed Datastreams and Forms The Video Solution Pack comes with the following objects in Islandora Video Content Model (islandora:sp_videocmodel) Video Collection (islandora:video_collection) A collection created using the Video Solution Pack's content model will have the following datastreams: RELS- EXT Default Fedora relationship metadata MODS DC OBJ MP4 OGG MKV TN MODS metadata record created during ingest Dublin Core record The original video file ingested MP4 derivative created during ingest by ffmpeg and used by JWPlayer if no suitable video exists OGG audio-only derivative created by ffmpeg2theora MKV derivative created during ingest by ffmpeg Thumbnail image pulled from a frame of the video by ffmpeg2theora The Video Solution Pack comes with the Video MODS Form Page 50

51 Searching This section is an overview of searching in Islandora. For more detailed information, see the official documentation: Islandora uses Solr and the Solr module with GSearch to provide search functions. Solr makes it easy to create advanced search features, like faceting. Islandora simple search provides a simple full-text search of all items in the repository. A term will appear, no matter where it is in the metadata. Islandora advanced search is configurable, where specific metadata fields can be search and combined with Boolean operators. With the advanced search you can, for example, configure it to give you the ability to choose between OR or AND and do more sophisticated searches. Searching basketball with simple search: Page 51

52 An example of a customized Advanced Search: Subject search for test : Page 52

53 PALS Islandora Services PALS has the staff and the knowledge to host and support your instance of Islandora, handle the configuration and customization, and guide you through the process of building your Islandora repository. 1. Hosting PALS assumes responsibility for the hardware and software needed to ensure the ongoing availability and quality of Islandora instances and related services that we host and support. In addition, PALS provides storage space for all ingested objects and their derivatives, metadata, and indexes. Administrative access to the system is available to our customers via the Islandora web interface, which can be used to configure Islandora and the Drupal interface. System and support functions and tasks are divided between the customer and PALS staff as mutually agreed upon. The PALS data center is co-located with the Minnesota State University, Mankato data center. We continuously work to ensure that our servers and the network perform at optimal levels. For production systems, PALS leases space on the storage system administered by the University. Development systems are hosted on PALS-administered systems. Processing power, memory and space are allocated based on our specifications and can be adjusted dynamically as needed. Our operating environment allows us to easily scale our systems to meet increasing system requirements. The University/PALS data center is on a 1Gb State trunk line with redundant routing available through a local ISP. 2. Support Services As part of our Islandora services, PALS staff will work with the customer to plan the repository and each collection, determine the appropriate metadata standard and elements to use, and provide support throughout the configuration and ingest phases of the project. Once the repository is operational, PALS will offer ongoing support and consultation services to assist the customer in using Islandora functionality to its fullest. PALS offers an online support center through which customers can input problems or questions. Keyword searching is utilized to offer existing potential answers to any question entered. Additionally, the PALS office support staff is available by phone or . Page 53