FL-Islandora Glossary

From FIG

Jump to: navigation, search
The FIG wiki has moved to a LibGuide at http://falsc.libguides.com/FL-Islandora/Guide_home . Please update any links you maintain and link to the new location. If any information is missing from the new guide, or if you have any feedback you would like to share regarding the new FIG LibGuide, please email to help@flvc.org and let us know!
The specific information previously maintained on this page can now be found at http://falsc.libguides.com/FL-Islandora/Glossary .
FL-Islandora Guides (FIG)
FL-Islandora Overview
User Interface
Permissions and users
Collection Creation and Management
Content models
Creating Content Objects
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
  • Breadcrumbs: or breadcrumb trail is a website navigation tool consisting of a series of clickable horizontal links that display a page searching/viewing history.

  • Content Model: Content models describe the characteristics of objects in the Fedora repository.

  • 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 datasteams; for example, a collection object has a collection policy Datastream, while an image might contain a thumbnail Datastream.

  • Fedora Commons (Repository Software): Fedora (Flexible Extensible Digital Object Repository Architecture) is an open source architecture for storing, managing, and accessing digital content in the form of digital objects.

  • FL-Islandora: FL-Islandora is FLVC’s implementation of Islandora software. It is somewhat different from the “basic” Islandora open source software in that FLVC has customized the software to some extent to meet our users’ needs. At the same time, FL-Islandora code still utilizes the main Islandora software code base.

  • FL-Islandora “sites”: Each college or university that uses FL-Islandora has its own FL-Islandora “site” or website (similar to a Drupal “site). Each site has its own branding and theming, its own set of collections and users/logins. Their materials appear separately in that site. At the same time, all sites share one Fedora Commons repository and one instance of FL-Islandora software. By using unique Islandora “namespaces” or prefixes FL-Islandora is able to display objects in separate institutional FL-Islandora sites.

  • IID (item identifier): In the FL-Islandora implementation, exactly one identifier with type “IID” (Item Identifier) is required in the MODS metadata of each content object. The value of the IID identifier must be unique in the system. The inclusion of additional Identifiers in the MODS record are allowed, but they must be of a different type value than IID. The IID is intended to be an identifier meaningful to the institution outside of the Islandora system. Note that FL-Islandora will create a PURL (Persistent URL) from the IID. Valid IID characters are limited to alphanumeric, underscore, hyphen, period, and parentheses.

  • Islandora Collection/Collection Object: Collections are a way of grouping related objects together in Fedora. They function much like directories on a computer; a collection can “contain” any number of related objects and sub-collections. Everything stored in Fedora is an object, including collections.

  • Islandora Persistent Identifier (PID): Every object in a Fedora repository has a unique persistent identifier of the format namespace:ID. This identifier is assigned when the object is created, and cannot be changed.

  • Islandora namespace: The namespace is a component of the persistent identifier (namespace:ID). The namespace is defined in the collection policy, and will then be used to generate PIDs for the objects ingested into that collection. Note: It is FL-Islandora policy that all namespaces within an FL-Islandora site be consistent. To determine the namespaces that should be used in your site, click on your site's "Home" button/options and you will see a URL that ends with [code]%3Aroot, that is [code:root], e.g., fsu:root on the FSU production site. That "code:" is the namespace that you should use for all objects on your site.

  • MODS (Metadata Object Description Schema): Metadata Object Description Schema (MODS) is a schema for a bibliographic element set that may be used for a variety of purposes, and particularly for library applications. The Library of Congress' Network Development and MARC Standards Office, with interested experts, developed the Metadata Object Description Schema (MODS) in 2002 for a bibliographic element set that may be used for a variety of purposes, and particularly for library applications. As an XML schema it is intended to be able to carry selected data from existing MARC 21 records as well as to enable the creation of original resource description records. It includes a subset of MARC fields and uses language-based tags rather than numeric ones, in some cases regrouping elements from the MARC 21 bibliographic format.

  • OBJ datastream: This is the original file loaded into Islandora to create a content object. A variety of derivative datastreams may be created from the original file, depending on the object’s Content Model, and stored with the Islandora object.

  • PURL (Persistent Uniform Resource Locator): a Web address that acts as a permanent identifier for an object. In FL-Islandora PURLs are created at the time of loading and are stored in the MODS descriptive metadata and displayed to the public with the label “Persistent Link to This Record”. FL-Islandora PURLs are stored on FLVC’s PURL server. A content object can be deleted and reloaded, and while deletion and reloading changes the object’s PID, the object’s PURL should not change.

  • RELS-EXT datastream: The RELS-EXT, or external relationships datastream, stores information about an Islandora object (its PID and Content Model) and its relationships to other Islandora objects, notably the collection(s) and object belongs to.

  • XACML Policies / Object Policies: "XACML Policies" are a Fedora standard for implementing access control policies (in Islandora terms Object Policies) that can limit viewing and management of Islandora objects to logged-in users assigned to specific Islandora user roles. They are written in eXtensible Access Control Markup Language. XACML or Object Policies are implemented via the "Object Policy" tab in a collection or content object. For details, see Suppressing collections and content from view.
Personal tools