Struts 1.02 Oracle Database, Search and Persistence frameworks JBoss on Windows • Challenges Domain specific knowledge needed for development Proprietary software limits ability to leverage the community Bolting on partial solutions can become problematic
code Thousands of modules help reduce development time Lower barrier to entry to encourage participation • UCLA Library move to Drupal CMS shift to Drupal within UCLA Library increases local expertise • Trend towards Drupal on campus Shift from Plone to Drupal in other departments
Assets and metadata stored only in Fedora repository Limits which Drupal modules can be used out of the box • Leveraging the Drupal community Harnessing the collective power of Drupal ecosystem is limited • Option: Make Islandora more Drupal-ish? Yep, we sure can!
Sync Workflow Islandora Modules Drupal Modules 1) User updates an Islandora object, saves data to Fedora 2) With Islandora Sync enabled, hooks are fired to populate native Drupal entities with Fedora data Views Services Gallery Gmap Basic Image Large Image Book PDF Audio Video
The UCLA Digital Library is the gatekeeper for our Fedora instance Changes via processes outside of Islandora might not be sync’d • One way sync Initial use cases placed most weight on Fedora to Drupal direction Hooks in place for Drupal push to Fedora • Scalability Still need to tweak Drupal for performance for large imports
By lowering barrier, we hope to encourage increased development • Continued improvement of core code Goal to contribute regular development to support roll into Islandora core • Increased Drupal Features packages MODS image mapping example is available now