Hi all,
as some/many people will know, Zotero used to work with DSpace 1.4, but no
longer works with 1.5 and higher. This isn't DSpace's fault -- Zotero is
merely being too eager to invoke the wrong translator when it recognises a
DSpace site.
If other people think this is important (and
Hello Panyarak,
Panyarak Ngamsritragul schrieb:
1. I tried both JSPUI and XMLUI of the same site. It surprised me that I
had to registered for each UI separately. If I am not wrong, in previous
version, there is no need to register to each UI.
This is just the setup for test. To have
Good day all,
I downloaded and tried installing the dspace 1.6 testathon. It gave me these
error:
2009-12-09 14:17:02,031 WARN org.dspace.app.webui.servlet.FeedbackServlet @
an...@unijos.edu.ng:
session_id=CDE8C95175D71897B0E490CB1BB4E191:ip_addr=127.0.0.1:
error_mailing_feedback:
No route to host. So it appears that the name smtp.unijos.edu.ng
is resolvable (for you, though not for me) but your DSpace host
doesn't know how to send packets to that address. Possibly the SMTP
host is administratively hidden from the DSpace host, and you need to
talk to your network security
Is it possible to show the results of SRW-operations without the xsl
parsing? only showing the xml file?
I mean... I just want to recieve
searchRetrieveResponse
version1.1/version
numberOfRecords47/numberOfRecords
resultSetIdsppfif/resultSetId
resultSetIdleTime300/resultSetIdleTime
records
record
As the XML is generated on the fly and probably transformed
programmatically, the easiest solution may be to just comment out or
delete the contents of searchRetrieveResponse.xsl. If you delete or
comment out everything below;
xsl:stylesheet version=1.0
The HTML is being generated dynamically on your browser. Is it
sufficient to simply view the source of the response? You'll see the
XML there. If you always want to see the XML and never let the browser
render it into HTML, then we can probably find a way to suppress the
stylesheet reference
I agree, please do comment.
Mark
On Wed, Dec 9, 2009 at 2:50 AM, Tom De Mulder td...@cam.ac.uk wrote:
as some/many people will know, Zotero used to work with DSpace 1.4, but no
longer works with 1.5 and higher. This isn't DSpace's fault -- Zotero is
merely being too eager to invoke the wrong
Hi,
Our organisation is currently using DSpace version 1.4.2 and about to upgrade
to 1.5.0 to 1.5.1 then 1.5.2.
We're trying to find a solution to our dates' dilemma on DSpace - i.e., we
would like them to appear in chronological order. Currently they're not:
See
Saeed,
I want to resurrect this thread to discuss the possibility of your sharing
this BIDI work within the i18n projects for DSpace.
https://scm.dspace.org/svn/repo/modules/dspace-api-lang/trunk/
https://scm.dspace.org/svn/repo/modules/dspace-xmlui-lang/trunk/
Specifically, in the JSPUI and
Ruby,
Given your using JSPUI I would alter the following ItemTag class to take the
Bitstreams and order them according to your requirements.
https://scm.dspace.org/svn/repo/dspace/tags/dspace-1_4_2/dspace/src/org/dspace/app/webui/jsptag/ItemTag.java
/**
* List bitstreams in the item
11 matches
Mail list logo
