Hi Shannon,
Hmmm.. it does sound like an error related to trying to use the wrong
convert command (as you noted Windows has it's own convert.exe
command). This StackOverflow answer says something similar:
http://stackoverflow.com/a/26163068
After some searching around, it seems like there's a
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
Hi,
thank you for your interest in this work. Te feature did not make it into
DSpace 5 in its current form. You can read the specific context here:
https://jira.duraspace.org/browse/DS-2169
However, you can still get the contributed code from:
https://github.com/DSpace/DSpace/pull/668
One of
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
Hello,
Recently, I have tried to delete an item from my Dspace 3.2 instance, but I
get a blank page after confirming the operation, and the item is not
deleted.
However, I am able to delete the bitstreams, and then withdraw the item.
I get the following messages in the logs (replaced ip address
This is where the This Collection radio button is rendered in Mirage2:
https://github.com/DSpace/DSpace/blob/dspace-5_x/dspace-xmlui-mirage2/src/main/webapp/xsl/core/navigation.xsl#L66-89
The simplest way would be to duplicate this code and render it for each
collection you want (xsl:for-each).
Hi!
Using the XMLUI (particularly, the Mirage2 theme), when you drill down into a
community or a collection, a couple of radio buttons appear that make it
possible for you to limit your search to that specific community or collection.
What I'd like to do is have radio buttons for each
Hello:
I recently upgraded from DSpace 4.3 to DSpace 5.1 (XMLUI) using a theme based
on Mirage2.
We just noticed a peculiar problem. In our theme, we place the name of the
user on the screen when they log in.
This worked fine in DSpace 4.3, but when I went to DSpace 5.1, I see the
following
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
Xmlui dspace 5.1 update from 4.1
Basically the sql updater expects only one entry for element=rights in the
table metadatafieldregistry but ours has two.
Does anyone have any idea what I should do?
Should I merge the two rights: how would I do that?
thank You,
Ben
From the dspace.log
Hi George,
probably just a piece of the puzzle at this point, but your report made me
think about:
https://jira.duraspace.org/browse/DS-2347
https://jira.duraspace.org/browse/DS-2164
These fixes made it into 5.0 so you're probably seeing something different.
But I would definitely look in the
Hi All,
We are using dspace 4.2/xmlui version and we are about to harvest data from a
web based application developed in house
using php and Zend Framework, database is MySQL.
Is there a way to harvest data from this application
Thanks, Sisay
Hi Gibson,
The source is the application that was developed in PHP while dspace is the
destination.
Thanks,Sisay
From: Hilton Gibson [mailto:hilton.gib...@gmail.com]
Sent: Wednesday, April 15, 2015 11:50 AM
To: Webshet, Sisay (ILRI)
Cc: dspace-tech@lists.sourceforge.net
Subject: Re:
Hi Sisay
More details would help. The destination and source of the harvesting is
needed.
In other other words, knowing who is the producer and who is the consumer
would help.
Cheers
hg
*Hilton Gibson*
Ubuntu Linux Systems Administrator
JS Gericke Library
Room 1025C
Stellenbosch University
I recently upgraded from 1.8.3 to 4.2 (just before 4.3 was released!).
Embargo lifting is modifying metadata correctly, but bitstreams remain
inaccessible.
Embargoed content created under 1.8.3 has no policies on the original bundle
and bitstream(s), so restricting access. Embargoed content
15 matches
Mail list logo
