UCDavisLibrary / ucd-hyku

The Hydra-in-a-Box repository application
http://hydrainabox.projecthydra.org/
Other
3 stars 0 forks source link

Image characterization not correct for `:inline` queue #4

Open qjhart opened 7 years ago

qjhart commented 7 years ago

Descriptive summary

If you set the queuing behavior to :inline, then while importing new items to the system, the images do not show up as having been characterized. Even though they have been.

Expected behavior

You would expect the image data to become immediately become available.

Actual behavior

You would expect the image data to become immediately become available. Instead the image is identified as not characterized. Any further edits, (fro example , just navigating to the Edit->permissions tab and saving the current permissions, will fix this issue.

Steps to reproduce the behavior

  1. Start fresh,
    
    alias dc='docker-compose'
    git diff

diff --git a/config/environments/production.rb b/config/environments/production.rb index 28f9b0a..747274a 100644 --- a/config/environments/production.rb +++ b/config/environments/production.rb @@ -56,8 +56,9 @@ Rails.application.configure do

config.cache_store = :mem_cache_store

Use a real queuing backend for Active Job (and separate queues per environment)

This image shows the results after upload image

This image shows the file status.

image

Even though, and investigation of the fedora backend seems to indicate that they have been properly indexed.

image

Any sort of update to the file, will bring in the characterization.

image

mjgiarlo commented 7 years ago

@qjhart Good find! Might you be inclined to troubleshoot why this method would be returning false if the characterization metadata is present in Fedora? https://github.com/samvera/hyrax/blob/master/app/presenters/hyrax/characterization_behavior.rb#L22-L24 When this method returns false, the not yet characterized message is printed out.

This could be a bug we ought to fix in Hyrax.

qjhart commented 7 years ago

@mjgiarlo, yeah, we will continue to pursue. Not the best rails programmers here :)