Re: [Dspace-tech] Error Importing UTF-8 encoded file (some Chinese Characters)..
Did you run index-init and (update-discovery-index if you're using Discovery) after enabling ChieneseAnalyzer? This might be related: https://jira.duraspace.org/browse/DS-1170 Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] [KE1019161] OAI XML output not well formated
On Fri, Dec 14, 2012 at 8:42 AM, marco.we...@kesslernetworks.de wrote: if i send a request to the OAI interface with my browser i get an XML back that have all lines on the left side without indentation. Can you tell me how i can create a output that is much better readable for humans? Hi Marco, in [dspace]/config/crosswalks/oai/xoai.xml set the identation attribute of Configuration to true. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] [KE1019161] Adding new metadata formats to OAI interface
On Fri, Dec 14, 2012 at 8:31 AM, marco.we...@kesslernetworks.de wrote: i'm very in the XML world but i think you mean something like this (the xsd and the xsl) do you need to include it in DSpace? xsi:schemaLocation=urn:nbn:de:-2004033116 http://www.persistent-identifier.de/xepicur/version1.0/xepicur.xsd; Yes, exactly. I don't think it's absolutely necessary to include it (as opposed to linking to it), but it's probably a good idea because tests should work offline, too. It would be in the testing framework,. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] [KE1019161] OAI XML output not well formated
Hi Helix, sorry wont work, the header is well formated but the rest not. Looks like this now. ?xml version=1.0 encoding=UTF-8??xml-stylesheet type=text/xsl href=static/style.xsl?OAI-PMH xmlns=http://www.openarchives.org/OAI/2.0/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd;responseDate2012-12-14T10:32:19Z/responseDate request identifier=oai:urntest:123456789/5 metadataPrefix=oai_dc verb=GetRecordhttp://urntest.hsta.int:8080/oai/request/request GetRecord record header identifieroai:urntest:123456789/5/identifier datestamp2012-12-13T10:15:18Z/datestamp setSpeccom_123456789_1/setSpec setSpeccol_123456789_2/setSpec /header metadata oai_dc:dc xmlns:dc=http://purl.org/dc/elements/1.1/; xmlns:doc=http://www.lyncode.com/xoai; xmlns:oai_dc=http://www.openarchives.org/OAI/2.0/oai_dc/; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd; dc:titledfasfasf/dc:title dc:creatorVorname, Nachname/dc:creator dc:descriptionZusammengetragen und in Auftrag gegeben von der Äbtissin Katherina Nussperger, geschrieben von Hermann Sack (s.f.61v)/dc:description dc:descriptionEnthält: f.2-3v Geschichte des Klosters mit Beschreibung der Reformation des Klosters 1480 (dt.). f.4-5v: Notizen zur Geschichte des Klosters und anderen Ereignissen (lat.). f.6-11v: Angaben über Schenkungen. f.12-61v: Totenbuch. Mit vielen Namen der Klosterangehörigen./dc:description dc:date2012-12-13T09:14:01Z/dc:date dc:date2012-12-13T09:14:01Z/dc:date dc:date2012-12-13/dc:date dc:typeBook/dc:type dc:identifierhttp://www.gda.bayern.de/findmittel/ead/index.php?fb=415/dc:identifier dc:identifierhttp://hdl.handle.net/123456789/5/dc:identifier dc:identifierurn:nbn:de:stab-6cbfa16d-a865-4dc3-bd31-e9d4f7c12e4f/dc:identifier dc:languagede/dc:language /oai_dc:dc /metadata /record /GetRecord /OAI-PMH Zitat von helix84 heli...@centrum.sk: On Fri, Dec 14, 2012 at 8:42 AM, marco.we...@kesslernetworks.de wrote: if i send a request to the OAI interface with my browser i get an XML back that have all lines on the left side without indentation. Can you tell me how i can create a output that is much better readable for humans? Hi Marco, in [dspace]/config/crosswalks/oai/xoai.xml set the identation attribute of Configuration to true. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] [KE1019161] OAI XML output not well formated
I see, that's strage, it should be indented: https://github.com/DSpace/DSpace/blob/dspace-3_x/dspace/config/crosswalks/oai/metadataFormats/oai_dc.xsl#L19 Probably a bug, I'll see what I can do. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] [KE1019161] OAI XML output not well formated
Hi Helix, ok possibly i have a solution. I changed the indent from yes to true see following line in my xsl and now i get well formated XML. xsl:output omit-xml-declaration=yes method=xml indent=true / But this only works if identation=true is set in the config/crosswalks/oai/xoai.xml If identation=false is set in config/crosswalks/oai/xoai.xml i get just one line for all elements from my epicur xml. But strange is if i change this in the oai_dc.xsl it wont work for oai_dc here i get all on the left side furthermore. Regards Marco Zitat von helix84 heli...@centrum.sk: I see, that's strage, it should be indented: https://github.com/DSpace/DSpace/blob/dspace-3_x/dspace/config/crosswalks/oai/metadataFormats/oai_dc.xsl#L19 Probably a bug, I'll see what I can do. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Mvn package build fail
Issue Resolved. Actually the problem is (due to dspace online documentaation which says: to manually install Oracle JDBC Driver with maven command : mvn install:install . , as incomplete oracle version is mentioned 11.2.0.3 instead of 11.2.0.3.0) . Secondly again according to dspace online documentation: add Oracle dependency descriptor in pom.xml , which is not required, because it is already mentioned in pom.xml file, ALL you need is to correct the driver version 11.2.0.2.0 TO 11.2.0.3.0 After that run mvn package command to build your package for oracle . You will be successful. --- On Thu, 12/13/12, mErRYo merryob...@yahoo.com wrote: From: mErRYo merryob...@yahoo.com Subject: Re: Mvn package build fail To: heli...@centrum.sk Cc: hilton.gib...@gmail.com, lighton.ph...@gmail.com, jm...@lyncode.com, dspace-tech@lists.sourceforge.net, mw...@iupui.edu Date: Thursday, December 13, 2012, 9:14 PM Guys I already these steps as mentioned by Mr. Wood and Helix but the result is same error. I got few warnings also which is as follows: [WARNING] Some problems were encountered while building the effective model for org.dspace:dspace:pom:3.0 [WARNING] 'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: com.oracle:ojdbc6:jar - version 11.2.0.2 vs 11.2.0.2.0 @ org.dspace:dspace-parent:3.0, /usr/local/dspace-3.0-src-release/pom.xml, line 853, column 22 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. my log file is also attached. --- On Thu, 12/13/12, helix84 heli...@centrum.sk wrote: From: helix84 heli...@centrum.sk Subject: Re: Mvn package build fail To: mErRYo merryob...@yahoo.com Cc: hilton.gib...@gmail.com, lighton.ph...@gmail.com, jm...@lyncode.com, dspace-tech@lists.sourceforge.net Date: Thursday, December 13, 2012, 7:22 PM On Thu, Dec 13, 2012 at 1:46 PM, mErRYo merryob...@yahoo.com wrote: I am using dspace 3.0 release and my maven build is failing when i try to run this command mvn -Ddb.name=oracle package The correct installation procedure for Oracle is described in the official documentation: https://wiki.duraspace.org/display/DSDOC3x/Installation Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] [KE1019161] OAI XML output not well formated
On Fri, Dec 14, 2012 at 12:01 PM, marco.we...@kesslernetworks.de wrote: ok possibly i have a solution. I changed the indent from yes to true see following line in my xsl and now i get well formated XML. That's strange. http://www.w3.org/XML/2000/04schema-hacking/xslt.xsd attribute name=indent type=xsl:yesno/ simpleType name=yesno base=NMTOKEN enumeration value=yes/ enumeration value=no/ /simpleType Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Mvn package build fail
On Fri, Dec 14, 2012 at 12:03 PM, mErRYo merryob...@yahoo.com wrote: Actually the problem is (due to dspace online documentaation which says: to manually install Oracle JDBC Driver with maven command : mvn install:install . , as incomplete oracle version is mentioned 11.2.0.3 instead of 11.2.0.3.0) . I corrected the documentation to say 11.2.0.3.0. But I think it would work as it was (because it told you to put 11.2.0.3 also in pom). Secondly again according to dspace online documentation: add Oracle dependency descriptor in pom.xml , which is not required, because it is already mentioned in pom.xml file, ALL you need is to correct the driver version 11.2.0.2.0 TO 11.2.0.3.0 It is there because you need to install the same version as you have in pom. By default, that is 11.2.0.2.0 (see link), so you needed to change it if you installed 11.2.0.3.0. https://github.com/DSpace/DSpace/blob/dspace-3_x/pom.xml#L849 Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Ant fresh_install fails
On Fri, Dec 14, 2012 at 12:33 PM, mErRYo merryob...@yahoo.com wrote: [java] 2012-12-14 16:23:17,461 FATAL org.dspace.administer.RegistryLoader @ anonymous::error_loading_registries: [java] java.lang.NullPointerException [java] at org.dspace.storage.rdbms.ColumnInfo.canonicalize(ColumnInfo.java:154) That's strange, there's nothing on this line that would cause a NPE: https://github.com/DSpace/DSpace/blob/dspace-3_x/dspace-api/src/main/java/org/dspace/storage/rdbms/ColumnInfo.java#L154 What do you see there in your sources? Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Internal System Error
On Fri, Dec 14, 2012 at 8:20 AM, Parul Dubey parul.du...@itsl.in wrote: After adding some fields to metadata .Again clicking to the adminstrator on the navigation bar it shows an internal error. Kindly suggest how to handle this error. Hi Parul, this Internal System Error message is just a generic message. To track down the cause of the error, you'll want to look at your dspace log files for any errors noted there. We've written a Troubleshoot an error guide to help you figure out what to look for: https://wiki.duraspace.org/display/DSPACE/Troubleshoot+an+error Once you locate the error message, if you cannot figure out its meaning, you are welcome to send it off to this dspace-tech list. Someone on this list can help you determine what the issue may be. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] [KE1019161] OAI XML output not well formated
Hi, ok that explain it to me why it works with true ;) If you put indent=true it's like you did set nothing because its wrong Now after deleting indent=true from my xsl and setting identation=true in xoai.xml it works Doing the same in oai_dc.xsl, deleting indent=yes it, works there too! Setting indent=no in oai_dc.xsl gives you furthermore a well formatted XML so the xoai.xml overwrites the setting, or? Setting indent=yes in oai_dc.xsl gives you bad formatted XML and thats strange because if xoai.xml overwrites the xsl setting i'll expect a well formatted XML. Setting indent=yes in oai_dc.xsl an deleteing identation=true in xoai.xml gives you a bad formatted XML. So my knowledge in XML is too insufficient to work out what is wrong. For me it works with that solution above. The question is, should i open a bug report for that for dspace? Best regards Marco Zitat von helix84 heli...@centrum.sk: On Fri, Dec 14, 2012 at 12:01 PM, marco.we...@kesslernetworks.de wrote: ok possibly i have a solution. I changed the indent from yes to true see following line in my xsl and now i get well formated XML. That's strange. http://www.w3.org/XML/2000/04schema-hacking/xslt.xsd attribute name=indent type=xsl:yesno/ simpleType name=yesno base=NMTOKEN enumeration value=yes/ enumeration value=no/ /simpleType Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] [KE1019161] OAI XML output not well formated
Hi Marco, that's strange, XOAI.xml indentation is applied to the final XML result. So if the output coming from the XSL is indented or not doesn't matter. Are you cleaning OAI cache? Is there any exception being thrown? On 14 December 2012 12:34, marco.we...@kesslernetworks.de wrote: Hi, ok that explain it to me why it works with true ;) If you put indent=true it's like you did set nothing because its wrong Now after deleting indent=true from my xsl and setting identation=true in xoai.xml it works Doing the same in oai_dc.xsl, deleting indent=yes it, works there too! Setting indent=no in oai_dc.xsl gives you furthermore a well formatted XML so the xoai.xml overwrites the setting, or? Setting indent=yes in oai_dc.xsl gives you bad formatted XML and thats strange because if xoai.xml overwrites the xsl setting i'll expect a well formatted XML. Setting indent=yes in oai_dc.xsl an deleteing identation=true in xoai.xml gives you a bad formatted XML. So my knowledge in XML is too insufficient to work out what is wrong. For me it works with that solution above. The question is, should i open a bug report for that for dspace? Best regards Marco Zitat von helix84 heli...@centrum.sk: On Fri, Dec 14, 2012 at 12:01 PM, marco.we...@kesslernetworks.de wrote: ok possibly i have a solution. I changed the indent from yes to true see following line in my xsl and now i get well formated XML. That's strange. http://www.w3.org/XML/2000/04schema-hacking/xslt.xsd attribute name=indent type=xsl:yesno/ simpleType name=yesno base=NMTOKEN enumeration value=yes/ enumeration value=no/ /simpleType Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- Thanks, João Melo (My Portfolio http://www.lyncode.com/m/jmelo/) DSpace Department *Lyncode*: Official websitehttp://www.google.com/url?q=http%3A%2F%2Fwww.lyncode.com%2Fsa=Dsntz=1usg=AFrqEzdV8iS6rMxflxnn138XReuRfUG3OQ [image: Follow us on Facebook]http://www.google.com/url?q=http%3A%2F%2Ftwitter.com%2Flyncodesa=Dsntz=1usg=AFrqEzeDuT3ZqMW5uVIA8AoxtTtAeiCX3Q http://www.google.com/url?q=http%3A%2F%2Fwww.facebook.com%2Flyncodesa=Dsntz=1usg=AFrqEzcWXjHa3gKBGLsNVxktapxkiWDnww -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Statistics question
On Thu, Dec 13, 2012 at 9:52 PM, Andrea Schweer schw...@waikato.ac.nz wrote: Jira issue pull request done -- I was just waiting for feedback from Ian. Thanks for your comments, Ian! https://jira.duraspace.org/browse/DS-1426 https://github.com/DSpace/DSpace/pull/157 Thanks! The pull request is against master; I can make a new one against dspace-3_x if that helps. No need, I cherry-picked it instead. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Do not remove certain metadata (qualifier = extent) when using migrate (- m) in Item Export (v 1.6.2)
Hi Helix84 From the documentation indicates that there are more fields that are deleted when you use the flag -m: http://www.dspace.org/1_6_2Documentation/ch08.html # N15CA6 That is, not only are you say, but also: data.issued format.extent format.mimetype The key should be in class ItemExport, which is the class that manages the migration export items. File not know metadata_local.xml use. Thanks a lot. -- View this message in context: http://dspace.2283337.n4.nabble.com/Do-not-remove-certain-metadata-qualifier-extent-when-using-migrate-m-in-Item-Export-v-1-6-2-tp4660367p4660508.html Sent from the DSpace - Tech mailing list archive at Nabble.com. -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Ant fresh_install fails
Well the code is right and according to github (weblink that helix provided). I think the problem is with oracle db scripts. I don't understand why its not working with oracle when it is working fine with postgre. I mean i have dspace3.0 release with postgre also and it worked fine. Postgre DB schema is created and values inserted fine. Please help. Its very urgent as my production installation got broke and i have timelines to meet. --- On Fri, 12/14/12, helix84 heli...@centrum.sk wrote: From: helix84 heli...@centrum.sk Subject: Re: Ant fresh_install fails To: mErRYo merryob...@yahoo.com Cc: hilton.gib...@gmail.com, lighton.ph...@gmail.com, jm...@lyncode.com, dspace-tech@lists.sourceforge.net, mw...@iupui.edu Date: Friday, December 14, 2012, 5:00 PM On Fri, Dec 14, 2012 at 12:33 PM, mErRYo merryob...@yahoo.com wrote: [java] 2012-12-14 16:23:17,461 FATAL org.dspace.administer.RegistryLoader @ anonymous::error_loading_registries: [java] java.lang.NullPointerException [java] at org.dspace.storage.rdbms.ColumnInfo.canonicalize(ColumnInfo.java:154) That's strange, there's nothing on this line that would cause a NPE: https://github.com/DSpace/DSpace/blob/dspace-3_x/dspace-api/src/main/java/org/dspace/storage/rdbms/ColumnInfo.java#L154 What do you see there in your sources? Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] input-forms.xml : bug on comments
Hi All, according to https://wiki.duraspace.org/display/DSPACE/TechnicalFaq#TechnicalFaq-HowdoIreportbugs? Bugs should be sent to the list first, so here it is. I stumbled on a quite annoying little bug, given how simple it is, and WHERE it lies: I was doing some tests on the input-forms.xml file in order to include some new fields and value-pairs Lng debugging story short: I was including some !-- comments -- in order not to get lost, so I had the brilliant idea of being quite graphical in separating a few value-pairs lists. Something like this: !--Value-pairs for XYZ list--- !--Value-pairs for 123 list--- And so I got Error interno del sistema aka Internal System Error Every time I tried to describe and submit some new document. I finally found that these variations give the same error: !--Value-pairs for XYZ list--- !--Value-pairs for XYZ list-- - -- !--Value-pairs for XYZ list -- -- !--Value-pairs for XYZ list- - - - - - - - - - - - - - - -- -- !--Value-pairs for XYZ list- -- - - - - - - - - - - - - - - -- While these ones work fine: !--Value-pairs for XYZ list - -- !--Value-pairs for XYZ list-- !--Value-pairs for XYZ list- - - - - - - - - - - - - - - - -- So, I think we are apparently not allowed to include comments with more than 1 - anywhere inside! :S Hope this helps someone, and gets corrected some day (obviously, this is easy to work around, but annoying to me). This happen both with DSpace 1.8.1 on Windows XP and with DSpace 1.8.2 on Ubuntu (12.04.1) Kindest regards, Nicolas Rucks. -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] [KE1019161] OAI XML output not well formated
Hi Joao, yes every time i restart my tomcat and cleaning the oai cache like it is written in the documentation. No, no exception is being thrown during the start of tomcat or cache cleaning or oai request ... Zitat von João Melo jm...@lyncode.com: Hi Marco, that's strange, XOAI.xml indentation is applied to the final XML result. So if the output coming from the XSL is indented or not doesn't matter. Are you cleaning OAI cache? Is there any exception being thrown? On 14 December 2012 12:34, marco.we...@kesslernetworks.de wrote: Hi, ok that explain it to me why it works with true ;) If you put indent=true it's like you did set nothing because its wrong Now after deleting indent=true from my xsl and setting identation=true in xoai.xml it works Doing the same in oai_dc.xsl, deleting indent=yes it, works there too! Setting indent=no in oai_dc.xsl gives you furthermore a well formatted XML so the xoai.xml overwrites the setting, or? Setting indent=yes in oai_dc.xsl gives you bad formatted XML and thats strange because if xoai.xml overwrites the xsl setting i'll expect a well formatted XML. Setting indent=yes in oai_dc.xsl an deleteing identation=true in xoai.xml gives you a bad formatted XML. So my knowledge in XML is too insufficient to work out what is wrong. For me it works with that solution above. The question is, should i open a bug report for that for dspace? Best regards Marco Zitat von helix84 heli...@centrum.sk: On Fri, Dec 14, 2012 at 12:01 PM, marco.we...@kesslernetworks.de wrote: ok possibly i have a solution. I changed the indent from yes to true see following line in my xsl and now i get well formated XML. That's strange. http://www.w3.org/XML/2000/04schema-hacking/xslt.xsd attribute name=indent type=xsl:yesno/ simpleType name=yesno base=NMTOKEN enumeration value=yes/ enumeration value=no/ /simpleType Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- Thanks, João Melo (My Portfolio http://www.lyncode.com/m/jmelo/) DSpace Department *Lyncode*: Official websitehttp://www.google.com/url?q=http%3A%2F%2Fwww.lyncode.com%2Fsa=Dsntz=1usg=AFrqEzdV8iS6rMxflxnn138XReuRfUG3OQ [image: Follow us on Facebook]http://www.google.com/url?q=http%3A%2F%2Ftwitter.com%2Flyncodesa=Dsntz=1usg=AFrqEzeDuT3ZqMW5uVIA8AoxtTtAeiCX3Q http://www.google.com/url?q=http%3A%2F%2Fwww.facebook.com%2Flyncodesa=Dsntz=1usg=AFrqEzcWXjHa3gKBGLsNVxktapxkiWDnww -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] input-forms.xml : bug on comments
Hi Nicolás, this is part of the XML specification: http://www.w3.org/TR/2004/REC-xml-20040204/#sec-comments There's nothing to do here, sorry. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] input-forms.xml : bug on comments
I can see it is quite well documented there: For compatibility, the string -- (double-hyphen) MUST NOT occur within comments. Sorry for the false report then. What an interesting XML feature, a restriction on a comment you cannot do... I guess there are quite serious reasons to do that: http://www.w3.org/TR/2004/REC-xml-20040204/#dt-compat for compatibility [Definition: Marks a sentence describing a feature of XML included solely to ensure that XML remains compatible with SGML.] My mistake. Nicolas Rucks. -Mensaje original- De: ivan.ma...@gmail.com [mailto:ivan.ma...@gmail.com] En nombre de helix84 Enviado el: viernes 14 de diciembre de 2012 10:38 Para: Nicolás Rucks CC: dspace-tech@lists.sourceforge.net Asunto: Re: [Dspace-tech] input-forms.xml : bug on comments Hi Nicolás, this is part of the XML specification: http://www.w3.org/TR/2004/REC-xml-20040204/#sec-comments There's nothing to do here, sorry. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Do not remove certain metadata (qualifier = extent) when using migrate (- m) in Item Export (v 1.6.2)
Right, I didn't find it in the documentation, but you did. The point seems to be that these metadata fields should be recreated after being transferred (but I don't know how dc.format.extent is supposed to be recreated - perhaps by media filter?). If you really need a workaround, I suggest you rename (in database) the metadatafields you need to keep to something else, export, import them and then rename them back. File not know metadata_local.xml use. Nevermind that, I also tested with a new namespace called local. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Unwanted errors in Cocoon.log
The DSpace Page Not Found page is rendered from the main sitemap, here: https://github.com/DSpace/DSpace/blob/master/dspace-xmlui/src/main/webapp/sitemap.xmap#L673 - Tim On 12/13/2012 4:56 PM, Ian Boston wrote: Hi Tim, Thank you. Could you give me a pointer to where the DSpace page is rendered? Looking at the Coocon code it should be done by [1], but in DSpace that doesnt take the blindest bit of notice of the setting org.apache.cocoon.manageexceptions, which if set to false should just set the status. Incidentally, in the code I am looking at the status is set correctly when managed, at least in the cocoon codebase. If a ResourceNotFoundException appears as a 404 with html content, see [2], and the log message is issued at warn level. I am looking at the section of the stack below where think the ResourceNotFoundException is handled (line 189 in org.apache.cocoon.servlet.RequestProcessor ) at org.apache.cocoon.servlet.RequestProcessor.process(RequestProcessor.java:351) at org.apache.cocoon.servlet.RequestProcessor.service(RequestProcessor.java:169) at org.apache.cocoon.sitemap.SitemapServlet.service(SitemapServlet.java:84) Thanks Ian 1 org.apache.cocoon.servlet.RequestUtil.manageException(HttpServletRequest, HttpServletResponse, Environment, String, int, String, String, String, Exception, ServletSettings, boolean, Object) 2 org.apache.cocoon.servlet.RequestProcessor line 200: RequestUtil.manageException(request, res, env, uri, HttpServletResponse.SC_NOT_FOUND, Resource Not Found, Resource Not Found, The requested resource \ + request.getRequestURI() + \ could not be found, e, this.servletSettings, getLogger(), this); return; On 14 December 2012 02:21, Tim Donohue tdono...@duraspace.org wrote: Hi Ian, Just now saw this thread about the ugly 404 error page logs in DSpace XMLUI / Cocoon. You may already be aware of when/why this came about. But, I figured I'd fill in some history just in case you (or others) are not. Essentially, prior to DSpace 1.8.x, DSpace XMLUI actually had a nicer looking XMLUI Page Not Found Error page. It just simply said page not found and looked like every other page in your XMLUI theme. However, then we discovered that Apache Cocoon was responding with 200 OK on *every error page* in the XMLUI, see this ticket https://jira.duraspace.org/browse/DS-768 Essentially, the only resolution we were able to come up with was to actually patch Apache Cocoon to throw the proper 404 error. So we created a patched copy of the Cocoon code which was throwing 200 instead of 404. That patched code is maintained here: https://github.com/DSpace/dspace-cocoon-servlet-service-impl Unfortunately though, in our patching of this Cocoon bug, we were not able to get our nicer looking Page Not Found error page to display again...instead, we were left with the ugly error page you see now. That patch to Cocoon may have also been the cause of the messages you are seeing in the Cocoon.log. There may be ways to fix this clean up both the Page Not Found error page and limit the output in the Cocoon.log. I haven't looked into it in some time. But, if you find anything that works for you, I'd highly encourage you to send us a Pull Request or a patch -- I think this is something we'd all like to see fixed. Not sure if this info will be of help. But, at least know you know the full story of where this issue began. - Tim On 12/12/2012 3:42 AM, Ian Boston wrote: On 12 December 2012 20:15, helix84 heli...@centrum.sk wrote: Hi Ian, I don't know about shortening the stacktrace, but that's a pretty generic Java question so you may try googling around. I dont think there is a way other than changing the Cocoon code, blocking the logger or not throwing the exception and setting a 404 status code in the Dspace code. I might just do the latter. To answer at least a part of your question, this is where 404s are handled in Cocoon. You may want to edit the XSL to filter what you send to the user for specific exceptions and leave the rest (the unexpected ones) as stacktraces. https://github.com/DSpace/DSpace/blob/dspace-3_x/dspace-xmlui/src/main/webapp/sitemap.xmap#L673 Ok, thanks for the pointer. Ian Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add
