-
Notifications
You must be signed in to change notification settings - Fork 0
Home
We are grateful for the excellent work in Islandora 2.0! But, in reviewing our functional requirements, we just didn't need it all. Islandora Lite is an UTSC-developed implementation of Islandora that does not use Fedora and is motivated by the following values and goals. In Summer 2021 we are in a prototyping phase. The following documentation is a work in progress.
- Adhere to Drupal’s way of doing things (work with 5,862 modules)
- Prefer modular to monolithic out of the box.
- Consider accessibility first.
- Prioritize and test for multilingual support.
- Focus on supporting migration from an Islandora 7 multisite before derivative creation.
- Preservation is practice, not software. We will monitor the health of content in the system using checksum checking and will serialize to a OCFL object that complies with the bagit specification.
- We will maintain a playbook to simplify deployment and testing for us and others.
In this first phase (2021) we are focused on how to bring content from an Islandora 7 repository into Drupal 9 starting with Fedora 3.x’s native atom.zip exports, processing them using Python in Jupyter Notebooks, and then importing them using the Islandora Workbench integration.
- Drupal uses the concepts of 'entities' and 'files'.
- All entities have 'IDs' and 'UUIDs'.
- Entities are grouped in 'bundles' ('nodes' and 'taxonomies' are bundles). These also have IDs and UUIDs.
- 'media' entities hold 'files'.
- Files can have fields that are indexed.
- Nodes know about all their entities (including media entities).
- Media entities know about their files.
- Entities can reference each other.
We maintain Islandora_Lite_Defaults. The default content type is installed and cloned. You can further clone and adjust content types as needed, reusing the entities that Islandora_Lite_Defaults installs.
Nodes that contain repository content have descriptive metadata, and contain Media entities. Nodes know about their media entities. Media entities have files, and the files have fields containing file-specific information, including technical metadata.
Like all Drupal content types, the Islandora Lite content type has options to configure how it displays. This is where viewers are configured for each content type. For viewers to become available to the content type configuration, they must be configured as display modes in media type and content type displays. Users can select to apply the desired view mode when creating/editing the content.
- Drupal 9 installation
- View Mode Switch
- Ark Minting and Binding Service
- Triple-store Indexer