Re: [Dspace-tech] PostgreSQL refuse access
Thanks for Your hint. The result of 'lsof -i tcp:5432' is: COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME postgres 5384 postgres3u IPv4 17284 TCP localhost:postgresql (LISTEN) This looks quite ok. Or should there are more processes / files? Regards Robert James Rutherford schrieb: Robert Roggenbuck wrote: Connection denied. Check the hostname and portnumber and be sure the the database server accept TCP/IP-connections. Did you check this? Try running lsof -i tcp:5432 as root on the database server to see if postgres is listening for TCP connections. cheers, Jim - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] PostgreSQL refuse access
On Tue, Nov 20, 2007 at 08:58:04AM +, Robert Roggenbuck wrote: Thanks for Your hint. The result of 'lsof -i tcp:5432' is: COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME postgres 5384 postgres3u IPv4 17284 TCP localhost:postgresql (LISTEN) This looks quite ok. Or should there are more processes / files? No, this is fine. The only thing I can think of then is that either something changed in your pg_hba.conf to deny access to your DSpace user or your dspace.cfg has been updated, and the incorrect password is in there. Is the database running on the same machine as tomcat? cheers, Jim -- James Rutherford | Hewlett-Packard Limited registered Office: Research Engineer | Cain Road, HP Labs | Bracknell, Bristol, UK | Berks +44 117 312 7066 | RG12 1HN. [EMAIL PROTECTED] | Registered No: 690597 England The contents of this message and any attachments to it are confidential and may be legally privileged. If you have received this message in error, you should delete it from your system immediately and advise the sender. To any recipient of this message within HP, unless otherwise stated you should consider this message and attachments as HP CONFIDENTIAL. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] itemexport.java
Hi!
In the writeMetadata()method of
DSPace141\src\org\dspace\app\itemexport.java, if the qualifier value is
changed from qualifier == null to qualifier=uri or
qualifier=available, changes to the dublin core file (i.e.
dcv.qualifier) is not reflected. Please suggest how to make changes to
the qualifier values in the exported dublin core file through the
itemexport method. I was trying this out to eliminate the dublin core
handler field while exporting items from one instance to another
instance.
if (qualifier == null)
{
qualifier = none;
}
utf8 = ( dcvalue element=\ + dcv.element + \
+ qualifier=\ + qualifier + \
+ Utils.addEntities(dcv.value) +
/dcvalue\n).getBytes(UTF-8);
Thanks,
Jayan
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] PostgreSQL refuse access
James Rutherford schrieb: No, this is fine. The only thing I can think of then is that either something changed in your pg_hba.conf to deny access to your DSpace user or your dspace.cfg has been updated, and the incorrect password is in there. Is the database running on the same machine as tomcat? The database runs on the same machine as Tomcat. The password in dspace.cfg is correct (and without trailing spaces). I added one line in pg_hba.conf after (!) the connection failes - but without success (it is the last line in the following snippet): begin pg_hba.conf# local all postgres ident sameuser # TYPE DATABASEUSERCIDR-ADDRESS METHOD # local is for Unix domain socket connections only local all all ident sameuser # IPv4 local connections: hostall all 127.0.0.1/32 md5 # IPv6 local connections: hostall all ::1/128 md5 # DSpace settings: hostdspace dspace 127.0.0.1 255.255.255.255 md5 # hostdspace dspace 131.173.148.100 255.255.255.255 md5 end pg_hba.conf Greetings Robert - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Differences between the data model and the trunk
On Nov 20, 2007, at 3:55 AM, Andrea Bollini wrote: Larry Stone ha scritto: Collection * - * Item It's worth noting that while an Item may be a member of multiple Collections, it still refers to only one of them as its owner; it is returned by getOwningCollection(). true but IMHO this is not really needed... Well, what I've suggested in my previous email is not wether it is needed or not, but where it should correctly reside in relational terms, owner is a relationship, not an attribute of Item and Collection, thus the more appropriate location would be in the container or relationship tables. I.E. rather than: --- -- Item table --- CREATE TABLE Item ( item_id INTEGER PRIMARY KEY, submitter_idINTEGER REFERENCES EPerson(eperson_id), in_archive BOOL, withdrawn BOOL, last_modified TIMESTAMP WITH TIME ZONE, owning_collection INTEGER ); --- -- Collection2Item table --- CREATE TABLE Collection2Item ( idINTEGER PRIMARY KEY, collection_id INTEGER REFERENCES Collection(collection_id), item_id INTEGER REFERENCES Item(item_id), ); instead have --- -- Item table --- CREATE TABLE Item ( item_id INTEGER PRIMARY KEY, submitter_idINTEGER REFERENCES EPerson(eperson_id), in_archive BOOL, withdrawn BOOL, last_modified TIMESTAMP WITH TIME ZONE ); --- -- Collection2Item table --- CREATE TABLE Collection2Item ( idINTEGER PRIMARY KEY, collection_id INTEGER REFERENCES Collection(collection_id), item_id INTEGER REFERENCES Item(item_id), owning_collection BOOL ); Ownership is a relationship and not a attribute and the dependency is one way. This also is an example that enforces third normal form because you cannot have a owning collection for which the item is not a member. (Although you can have multiple owners). When an Item is accessed directly, by itself without the navigational context of one of the Collections it belongs to, it consults the owning Collection for display style this is only one possibility and it is not the most useful (see MedataStyleSelection in 1.5) Very true and we will see that Manakin will mix this up even more. and policies (e.g. access control by Collection admins). the auth system need a lot of work, in my path community admin that introduce some hierarchy control I have used the owning collection as the only real parent i.e. if I want modify the item but I have not direct permission I check for ADMIN right on owning collection... this is not optimal, if we have an item mapped in an other collection I think that only directly authorized people or ADMIN of both collection should manage it For Daniele works I recommend to keep ownCollection in place but I think that we need to remove it in future version. PS:the concept of owning collection is used also in workflow and submission system but there is a main difference: the data are stored in inProgressSubmission object not in the item object. Also in this case I hope that we can introduce a more modular way to select workflow process and submission process then simply use the owning collection. Andrea Andrea, that is another example of what I speak of above. At least in this case, we see that inProgressSubmission (or WorkspaceItem) is really a container like collection and we've attached the item to that rather than attaching it to the item. I just think this is much cleaner and actually does not require altering the item table to move an item between WorkspaceItem and WorkflowItem when it is moved from Submission to Management Workflows. I would support moving/or removing owning_collection if it improved the model and the ability to work with tools. I think we would want a path of deprecation however, and using the above relationship approach could more easily give us that. -Mark - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Stadistics Dspace
I need configure Stadistics in mu dspace. The follow message show: There are currently no reports available for this service. Please check back later. Thanks - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Manakin error
Manakin 1.1a with DSpace 1.4.2 produces the following when trying to access profile or submissions menu items with Reference theme. Any idea whats wrong? -Mika -- An error has occured org.mozilla.javascript.EvaluatorException: file:/home/dspace/tomcat/webapps/manakin/aspects/EPerson/eperson.js, line 47: Not a Java class: [JavaPackage org.dspace.aspect.eperson.EPerson] Cocoon stacktrace [hide] Sitemap: error calling function 'doUpdateProfile' context:/file:/home/dspace/tomcat/webapps/manakin/aspects/EPerson/sitemap.xmap - 117:45map:call context:/file:/home/dspace/tomcat/webapps/manakin/aspects/aspects.xmap - 124:72 map:mount context:/file:/home/dspace/tomcat/webapps/manakin/sitemap.xmap - 274:80 map:mount context:/file:/home/dspace/tomcat/webapps/manakin/aspects/Submission/sitemap.xmap - 369:38map:serialize type=xml context:/file:/home/dspace/tomcat/webapps/manakin/aspects/Submission/sitemap.xmap - 145:45map:transform type=Navigation context:/file:/home/dspace/tomcat/webapps/manakin/aspects/Submission/sitemap.xmap - 142:26map:generate context:/file:/home/dspace/tomcat/webapps/manakin/aspects/Administrative/sitemap.xmap - 797:31map:serialize type=xml context:/file:/home/dspace/tomcat/webapps/manakin/aspects/Administrative/sitemap.xmap - 265:38map:transform type=Navigation context:/file:/home/dspace/tomcat/webapps/manakin/aspects/Administrative/sitemap.xmap - 264:44map:transform type=SystemwideAlerts context:/file:/home/dspace/tomcat/webapps/manakin/aspects/Administrative/sitemap.xmap - 263:19map:generate context:/file:/home/dspace/tomcat/webapps/manakin/aspects/aspects.xmap - 120:34 map:serialize type=xml context:/file:/home/dspace/tomcat/webapps/manakin/aspects/aspects.xmap - 119:43 map:transform type=PageNotFound context:/file:/home/dspace/tomcat/webapps/manakin/aspects/aspects.xmap - 118:22 map:generate context:/file:/home/dspace/tomcat/webapps/manakin/themes/Reference/sitemap.xmap - 171:34map:serialize type=xhtml context:/file:/home/dspace/tomcat/webapps/manakin/themes/Reference/sitemap.xmap - 168:84map:transform type=NamespaceFilter context:/file:/home/dspace/tomcat/webapps/manakin/themes/Reference/sitemap.xmap - 167:78map:transform type=NamespaceFilter context:/file:/home/dspace/tomcat/webapps/manakin/themes/Reference/sitemap.xmap - 161:33map:transform type=i18n context:/file:/home/dspace/tomcat/webapps/manakin/themes/Reference/sitemap.xmap - 157:44map:transform context:/file:/home/dspace/tomcat/webapps/manakin/themes/Reference/sitemap.xmap - 142:45map:transform type=IncludePageMeta context:/file:/home/dspace/tomcat/webapps/manakin/themes/Reference/sitemap.xmap - 118:55map:generate type=file context:/file:/home/dspace/tomcat/webapps/manakin/themes/themes.xmap - 63:45 map:mount context:/file:/home/dspace/tomcat/webapps/manakin/sitemap.xmap - 338:73 map:mount Java stacktrace [hide] org.mozilla.javascript.EvaluatorException: file:/home/dspace/tomcat/webapps/manakin/aspects/EPerson/eperson.js, line 47: Not a Java class: [JavaPackage org.dspace.aspect.eperson.EPerson] at org.apache.cocoon.components.flow.javascript.JSErrorReporter.runtimeError(JSErrorReporter.java:66) at org.mozilla.javascript.Context.reportRuntimeError(Context.java:588) at org.mozilla.javascript.Context.reportRuntimeError(Context.java:627) at org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter$ThreadScope.importClass(FOM_JavaScriptInterpreter.java:490) at inv1.invoke() at org.mozilla.javascript.FunctionObject.doInvoke(FunctionObject.java:523) at org.mozilla.javascript.FunctionObject.callVarargs(FunctionObject.java:538) at org.mozilla.javascript.FunctionObject.call(FunctionObject.java:403) at org.mozilla.javascript.ScriptRuntime.call(ScriptRuntime.java:1244) at org.mozilla.javascript.continuations.ContinuationInterpreter.interpret(ContinuationInterpreter.java:1134) at org.mozilla.javascript.continuations.ContinuationInterpreter.interpret(ContinuationInterpreter.java:190) at org.mozilla.javascript.continuations.ContinuationInterpreter.interpret(ContinuationInterpreter.java:138) at org.mozilla.javascript.continuations.InterpretedScriptImpl.call(InterpretedScriptImpl.java:137) at org.mozilla.javascript.InterpretedScript.exec(InterpretedScript.java:59) at org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter.setupContext(FOM_JavaScriptInterpreter.java:611) at org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter.callFunction(FOM_JavaScriptInterpreter.java:717) at org.apache.cocoon.components.treeprocessor.sitemap.CallFunctionNode.invoke(CallFunctionNode.java:138) at
Re: [Dspace-tech] Stadistics Dspace
Hola Rodrio, in order to use the statistics you got to do some configuration see [dspace-source]/docs/configure.html#statistics To have them run regularly you must add the appropriate cronjob as listed in the DSpace installation instructions, e.g.: # Run stat analyses 0 1 * * * [dspace]/bin/stat-general 0 1 * * * [dspace]/bin/stat-monthly 0 2 * * * [dspace]/bin/stat-report-general 0 2 * * * [dspace]/bin/stat-report-monthly hope that helps Claudia Rodrigo Castro Artigas schrieb: I need configure Stadistics in mu dspace. The follow message show: There are currently no reports available for this service. Please check back later. Thanks - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Desired hierarchical display of communities and collection list
Hi, I am using dspace-1.4.2 version installed on Linux FC-7 server. How can I see the list of communities and collections in desired hierarchical order, not in alphabetically arranged order? Thanks in anticipation. With Regards, Mohammad Ehtesham DISCLAIMER:The information contained in this message and the attachments (if any) may be privileged and confidential and protected from disclosure. You are hereby notified that any unauthorized use, dissemination, distribution or copying of this communication, review, retransmission, or taking of any action based upon this information, by persons or entities other than the intended recipient, is strictly prohibited. If you are not the intended recipient or an employee or agent responsible for delivering this message, and have received this communication in error, please notify us immediately by replying to the message and kindly delete the original message, attachments, if any, and all its copies from your computer system. Thank you for your cooperation. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] DSpace error
Hi Does anyone know what the error below relates to? we've had these errors occurring intermittently today - perhaps tomcat needs a re-start? 2007-11-20 17:04:13,610 WARN org.dspace.app.webui.servlet.InternalErrorServlet @ :session_id=348891038422FF0478DC37B8F866ADA3:internal_error:-- URL Was: http://deneb.lib.bris.ac.uk/dspace/handle/1983/914 -- Method: GET -- Parameters were: java.lang.IllegalArgumentException: 11 Aug 2007 11:13:22 GMT at org.apache.coyote.tomcat5.CoyoteRequest.getDateHeader(CoyoteRequest.java:1887) at org.apache.coyote.tomcat5.CoyoteRequestFacade.getDateHeader(CoyoteRequestFacade.java:426) at org.dspace.app.webui.servlet.HandleServlet.doDSGet(HandleServlet.java:157) at org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:151) at org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:99) at javax.servlet.http.HttpServlet.service(HttpServlet.java:697) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) 9517,11 99% at org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:99) at javax.servlet.http.HttpServlet.service(HttpServlet.java:697) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:2 37) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:296) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:372) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:694) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:626) at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:807) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:644) at java.lang.Thread.run(Thread.java:595) Thanks, Naveed Naveed Hashmi Information Systems and Computing University of Bristol - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] DSpace error
On Nov 20, 2007 12:43 PM, Tim Donohue [EMAIL PROTECTED] wrote: Naveed, Funny, we just started getting the same error intermittently today, as well. For us it's only happening once every few hours. By way of additional evidence: An internal server error occurred on http://minds.wisconsin.edu: Date: 11/20/07 12:20 PM Session ID: D220224E7826EEFAC75CAB7721F3D99D -- URL Was: http://minds.wisconsin.edu/handle/1793/7881 -- Method: GET -- Parameters were: Exception: java.lang.IllegalArgumentException: 3 Sep 2007 10:20:16 GMT at org.apache.catalina.connector.Request.getDateHeader(Request.java:1798) at org.apache.catalina.connector.RequestFacade.getDateHeader(RequestFacade.java:631) at org.dspace.app.webui.servlet.HandleServlet.doDSGet(HandleServlet.java:193) at org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:151) at org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:99) at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) Ramped up earlier this week; I'm getting one three to five times an hour now. 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: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] DSpace error
Naveed, Funny, we just started getting the same error intermittently today, as well. For us it's only happening once every few hours. I've been digging through our logs for more info. For us, these errors *always* occur from the same web crawler/bot, which is identifying itself as: Yeti/0.01 (nhn/1noon, [EMAIL PROTECTED], check robots.txt daily and follow it) I've been searching around on this bot now. There's some indications that this may just be a bad bot: http://www.webmasterworld.com/search_engine_spiders/3449200.htm I'm not sure if this is the same problem you are seeing, Naveed? - Tim NS Hashmi, Information Systems and Computing wrote: Hi Does anyone know what the error below relates to? we've had these errors occurring intermittently today - perhaps tomcat needs a re-start? 2007-11-20 17:04:13,610 WARN org.dspace.app.webui.servlet.InternalErrorServlet @ :session_id=348891038422FF0478DC37B8F866ADA3:internal_error:-- URL Was: http://deneb.lib.bris.ac.uk/dspace/handle/1983/914 -- Method: GET -- Parameters were: java.lang.IllegalArgumentException: 11 Aug 2007 11:13:22 GMT at org.apache.coyote.tomcat5.CoyoteRequest.getDateHeader(CoyoteRequest.java:1887) at org.apache.coyote.tomcat5.CoyoteRequestFacade.getDateHeader(CoyoteRequestFacade.java:426) at org.dspace.app.webui.servlet.HandleServlet.doDSGet(HandleServlet.java:157) at org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:151) at org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:99) at javax.servlet.http.HttpServlet.service(HttpServlet.java:697) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) 9517,11 99% at org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:99) at javax.servlet.http.HttpServlet.service(HttpServlet.java:697) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:2 37) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:296) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:372) at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:694) at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:626) at
Re: [Dspace-tech] how to create a non-interative submission step in manakin
Hi Tim,
Thanks for the help.
I had problem to generate the DSpace log. Somehow variable ${log.dir} in
log4j.properties can't be interpreted correctly and I now hard coded the
path.
I got tons of these messages in DSpace log when I clicked the submit to
this collection button.
2007-11-20 12:14:49,787 INFO org.dspace.content.Item @
[EMAIL
PROTECTED]:session_id=7996091CCADE661966DC61371FFDACD2:update_item:item_id=11
2007-11-20 12:14:49,790 INFO org.dspace.content.WorkspaceItem @
[EMAIL
PROTECTED]:session_id=7996091CCADE661966DC61371FFDACD2:update_workspace_item:workspace_item
_id=11
2007-11-20 12:14:49,790 INFO org.dspace.content.Item @
[EMAIL
PROTECTED]:session_id=7996091CCADE661966DC61371FFDACD2:update_item:item_id=11
2007-11-20 12:14:49,793 INFO org.dspace.content.WorkspaceItem @
[EMAIL
PROTECTED]:session_id=7996091CCADE661966DC61371FFDACD2:update_workspace_item:workspace_item
_id=11
2007-11-20 12:14:49,825 INFO org.dspace.content.Item @
[EMAIL
PROTECTED]:session_id=7996091CCADE661966DC61371FFDACD2:update_item:item_id=11
2007-11-20 12:14:49,828 INFO org.dspace.content.WorkspaceItem @
[EMAIL
PROTECTED]:session_id=7996091CCADE661966DC61371FFDACD2:update_workspace_item:workspace_item
_id=11
This explains why DSpace hangs there. The item will be created in
workspaceitem table and in item table. Could you help me on how to fix the
problem?
Thanks very much,
Ying
- Original Message -
From: Tim Donohue [EMAIL PROTECTED]
To: yinjin [EMAIL PROTECTED]
Cc: dspace-tech@lists.sourceforge.net
Sent: Monday, November 19, 2007 10:41 AM
Subject: Re: [Dspace-tech] how to create a non-interative submission step in
manakin
Ying,
To be honest, your code configuration all look correct. I'm not sure
offhand what the problem could be, unless for some reason DSpace or
Manakin isn't able to find the custom class you created.
Are you getting any errors in any of the following logs when you click
on the submission button?
DSpace log @ [dspace]/log/dspace.log
Tomcat logs @ [tomcat]/logs/
Manakin logs @ [tomcat]/webapps/dspace-xmlui/WEB-INF/logs/
If Manakin/DSpace is hanging, it's highly likely it's erroring out
somewhere along the way.
- Tim
yinjin wrote:
Hi Tim,
Thanks for the information. I have tried to create a non-interative step
by
following the instructions. It doesn't seem difficult. However, the
DSpace
will hang there whenever I click the submission or submit to this
collection button.
Here is what I did. Can you point out where I'm doing wrong?
===
public class NonInteractiveStep extends AbstractProcessingStep
{
/** log4j logger */
private static Logger log =
Logger.getLogger(NonInteractiveStep.class);
/**
* Do any processing of the information input by the user, and/or
perform
* step processing (if no user interaction required)
* P
* It is this method's job to save any data to the underlying
database,
as
* necessary, and return error messages (if any) which can then be
processed
* by the appropriate user interface (JSP-UI or XML-UI)
* P
* NOTE: If this step is a non-interactive step (i.e. requires no
UI),
then
* it should perform *all* of its processing in this method!
*
* @param context
*current DSpace context
* @param request
*current servlet request object
* @param response
*current servlet response object
* @param subInfo
*submission info object
* @return Status or error flag which will be processed by
* doPostProcessing() below! (if STATUS_COMPLETE or 0 is
returned,
* no errors occurred!)
*/
public int doProcessing(Context context, HttpServletRequest request,
HttpServletResponse response, SubmissionInfo subInfo)
throws ServletException, IOException, SQLException,
AuthorizeException
{
boolean multipleTitles = false;
boolean publishedBefore = true;
boolean multipleFiles = false;
// If step is complete, save the changes
subInfo.getSubmissionItem().setMultipleTitles(multipleTitles);
subInfo.getSubmissionItem().setPublishedBefore(publishedBefore);
subInfo.getSubmissionItem().setMultipleFiles(multipleFiles);
// commit all changes to DB
subInfo.getSubmissionItem().update();
context.commit();
return STATUS_COMPLETE; // no errors!
}
/**
* Retrieves the number of pages that this step extends over. This
method
* is used to build the progress bar.
* P
* This method may just return 1 for most steps (since most steps
consist of
* a single page). But, it should return a number greater than 1 for
any
* step which spans across a number of HTML pages. For example, the
* configurable Describe step (configured
Re: [Dspace-tech] Manakin error
This seems strange, since I get this when using the latest stable (1.1a) version. If I use version 1.0 I get another error below - whats it about? -- Internal Server Error Message: null Description: No details available. Sender: org.dspace.app.xmlui.DSpaceCocoonServlet Source: Cocoon Servlet Request URI submit cause null request-uri /manakin/submit Apache Cocoon 2.1.9 -- -Mika -Alkuperäinen viesti- Lähettäjä: Paulo Jobim [mailto:[EMAIL PROTECTED] Lähetetty: 20. marraskuuta 2007 18:12 Vastaanottaja: Mika Stenberg Kopio: 'dspace-tech@lists.sourceforge.net' Aihe: Re: [Dspace-tech] Manakin error Hi Mika There was a point where this eperson.js pointed to a class that has been modified. try geting a more recent code or modify the java script to point to the right class I hope this helps Paulo Em Nov 20, 2007, às 11:56 AM, Mika Stenberg escreveu: Manakin 1.1a with DSpace 1.4.2 produces the following when trying to access profile or submissions menu items with Reference theme. Any idea whats wrong? -Mika -- An error has occured org.mozilla.javascript.EvaluatorException: file:/home/dspace/tomcat/webapps/manakin/aspects/EPerson/eperson.js, line 47: Not a Java class: [JavaPackage org.dspace.aspect.eperson.EPerson] Cocoon stacktrace [hide] Sitemap: error calling function 'doUpdateProfile' context:/file:/home/dspace/tomcat/webapps/manakin/aspects/EPerson/ sitemap.xmap - 117:45 map:call context:/file:/home/dspace/tomcat/webapps/manakin/aspects/ aspects.xmap - 124:72map:mount context:/file:/home/dspace/tomcat/webapps/manakin/sitemap.xmap - 274:80map:mount context:/file:/home/dspace/tomcat/webapps/manakin/aspects/ Submission/sitemap.xmap - 369:38 map:serialize type=xml context:/file:/home/dspace/tomcat/webapps/manakin/aspects/ Submission/sitemap.xmap - 145:45 map:transform type=Navigation context:/file:/home/dspace/tomcat/webapps/manakin/aspects/ Submission/sitemap.xmap - 142:26 map:generate context:/file:/home/dspace/tomcat/webapps/manakin/aspects/ Administrative/sitemap.xmap - 797:31 map:serialize type=xml context:/file:/home/dspace/tomcat/webapps/manakin/aspects/ Administrative/sitemap.xmap - 265:38 map:transform type=Navigation context:/file:/home/dspace/tomcat/webapps/manakin/aspects/ Administrative/sitemap.xmap - 264:44 map:transform type=SystemwideAlerts context:/file:/home/dspace/tomcat/webapps/manakin/aspects/ Administrative/sitemap.xmap - 263:19 map:generate context:/file:/home/dspace/tomcat/webapps/manakin/aspects/ aspects.xmap - 120:34map:serialize type=xml context:/file:/home/dspace/tomcat/webapps/manakin/aspects/ aspects.xmap - 119:43map:transform type=PageNotFound context:/file:/home/dspace/tomcat/webapps/manakin/aspects/ aspects.xmap - 118:22map:generate context:/file:/home/dspace/tomcat/webapps/manakin/themes/Reference/ sitemap.xmap - 171:34 map:serialize type=xhtml context:/file:/home/dspace/tomcat/webapps/manakin/themes/Reference/ sitemap.xmap - 168:84 map:transform type=NamespaceFilter context:/file:/home/dspace/tomcat/webapps/manakin/themes/Reference/ sitemap.xmap - 167:78 map:transform type=NamespaceFilter context:/file:/home/dspace/tomcat/webapps/manakin/themes/Reference/ sitemap.xmap - 161:33 map:transform type=i18n context:/file:/home/dspace/tomcat/webapps/manakin/themes/Reference/ sitemap.xmap - 157:44 map:transform context:/file:/home/dspace/tomcat/webapps/manakin/themes/Reference/ sitemap.xmap - 142:45 map:transform type=IncludePageMeta context:/file:/home/dspace/tomcat/webapps/manakin/themes/Reference/ sitemap.xmap - 118:55 map:generate type=file context:/file:/home/dspace/tomcat/webapps/manakin/themes/themes.xmap - 63:45 map:mount context:/file:/home/dspace/tomcat/webapps/manakin/sitemap.xmap - 338:73map:mount Java stacktrace [hide] org.mozilla.javascript.EvaluatorException: file:/home/dspace/tomcat/webapps/manakin/aspects/EPerson/eperson.js, line 47: Not a Java class: [JavaPackage org.dspace.aspect.eperson.EPerson] at org.apache.cocoon.components.flow.javascript.JSErrorReporter.runtimeEr ror(JSErrorReporter.java:66) at org.mozilla.javascript.Context.reportRuntimeError(Context.java: 588) at org.mozilla.javascript.Context.reportRuntimeError(Context.java: 627) at org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpr eter$ThreadScope.importClass(FOM_JavaScriptInterpreter.java:490) at inv1.invoke() at org.mozilla.javascript.FunctionObject.doInvoke (FunctionObject.java:523) at org.mozilla.javascript.FunctionObject.callVarargs (FunctionObject.java:538) at org.mozilla.javascript.FunctionObject.call(FunctionObject.java: 403) at org.mozilla.javascript.ScriptRuntime.call(ScriptRuntime.java:1244) at
Re: [Dspace-tech] DSpace error
Hi Tim, Yes, same problem - our apache access log shows the bot:- 61.247.217.34 - - [20/Nov/2007:20:06:18 +] GET /robots.txt HTTP/1.1 200 166 - Yeti/0.01 (nhn/1noon, yetibot@ naver.com, check robots.txt daily and follow it) I'll block this IP. Thanks, Naveed --On 20 November 2007 12:43 -0600 Tim Donohue [EMAIL PROTECTED] wrote: Naveed, Funny, we just started getting the same error intermittently today, as well. For us it's only happening once every few hours. I've been digging through our logs for more info. For us, these errors *always* occur from the same web crawler/bot, which is identifying itself as: Yeti/0.01 (nhn/1noon, [EMAIL PROTECTED], check robots.txt daily and follow it) I've been searching around on this bot now. There's some indications that this may just be a bad bot: http://www.webmasterworld.com/search_engine_spiders/3449200.htm I'm not sure if this is the same problem you are seeing, Naveed? - Tim NS Hashmi, Information Systems and Computing wrote: Hi Does anyone know what the error below relates to? we've had these errors occurring intermittently today - perhaps tomcat needs a re-start? 2007-11-20 17:04:13,610 WARN org.dspace.app.webui.servlet.InternalErrorServlet @ :session_id=348891038422FF0478DC37B8F866ADA3:internal_error:-- URL Was: http://deneb.lib.bris.ac.uk/dspace/handle/1983/914 -- Method: GET -- Parameters were: java.lang.IllegalArgumentException: 11 Aug 2007 11:13:22 GMT at org.apache.coyote.tomcat5.CoyoteRequest.getDateHeader(CoyoteRequest.java :1887) at org.apache.coyote.tomcat5.CoyoteRequestFacade.getDateHeader(CoyoteReques tFacade.java:426) at org.dspace.app.webui.servlet.HandleServlet.doDSGet(HandleServlet.java:15 7) at org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet. java:151) at org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:99) at javax.servlet.http.HttpServlet.service(HttpServlet.java:697) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:237) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:157) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e.java:214) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo ntext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:5 20) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardCon textValve.java:198) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e.java:152) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo ntext.java:104) 9517,11 99% at org.dspace.app.webui.servlet.DSpaceServlet.doGet(DSpaceServlet.java:99) at javax.servlet.http.HttpServlet.service(HttpServlet.java:697) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica tionFilterChain.java:2 37) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt erChain.java:157) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv e.java:214) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo ntext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:5 20) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardCon textValve.java:198) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv e.java:152) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo ntext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:5 20) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java :137) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo ntext.java:104) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java :117) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo ntext.java:102) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:5 20) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. java:109) at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveCo ntext.java:104) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:5 20) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160) at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:296) at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:372) at
[Dspace-tech] Creative Commons issues EVEN AFTER recent fixes
One of the individuals who deposits documents into our IR is continuining to have issues with the Creative Commons portion of the process. When the individual clicks on the proceed link, the iFrame goes blank and the page remains static. Only by skipping the creative commons process with the Skip button is the user able to get to the normal license. The user is using a PC, and we have tried both Firefox and IE. However, I do not run into this problem on my Mac. I have tried logging into the users account on my Mac, and into my account on the users PC, but the problem appears to be related to the PC itself. I tried a public PC in our library and ran into the same issue. In IE, I am able to generate an error that reads: Line: 14 Char: 1 Error: Access is denied. Code: 0 URL: http://u2.gmu.edu:8080/dspace/submit/cc-license.jsp?license_url=http%3A//creativecommons.org/licenses/by-nc-nd/3.0 The only strange thing I have noticed is the http%3A// in the URL, but I'm unable to determine where that URL comes from and why it wouldn't cause an issue on the Mac. Ideas? Shane Beers Digital Repository Services Librarian George Mason University [EMAIL PROTECTED] 703-993-3742 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Creative Commons issues EVEN AFTER recent fixes
Shane Beers wrote: One of the individuals who deposits documents into our IR is continuining to have issues with the Creative Commons portion of the process. When the individual clicks on the proceed link, the iFrame goes blank and the page remains static. Only by skipping the creative commons process with the Skip button is the user able to get to the normal license. The user is using a PC, and we have tried both Firefox and IE. Hi Shane, The CC iframe has been a source of problems before: http://sourceforge.net/tracker/index.php?func=detailaid=1644932group_id=19984atid=119984 it's quite an ugly way of handling the creative commons license as well. Thankfully, there is a better solution - a web service API: http://api.creativecommons.org/docs/ and http://wiki.creativecommons.org/Creative_Commons_Web_Services also, http://api.creativecommons.org/docs/readme_dev.html unfortunately, it's not been implemented as part of DSpace as yet. If anyone has the time to take a stab at this, I would be very keen to see this take the place of the existing integration. G This email has been scanned by Postini. For more information please visit http://www.postini.com - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Creative Commons issues EVEN AFTER recent fixes
Hi Shane, It sounds like a problem we’re having here were DSpace is causing some characters to become encoded ( %3A = : ), so your URL is becoming http%3A//creativecommons.org/licenses/by-nc-nd/3.0 instead of HYPERLINK http://creativecommons.org/licenses/by-nc-nd/3.0http://creativecommons.org/licenses/by-nc-nd/3.0. DSpace encodes characters to their escape characters and I’ve not been able to figure out myself how to stop it, but my advanced search encodes (‘s, )’s and %’s to %28, %29 and %25 respectively. I know that the code for my problem is in the URLencode portion of the JSPs, but I couldn’t tell you why you are having that issue. Jake -- Jake Cameron, BCSc(UNB) Technical Specialist III Library Systems and Web Services University of Lethbridge Phone: (403) 329-2756 Office: L1110C Email: [EMAIL PROTECTED] _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Shane Beers Sent: Tuesday, November 20, 2007 1:44 PM To: dspace-tech Subject: [Dspace-tech] Creative Commons issues EVEN AFTER recent fixes One of the individuals who deposits documents into our IR is continuining to have issues with the Creative Commons portion of the process. When the individual clicks on the proceed link, the iFrame goes blank and the page remains static. Only by skipping the creative commons process with the Skip button is the user able to get to the normal license. The user is using a PC, and we have tried both Firefox and IE. However, I do not run into this problem on my Mac. I have tried logging into the users account on my Mac, and into my account on the users PC, but the problem appears to be related to the PC itself. I tried a public PC in our library and ran into the same issue. In IE, I am able to generate an error that reads: http://u2.gmu.edu:8080/dspace/submit/cc-license.jsp?license_url=http%3A//creativecommons.org/licenses/by-nc-nd/3.0 The only strange thing I have noticed is the http%3A// in the URL, but I'm unable to determine where that URL comes from and why it wouldn't cause an issue on the Mac. Ideas? Shane Beers Digital Repository Services Librarian George Mason University HYPERLINK mailto:[EMAIL PROTECTED][EMAIL PROTECTED] 703-993-3742 No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.503 / Virus Database: 269.16.1/1140 - Release Date: 11/19/2007 7:05 PM No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.503 / Virus Database: 269.16.1/1140 - Release Date: 11/19/2007 7:05 PM - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Export Import - URI -- Test to Production server
Hi! Mark,
While items are transferred from the Test server (Export) to the
Production server (Import), by default the handler URI appears twice.
Since the handler assigned by the test server is not relevant it looks
fine to remove the assigned handler by slightly modifying the
C:\DSPace141\src\org\dspace\app\itemexport\ItemExport.java. The
//writeHandle(c, myItem, itemDir); method was commented and the
following conditional statement was added to remove the dublin core
handler specific elements and qualifiers. This helps the production
system to generate a new handler to the batch ingested items. Could you
please suggest whether it could be practiced for solving the double uri
representation. Is there any other easy solution for this from
postgresql. Please suggest. Thanks, Jayan
if (qualifier == null)
{
qualifier = none;
}
boolean b = String.valueOf(qualifier).equals(String.valueOf(uri));
if (b)
{
System.out.println(Handler URI DC statement removed);
}
else
{
utf8 = ( dcvalue element=\ + dcv.element + \
+ qualifier=\ + qualifier + \
+ Utils.addEntities(dcv.value) +
/dcvalue\n).getBytes(UTF-8);
out.write(utf8, 0, utf8.length);
}
From: Mark Diggory [mailto:[EMAIL PROTECTED]
Sent: Sat 11/3/2007 12:26 PM
To: Jayan Chirayath Kurian
Cc: Dorothea Salo; DSpace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] Export Import - URI
Hello Jayan,
For:
http://repository.ntu.edu.sg/handle/X23456789/2215
The uri are:
1.) Older uri from the previous system:
http://hdl.handle.net/123456789/2741
2.) the Newer URI assigned by the new system
http://hdl.handle.net/X23456789/2215
Then challenge is what to do with the Handle URI creation process.
Because the handles are assigned sequentially as items are created in
dspace, they cannot be designated on ingest. In reality, they are
representative of the identical logical item existing in each system.
If you have real handle systems configured, both would resolve to their
corresponding dspace instances appropriately.
If you can do without the older handle, you might process the dublincore
file in the export directory if your using ItemExport (or the mets
package if your using the packager framework) to remove that field.
Cheers,
Mark
On Nov 3, 2007, at 12:03 AM, Jayan Chirayath Kurian wrote:
Hi! Dorothea,
All items appear to have this double URI. I was wondering whether it
could be to specify that the item has been imported from another dspace
instance with xyz URI and now the item is with the present instance with
the 2nd URI. Any suggestions. http://repository.ntu.edu.sg/
Thanks,
Jayan
From: [EMAIL PROTECTED] on behalf of Dorothea
Salo
Sent: Fri 11/2/2007 10:15 PM
To: DSpace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] Export Import - URI
I was trying to export a collection from one server and import into
another
dspace server. The ingestion process was fine but the URI: appears
twice one
below the other. Is there any specific reason for the uri to get
displayed
twice? How to get this displayed only once. Please suggest
I see a couple of possibilities. One thing that may have happened is
some metadata duplication during the export/ingest cycle. (I've only
ever had this happen during actual database migration, but your
mileage may vary.) Go into your database and ask the metadatavalues
table for all the metadata surrounding this particular item; if you've
doubled the URI field somehow, you'll see it and be able to deal with
it.
The other possibility is that something's gone wrong with your JSP
such that it is calling for the URI twice. That should be an easy fix!
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: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now http://get.splunk.com/
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now
http://get.splunk.com/___
DSpace-tech mailing list
