hyrax-iiif_av 0.1.0 → 0.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA1:
-  metadata.gz: 7175259d686db59f6e4d217489dc482160627417
-  data.tar.gz: 625d46c52ad2e322f43404ce59d463e2a2fa66a1
+SHA256:
+  metadata.gz: 155e529eda163eb4a1783739f0a2e3fd42315f1768a8448f5186b9e2ee6edd89
+  data.tar.gz: fb381ed8f314b4b88a1c4d7b626d08576bd7044ba97360047b08b229e687a2e2
 SHA512:
-  metadata.gz: 84d57cae07a601937a22832fe3591b3303de66f766bdc1fafec4a03f7baa588761c7c28f271650918d9c90da6444d2f2476fb12c85a1a66c78c9a3a39b6b9eb1
-  data.tar.gz: c5f7569a394a53b5de49406402cb30d3d26cd741a97b3a0810651726e9f9ecf8f1ac2f406869d7ba3b0f2b1c2b7e8225baaa5f4435ca04012bcf25c74ced2aaa
+  metadata.gz: a3622bb4c1657924c6c66667d4ad53148d4c4fc159ff4236583b1a4faf099ccbac562ed51f1fcd707cc7a910d537724ebfb511e2945f2c93497a6e81c090f6ea
+  data.tar.gz: d360b921021bc1fb1369d9a10787ec5aab50386efa7667365089afe82e704940d9ea19ac9c9180c0bc7e7da98b50e821160f8bf1f4e9275c62d5379d3265ea9c

data/.circleci/config.yml

@@ -0,0 +1,48 @@
+version: 2.1
+orbs:
+  samvera: samvera/circleci-orb@1.0
+jobs:
+  bundle_and_test:
+    parameters:
+      ruby_version:
+        type: string
+        default: 2.5.5
+      bundler_version:
+        type: string
+        default: 2.3.0
+        
+    executor:
+      name: 'samvera/ruby_fcrepo_solr'
+      ruby_version: << parameters.ruby_version >>
+      solr_version: 7-slim
+
+    working_directory: ~/project
+
+    environment:
+      ENGINE_CART_RAILS_OPTIONS: --skip-git --skip-bundle --skip-listen --skip-spring --skip-yarn --skip-keeps --skip-coffee --skip-puma --skip-test
+      
+    steps:
+      - samvera/cached_checkout
+          
+      - samvera/bundle:
+          ruby_version: << parameters.ruby_version >>
+          bundler_version: << parameters.bundler_version >>
+    
+      - samvera/engine_cart_generate:
+          cache_key: v2-internal-test-app-{{ checksum "hyrax-iiif_av.gemspec" }}-{{ checksum "spec/test_app_templates/lib/generators/test_app_generator.rb" }}-{{ checksum "lib/generators/hyrax/iiif_av/install_generator.rb" }}
+
+      - samvera/install_solr_core:
+          solr_config_path: .internal_test_app/solr/conf
+
+      - samvera/bundle:
+          ruby_version: << parameters.ruby_version >>
+          bundler_version: << parameters.bundler_version >>
+          
+      - samvera/parallel_rspec
+
+workflows:
+  ci:
+    jobs:
+      - bundle_and_test:
+          name: ruby2-7
+          ruby_version: 2.7.5

data/.github/workflows/release.yml

@@ -0,0 +1,33 @@
+name: Release Gem
+on:
+  workflow_dispatch:
+  push:
+    tags:
+      - -v*
+
+jobs:
+  push:
+    if: github.repository == 'samvera-labs/hyrax-iiif_av'
+    name: Push gem to RubyGems.org
+    runs-on: ubuntu-latest
+
+    permissions:
+      id-token: write # IMPORTANT: this permission is mandatory for trusted publishing
+      contents: write # IMPORTANT: this permission is required for `rake release` to push the release tag
+
+    environment: release
+    
+    steps:
+      # Set up
+      - uses: actions/checkout@v5
+        with:
+          persist-credentials: false
+      - name: Set up Ruby
+        uses: ruby/setup-ruby@v1
+        with:
+          bundler-cache: true
+          ruby-version: ruby
+
+      # Release
+      - uses: rubygems/release-gem@v1
+

data/.gitignore

@@ -4,3 +4,4 @@ pkg/
 Gemfile.lock
 .internal_test_app
 .byebug_history
+vendor/bundle/**

data/.rubocop.yml

@@ -2,7 +2,7 @@ inherit_gem:
   bixby: bixby_default.yml
 
 AllCops:
-  TargetRubyVersion: 2.3
+  TargetRubyVersion: 2.4
   DisplayCopNames: true
 
 Naming/FileName:
@@ -20,7 +20,11 @@ Metrics/BlockLength:
     - 'lib/hyrax/iiif_av/spec/shared_specs/displays_content.rb'
     - 'lib/hyrax/iiif_av/spec/shared_specs/displays_iiif_av.rb'
     - 'spec/controllers/generic_works_controller_spec.rb'
+    - 'spec/controllers/iiif_av_controller_spec.rb'
+    - 'spec/factories/users.rb'
     - 'spec/helpers/iiif_av_helper_spec.rb'
+    - 'spec/requests/auth_controller_behavior_spec.rb'
+    - 'spec/support/features/session_helpers.rb'
 
 RSpec/VerifiedDoubles:
   Exclude:
@@ -31,3 +35,15 @@ RSpec/VerifiedDoubles:
 RSpec/ExampleLength:
   Exclude:
     - 'lib/hyrax/iiif_av/spec/shared_specs/displays_content.rb'
+
+Metrics/ModuleLength:
+  Exclude:
+    - 'app/presenters/concerns/hyrax/iiif_av/displays_content.rb'
+
+Metrics/MethodLength:
+  Exclude:
+    - 'app/presenters/concerns/hyrax/iiif_av/displays_content.rb'
+
+Rails/OutputSafety:
+  Exclude:
+    - 'app/controllers/hyrax/iiif_av/iiif_av_controller.rb'

data/CONTRIBUTING.md

@@ -0,0 +1,181 @@
+# How to Contribute
+
+We want your help to make the Samvera community great. There are a few guidelines
+that we need contributors to follow so that we can have a chance of
+keeping on top of things.
+
+## Code of Conduct
+
+The Samvera Community is dedicated to providing a welcoming and positive
+experience for all its members, whether they are at a formal gathering, in
+a social setting, or taking part in activities online. Please see our
+[Code of Conduct](CODE_OF_CONDUCT.md) for more information.
+
+## Language
+
+The language we use matters. Today, tomorrow, and for years to come
+people will read the code we write. They will judge us for our
+design, logic, and the words we use to describe the system.
+
+Our words should be accessible. Favor descriptive words that give
+meaning while avoiding reinforcing systemic inequities. For example,
+in the Samvera community, we should favor using allowed_list instead
+of whitelist, denied_list instead of blacklist, or source/copy
+instead of master/slave.
+
+We're going to get it wrong, but this is a call to keep working to
+make it right. View our code and the words we choose as a chance to
+have a conversation. A chance to grow an understanding of the systems
+we develop as well as the systems in which we live.
+
+See [“Blacklists” and “whitelists”: a salutary warning concerning the
+prevalence of racist language in discussions of predatory
+publishing](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6148600/) for
+further details.
+
+## Contribution Tasks
+
+- Reporting Issues
+- Making Changes
+- Documenting Code
+- Committing Changes
+- Submitting Changes
+- Reviewing and Merging Changes
+
+### Reporting Issues
+
+- Make sure you have a [GitHub account](https://github.com/signup/free)
+- Submit a [Github issue](https://github.com/samvera-labs/hyrax-iiif_av/issues/) by:
+  - Clearly describing the issue
+    - Provide a descriptive summary
+    - Explain the expected behavior
+    - Explain the actual behavior
+    - Provide steps to reproduce the actual behavior
+
+### Making Changes
+
+- Fork the repository on GitHub
+- Create a topic branch from where you want to base your work.
+  - This is usually the `main` branch.
+  - To quickly create a topic branch based on `main`; `git branch fix/main/my_contribution main`
+  - Then checkout the new branch with `git checkout fix/main/my_contribution`.
+  - Please avoid working directly on the `main` branch.
+  - Please do not create a branch called `master`. (See note below.)
+  - You may find the [hub suite of commands](https://github.com/defunkt/hub) helpful
+- Make sure you have added sufficient tests and documentation for your changes.
+  - Test functionality with RSpec; Test features / UI with Capybara.
+- Run _all_ the tests to assure nothing else was accidentally broken.
+
+NOTE: This repository follows the [Samvera Community Code of Conduct](https://samvera.atlassian.net/wiki/spaces/samvera/pages/405212316/Code+of+Conduct)
+and [language recommendations](#language).
+Please **_do not_** create a branch called `master` for this repository or as part of
+your pull request; the branch will either need to be removed or renamed before it can
+be considered for inclusion in the code base and history of this repository.
+
+### Documenting Code
+
+- All new public methods, modules, and classes should include inline documentation in [YARD](http://yardoc.org/).
+  - Documentation should seek to answer the question "why does this code exist?"
+- Document private / protected methods as desired.
+- If you are working in a file with no prior documentation, do try to document as you gain understanding of the code.
+  - If you don't know exactly what a bit of code does, it is extra likely that it needs to be documented. Take a stab at it and ask for feedback in your pull request. You can use the 'blame' button on GitHub to identify the original developer of the code and @mention them in your comment.
+  - This work greatly increases the usability of the code base and supports the on-ramping of new committers.
+  - We will all be understanding of one another's time constraints in this area.
+- [Getting started with YARD](http://www.rubydoc.info/gems/yard/file/docs/GettingStarted.md)
+
+### Committing changes
+
+- Make commits of logical units.
+- Check for unnecessary whitespace with `git diff --check` before committing.
+- Make sure your commit messages are [well formed](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+- If you created an issue, you can close it by including "Closes #issue" in your commit message. See [Github's blog post for more details](https://github.com/blog/1386-closing-issues-via-commit-messages)
+
+```
+    Present tense short summary (50 characters or less)
+
+    More detailed description, if necessary. It should be wrapped to 72
+    characters. Try to be as descriptive as you can, even if you think that
+    the commit content is obvious, it may not be obvious to others. You
+    should add such description also if it's already present in bug tracker,
+    it should not be necessary to visit a webpage to check the history.
+
+    Include Closes #<issue-number> when relavent.
+
+    Description can have multiple paragraphs and you can use code examples
+    inside, just indent it with 4 spaces:
+
+        class PostsController
+          def index
+            respond_to do |wants|
+              wants.html { render 'index' }
+            end
+          end
+        end
+
+    You can also add bullet points:
+
+    - you can use dashes or asterisks
+
+    - also, try to indent next line of a point for readability, if it's too
+      long to fit in 72 characters
+```
+
+- Make sure you have added the necessary tests for your changes.
+- Run _all_ the tests to assure nothing else was accidentally broken.
+- When you are ready to submit a pull request
+
+### Submitting Changes
+
+- Read the article ["Using Pull Requests"](https://help.github.com/articles/using-pull-requests) on GitHub.
+- Make sure your branch is up to date with its parent branch (i.e. main)
+  - `git checkout main`
+  - `git pull --rebase`
+  - `git checkout <your-branch>`
+  - `git rebase main`
+  - It is a good idea to run your tests again.
+- If you've made more than one commit take a moment to consider whether squashing commits together would help improve their logical grouping.
+  - [Detailed Walkthrough of One Pull Request per Commit](http://ndlib.github.io/practices/one-commit-per-pull-request/)
+  - `git rebase --interactive main` ([See Github help](https://help.github.com/articles/interactive-rebase))
+  - Squashing your branch's changes into one commit is "good form" and helps the person merging your request to see everything that is going on.
+- Push your changes to a topic branch in your fork of the repository.
+- Submit a pull request from your fork to the project.
+
+### Reviewing and Merging Changes
+
+We adopted [Github's Pull Request Review](https://help.github.com/articles/about-pull-request-reviews/) for our repositories.
+Common checks that may occur in our repositories:
+
+1. [CircleCI](https://circleci.com/gh/samvera) - where our automated tests are running
+2. RuboCop/Bixby - where we check for style violations
+3. Approval Required - Github enforces at least one person approve a pull request. Also, all reviewers that have chimed in must approve.
+4. CodeClimate - is our code remaining healthy (at least according to static code analysis)
+
+If one or more of the required checks failed (or are incomplete), the code should not be merged (and the UI will not allow it). If all of the checks have passed, then anyone on the project (including the pull request submitter) may merge the code.
+
+_Example: Carolyn submits a pull request, Justin reviews the pull request and approves. However, Justin is still waiting on other checks (CI tests are usually the culprit), so he does not merge the pull request. Eventually, all of the checks pass. At this point, Carolyn or anyone else may merge the pull request._
+
+#### Things to Consider When Reviewing
+
+First, the person contributing the code is putting themselves out there. Be mindful of what you say in a review.
+
+- Ask clarifying questions
+- State your understanding and expectations
+- Provide example code or alternate solutions, and explain why
+
+This is your chance for a mentoring moment of another developer. Take time to give an honest and thorough review of what has changed. Things to consider:
+
+- Does the commit message explain what is going on?
+- Does the code changes have tests? _Not all changes need new tests, some changes are refactorings_
+- Do new or changed methods, modules, and classes have documentation?
+- Does the commit contain more than it should? Are two separate concerns being addressed in one commit?
+- Does the description of the new/changed specs match your understanding of what the spec is doing?
+- Did the Continuous Integration tests complete successfully?
+
+If you are uncertain, bring other contributors into the conversation by assigning them as a reviewer.
+
+# Additional Resources
+
+- [General GitHub documentation](http://help.github.com/)
+- [GitHub pull request documentation](https://help.github.com/articles/about-pull-requests/)
+- [Pro Git](http://git-scm.com/book) is both a free and excellent book about Git.
+- [A Git Config for Contributing](http://ndlib.github.io/practices/my-typical-per-project-git-config/)

data/README.md

@@ -1,43 +1,40 @@
 # hyrax-iiif_av
 Hyrax plugin for IIIF Presentation 3.0 Audiovisual support
 
-# Steps to use this plugin
-1. Include controller mixin in your model controller:
-```ruby
-# Generated via
-#  `rails generate hyrax:work GenericWork`
-module Hyrax
-  # Generated controller for GenericWork
-  class GenericWorksController < ApplicationController
-    # Adds Hyrax behaviors to the controller.
-    include Hyrax::WorksControllerBehavior
-    include Hyrax::BreadcrumbsForWorks
-    include Hyrax::IiifAv::ControllerBehavior
-    self.curation_concern_type = ::GenericWork
-
-    # Use this line if you want to use a custom presenter
-    self.show_presenter = Hyrax::GenericWorkPresenter
-  end
-end
+# How to use this plugin
+1. Add `hyrax-iiif_av` to your `Gemfile` and `bundle install`
+
+2. Run generator passing your work type:
+```
+rails g hyrax:iiif_av:add_to_work_type MyWorkType
 ```
+Notice that this generator includes mixins in the work controller and work show presenter.
 
-2. Setup work presenter:
-```ruby
-# Generated via
-#  `rails generate hyrax:work GenericWork`
-module Hyrax
-  class GenericWorkPresenter < Hyrax::WorkShowPresenter
-    include Hyrax::IiifAv::DisplaysIiifAv
-
-    Hyrax::MemberPresenterFactory.file_presenter_class = Hyrax::IiifAv::IiifFileSetPresenter
-
-    # Optional override to select iiif viewer to render
-    # default :avalon for AV, :universal_viewer for images
-    def iiif_viewer
-      :universal_viewer
-    end
-  end
-end
+3. (Optional) Run avalon player generator:
 ```
+rails g hyrax:iiif_av:install_avalon_player
+```
+This will install `webpacker`, `react-rails`, and the avalon player (view partial, react JS, and yarn dependency).  This might take a while.
+
+4. Ingest audiovisual content and see a IIIF viewer render on the work show page.
+
+For a walkthrough of this in a demo application try running through this repository's README: https://github.com/avalonmediasystem/connect2018-workshop
+
+
+# Set up dev / test environment
+This project uses engine cart for testing and development purposes. To generate the .internal_test_app directory do the following
+
+```bash
+export ENGINE_CART_RAILS_OPTIONS="--skip-git --skip-bundle --skip-listen --skip-spring --skip-yarn --skip-keeps --skip-coffee --skip-puma --skip-test"
+bundle exec rake engine_cart:generate
+```
+
+Spec and rubocop can then be run using the `rake` command.
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at <https://github.com/samvera-labs/hyrax-iiif_av>. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
+
+If you're working on PR for this project, create a feature branch off of `main`.
 
-3. Ingest audiovisual content and see the Avalon IIIF viewer render on the work show page.
+This repository follows the [Samvera Community Code of Conduct](https://samvera.atlassian.net/wiki/spaces/samvera/pages/405212316/Code+of+Conduct) and [language recommendations](https://github.com/samvera-labs/hyrax-iiif_av/blob/main/CONTRIBUTING.md#language).  Please ***do not*** create a branch called `master` for this repository or as part of your pull request; the branch will either need to be removed or renamed before it can be considered for inclusion in the code base and history of this repository.

data/app/controllers/concerns/hyrax/iiif_av/auth_controller_behavior.rb

@@ -0,0 +1,53 @@
+# frozen_string_literal: true
+
+# Copyright 2011-2018, The Trustees of Indiana University and Northwestern
+# University. Additional copyright may be held by others, as reflected in
+# the commit history.
+#
+# Licensed under the Apache License, Version 2.0 (the "License");
+# you may not use this file except in compliance with the License.
+# You may obtain a copy of the License at
+#
+#    http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+# ---  END LICENSE_HEADER BLOCK  ---
+
+module Hyrax
+  module IiifAv
+    module AuthControllerBehavior
+      extend ActiveSupport::Concern
+
+      def after_sign_in_path_for(resource_or_scope)
+        return Hyrax::IiifAv::Engine.routes.url_helpers.iiif_av_sign_in_path if referer_iiif_login? || request_iiif_login?
+        super
+      end
+
+      private
+
+        def referer_iiif_login?
+          # When going through the login form
+          referer_uri_string = request.env.fetch("HTTP_REFERER", nil)
+          return false unless referer_uri_string.present?
+          referer_uri = URI(referer_uri_string)
+          # Don't worry about referers that come from a different site (includings where the IIIF viewer is embedded)
+          return false if referer_uri.host.present? && referer_uri.host != request.host
+          query_params = Rack::Utils.parse_query(referer_uri.query)
+          query_params && ActiveModel::Type::Boolean.new.cast(query_params["iiif_auth_login"])
+        end
+
+        def request_iiif_login?
+          # When already logged in
+          request_uri_string = request.env.fetch("REQUEST_URI", nil)
+          return false unless request_uri_string.present?
+          request_uri = URI(request_uri_string)
+          query_params = Rack::Utils.parse_query(request_uri.query)
+          ActiveModel::Type::Boolean.new.cast(query_params["iiif_auth_login"])
+        end
+    end
+  end
+end

data/app/controllers/concerns/hyrax/iiif_av/controller_behavior.rb

@@ -24,22 +24,29 @@ module Hyrax
 
       included do
         prepend_view_path(Hyrax::IiifAv::Engine.view_path)
-        helper Hyrax::IiifAv::IiifAvHelper
       end
 
-      IIIF_PRESENTATION_2_MIME = 'application/json;profile=http://iiif.io/api/presentation/2/context.json'
-      IIIF_PRESENTATION_3_MIME = 'application/json;profile=http://iiif.io/api/presentation/3/context.json'
+      IIIF_PRESENTATION_2_MIME = 'application/ld+json;profile="http://iiif.io/api/presentation/2/context.json"'
+      IIIF_PRESENTATION_3_MIME = 'application/ld+json;profile="http://iiif.io/api/presentation/3/context.json"'
 
       def manifest
         add_iiif_header
-        super
+
+        headers['Access-Control-Allow-Origin'] = '*'
+
+        json = iiif_manifest_builder.manifest_for(presenter: iiif_manifest_presenter, iiif_manifest_factory: manifest_factory)
+
+        respond_to do |wants|
+          wants.json { render json: json }
+          wants.html { render json: json }
+        end
       end
 
       private
 
         # @return true if the request is for IIIF version 3; false otherwise
         def iiif_version_3?
-          presenter.respond_to?(:iiif_version) ? presenter.iiif_version == 3 : false
+          iiif_manifest_presenter.respond_to?(:iiif_version) ? iiif_manifest_presenter.iiif_version == 3 : false
         end
 
         def iiif_mime
@@ -51,11 +58,19 @@ module Hyrax
           headers['Content-Type'] = iiif_mime
         end
 
-        def manifest_builder
+        # Override this method to return classes instead of instances
+        # This forces the manifest action to call Hyrax::ManifestBuilderService.manifest_for
+        # which allows for the passing in of the manifest factory
+        def iiif_manifest_builder
+          self.class.iiif_manifest_builder ||
+            (Flipflop.cache_work_iiif_manifest? ? Hyrax::CachingIiifManifestBuilder : Hyrax::ManifestBuilderService)
+        end
+
+        def manifest_factory
           if iiif_version_3?
-            ::IIIFManifest::V3::ManifestFactory.new(presenter)
+            ::IIIFManifest::V3::ManifestFactory
           else
-            ::IIIFManifest::ManifestFactory.new(presenter)
+            ::IIIFManifest::ManifestFactory
           end
         end
     end

data/app/controllers/hyrax/iiif_av/iiif_av_controller.rb

@@ -0,0 +1,88 @@
+# frozen_string_literal: true
+module Hyrax
+  module IiifAv
+    class IiifAvController < ApplicationController
+      include Blacklight::Base
+      include Blacklight::AccessControls::Catalog
+
+      def content
+        file_set_id = params[:id]
+        label = params[:label]
+        if request.head?
+          return head :ok if valid_token? || can?(:read, params[:id])
+          return head :unauthorized
+        else
+          return head :unauthorized unless presenter
+          return redirect_to hyrax.download_path(file_set_id, file: label, locale: nil) unless stream_urls[label]
+          redirect_to stream_urls[label]
+        end
+      end
+
+      def auth_token
+        return head :unauthorized unless can? :read, params[:id]
+        response.set_header('Content-Security-Policy', 'frame-ancestors *')
+        render html: auth_token_html_response(generate_auth_token)
+      end
+
+      # This route is meant to be used with devise's `after_sign_in_path_for` as part of the IIIF Auth flow
+      # See the override of `after_sign_in_path_for` in Hyrax::IiifAv::AuthControllerBehavior
+      def sign_in
+        render inline: "<html><head><script>window.close();</script></head><body></body></html>".html_safe
+      end
+
+      private
+
+        def generate_auth_token
+          # This is the same method used by ActiveRecord::SecureToken
+          token = SecureRandom.base58(24)
+          Rails.cache.write("iiif_auth_token-#{token}", params[:id])
+          token
+        end
+
+        def auth_token_html_response(token)
+          message = { messageId: params[:messageId], accessToken: token }
+          origin = Rails::Html::FullSanitizer.new.sanitize(params[:origin])
+          "<html><body><script>window.parent.postMessage(#{message.to_json}, \"#{origin}\");</script></body></html>".html_safe
+        end
+
+        def valid_token?
+          auth_token = request.headers['Authorization']&.sub('Bearer ', '')&.strip
+          resource_id = Rails.cache.read("iiif_auth_token-#{auth_token}")
+          params[:id] == resource_id
+        end
+
+        # Override of Blacklight::RequestBuilders
+        def search_builder_class
+          Hyrax::FileSetSearchBuilder
+        end
+
+        def presenter
+          @presenter ||= begin
+            _, document_list = search_results(params)
+            curation_concern = document_list.first
+            return nil unless curation_concern
+            # Use the show presenter configured in the FileSetsController
+            Hyrax::FileSetsController.show_presenter.new(curation_concern, current_ability, request)
+          end
+        end
+
+        # Duplicated here from Hyrax::IiifAv::DisplaysContent
+        def stream_urls
+          @stream_urls ||= begin
+            return {} unless presenter.solr_document['derivatives_metadata_ssi'].present?
+            files_metadata = JSON.parse(presenter.solr_document['derivatives_metadata_ssi'])
+            file_locations = files_metadata.select { |f| f['file_location_uri'].present? }
+            return {} unless file_locations.present?
+            streams = {}
+            file_locations.each do |f|
+              streams[f['label']] = Hyrax::IiifAv.config.iiif_av_url_builder.call(
+                f['file_location_uri'],
+                request.base_url
+              )
+            end
+            streams
+          end
+        end
+    end
+  end
+end