[Dspace-tech] DSpace Windows installation error; Build Failed - Java Returned: 1
Hi all Herewith a problem that I see on many forums, yet cannot find a good answer to. I hope someone can help me with this. I am running (or trying to run): - tomcat 5.5.27 - ant 1.7.1 - dspace 1.5.1 - java: JDK JRE 5.0 Update 16 (from installer jdk-1_5_0_16-windows-i586-p.exe) I’ve followed the steps that can be seen at http://ardb4.ncsi.iisc.ernet.in/dspace/dspacewindows.htm - this is a really excellent guide by the way – and have gotten up to the last part where it says that you must run: ant fresh_install. But when i run ant fresh_install, i get an error saying: BUILD FAILED C:\DSpace\dspace\build.xml:380: Java returned: 1 Now I’ve searched many forums and seen this exact problem bemoaned countless times. However I have yet to find a good answer, especially a good Windows specific answer. I REALLY hope someone can help me out with this. Many thanks -- View this message in context: http://www.nabble.com/DSpace-Windows-installation-error--Build-Failed---Java-Returned%3A-1-tp19881409p19881409.html Sent from the DSpace - Tech mailing list archive at Nabble.com. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] DSpace Windows installation error; Build Failed - Java Returned: 1
Hi, this dspace for windows guide is for dspace 1.4.2 and lower. The build process (now maven and ant based) has changed with DSpace 1.5. You'll need Apacha Maven 2.0.8 or later, see [dspace-source]/dspace/docs/html/ch03.html#N10587 for prerequisite software. The installation instructions are at: [dspace-source]/dspace/docs/html/ch03.html#N10787 Hope that helps Claudia Jürgen juuventud schrieb: Hi all Herewith a problem that I see on many forums, yet cannot find a good answer to. I hope someone can help me with this. I am running (or trying to run): - tomcat 5.5.27 - ant 1.7.1 - dspace 1.5.1 - java: JDK JRE 5.0 Update 16 (from installer jdk-1_5_0_16-windows-i586-p.exe) I’ve followed the steps that can be seen at http://ardb4.ncsi.iisc.ernet.in/dspace/dspacewindows.htm - this is a really excellent guide by the way – and have gotten up to the last part where it says that you must run: ant fresh_install. But when i run ant fresh_install, i get an error saying: BUILD FAILED C:\DSpace\dspace\build.xml:380: Java returned: 1 Now I’ve searched many forums and seen this exact problem bemoaned countless times. However I have yet to find a good answer, especially a good Windows specific answer. I REALLY hope someone can help me out with this. Many thanks - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Removing all items
Hi all, is there a way to remove all items from a DSpace installation (1.5, JSPUI)? I do not want to drop the database, because I do not want to loose all configurations and collections. Best regards Robert -- === Robert Roggenbuck Universitaetsbibliothek Osnabrueck D-49074 Osnabrueck Germany === - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Two more questions regarding handles
You could use the script update-handle-prefix (in dspace/bin) to change your spaced prefix to a trimmed one. On Wed, Oct 8, 2008 at 6:49 PM, Jason Fowler [EMAIL PROTECTED] wrote: First, and most important, Handle.net is not resolving my prefix. I know it's probably a problem on my end. My firewall is open for incoming and outgoing on the appropriate ports. However, I keep getting this error in my handle server error log: 2008/10/08 11:41:54 CDT 100 class net.handle.server.HdlHttpInterface: Error setting up server socket: java.net.BindException: Cannot assign requested address Any ideas as to what might be causing this? Second, when I first set up my handle configuration, I accidentally had a small bit of whitespace after the prefix in dspace.cfg. Now, every item i add has a handle prefix that looks like this: handle/10392 /11 Any ideas as to how I should go about correcting this? Thanks, Jason Fowler, CA Archives and Special Collections Librarian The Southern Baptist Theological Seminary 502-897-4573 [EMAIL PROTECTED] - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Submission form's initial questions
On Thu, Oct 9, 2008 at 3:56 AM, mikan.d.dspace listmail [EMAIL PROTECTED] wrote: DSpace should definetely get rid of hard coded field settings and let the system read the form settings from configuration files. I tried to comment out some lines from the code, but couldnt achieve what Im looking after; that is to let user enter date.issued without having to use the initial questions in workflow. Would some of the developers comment on how to achieve this? This is somewhat hacky, but one way might be to replace the previously published checkbox with an option type=hidden that turns that option on. You'll be stuck with dc.identifier.citation, I'm afraid, but perhaps that's a tolerable tradeoff? Dorothea -- Dorothea Salo[EMAIL PROTECTED] Digital Repository Librarian AIM: mindsatuw University of Wisconsin Rm 218, Memorial Library (608) 262-5493 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] current status of UTF-8 in dspace and XML-UI / Manakin
[EMAIL PROTECTED] wrote: Hi Stuart, I'm replying to the list in case this helps anyone else, or, more probably, in case someone can point out the stupidity of my workaround when importing items. What problems are you suffering exactly? Funky characters showing up instead? We get error message during submission and bad characters showing up. If you take a look at http://hdl.handle.net/10289/875, the dc.identifier.citation field uses macrons (eg. Māori). We've had no real problem with this. That's Dspace 1.4.2, JSPUI. This is with 1.5.* and Manakin / XML/UI. I didn't have a lot to do with content on the server I've linked to there, but I've recently been importing large numbers of theses and dissertations from an ADT repository to a test Dspace server, and have had to convert a lot of UTF-8 characters like vowels with macrons and umlauts into their HTML equivalents to satisfy org.dspace.app.itemimport.ItemImport. A Maori macron a is #257;, for example. This might have very bad side effects when any non-HTML manipulation or indexing of metadata is going on, so I welcome any criticism or pointers there. (For instance, authors' names with umlaut-u in them display fine when browsing by title or after a search, but click that author's name to start a new 'browse by author', and the character becomes garbled and no search results are found.) I'd check that the connector was handling the URLs correctly. Check http://www.mail-archive.com/dspace-tech@lists.sourceforge.net/msg03041.html Alternatively, you could write an update for the text_value column of the metadatavalue table, which is where all these fields are stored. [I didn't see your response on the list, even though you cc'd the list, following up to the list in case other's are having these problems.] cheers stuart -- Stuart Yeates Te Pātaka Kōrero o Te Whare Wānanga o te Ūpoko o te Ika a Māui http://www.nzetc.org/ New Zealand Electronic Text Centre http://researcharchive.vuw.ac.nz/ Institutional Repository - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] current status of UTF-8 in dspace and XML-UI / Manakin
Quoting stuart yeates [EMAIL PROTECTED]: I'd check that the connector was handling the URLs correctly. Check http://www.mail-archive.com/dspace-tech@lists.sourceforge.net/msg03041.html Good point, thanks. Alternatively, you could write an update for the text_value column of the metadatavalue table, which is where all these fields are stored. They are stored fine in metadatavalue.text_value, as are all the other metadata fields. I'm guessing that because the other metadata fields don't get used as GET params very often (whereas Browse By Author then clicking an author does), you're right about the URL handling. [I didn't see your response on the list, even though you cc'd the list, following up to the list in case other's are having these problems.] Yeah, the list is fairly smart like that, you won't get duplicates. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Problem with filter-media
We've been having a problem with filter-media for as long as I can remember, with DSpace 1.3.1 and now with DSpace 1.4.2. I've emailed the list and discussed this problem with some of the developers before, but we've never had a resolution. I've been doing some more research on it myself for the past day or so and here are some interesting things that I've found: 1. 99% of our documents are .pdf files. filter-media seems to fail with two different types of errors: a. Java heap space - memory error b. Possibly unreadable character(s) error or problem with the actual format and/or scanning of the document 2. filter-media does not actually fail with error type (b.) above, but it does fail with error type (a.). This error has resulted in hundreds, maybe thousands of our documents not being filtered and, consequently, not being full-text searchable. 3. I used to think that perhaps the memory error was caused by our repository being fairly large (right now we have a total of 101,633 Items and are in the process of loading thousands more) - that perhaps the memory problem resulted *after* filtering lots of documents - maybe it had eaten up all the memory in the process. Today I figured out that is absolutely not the problem. What I did in an attempt to get all the unfiltered documents filtered, is I wrote a sql query that created a filter-media execution line ($BINDIR/dsrun org.dspace.app.mediafilter.MediaFilterManager -n -i 2121/68481 $@) for each individual Item in DSpace that did NOT have a $$$.pdf.txt document in the Bitstream table, then I copied all these lines into one script and ran it. So basically what happens is that filter-media executes over and over again, with the -i option (where you specify a handle you want filtered), once for each document that hadn't been previously filtered. What I found is that the errors were occurring on the filtering of a *single* document and were not caused by an memory accumulation effect. 4. In looking at some of the documents that were causing the errors, it appears that perhaps it is the larger documents that are getting the Java heap space error, although I'm not quite sure of this. Here is one of the errors that occurred: Exception in thread main java.lang.OutOfMemoryError: Java heap space at java.nio.CharBuffer.wrap(CharBuffer.java:350) at java.nio.CharBuffer.wrap(CharBuffer.java:373) at java.lang.StringCoding$StringDecoder.decode(StringCoding.java:138) at java.lang.StringCoding.decode(StringCoding.java:173) at java.lang.String.init(String.java:444) at java.lang.String.init(String.java:516) at org.fontbox.cmap.CMapParser.createStringFromBytes(CMapParser.java:418) at org.fontbox.cmap.CMapParser.parse(CMapParser.java:152) at org.pdfbox.pdmodel.font.PDFont.parseCmap(PDFont.java:535) at org.pdfbox.pdmodel.font.PDFont.encode(PDFont.java:387) at org.pdfbox.util.PDFStreamEngine.showString(PDFStreamEngine.java:325) at org.pdfbox.util.operator.ShowText.process(ShowText.java:64) at org.pdfbox.util.PDFStreamEngine.processOperator(PDFStreamEngine.java:452 ) at org.pdfbox.util.PDFStreamEngine.processSubStream(PDFStreamEngine.java:21 5) at org.pdfbox.util.PDFStreamEngine.processStream(PDFStreamEngine.java:174) at org.pdfbox.util.PDFTextStripper.processPage(PDFTextStripper.java:336) at org.pdfbox.util.PDFTextStripper.processPages(PDFTextStripper.java:259) at org.pdfbox.util.PDFTextStripper.writeText(PDFTextStripper.java:216) at org.dspace.app.mediafilter.PDFFilter.getDestinationStream(PDFFilter.java :142) at org.dspace.app.mediafilter.MediaFilter.processBitstream(MediaFilter.java :169) at org.dspace.app.mediafilter.MediaFilterManager.filterBitstream(MediaFilte rManager.java:344) at org.dspace.app.mediafilter.MediaFilterManager.filterItem(MediaFilterMana ger.java:313) at org.dspace.app.mediafilter.MediaFilterManager.applyFiltersItem(MediaFilt erManager.java:280) at org.dspace.app.mediafilter.MediaFilterManager.main(MediaFilterManager.ja va:219) Seems a lot of the Googling I've been doing on this indicates either the document is too large to be filtered, or there are some strings in the document that are too large for the String or Substring it's trying to do. 5. The other errors seem to be caused by, perhaps, non-readable characters (maybe a bad scan of the document..??) or something actually wrong with the scanned document. Here are some of those errors: ERROR filtering, skipping bitstream #46251 java.io.IOException: Error expected floating point number actual='110.-21' ERROR filtering, skipping bitstream #46372 java.io.StreamCorruptedException: Error: data is null ERROR filtering, skipping bitstream #46675 java.io.IOException: Error expected
Re: [Dspace-tech] Problem with filter-media
Hi Susan, These are long known issues with PDF text extraction. And they are both due to bugs in the underlying libraries that are used, and not necessarily an issue with the PDF content or size. For the heap space issue, a new configuration option was added to DSpace 1.5 - if you add to your dspace.cfg: pdffilter.skiponmemoryexception=true then it will skip the PDF when an out of memory exception occurs, rather than failing the process. But there isn't anything that we can do to extract data from PDFs where the errors are occurring. Note that if you aren't running DSpace 1.5, you might want to make changes to your local PDFFilter class, in line with the diff here: http://fisheye3.atlassian.com/browse/dspace/branches/dspace-1_5_x/dspace-api/src/main/java/org/dspace/app/mediafilter/PDFFilter.java?r1=2260r2=2581 G On 9 Oct 2008, at 21:20, Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS] wrote: We’ve been having a problem with filter-media for as long as I can remember, with DSpace 1.3.1 and now with DSpace 1.4.2. I’ve emailed the list and discussed this problem with some of the developers before, but we’ve never had a resolution. I’ve been doing some more research on it myself for the past day or so and here are some interesting things that I’ve found: 99% of our documents are .pdf files. filter-media seems to fail with two different types of errors: Java heap space – memory error Possibly unreadable character(s) error or problem with the actual format and/or scanning of the document filter-media does not actually fail with error type (b.) above, but it does fail with error type (a.). This error has resulted in hundreds, maybe thousands of our documents not being filtered and, consequently, not being full-text searchable. I used to think that perhaps the memory error was caused by our repository being fairly large (right now we have a total of 101,633 Items and are in the process of loading thousands more) – that perhaps the memory problem resulted *after* filtering lots of documents – maybe it had eaten up all the memory in the process. Today I figured out that is absolutely not the problem. What I did in an attempt to get all the unfiltered documents filtered, is I wrote a sql query that created a filter-media execution line (“$BINDIR/dsrun org.dspace.app.mediafilter.MediaFilterManager -n -i 2121/68481 [EMAIL PROTECTED]) for each individual Item in DSpace that did NOT have a $$$.pdf.txt document in the Bitstream table, then I copied all these lines into one script and ran it. So basically what happens is that filter-media executes over and over again, with the –i option (where you specify a handle you want filtered), once for each document that hadn’t been previously filtered. What I found is that the errors were occurring on the filtering of a *single* document and were not caused by an “memory accumulation” effect. In looking at some of the documents that were causing the errors, it appears that perhaps it is the larger documents that are getting the Java heap space error, although I’m not quite sure of this. Here is one of the errors that occurred: Exception in thread main java.lang.OutOfMemoryError: Java heap space at java.nio.CharBuffer.wrap(CharBuffer.java:350) at java.nio.CharBuffer.wrap(CharBuffer.java:373) at java.lang.StringCoding $StringDecoder.decode(StringCoding.java:138) at java.lang.StringCoding.decode(StringCoding.java:173) at java.lang.String.init(String.java:444) at java.lang.String.init(String.java:516) at org.fontbox.cmap.CMapParser.createStringFromBytes(CMapParser.java:418) at org.fontbox.cmap.CMapParser.parse(CMapParser.java:152) at org.pdfbox.pdmodel.font.PDFont.parseCmap(PDFont.java:535) at org.pdfbox.pdmodel.font.PDFont.encode(PDFont.java:387) at org.pdfbox.util.PDFStreamEngine.showString(PDFStreamEngine.java:325) at org.pdfbox.util.operator.ShowText.process(ShowText.java:64) at org.pdfbox.util.PDFStreamEngine.processOperator(PDFStreamEngine.java: 452) at org .pdfbox.util.PDFStreamEngine.processSubStream(PDFStreamEngine.java: 215) at org.pdfbox.util.PDFStreamEngine.processStream(PDFStreamEngine.java: 174) at org.pdfbox.util.PDFTextStripper.processPage(PDFTextStripper.java:336) at org.pdfbox.util.PDFTextStripper.processPages(PDFTextStripper.java:259) at org.pdfbox.util.PDFTextStripper.writeText(PDFTextStripper.java:216) at org .dspace .app.mediafilter.PDFFilter.getDestinationStream(PDFFilter.java:142) at org .dspace .app.mediafilter.MediaFilter.processBitstream(MediaFilter.java:169) at org .dspace .app .mediafilter .MediaFilterManager.filterBitstream(MediaFilterManager.java:344) at org .dspace .app
Re: [Dspace-tech] Problem with filter-media
Hi Graham, Are you saying that I need the 1.5 version of PDFFilter.java (or make the changes in the diff link) in order for the new parameter in dspace.cfg to work? Will it work if I download a 1.5 version of PDFFilter.java? Did any of those other error messages mean anything to you? Thanks a bunch Graham, Sue From: Graham Triggs [mailto:[EMAIL PROTECTED] Sent: Thursday, October 09, 2008 5:02 PM To: Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS] Cc: dspace-tech@lists.sourceforge.net; Smail, James W. (LARC-B702)[NCI INFORMATION SYSTEMS] Subject: Re: [Dspace-tech] Problem with filter-media Hi Susan, These are long known issues with PDF text extraction. And they are both due to bugs in the underlying libraries that are used, and not necessarily an issue with the PDF content or size. For the heap space issue, a new configuration option was added to DSpace 1.5 - if you add to your dspace.cfg: pdffilter.skiponmemoryexception=true then it will skip the PDF when an out of memory exception occurs, rather than failing the process. But there isn't anything that we can do to extract data from PDFs where the errors are occurring. Note that if you aren't running DSpace 1.5, you might want to make changes to your local PDFFilter class, in line with the diff here: http://fisheye3.atlassian.com/browse/dspace/branches/dspace-1_5_x/dspace -api/src/main/java/org/dspace/app/mediafilter/PDFFilter.java?r1=2260r2= 2581 G On 9 Oct 2008, at 21:20, Thornton, Susan M. (LARC-B702)[NCI INFORMATION SYSTEMS] wrote: We've been having a problem with filter-media for as long as I can remember, with DSpace 1.3.1 and now with DSpace 1.4.2. I've emailed the list and discussed this problem with some of the developers before, but we've never had a resolution. I've been doing some more research on it myself for the past day or so and here are some interesting things that I've found: 1. 99% of our documents are .pdf files. filter-media seems to fail with two different types of errors: a. Java heap space - memory error b. Possibly unreadable character(s) error or problem with the actual format and/or scanning of the document 2. filter-media does not actually fail with error type (b.) above, but it does fail with error type (a.). This error has resulted in hundreds, maybe thousands of our documents not being filtered and, consequently, not being full-text searchable. 3. I used to think that perhaps the memory error was caused by our repository being fairly large (right now we have a total of 101,633 Items and are in the process of loading thousands more) - that perhaps the memory problem resulted *after* filtering lots of documents - maybe it had eaten up all the memory in the process. Today I figured out that is absolutely not the problem. What I did in an attempt to get all the unfiltered documents filtered, is I wrote a sql query that created a filter-media execution line ($BINDIR/dsrun org.dspace.app.mediafilter.MediaFilterManager -n -i 2121/68481 $@) for each individual Item in DSpace that did NOT have a $$$.pdf.txt document in the Bitstream table, then I copied all these lines into one script and ran it. So basically what happens is that filter-media executes over and over again, with the -i option (where you specify a handle you want filtered), once for each document that hadn't been previously filtered. What I found is that the errors were occurring on the filtering of a *single* document and were not caused by an memory accumulation effect. 4. In looking at some of the documents that were causing the errors, it appears that perhaps it is the larger documents that are getting the Java heap space error, although I'm not quite sure of this. Here is one of the errors that occurred: Exception in thread main java.lang.OutOfMemoryError: Java heap space at java.nio.CharBuffer.wrap(CharBuffer.java:350) at java.nio.CharBuffer.wrap(CharBuffer.java:373) at java.lang.StringCoding$StringDecoder.decode(StringCoding.java:138) at java.lang.StringCoding.decode(StringCoding.java:173) at java.lang.String.init(String.java:444) at java.lang.String.init(String.java:516) at org.fontbox.cmap.CMapParser.createStringFromBytes(CMapParser.java:418) at org.fontbox.cmap.CMapParser.parse(CMapParser.java:152) at org.pdfbox.pdmodel.font.PDFont.parseCmap(PDFont.java:535) at org.pdfbox.pdmodel.font.PDFont.encode(PDFont.java:387) at org.pdfbox.util.PDFStreamEngine.showString(PDFStreamEngine.java:325) at org.pdfbox.util.operator.ShowText.process(ShowText.java:64) at org.pdfbox.util.PDFStreamEngine.processOperator(PDFStreamEngine.java:452 ) at org.pdfbox.util.PDFStreamEngine.processSubStream(PDFStreamEngine.java:21 5) at
Re: [Dspace-tech] current status of UTF-8 in dspace and XML-UI / Manakin
Hi Stuart I have a couple of modifications I use in XMLUI to get this working better In XMLUI (Manakin) I have the following: In xmlui/artfactbrowser/SimpleSearch.java I have changed the methodo POST to GET ... Division query = search.addInteractiveDivision(general-query, ,Division.METHOD_GET,secondary search); ... In ArtifactBrowser/sitemap.xml I have: In map:actions use: map:actions map:action name=set-encoding src=org.apache.cocoon.acting.SetCharacterEncodingAction/ in each map:match pattern=search use: map:act type=set-encoding map:parameter name=form-encoding value=ISO-8859-1/ /map:act before the lines that say: map:serialize type=xml/ this was done for: search, handle/*/*/simple-search, simple-search, handle/*/*/search, advanced-search, handle/*/*/advanced-search, browse- author, browse-author-items, browse-subject, browse-subject-items, handle/*/*/browse-author, handle/*/*/browse-author-items, handle/*/*/ browse-subject e handle/*/*/browse-subject-items. I hope this helps Paulo- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Manakin home page links
Hello, I have simple question about Manakin. I need to edit text in dspace/config/news-xmlui.xml and have some html links along with the text there. This appears on the home page of DSpace. When I add links they are striped out, when I use HTML entities for brackets link shows up literally but not as a hot link. Thanks, Serhiy - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
