Code:
Docs:
Jump in:
This Gem allows your rails application to access user files from cloud storage. Currently there are drivers implemented for Dropbox, Google Drive, Box, Amazon S3, and a server-side directory share.
The gem uses OAuth to connect to a user's account and generate a list of single use urls that your application can then use to download the files.
This gem does not depend on hydra-head
BrowseEverything is a Core Component of the Samvera community. The documentation for what this means can be found here.
Currently, the following releases of Ruby are supported:
- 2.6.3
- 2.5.5
- 2.4.6
The supported Rail releases follow those specified by the security policy of the Rails Community. As is the case with the supported Ruby releases, it is recommended that one upgrades from any Rails release no longer receiving security updates.
- 5.2.3
- 5.1.7
Add this lines to your application's Gemfile:
gem 'jquery-rails'
gem 'browse-everything'
And then execute:
$ bundle
Or install it yourself as:
$ gem install browse-everything
After installing the gem, run the generator
$ rails g browse_everything:install
This generator will set up the config/browse_everything_providers.yml file and add the browse-everything engine to your application's routes.
If you prefer not to use the generator, or need info on how to set up providers in the browse_everything_providers.yml, use the info on Configuring browse-everything.
Browse-everything depends on bootstrap, it can work with bootstrap 3 or bootstrap 4.
For bootstrap3 support, your app should include the bootstrap-sass gem in it's Gemfile, and following the install directions for bootstrap-sass, should have @import 'bootstrap-sprockets' and @import 'bootstrap' in it's application.scss. After those lines, add @import "browse_everything/browse_everything_bootstrap3"; to your application.scss.
For bootstrap4 support, your app should include the bootstrap gem in it's Gemfile, and following the install directions for that gem should have @import "bootstrap"; in it's application.scss. After that line, add @import 'browse_everything/browse_everything_bootstrap4' to your application.scss.
In app/assets/javascripts/application.js include jquery and the BrowseEverything
//= require jquery
//= require browse_everything(Same for bootstrap3 or bootstrap 4)
If your app has installed a previous version of browse-everything, you may have a generated file at ./app/assets/stylesheets/browse_everything.scss, which has a line in it @import "browse_everything/browse_everything";. That import should no longer be used; it can be changed to @import "browse_everything/browse_everything_bootstrap3" instead.
However, we also recommend merging the contents of this file into your main application.scss file, as documented in the current install instructions. With the separate generated file with bootstrap imports, you may likely be including bootstrap CSS in your generated CSS bundle twice, if you also have that import in your main application.scss already.
This is a Rails Engine which is tested using the engine_cart Gem and rspec.
One rspec test invokes karma to run Javascript tests. For this test to succeed, you need to install karma on your system, first by making sure npm is installed, and then run npm install -g karma karma-jasmine karma-chrome-launcher.
Test suites may be executed with the following invocation:
bundle exec rakeTests by default will be run with bootstrap-4 integration. To test bootstrap-3 integration: TEST_BOOTSTRAP=3 bundle exec rake.
Should you attempt to execute the test suite and encounter the following error:
Your Ruby version is 2.x.x, but your Gemfile specified 2.y.z...then you must clean the internal test app generated by engine_cart with the following:
bundle exec rake engine_cart:cleanIn order to connect to a provider like Dropbox, Google Drive, or Box, you must provide API keys in config/browse_everything_providers.yml. For info on how to edit this file, see Configuring browse-everything
browse-everything can be triggered in two ways -- either via data attributes in an HTML tag or via JavaScript. Either way, it accepts the same options:
| Name | Type | Default | Description |
|---|---|---|---|
| route | path (required) | '' | The base route of the browse-everything engine. |
| target | xpath or jQuery | null | A form object to add the results to as hidden fields. |
| context | text | null | App-specific context information (passed with each request) |
| accept | MIME mask | / | A list of acceptable MIME types to browse (e.g., 'video/*') |
If a target is provided, browse-everything will automatically convert the JSON response to a series of hidden form fields
that can be posted back to Rails to re-create the array on the server side.
To trigger browse-everything using data attributes, set the data-toggle attribute to "browse-everything" on the HTML tag. This tells the javascript where to attach the browse-everything behaviors. Pass in the options using the data-route and data-target attributes, as in data-target="#myForm".
For example:
<button type="button" data-toggle="browse-everything" data-route="<%=browse_everything_engine.root_path%>"
data-target="#myForm" class="btn btn-large btn-success" id="browse">Browse!</button>To trigger browse-everything via javascript, use the .browseEverything() method to attach the behaviors to DOM elements.
$('#browse').browseEverything(options)The options argument should be a JSON object with the route and (optionally) target values set. For example:
$('#browse').browseEverything({
route: "/browse",
target: "#myForm"
})See JavaScript Methods for more info on using javascript to trigger browse-everything.
browse-everything returns a JSON data structure consisting of an array of URL specifications. Each URL specification is a plain object with the following properties:
| Property | Description |
|---|---|
| url | The URL of the selected remote file. |
| auth_header | Any headers that need to be added to the request in order to access the remote file. |
| expires | The expiration date/time of the specified URL. |
| file_name | The base name (filename.ext) of the selected file. |
For example, after picking two files from dropbox,
If you initialized browse-everything via JavaScript, the results data passed to the .done() callback will look like this:
[
{
"url": "https://dl.dropbox.com/fake/filepicker-demo.txt.txt",
"expires": "2014-03-31T20:37:36.214Z",
"file_name": "filepicker-demo.txt.txt"
}, {
"url": "https://dl.dropbox.com/fake/Getting%20Started.pdf",
"expires": "2014-03-31T20:37:36.731Z",
"file_name": "Getting Started.pdf"
}
]See JavaScript Methods for more info on using javascript to trigger browse-everything.
If you initialized browse-everything via data-attributes and set the target option (via the data-target attribute or via the target option on the javascript method), the results data be written as hidden fields in the <form> you've specified as the target. When the user submits that form, the results will look like this:
"selected_files" => {
"0"=>{
"url"=>"https://dl.dropbox.com/fake/filepicker-demo.txt.txt",
"expires"=>"2014-03-31T20:37:36.214Z",
"file_name"=>"filepicker-demo.txt.txt"
},
"1"=>{
"url"=>"https://dl.dropbox.com/fake/Getting%20Started.pdf",
"expires"=>"2014-03-31T20:37:36.731Z",
"file_name"=>"Getting Started.pdf"
}
}The BrowseEverything::Retriever class has two methods, #retrieve and #download, that
can be used to retrieve selected content. #retrieve streams the file by yielding it, chunk
by chunk, to a block, while #download saves it to a local file.
Given the above response data:
retriever = BrowseEverything::Retriever.new
download_spec = params['selected_files']['1']
# Retrieve the file, yielding each chunk to a block
retriever.retrieve(download_spec) do |chunk, retrieved, total|
# do something with the `chunk` of data received, and/or
# display some progress using `retrieved` and `total` bytes.
end
# Download the file. If `target_file` isn't specified, the
# retriever will create a tempfile and return the name.
retriever.download(download_spec, target_file) do |filename, retrieved, total|
# The block is still useful for showing progress, but the
# first argument is the filename instead of a chunk of data.
endSee spec/support/app/views/file_handler/index.html for an example use case. You can also run rake app:generate to
create a fully-functioning demo app in spec/internal (though you will have to create
spec/internal/config/browse_everything.providers.yml file with your own configuration info.)
The Samvera community is here to help. Please see our support guide.
This software has been developed by and is brought to you by the Samvera community. Learn more at the Samvera website.
