Dear sir,
I am using ubuntu 6.06 as operating system, the e mail feature is not
working in my server the error in the log file is
2007-10-11 11:55:11,915 INFO org.dspace.app.webui.servlet.RegisterServlet @
anonymous:session_id=7CBDA8042C27736FF48362A1D1056E8E:ip_addr=
Hi,
I am using ubuntu 6.06 as operating system, the e mail feature is not working
in my server the error in the log file is
2007-10-11 11:55:11,915 INFO org.dspace.app.webui.servlet.RegisterServlet @
anonymous:session_id=7CBDA8042C27736FF48362A1D1056E8E:ip_addr=
Hi all,
I was wondering why we don't include date.modified in our DC registry.
It appears here http://dublincore.org/documents/dcmi-terms/, and I don't
see any reason why we shouldn't include it. I was also wondering about
our use of date.submitted[1], rather than dateSubmitted[2]. Was this
Hi all
Im having problems trying to use DSpace with a latin1 oracle database. I
cannot use another charset due to production constrains. I know DSpace
is prepared to be used in UTF8, but... Is there a workarround to such a
case? Or, is there an easy way to intercept SQL queries and perform the
Hi,
We are planning to migrate from 1.3.2 to 1.4.1. In the operational
DSpace1.3.2 (http://drs.nio.org) there are lots of customisations. So we
don't want to migrate directly. But to check the migration in a test server
first.
I have installed DSpace1.4.1 in test server. Now I want to use
On Thu, Oct 11, 2007 at 03:47:56PM +0530, Satya Ranjan Sahu wrote:
I tried following but unsuccessful:
1. Drop the database of 1.4.1
2. Creat new database
3. psql dspace dspace.sql (1.3.2)
But it is showing problem as follows:
SET
SET
ERROR: permission denied to set session
Jose,
It's vaguely possible to run it using national character set columns
(NCHAR, NCLOB), to allow for a different character encoding (the ncs
columns could be UTF-8, whilst everything else remain Latin-1).
However, we've been down that route, and it involves some very nasty
customisations to
We had the same issue here, having an Oracle instance in ISO-8859-1 charset.
While it doesn't seems to be a problem for CLOB columns (our metadatas contains
a lot of accents and everything is working fine, including insertions and
updates tests), it does cause one with the VARCHAR2 columns,
In case it wasn't obvious, I meant to follow up:
And then added in the appropriate element in Messages.properties,
rebuilt
with rebuilt, reindexed, etc.
No idea where that sentence went.
Thanks again.
On Oct 11, 2007, at 4:15 PM, Shane Beers wrote:
I am having issues with my search
I am having issues with my search results when using the advanced
search in our archive. I have added the thesis metadata schema to
handle ETD documents, and these documents work great normally. I have
edited the dspace.cfg to add:
search.index.13 = edt_disc:thesis.degree.discipline
10 matches
Mail list logo