It was an issue with DSpace not being able to "find" ImageMagick
convert.exe, even though the path and environment variables are properly
defined. You do have to set the path in dspace.cfg, but that in itself is
tricky as none the following worked:
--
- "C:\\Program Files\\ImageMagick"
- C:\Program Files\ImageMagick
- "C:\Program Files\ImageMagick"
- C:/Program Files/ImageMagick
--
Monkeying with the registry or modifying sys32 applications was a last
resort for me, so what I tried that worked was:
1. Install ImageMagick and Ghostscript to c:\dspace\imagemagick. I
chose a lower case for the subfolder not knowing if config definitions for
file paths in dspace.cfg would be case sensitive. I went with the
assumption that they are.
2. Define
'org.dspace.app.mediafilter.ImageMagickThumbnailFilter.ProcessStarter' in
dspace.cfg as '${dspace.dir}/imagemagick'.
Turns out the relative path did the trick. ... Or it could be that Program
Files has a space in it, I would think quote encapsulation would deal with
that. Either way it's working now :)
Thanks all,
Shannon
--
Mr. Shannon Meisenheimer
CentralNet - Office of Technology
Blackboard Administration and Support
University of Central Missouri
Dockery 207A
meisenhei...@ucmo.edu
Work Phone: (660) 543-8483
On Wed, Apr 15, 2015 at 9:51 AM, Tim Donohue <tdono...@duraspace.org> wrote:
>
>
> On 4/15/2015 9:27 AM, Shannon Meisenheimer wrote:
>
>> Thanks Tim, I had read some of those, but hadn't seen the third. I'll
>> try the regedit,or just rename windows convert. I already have
>> ImageMagick at the beginning of the PATH. It's seems like I can
>> run/access ImageMagick convert from cmd when I call/run it directly, but
>> DSpace is trying to use Windows convert.
>>
>> Is the double extension ".pdf.jpg" normal?
>>
>
> Yes, this is just the extension of the *generated* PDF thumbnail (by the
> ImageMagick media filter). You actually may want to see if those referenced
> ".pdf.jpg" files were generated on your local system -- if so, that'd mean
> that ImageMagick actually *did* create those thumbnails (or at least
> started to do so, but ran into a later issue).
>
>
>> Do Ghostscript and ImageMagick need to be in the same folder? I know it
>> states to install them both to /usr/bin (linux path) in the
>> documentation, but is that needed on a win box?
>>
>
> Yes. Well, actually, they either need to be in the same folder OR you'd
> need to specify TWO paths in the "org.dspace.app.mediafilter.
> ImageMagickThumbnailFilter.ProcessStarter" setting. Since that setting is
> just passed directly to the "im4java" script (from imageMagick), it seems
> like you should be able to specify multiple folders separated by a
> semicolon, as noted here: http://im4java.sourceforge.
> net/docs/dev-guide.html
>
> But, again, I'm going to admit, I've not tried that (especially on
> Windows). I'm only just getting more familiar with the ImageMagick code
> myself, so this is just from my reading of the existing code here.
>
> It is also possible there's a bug here in how the ImageMagick media filter
> is referencing the scripts and/or generated thumbnail files. But, I don't
> know enough yet to state that for certain.
>
> - Tim
>
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
