Theme Package

Theme

Module

The site’s initial install profile module (bd_core) relies on several third party modules which are enforced as install dependencies, modules with an * are nice to have but not required for full functionality, each module has notes on why it was added.

  • Site configuration for Islandora using core install profile.
    • Install profile initially imports configurations, after that, local settings will override, such as logo, so any future configuration will need to be done manually.
    • Has plugins for blocks, conditions, field formatter, search api processor, TWIG custom filters, and view styling.
  • Compound Object theme support
  • Paged Content theme support
  • Blank /home route to create homepages
  • Removes exposed filters from default solr_search from search
  • Enables custom solr_search header (sort/pagination/grid/list)
  • Adds Compound objects and its related components (views/themes/ajax/viewmode)
  • Tweaks Collection (view/viewmode/theme)
  • Defines Items in Collection Field
  • Defines Entity Reference Count Formatter
  • Defines General Use ajax view render block
  • Adds new libraries (CSS/JS) to support it
  • Adds new OpenSeaDragon Field to render openseadragon viewer
  • Modifies solr_content_search to render facets automatically as attachments before view gets rendered
  • Defines Permalink field to show the permanent URL of an object
  • Supplies configurations to tweak existing and new islandora configurations to alter layouts, field order and more.

For more information see https://gitlab.com/born-digital-us/whitman/whit-arm-i8/-/tree/main/codebase/assets/sites/all/profiles/bd/modules/bd_core

Theme Configuration

This section covers the subset of customization options from the theme that will be most helpful to users ready to configure their site. Altering additional items has not been tested and may not render as desired.

Customize sites by editing the variables in: 

Appearance > Settings > Islandora Starter Theme

Bootstrap Settings

Layout

Page layout has been configured for use with this theme and alterations may lead to unexpected results.

Region

In some cases, desired header and footer colors may be darker than the default theme expectations. Apply the “region--dark” class to the following regions to reverse the text color (also make sure “Clean wrapper” is not selected for each of these regions):

  • Header
  • Primary Nav
  • Footer First
  • Footer Second
  • Footer Third

Fonts and Icons

The theme supports any Google font or pairing of Google fonts. You may specify one font for the headings and a different font for the body. The theme default is:

  • Headings (H1 – H6): Roboto Bold
  • Body: Roboto Normal


The theme uses the following font sizes:

  • H1 - 40px
  • H2 - 32px
  • H3 - 28px
  • Body - 16px


Color Scheme

Developer note: theme colors are set in variables.scss and used in colors.scss, but otherwise kept out of the SCSS. This is because colors can be changed in the UI, you can end up with some very strange colors if you set colors outside color.scss as the theme tries to calculate the hex value change without having a defined variable. 

The site color variables available for customization are:

Base

Default: #000000

Used for object page viewer borders (PDF, OpenSeadragon, Video)

Text Color

Default: #1a2747

  • The base text color for the site.
  • Also used for headers 3-6 (H3, H4, H5, H6)

Highlight Color

Default: #dbf5f0

  • The background color used in the header and footer
  • Used as the background color for second-level accordions on newspaper parent pages
  • Used as the secondary button background color, if secondary buttons are used

Secondary Highlight Color

Default: #a4e5e0

  • An additional background color, used for the search bar section and the optional disclaimer footer
  • Used as the secondary accordion border color on newspaper parent pages
  • Used as the secondary button hover background color, if secondary buttons are used

Link Color

Default: #0c6170

  • The primary link color for the site
  • Used for primary button background color
  • Headers 1 and 2 (H1, H2)
  • Text color in the site header and footer

Alternate Link Color

Alternate link color

Default: #0e7e92

  • Used for search header links
  • Used for link hover color

Body

Default: #ffffff

  • Background color for the site
  • Used for button link colors

Borders

Default: #e5e5e5

  • Border color for images, tables, tabs, horizontal rules
  • Used as the breadcrumb separator color
  • Used as the accordion container background on newspaper parent pages 

Borders Light

Default: #f5f5f5

  • Used for pagination button hover background color
  • Used as the accordion background on newspaper parent pages

Logo Image

Upload a custom image to be used in the site header. For optimal layout, the logo image should be close cropped (no extra whitespace) and no wider than 300px. The logo will appear to the left of the site title and in the bottom left of the site footer.

Favicon

Upload a custom image to be used as the favicon.

Site Configuration

Site Settings

Go to Configuration > System > Basic Site Settings to input the following:

  • Site name
  • Slogan (appears beneath Site Name in the header)
  • Email address
  • Path to homepage (e.g., node/1) - do this after you’ve created your Homepage.
  • Path to custom Access Denied (403) or Error (404) pages - do this after you’ve created these custom Basic Pages (optional).

Banner Images

Custom banner images may be uploaded for all pages except search results. Images are uploaded from within the page itself. Navigate to the page, click “edit,” and find the image upload field.

Menu

Links can be added to the top nav menu by going to Structure > Menus > Main Navigation and adding a link.

To add child links:

  1. Go to Structure > Menus > Main Navigation and click “Add link”.
  2. Add your link title and URL. 
  3. Under “Parent link,” select the parent link.
  4. Click “Save.”
  5. Find the parent link and click “edit”.
  6. Check the box for “Show as expanded.”
  7. If you would like the parent menu item to just be a header for a group of child links (i.e., you do not want it to link to any page), put <nolink> in the “Link” field.
  8. Click “Save.”


Social Media Sharing

Social media sharing icons can be added to any page type. These can include any of the services here: https://www.addtoany.com/services/ (which is basically anything except Instagram or YouTube, which do not allow sharing from other sites).

These are configured at Configuration > Web Services > AddToAny.

Once you have added the services you’d like to include, you will control whether they appear on various pages via Structure > Content Type > [select a content type] > Manage Display. On the display edit page, you will see a field called “AddToAny” which you can drag to the “Disabled” region if you do NOT wish for it to appear on pages of that content type. 

Footer Blocks

Fixed Content Blocks

The Footer region contains several customizable “Fixed Content” blocks. These can all be configured from Structure > Block Layout > Custom Block Library > Fixed Blocks.

Contact Information

Under “Block Content” select “Footer: Contact”.

Copyright Date

Under “Block Content” select “Footer: Copyright”.

Social Media Icons

Under “Block Content” select “Footer: Social Media”.

Disclaimer

Under “Block Content” select “Disclaimer”.

Other Blocks

User login 

Enable the user account menu block in: Structure > Block layout > Footer Third > User Account Menu.

Manage Display

Page display is managed from Structure > Content Types > [content type] > Manage Display.

Object and Collection Pages

Manage displays for most object and collection pages, depending on viewer type, at Structure > Content Types > Repository Item > Manage Display.

  • Default - used for objects with no media
  • PDFjs - used for objects with PDFs
  • Binary - used for objects with files (no viewer)
  • Basic - used for objects with images and no viewer
  • Compound object - member - used for layout of the compound child object page aside from the object metadata (e.g., viewers, share icons); the Islandora Object Metadata View is used for configuring compound child fields for display
  • OpenSeadragon - used for objects with images and a viewer
  • Collection - used for the layout of the page above the list of objects in the collection (e.g., title, share icons, description)
  • Paged - used for the parent object of newspaper issues and books


Reordering Fields: Select the applicable display, and drag/drop fields to reorder them. 

Removing Fields: To remove fields from display, drag them under the “Disabled” header.

Adding an Existing Field to the Display: Drag the field from the “Disabled” section into the “Item Description” field group under “Default object detail.” In order for metadata fields to display within the metadata “box” on the object page, the field must be within the “Item Description” group. Otherwise it will display outside of the box.

MAKE SURE TO CLICK THE “SAVE” BUTTON WHEN YOU ARE DONE MAKING CHANGES TO THE DISPLAY!

Compound Parent and Child Metadata

The metadata display for Compound Objects (parents and children) is managed from Structure > Views > Islandora Object Metadata. There are two displays here: "Current" (for child object) and "Parent Object” (for parent).

Reordering Fields: In the Fields section, click the “Add” dropdown and select “Rearrange.” Drag and drop the fields as desired, and click “Apply (this display).”

Removing Fields: In the Fields section, click the field you want to remove. In the modal that opens, click the red “Remove” text.

Adding an Existing Field to the Display: 

  1. In the Fields section, click “Add” in the “Add” dropdown. 
  2. Search for the field you want to add. 
  3. Check the box next to the field name, and click “Apply (this display).” 
  4. In the modal that opens, check the box “Create a label.” 
  5. Add the field label and UNCHECK the box that says “Place a colon after the label.” 
  6. Click “Apply (this display).”


NOTE: Drupal will let you add a field multiple times to the view, so beware! If you think the field isn’t there (but it is, and you just didn’t see it in the list), you can accidentally add it again.

MAKE SURE TO CLICK THE “SAVE” BUTTON WHEN YOU ARE DONE MAKING CHANGES TO THE VIEW!

Search Results

Select which object metadata is displayed as teaser content on the search results and collection pages by going to Structure > Content Types > Repository Item > Manage Display and selecting “Search index.”

Reordering Fields: Select the applicable display, and drag/drop fields to reorder them. 

Removing Fields: To remove fields from display, drag them under the “Disabled” header.

Adding an Existing Field to the Display: Drag the field from the “Disabled” section into the “Search results details” field group. 

MAKE SURE TO CLICK THE “SAVE” BUTTON WHEN YOU ARE DONE MAKING CHANGES TO THE DISPLAY!

Homepage

The Homepage display can’t be managed in the same way as object pages. But you can go into the Homepage node and change (or add/remove) a banner image, edit the header text, and add/edit body text that can appear below the header.

To edit the Homepage node, log in to the site, navigate to the homepage, and click the “edit” tab. You can also click on Content in the black admin menu, search for the homepage node, and click “edit.”

Selecting Collections to Appear on the Homepage

To feature a collection on the homepage (up to 3 collections will show at a time), navigate to the collection and click the “edit” tab. In the right-hand column, click “Promotion Options” and check the box “Promoted to front page.”

This box will automatically be checked for Repository Item nodes categorized as Repository Type=Collection and Model=Collection. The 3 most recently created of these will appear on the Homepage. You can uncheck the box to remove a collection from the homepage.

Basic Pages (Including “Browse Collections”)

Basic Page display (including Browse Collections [aside from the list of collections]) is managed from Structure > Content Types > Basic Page > Manage Display > Default.

Primarily what you can do from this page is remove the social media links (drag the AddToAny field down to the “Disabled” section).

If you’d like to edit the title, banner image, or text of a Basic Page node (this includes the “Browse Collections” page), log in to the site, navigate to the page, and click the “edit” tab.

Adding/Editing Fields and Field Labels

Adding a Custom Field to the Repository Item Content Type

If your metadata contains fields that do not map to any of the default fields available in the Repository Item Content Type (go to Structure > Configuration > Content Types > Repository Item > Manage Fields to see a list of available fields), you can add new fields. It is a multi-step process. 

Add the Field

  1. Go to admin/structure/types/manage/islandora_object/fields (Structure > Content Types > Repository Item > Manage fields) to add custom fields. 
  2. Click “Add Field” and choose the field type you need. NOTE:  If you are adding a field to reference a new taxonomy, choose Reference > Taxonomy Term.
  3. Add a name for the field (“Label”).
    1. If you would like the machine name to match an existing metadata field name (when migrating from another site, for example), you can customize the field name when adding the Label (machine name is to the right of the Label field).
  4. Click “Save and continue.” 
  5. Choose how many values are allowed. Click “Save field settings.”
  6. Check “Required field” if applicable.
  7. Leave “Field visibility and permissions” as-is.
  8. Click “Save settings.”

Organize the New Fields in the Form

  1. Go to structure/types/manage/islandora_object/form_display (Structure > Content Types > Repository Item > Manage form display).
  2. Ensure the new fields aren’t in the “Disabled” area. If so, drag them into the enabled region.
  3. Drag/drop the fields into your preferred order.
  4. If you’d like to group all of your custom fields together: Click “Add field group” > choose “Fieldset” from the dropdown. Give the fieldset a name (e.g., “Custom”). Click “Save and continue.” Drag the custom fields into this fieldset.

Add the Custom Fields to All Displays

  1. Go to admin/structure/types/manage/islandora_object/display (Structure > Content Types > Repository Item > Manage display). The ones that are important for objects are:
    • Default - for objects with no media
    • PDFjs - for PDFs, Video, and Audio
    • Binary - for files (no viewer)
    • Basic - for images with no viewer
    • Compound object - member - used for layout of the page aside from the object metadata (e.g., viewers, share icons); the Islandora Object Metadata View is used for configuring compound child fields for display (see bullet below)
    • Collection - used for the layout of the page above the list of objects in the collection (e.g., title, share icons, description)
    • Open Seadragon - for images w/ viewer
    • Paged - for newspaper issues and books
  2. To update the metadata fields for Compound Objects, go to admin/structure/views/view/islandora_object_metadata (Structure > Views > Islandora Object Metadata > edit), and you need to update both the "Current" (for child object) and "Parent Object" tabs. 
    1. To add a field, click “Add” in the “Fields” section.
    2. Be sure to select the “Create a label” checkbox and add the field label.
    3. To rearrange fields to match the order in the other displays, in the “Fields” section of the view, click the arrow next to the “Add” dropdown and click the option “Rearrange.” Then you can drag/drop the fields into the desired order.

Map the Fields to RDF

New fields need to be mapped to RDF - this requires hand editing of rdf.mapping.node.islandora_object.yml. Each field has its own yaml chunk, e.g., 

field_geographic_subject:  
  properties:
    - 'dcterms:spatial'

or a more complex example -

field_edtf_date_issued:
  properties:
    - 'dcterms:issued'
  datatype_callback:
    callable: 'Drupal\controlled_access_terms\EDTFConverter::dateIso8601Value'

Editing a Field Label

To change a field label (what appears on the front-end), click “Edit” next to the field you want to change and update the Label field.

Editing a Field

Once you create a field, you cannot change the type of field that it is (e.g., you can’t change from a plain text field to a formatted text field). You will need to delete the field and create a new one (in which case any data that is in that field will be lost!).

Up until there is data in the field, you can change the setting for the “Allowed number of values.” Click “Edit” next to the field at /admin/structure/types/manage/islandora_object/fields, and then click “Field settings.” Or click the “edit” dropdown next to the field and then select “Storage settings.”

Deleting a Field

Do NOT delete fields that you did not create custom for your site. Deleting a field that is part of the Islandora defaults can break your site.

To delete a custom field that you added, go to /admin/structure/types/manage/islandora_object/fields, click the “edit” dropdown and select “Delete.” On the following screen, click the “Delete” button.

Adding a Collection

Collection pages can be created manually or migrated in via Workbench. (If you create the collection via Workbench, you will need to add a banner image manually within the node in Drupal.) To manually create a Collection page:

  1. Go to Content > Add Content > Repository Item.
  2. Set Resource Type as “Collection” and Model as “Collection.”
  3. Add collection metadata into the relevant fields.
    • To add a banner image: Upload an image to the Main Banner field. Images must be larger than 1280x400 pixels.
    • To add a description to appear above the list of objects: Add text to the Description field.
  4. Click “Save.”


Collections need thumbnails added separately:

  1. In the collection node, click the Media tab and upload an image, setting the Media Use to “Thumbnail Image.”
  2. Thumbnail images should be 650x650 (or 550x550 minimum), square.

Adding an Object

Objects can be created manually or migrated in via Workbench. (If you create the certain object pages via Workbench, you will need to add a thumbnail image manually within the node in Drupal.) To migrate objects using Workbench, see the separate documents “Prepare Metadata for Ingest into Islandora 8 with Workbench” and “Islandora 8: Migrating Metadata with Workbench.”

To manually create an object page:

Create the Node

  1. Go to Content > Add Content > Repository Item.
  2. Set the Resource Type and Model following the table shown below under Object Configuration. 
  3. Add object metadata into the relevant fields.
  4. If your object includes media that requires a viewer, make sure to choose a viewer in the “Display Hints” field.
    • Open Seadragon: Used for jpg, tiff, png
    • PDFjs: Used for PDF
  5. Click “Save.”

Add the Media

  1. In the object node, click the Media tab, and then click “Add Media.”
  2. Select the type of media you are uploading. NOTE: “File” must be used for TIFFs.
  3. Upload your file, and set the Media Use to “Original File.”
  4. Click “Save.”
  5. Thumbnail derivatives (and OCR derivatives for PDFs) will be automatically created.

Add Thumbnails

Audio, Video, Book (parent), Newspaper (parent), and Compound Object (parent) need thumbnails added separately:

  1. In the object node, click the Media tab, and then click “Add Media.”
  2. Upload an image, setting the Media Use to “Thumbnail Image.”
  3. Thumbnail images should be 650x650 (or 550x550 minimum), square.

Regenerating an Object’s Derivatives

In order to regenerate derivatives for an object’s media file, you will need to delete and then re-upload the media file. (Selecting the object from the list at admin/content and then choosing an Action from the dropdown list - e.g., “Image - Generate a thumbnail from an original file” - and clicking “Apply to selected items” does not seem to work.)

  1. Log in to the site and navigate to the object. Click the “Media” tab.
  2. Select all media files on the list, ensure “Delete media and file(s)” is showing in the Action dropdown, and click “Apply to selected items.”
  3. On the confirmation screen, click “Delete.”
  4. Click the “Add Media” button and re-upload your media file, ensuring that Media Use is set to “Original File.”

Adding or Editing an Object’s Thumbnail

Thumbnails should be PNG, JPEG or GIF images.

A thumbnail image can either be generated automatically from a media file whose Media Use type is “Original File,” or it can be uploaded separately.

To generate a thumbnail image from an original file: Upload the .pdf, .tiff, .png, .jpeg, or .mp4 file and set the Media Use as “Original File.” A thumbnail image will automatically be generated.

To add a thumbnail image manually: Follow the process outlined in the “Add thumbnails” section above.

To edit a thumbnail image: 

  • If the thumbnail image was automatically generated: Delete all the media files associated with the object, re-upload the original file and have the derivatives regenerate.
  • If you uploaded the thumbnail image manually: Delete the thumbnail image file and re-upload a new one with Media Use set to “Thumbnail Image.”


Object Configuration

Objects (and collections) are all Repository Item nodes. To ensure each object is displayed as desired, the theme relies on the following combinations of Resource Type and Model terms. The object must also have a Display Hint selected (PDFjs or Open Seadragon) if a viewer is required.

Object Type

Resource Type term

System Model term

Collection

Collection

Collection

Audio

Sound

Audio

Basic Image (jpg)

Still Image

Image

Binary

[any]

Binary

Book (parent of pages)

Collection

Paged Content

Compound Object

Collection

Compound Object [new term]

Large Image (tiff)

Still Image

Image

Newspaper (parent of issues)

Collection

Newspaper [new term]

Newspaper Issue (parent of pages)

Collection

Publication Issue

Newspaper Page

Text

Page

Page

Text

Page

PDF

[any]

Digital Document

Video

Moving Image

Video

Creating Content Pages

Homepage

A homepage is required. To create the homepage:

  • Go to Content > Add Content > Home Page. 
    • Title (e.g., Explore the Collection)
    • Banner Image (optional)

The homepage also uses the Featured Collections view as a block to display collections that have been “Promoted to homepage”.

Browse Collections

The Browse Collections page is a Basic Page that uses the Featured Collections view to display all top-level collections on the site. To create the Browse Collections page:

  • Go to Content > Add Content > Basic Page.
    • Title (Browse Collections) - the URL for this page must be /browse-collections in order for the view to work.
    • Banner Image (optional)

Basic Pages

Basic Pages can hold any of your static page content. To create a Basic Page:

  • Go to Content > Add Content > Basic Page.
    • Title
    • Banner image (optional)
    • Add content to the WYSIWYG and apply various styles (h2, h3, links, italic, bold, underline, etc.)

Configuring Global Search and Faceting

Configuring Sort Options

By default, the fields used in the “sort” dropdown on search results and collection pages are “Relevance” (not a field in the object node, but calculated by Solr), “Date Created,” and “Title.” These fields can be changed, and additional fields can be added, but code changes are required to accomplish this. In addition to the code changes, however, you will also need to update what is listed in “Sort Criteria” within the Solr Search Content view (both displays). To do that, follow these steps:

  1. Navigate to the Solr Search Content View: Structure > Views > Solr Search Content > edit 
  2. There are two tabs (Displays) here: Site Search: Global Search and Site Search: Collections. On each tab, look at the “SORT CRITERIA” section to see what fields are being used in the sort dropdown.
  3. To add a field, click “Add” in the SORT CRITERIA section.
  4. Select the field to add, and click “Apply (all displays).”
  5. In the modal that appears, check the box “Expose this sort to visitors, to allow them to change it”. Click “Apply (all displays).”
  6. To remove a field, click the relevant field in the SORT CRITERIA section, and then click “Remove.”
  7. Click the “Save” button before leaving the page!

Indexing Fields

To add fields to the list indexed by Solr:

  1. Go to Configuration > Search and Metadata > Search API > Default Solr content index and click “edit”.
  2. Click the “Fields” tab.
    1. This is where you will see which fields are being indexed, and their “Boost” number. 
    2. You can add, remove, or edit fields here (including increasing or decreasing - or adding - a Boost number). 
  3. To add a field, click the “Add fields” button. Select the field and click “Add.” You can select more than one. Click “Done” when you’re finished.
  4. Click “Save changes” before leaving the page!

Reindexing Content

If you add (or remove) fields to be indexed in Solr, you can trigger a re-index of the site content by doing the following:

  1. Go to Configuration > Search and Metadata > Search API and click “Default Solr content index.”
  2. In the “Start Indexing Now” section, update the batches from “50” to “100” and click the “Index now” button.

Configuring Facets

The following assumes that all fields you are faceting on have been added as indexed fields via Configuration > Search and Metadata > Search API.

  • Go to Configuration > Search and Metadata > Facets.
    • Here you will define the facets to be made available for search and for collections. The facets need to be defined twice - once in each place (“facet source”). Add your facets to the “...block_1” facet source  and to the “...page_1” facet source. 
      • Source machine name = search_api:views_block__solr_search_content__block_1: Corresponds to Collections
      • Source machine name = search_api:views_page__solr_search_content__page_1: Corresponds to Global Search
    • Click “Add facet.” Select the field you want to use for a facet. If you can’t find the field, you will need to add it to the list of indexed fields before you complete this step. 
      • In “List of Links” settings: 
        • Decide whether to “Show the amount of results.” 
        • Decide where to set a “Soft Limit”. 
      • You may need to check the box “Transform entity ID to label” when creating the facet.
      • Everything else can be left as-is. Click “Save.”
  • Add the facets to the Summary (you will need to do this for BOTH the block_1 and page_1 facet sets). 
    • Click “Summary.” You will go to a URL like admin/config/search/facets/facet-summary/facet_summary/edit. 
    • Check the box next to each facet you want to use.
    • Ensure the label is correct for each.
    • Under “Facet Summary Settings” ensure “Show a text when there are no results” box is checked.
    • Click “Save.”
    • NOTE: To change the name of the facets summary block that will appear in the left sidebar (and will indicate the selected facet[s]), click the Facet Summary Settings tab from within the Facets Summary and update the Name.
  • Go to Configuration > Views > Solr Search Content, and click “edit” (/admin/structure/views/view/solr_search_content). This is where you add the facets to the search and collection pages. You will need to update BOTH displays for this view (Site Search: Global Search and Site Search: Collections). Follow the steps below for both displays.
    • Under Filter Criteria, click “Add” and select “Facets Summary”. Select “Apply (this display)” and save. Then click “Add” and select “Facets”. Select “Apply (this display)” and save.
    • You will now see Index Default Solr content index: Facets summary and Index Default Solr content index: Facets under Filter Criteria. Click “Index Default Solr content index: Facets” and check the boxes next to each field that should appear as a facet in that display. Click “Apply (this display)”.
    • Click “Save”
    • Follow these steps again for the Site Search: Collection display.
  • The order in which the facets will appear on search results and collection pages is determined at Configuration > Search and Metadata > Facets (admin/config/search/facets).
  • To edit the Label of a previously made facet, go to the facet > Facet Settings tab.


If the “Reset” link isn’t showing for Facet Summaries, go to Configuration > Search and Metadata > Facets and click “edit” next to each “Facet Summary” (/admin/config/search/facets/facet-summary/facet_summary/edit). Under “Facet Summary Settings” click the box next to “Adds facet reset link”.

Nested Facets

  1. Add the facet following the instructions above (make sure the field is indexed first, and reindex the site after adding as an indexed field). But note the following:
    1. Set the facet as “Dropdown” (not “List of links”). You will also need to select “Ensure that only one result can be displayed.”
    2. Leave “Default option label” as “Choose.”
    3. Select “Use hierarchy.”
    4. Select “Always expand Hierarchy.”
  2. Click “Save.”
  3. Add the facet to the Summary, as directed above.
  4. Go to admin/config/search/search-api/index/default_solr_index/processors > Index Hierarchy tab and check the box for the field you want to use nested facets with.

Managing Users

Users in Islandora are assigned a “role” that determines the level of access and permissions.

The roles configured by default are:

  • administrator - the most powerful (and dangerous) role - can do anything - be careful!
  • fedoraAdmin - this role is required by Islandora for anyone who is adding/editing objects or media.
  • authenticated user - viewing is allowed by object and collection policy - no editing or management permissions.


Users  can be created by navigating to People > Add User - once the user has been created, an Administrator needs to manage that user’s permissions to set their allowed level of access. New users default to “Authenticated User” unless an Administrator reassigns them. “Authenticated Users” cannot edit anything, but object policies can be set to allow Authenticated Users to see content that anonymous users cannot (see “Setting Access Policies on Objects” below). 

Manage users from the “People” admin menu.


Setting Access Policies on Objects

Access may be restricted at the object level using the Islandora Access taxonomy. This functionality may need to be enabled, though it is in the base site install.

By default, the Islandora Access taxonomy has the following terms:

  • Admin-only access: objects can only be viewed and downloaded by Admin users
  • Differential access - limited: objects or media are only viewable by Authenticated users but not downloadable; objects/media are only downloadable by Admin users.
  • Differential access - open: objects or media are viewable by anonymous users but not downloadable. Objects/media are only downloadable by Admin users.
  • Limited access: objects can only be viewed and downloaded by Authenticated users, metadata isn't searchable by anonymous users. Anonymous users don't see the node and can't find it through search.
  • Open access: this is the default; this term does not need to be added to objects in order for them to show and be downloadable by anonymous users


To set a policy on an object, follow these steps:

  • If you are importing the object via Workbench: Add a column to your ingest CSV called field_access_terms. Find the term ID associated with the access term you would like to use by going to Structure > Taxonomy > Islandora Access and clicking “edit” next to the term. Look in the browser bar and you will see a URL like https://your-site.com/taxonomy/term/97/edit. The number after term/ is the term ID that you will include in the field_access_terms column of your CSV ingest sheet.
  • If you are adding the object into Drupal manually: Within the Repository Item node edit form, scroll down to the “Access Control” section. Check the box for the term you would like to apply. Click “Save.”

Redirects from Old URLs to New URLs

Configuration > Search and Metadata > URL redirects 

To add a single redirect, click “Add redirect.”  In the “From” field, put the old slug without a pre-slash (without the site’s root). In the “To” field, use the new slug with a pre-slash to where it should go. 

To bulk-upload redirects, go to Configuration > Search and Metadata > URL redirects > Import. Here you can upload a CSV with the following information (only include these columns, in this exact order):

  • From URL - the old URL (must have the same root URL as the new URL; do not include the site’s root - i.e., only include what comes after the first “/”)
  • To URL - the new URL (do not include the site’s root - i.e., only include what comes after the first “/”)
  • Redirect Status - will always be: 301

Redirect Language - will always be: en



All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.