Hi,
it seems that I have a problem with the encoding using jspui.
I'm using DSpace 1.5.1
In the dspace.cfg I wrote:
# Name of the site
dspace.name = DSpace der Universitätsbibliothek Freiburg
The dspace.cfg is UTF-8 encoded.
In the Web-page the title and the menu looks like this:
DSpace der
Hi,
I have some questions about DSpace and Shibboleth.
I try to map the dspace-jspui to the ROOT of the tomcat.
In the apache mod_proxy I map / to localhost:8009.
Now I have the problem, that the Shibboleth endpoint can not be found.
How do you manage it? Did you use /jspui as start URL?
Hi Jochen,
... and now the hint about Messages_fr.properties:
At
http://dspace-sandbox.googlecode.com/svn/modules/dspace-api-lang/trunk/src/main/resources/
the
Messages.properties can be find. It seems Messages_fr.properties is not up to
date ... it is still 1.4.1 ;-)
This is correct.
Good morning all,
We are attempting to harvest some of the items in our dspace instance via
OAI-PMH for other purposes. We can easily pull the records but we are unable
to see the qualifiers in the records. Any suggestions on how we can also have
the qualifiers available via OAI? Thanks,
Hi Dale
The identifiers are not included in the standard:
http://www.openarchives.org/OAI/openarchivesprotocol.html#Record
Regards
George
Poulter, Dale wrote:
Good morning all,
We are attempting to harvest some of the items in our dspace instance
via OAI-PMH for other purposes. We can
Hi Dale,
you might expose qualified dublin core as just another schema via OAI,
there is allready a preliminary qdc crosswalk in
[dspace]/config/crosswalks.
Hope that helps
Claudia Jürgen
Good morning all,
We are attempting to harvest some of the items in our dspace instance via
OAI-PMH
I am having trouble getting Dspace to work with a version of manakin that I
have downloaded (from svn). The installation instructions say:
Compile Manakin using an existing DSpace source tree to link against. Use
the dspace ant parameter to tell Manakin where your DSpace source
directory is, as
Hi Jochen,
There is a better way to set UTF-8 encoding in JSP pages, and it should fix the
problem you're seeing:
%@ page contentType=text/html;charset=UTF-8 %
This goes near the other '%@ page' lines, where constants and config
parameters are being imported.
Cheers,
Kim.
-Original
On Tue, Dec 9, 2008 at 6:30 PM, Claudia Juergen
[EMAIL PROTECTED] wrote:
Hi Andrew,
seems as if you're following instructions dated before the integration of
Manakin as xmlui in the DSpace source.
Just follow the default installation instructions. Finished with these
you'll find both jspui
Hmm. I did wonder if it had been integrated. But now I am
left wondering how to configure the theme etc. I assume that
since there is no longer manakin as a separate product the
instructions are no good. I don't know what to do.
Hi, I expect you'll get plenty of responses on this, but
Hi Andrew,
As far as the webapp itself goes, it will look and act the same. The major
difference is that compiling it is easier, it’s just part of the dspace
rebuild, and your local customisations should go in
[dspace-source]/dspace/modules/xmlui/src/main/webapp.
From now on, just refer
Dear all:
Just for your knowledge, Shibboleth patch for dspace1.5.1 has been
submitted to sourceforge.
Here is the URL link:
http://sourceforge.net/tracker/index.php?func=detailaid=2412723group_id=19984atid=319984
If you are interested, give a try. If you have any concern, please feel
Hi
I was also facing the same problem.Hence did few modifications as said
below:-
1)Made the OAI-Response to give qualifier name instead of element name .
2)As said,it is little hack in the code,I truly agree but that's how I was
able to keep the code changes minimal in Dspace which can
Hi Kim,
%@ page contentType=text/html;charset=UTF-8 %
is in every jsp-File (default after compiling DSpace), but it does not work.
All other are OK, I think the problem must be somewhere between reading
the config-File and
putting the text in the Webpage.
Greetings
Jochen
Kim Shepherd
14 matches
Mail list logo
