Hello, We are having a problem exporting from OJS 2.4.4.1 into D-Space 3.2 xmlui using SWORDv1.
After some trial and error we have managed to enable SWORD on both D-Space and OJS, but are having some problems with depositing from OJS into D-Space. When we try and export from OJS to deposit into D-Space we get a message that "The item(s) selected have been deposited." However, the item never appears in the selected D-Space collection. When we check the D-Space logs we get the following warning and error: Cannot find named plugin for interface=org.dspace.sword.SWORDIngester, name="null" org.purl.sword.base.SWORDErrorException: No ingester configured for this package type Calling [dspaceurl]/sword/servicedocument works properly and we are using the "Optional; Flexible" setting for the deposit point in the OJS SWORD plugin. We are looking to see if anyone else has had this problem and how they resolved it. Cross posted from PKP Support forum. Karl Wirth Digital Repository Librarian Creighton University Health Sciences Library (402) 280-5130 -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Thursday, July 02, 2015 8:45 AM To: [email protected] Subject: DSpace-tech Digest, Vol 111, Issue 2 Send DSpace-tech mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/dspace-tech or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of DSpace-tech digest..." Today's Topics: 1. Build DSpace Installer on Different Machine (Shannon Meisenheimer) 2. Re: Build DSpace Installer on Different Machine (Peter Dietz) 3. Changing embargo dates in DSpace 5.2 (George Stanley Kozak) 4. Problems installing dSpace 5 in Ubuntu Server 14.04 (Camilo Freire) 5. Re: Problems installing dSpace 5 in Ubuntu Server 14.04 (Camilo Freire) 6. Solr stats queries - limiting by date (Gary Browne) 7. Re: Build DSpace Installer on Different Machine (Becker, Pascal-Nicolas) 8. Re: Solr stats queries - limiting by date ([email protected]) 9. Re: Dspace 3.2 to 5.2 (Lewatle Phaladi) 10. Re: Changing embargo dates in DSpace 5.2 (Becker, Pascal-Nicolas) 11. Dspace scripts not works in 1.7.2 (Ruben) 12. Re: Dspace 3.2 to 5.2 (euler) 13. Re: Dspace 3.2 to 5.2 (Lewatle Phaladi) 14. Re: Dspace 3.2 to 5.2 (euler) 15. Re: dc.date.accessioned incorrect setting (Graham Faulkner) 16. Re: Dspace 3.2 to 5.2 (Tim Donohue) 17. Re: Disable Handle? (Tim Donohue) 18. Re: Changing embargo dates in DSpace 5.2 (George Stanley Kozak) ---------------------------------------------------------------------- Message: 1 Date: Wed, 1 Jul 2015 09:24:53 -0500 From: Shannon Meisenheimer <[email protected]> Subject: [Dspace-tech] Build DSpace Installer on Different Machine To: [email protected] Message-ID: <can2wqg8arvdg+spgoxw+cedejy6yn8othxnzb5yfdht9ztm...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Has anyone tried building DSpace (Maven) on a different machine and then moving the resulting src package to the server for Ant install/update? We are pretty sure we are fighting network restrictions on the server when building DSpace 5.1 with Mirage 2. I'm running 'mvn -U clean package -Dmirage2.on=true -X > c:\Maven5_1.log' using Maven 3.2.3 and after installation, pdf delivery is very slow (sometimes 10-20 minutes). I was thinking I could build the package on my workstation where I'm not being firewalled as heavily and then transfer to the server for install. We've had our network team add FW exceptions allowing outbound from the server to any destination on ports 80, 443, and 9418 and outbound to any for the server in our proxy, but still are seeing some performance issues post install. Setting up the proxy in Maven had no effect. Does Ant use anything other what it is in the source package during install? I noticed maven created a bunch of files in my user'e temp folder (win server). Thanks, Shannon -- Mr. Shannon Meisenheimer Office of Technology Blackboard and Academic Application Management University of Central Missouri Dockery 207A [email protected] Work Phone: (660) 543-8483 -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ Message: 2 Date: Wed, 1 Jul 2015 10:51:45 -0400 From: Peter Dietz <[email protected]> Subject: Re: [Dspace-tech] Build DSpace Installer on Different Machine To: Shannon Meisenheimer <[email protected]> Cc: "[email protected]" <[email protected]> Message-ID: <cacl+z9ulbxghrbhckz8zzd9derf02bpnx12p-qmben8l5q3...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi Shannon, We do almost all builds using a dedicated build server. So one machine does the "mvn package" portion of the work, and then dspace/target/dspace-installer gets ftp/scp/rsync to application servers, and then on the app server does the ant update portion. The thing that you have to ensure is that each machine is very similar. Same OS, same version of java. I've never tried this with windows, but it works well for us on Linux. ________________ Peter Dietz Longsight www.longsight.com [email protected] p: 740-599-5005 x809 On Wed, Jul 1, 2015 at 10:24 AM, Shannon Meisenheimer <[email protected] > wrote: > Has anyone tried building DSpace (Maven) on a different machine and then > moving the resulting src package to the server for Ant install/update? > > We are pretty sure we are fighting network restrictions on the server when > building DSpace 5.1 with Mirage 2. I'm running 'mvn -U clean package > -Dmirage2.on=true -X > c:\Maven5_1.log' using Maven 3.2.3 and after > installation, pdf delivery is very slow (sometimes 10-20 minutes). > > I was thinking I could build the package on my workstation where I'm not > being firewalled as heavily and then transfer to the server for install. > > We've had our network team add FW exceptions allowing outbound from the > server to any destination on ports 80, 443, and 9418 and outbound to any > for the server in our proxy, but still are seeing some performance issues > post install. Setting up the proxy in Maven had no effect. > > Does Ant use anything other what it is in the source package during > install? I noticed maven created a bunch of files in my user'e temp folder > (win server). > > Thanks, > Shannon > -- > Mr. Shannon Meisenheimer > Office of Technology > Blackboard and Academic Application Management > University of Central Missouri > Dockery 207A > [email protected] > Work Phone: (660) 543-8483 > > > > ------------------------------------------------------------------------------ > Don't Limit Your Business. Reach for the Cloud. > GigeNET's Cloud Solutions provide you with the tools and support that > you need to offload your IT needs and focus on growing your business. > Configured For All Businesses. Start Your Cloud Today. > https://www.gigenetcloud.com/ > _______________________________________________ > DSpace-tech mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dspace-tech > List Etiquette: > https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette > -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ Message: 3 Date: Wed, 1 Jul 2015 18:08:38 +0000 From: George Stanley Kozak <[email protected]> Subject: [Dspace-tech] Changing embargo dates in DSpace 5.2 To: "[email protected]" <[email protected]> Message-ID: <blupr0401mb1684fe33d4ee0b99c0750efb9f...@blupr0401mb1684.namprd04.prod.outlook.com> Content-Type: text/plain; charset="us-ascii" Hi... How do people handle changing the Embargo dates in DSpace 5.2? As far as I can tell, once an item has been submitted as embargoed, it can only be changed by manually modifying the resourcepolicy table. Am I wrong of is there a programmatic way to change the dates? George Kozak Digital Library Specialist Cornell University Library Information Technologies (CUL-IT) 218 Olin Library Cornell University Ithaca, NY 14853 607-255-8924 -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ Message: 4 Date: Wed, 1 Jul 2015 18:24:09 -0300 From: Camilo Freire <[email protected]> Subject: [Dspace-tech] Problems installing dSpace 5 in Ubuntu Server 14.04 To: [email protected] Message-ID: <camzv8nygl_psfxbpn1q2c82o4uxoycsd8jp_qwxo8qh_r4d...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hi, I'm installing dSpace on Ubuntu 14.04 following step by step instructions of the dSpace Wiki, when I try to run up the application an error message message shown above is displayed: Can any one give me any suggestion about the possible ways of solving it? Best regards Camilo Freire Estado HTTP 500 - {msg=SolrCore 'search' is not available due to init failure: Could not load conf for core search: Error loading solr config from /dspace/solr/search/conf/solrconfig.xml,trace=org.apache.solr.common.SolrException: SolrCore 'search' is not available due to init failure: Could not load conf for core search: Error loading solr config from /dspace/solr/search/conf/solrconfig.xml at org.apache.solr.core.CoreContainer.getCore(CoreContainer.java:745) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:299) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:207) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.dspace.solr.filters.LocalHostRestrictionFilter.doFilter(LocalHostRestrictionFilter.java:50) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:313) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: org.apache.solr.common.SolrException: Could not load conf for core search: Error loading solr config from /dspace/solr/search/conf/solrconfig.xml at org.apache.solr.core.ConfigSetService.getConfig(ConfigSetService.java:66) at org.apache.solr.core.CoreContainer.create(CoreContainer.java:489) at org.apache.solr.core.CoreContainer$1.call(CoreContainer.java:255) at org.apache.solr.core.CoreContainer$1.call(CoreContainer.java:249) at java.util.concurrent.FutureTask.run(FutureTask.java:262) ... 3 more Caused by: org.apache.solr.common.SolrException: Error loading solr config from /dspace/solr/search/conf/solrconfig.xml at org.apache.solr.core.SolrConfig.readFromResourceLoader(SolrConfig.java:154) at org.apache.solr.core.ConfigSetService.createSolrConfig(ConfigSetService.java:80) at org.apache.solr.core.ConfigSetService.getConfig(ConfigSetService.java:61) ... 7 more Caused by: java.io.IOException: Can't find resource 'solrconfig.xml' in classpath or '/dspace/solr/search/conf' at org.apache.solr.core.SolrResourceLoader.openResource(SolrResourceLoader.java:362) at org.apache.solr.core.SolrResourceLoader.openConfig(SolrResourceLoader.java:308) at org.apache.solr.core.Config.<init>(Config.java:117) at org.apache.solr.core.Config.<init>(Config.java:87) at org.apache.solr.core.SolrConfig.<init>(SolrConfig.java:167) at org.apache.solr.core.SolrConfig.readFromResourceLoader(SolrConfig.java:145) ... 9 more ,code=500} -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ Message: 5 Date: Wed, 1 Jul 2015 18:57:04 -0300 From: Camilo Freire <[email protected]> Subject: Re: [Dspace-tech] Problems installing dSpace 5 in Ubuntu Server 14.04 To: Hilton Gibson <[email protected]>, [email protected] Message-ID: <CAMZv8nZfRoEpEVo0CvoxdL1a1Ty0SRSg3r=urcdlua0zzw5...@mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hilton, thank you very much, quite a valuable help. Finally I find out the problem: dSpace wasn't capable of reading the solrconfig.xml file because the Linux file permissions weren't set correctly (although an chmod 775 -R /dspace command was performed). Thank you very much Camilo Freire 2015-07-01 18:45 GMT-03:00 Hilton Gibson <[email protected]>: > http://wiki.lib.sun.ac.za/index.php/SUNScholar/DSpace > > *Hilton Gibson* > Ubuntu Linux Systems Administrator > Stellenbosch University Library > http://staff.lib.sun.ac.za/~hgibson/docs/cv/cv.html > > > On 1 July 2015 at 23:24, Camilo Freire <[email protected]> wrote: > >> Hi, I'm installing dSpace on Ubuntu 14.04 following step by step >> instructions of the dSpace Wiki, when I try to run up the application an >> error message message shown above is displayed: >> >> Can any one give me any suggestion about the possible ways of solving it? >> >> Best regards >> Camilo Freire >> >> Estado HTTP 500 - {msg=SolrCore 'search' is not available due to init >> failure: Could not load conf for core search: Error loading solr config >> from >> /dspace/solr/search/conf/solrconfig.xml,trace=org.apache.solr.common.SolrException: >> SolrCore 'search' is not available due to init failure: Could not load conf >> for core search: Error loading solr config from >> /dspace/solr/search/conf/solrconfig.xml at >> org.apache.solr.core.CoreContainer.getCore(CoreContainer.java:745) at >> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:299) >> at >> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:207) >> at >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) >> at >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) >> at >> org.dspace.solr.filters.LocalHostRestrictionFilter.doFilter(LocalHostRestrictionFilter.java:50) >> at >> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) >> at >> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) >> at >> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220) >> at >> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122) >> at >> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501) >> at >> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170) >> at >> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98) >> at >> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950) >> at >> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) >> at >> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) >> at >> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040) >> at >> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607) >> at >> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:313) >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >> at java.lang.Thread.run(Thread.java:745) Caused by: >> org.apache.solr.common.SolrException: Could not load conf for core search: >> Error loading solr config from /dspace/solr/search/conf/solrconfig.xml at >> org.apache.solr.core.ConfigSetService.getConfig(ConfigSetService.java:66) >> at org.apache.solr.core.CoreContainer.create(CoreContainer.java:489) at >> org.apache.solr.core.CoreContainer$1.call(CoreContainer.java:255) at >> org.apache.solr.core.CoreContainer$1.call(CoreContainer.java:249) at >> java.util.concurrent.FutureTask.run(FutureTask.java:262) ... 3 more Caused >> by: org.apache.solr.common.SolrException: Error loading solr config from >> /dspace/solr/search/conf/solrconfig.xml at >> org.apache.solr.core.SolrConfig.readFromResourceLoader(SolrConfig.java:154) >> at >> org.apache.solr.core.ConfigSetService.createSolrConfig(ConfigSetService.java:80) >> at >> org.apache.solr.core.ConfigSetService.getConfig(ConfigSetService.java:61) >> ... 7 more Caused by: java.io.IOException: Can't find resource >> 'solrconfig.xml' in classpath or '/dspace/solr/search/conf' at >> org.apache.solr.core.SolrResourceLoader.openResource(SolrResourceLoader.java:362) >> at >> org.apache.solr.core.SolrResourceLoader.openConfig(SolrResourceLoader.java:308) >> at org.apache.solr.core.Config.<init>(Config.java:117) at >> org.apache.solr.core.Config.<init>(Config.java:87) at >> org.apache.solr.core.SolrConfig.<init>(SolrConfig.java:167) at >> org.apache.solr.core.SolrConfig.readFromResourceLoader(SolrConfig.java:145) >> ... 9 more ,code=500} >> >> >> ------------------------------------------------------------------------------ >> Don't Limit Your Business. Reach for the Cloud. >> GigeNET's Cloud Solutions provide you with the tools and support that >> you need to offload your IT needs and focus on growing your business. >> Configured For All Businesses. Start Your Cloud Today. >> https://www.gigenetcloud.com/ >> _______________________________________________ >> DSpace-tech mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/dspace-tech >> List Etiquette: >> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette >> > > -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ Message: 6 Date: Thu, 2 Jul 2015 06:10:55 +0000 From: Gary Browne <[email protected]> Subject: [Dspace-tech] Solr stats queries - limiting by date To: "[email protected]" <[email protected]> Message-ID: <23DF3A1C5648DD43BCAE0666B5AFAD11D0334E0F@ex-mbx-pro-06> Content-Type: text/plain; charset="us-ascii" Hi all, I'm trying to figure out how to limit solr queries by date. I found this snippet online: http://mydspace.org/solr/statistics/select?bundleName:ORIGINAL&facet.date.start=NOW/MONTH/DAY-6MONTHS&facet.date.end=NOW&facet.date.gap=1MONTH+AND+type:0+bundleName:ORIGINAL it fails in my browser (yes, other solr searches work). I'm trying to come up, for starters, with a solr search query for top X items visited in the last X months. Can anyone point me in the right direction here, even to some documentation (I've done a lot of googling but nothing I've found so far helps with this question). THanks, Gary -- Gary Browne | Development Programmer University of Sydney Library THE UNIVERSITY OF SYDNEY Level 1, Fisher Library F03 | The University of Sydney | NSW | 2006 T +61 2 9351 5946 | M +61 405 647 868 E [email protected]<mailto:[email protected]> -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ Message: 7 Date: Thu, 2 Jul 2015 08:12:29 +0000 From: "Becker, Pascal-Nicolas" <[email protected]> Subject: Re: [Dspace-tech] Build DSpace Installer on Different Machine To: Shannon Meisenheimer <[email protected]> Cc: "[email protected]" <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset="utf-8" Hi, to answer your question: yes, ant needs more than the dspace-installer directory. It tries to download a free geodb to connect IPs to countries for the statistic (IIRC). We have a build server which is configured close to our production server (the build server runs centOS, the production server RHEL, but it works fine). On the build server I run maven *and* ant. I install DSpace on the build server to the same path that is used on the production server. Then I create a package (currently a tar, but we plan to build rpms here) and deploy this package on our test and production server. With DSpace 5 we will have to take care for our solr indexes as with DSpace 5 ant takes care for those. But that?s possibly a matter for another thread? Regards, Pascal From: Peter Dietz [mailto:[email protected]] Sent: Wednesday, July 01, 2015 4:52 PM To: Shannon Meisenheimer Cc: [email protected] Subject: Re: [Dspace-tech] Build DSpace Installer on Different Machine Hi Shannon, We do almost all builds using a dedicated build server. So one machine does the "mvn package" portion of the work, and then dspace/target/dspace-installer gets ftp/scp/rsync to application servers, and then on the app server does the ant update portion. The thing that you have to ensure is that each machine is very similar. Same OS, same version of java. I've never tried this with windows, but it works well for us on Linux. ________________ Peter Dietz Longsight www.longsight.com<http://www.longsight.com> [email protected]<mailto:[email protected]> p: 740-599-5005 x809 On Wed, Jul 1, 2015 at 10:24 AM, Shannon Meisenheimer <[email protected]<mailto:[email protected]>> wrote: Has anyone tried building DSpace (Maven) on a different machine and then moving the resulting src package to the server for Ant install/update? We are pretty sure we are fighting network restrictions on the server when building DSpace 5.1 with Mirage 2. I'm running 'mvn -U clean package -Dmirage2.on=true -X > c:\Maven5_1.log' using Maven 3.2.3 and after installation, pdf delivery is very slow (sometimes 10-20 minutes). I was thinking I could build the package on my workstation where I'm not being firewalled as heavily and then transfer to the server for install. We've had our network team add FW exceptions allowing outbound from the server to any destination on ports 80, 443, and 9418 and outbound to any for the server in our proxy, but still are seeing some performance issues post install. Setting up the proxy in Maven had no effect. Does Ant use anything other what it is in the source package during install? I noticed maven created a bunch of files in my user'e temp folder (win server). Thanks, Shannon -- Mr. Shannon Meisenheimer Office of Technology Blackboard and Academic Application Management University of Central Missouri Dockery 207A [email protected]<mailto:[email protected]> Work Phone: (660) 543-8483<tel:%28660%29%20543-8483> [Das Bild wurde vom Absender entfernt.] ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ DSpace-tech mailing list [email protected]<mailto:[email protected]> https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -------------- next part -------------- An HTML attachment was scrubbed... -------------- next part -------------- A non-text attachment was scrubbed... Name: ~WRD000.jpg Type: image/jpeg Size: 823 bytes Desc: ~WRD000.jpg ------------------------------ Message: 8 Date: Thu, 2 Jul 2015 08:32:40 +0000 From: <[email protected]> Subject: Re: [Dspace-tech] Solr stats queries - limiting by date To: <[email protected]>, <[email protected]> Message-ID: <3e44a0a4a74bb243a7b78adfa7b62c467e047...@exchmbx03.fed.cclrc.ac.uk> Content-Type: text/plain; charset="us-ascii" Hi Gary, I'm not familiar with solr within DSpace but I've done some implementations with solr so the type of query you are looking to do will be something like this: time:[NOW-6MONTH/MONTH TO NOW] AND bundleName:ORIGINAL If you look at the schema fields the only one which is a date field is time so I'm guessing that this is the timestamp of the stats event and this gives me results that look about right. http://localhost/solr/statistics/select?q=time%3A%5BNOW-6MONTH%2FMONTH+TO+NOW%5D+AND+bundleName%3AORIGINAL I've no idea what field bundleName stores ;-) Alastair From: Gary Browne [mailto:[email protected]] Sent: 02 July 2015 07:11 To: [email protected] Subject: [Dspace-tech] Solr stats queries - limiting by date Hi all, I'm trying to figure out how to limit solr queries by date. I found this snippet online: http://mydspace.org/solr/statistics/select?bundleName:ORIGINAL&facet.date.start=NOW/MONTH/DAY-6MONTHS&facet.date.end=NOW&facet.date.gap=1MONTH+AND+type:0+bundleName:ORIGINAL it fails in my browser (yes, other solr searches work). I'm trying to come up, for starters, with a solr search query for top X items visited in the last X months. Can anyone point me in the right direction here, even to some documentation (I've done a lot of googling but nothing I've found so far helps with this question). THanks, Gary -- Gary Browne | Development Programmer University of Sydney Library THE UNIVERSITY OF SYDNEY Level 1, Fisher Library F03 | The University of Sydney | NSW | 2006 T +61 2 9351 5946 | M +61 405 647 868 E [email protected]<mailto:[email protected]> -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ Message: 9 Date: Thu, 2 Jul 2015 08:33:30 +0000 From: Lewatle Phaladi <[email protected]> Subject: Re: [Dspace-tech] Dspace 3.2 to 5.2 To: "[email protected]" <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset="us-ascii" Hi All, To add on the email I have sent previously, when I create new items collection and add items on this new installation on my dev box new items loaded manually are visible, the old items are not showing. Regards, Lewatle From: Lewatle Phaladi Sent: 01 July 2015 11:09 AM To: [email protected] Subject: Dspace 3.2 to 5.2 Dear Team, I have upgraded dspace 3.2 straight to 5.2, I haven't upgraded to version 4 , I have just did upgrade to version 5.2, all steps went well database upgrade also went well, and after the upgrade all information shows well on XMLUI user interface, and the only part that is not showing is Bitstrams/PFD/Images etc are not visible under any collection, I have checked the path in dspace.cfg all indicated well, I have also asked my colleagues who are developing softwares to team up with me so that we all check where do we miss the step but we executed all commands and responded successfully but the PDF's are not showing, that is where they have started asking if maybe dspace 3.2 is not that upgradable to 5.2 although document seems to say it is upgradable. Regards, Lewatle <table width="100%" border="0" cellspacing="0" cellpadding="0" style="width:100%;"> <tr> <td align="left" style="text-align:justify;"><font face="arial,sans-serif" size="1" color="#999999"><span style="font-size:11px;">This communication is intended for the addressee only. It is confidential. If you have received this communication in error, please notify us immediately and destroy the original message. You may not copy or disseminate this communication without the permission of the University. Only authorised signatories are competent to enter into agreements on behalf of the University and recipients are thus advised that the content of this message may not be legally binding on the University and may contain the personal views and opinions of the author, which are not necessarily the views and opinions of The University of the Witwatersrand, Johannesburg. All agreements between the University and outsiders are subject to South African Law unless the University agrees in writing to the contrary. </span></font></td> </tr> </table -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ Message: 10 Date: Thu, 2 Jul 2015 08:43:37 +0000 From: "Becker, Pascal-Nicolas" <[email protected]> Subject: Re: [Dspace-tech] Changing embargo dates in DSpace 5.2 To: "[email protected]" <[email protected]> Cc: George Stanley Kozak <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset="us-ascii" Hi, if you use the JSPUI this should be fixed in DSpace 5.2. See the ticket in Jira describing the problem and its solution: https://jira.duraspace.org/browse/DS-1965. Starting with DSpace 5.2 you should see the date fields in the administrator interface you use to edit authorizations (login as admin, open an item, click on edit, click on edit, click on authorizations, look for the policy you want to change and click on edit). While writing this mail I see that the dates are not part of the table listing all authorizations of an item. We should change this too. I create the ticket DS-2638 and marked it as needs volunteer. Kind regards, Pascal From: George Stanley Kozak [mailto:[email protected]] Sent: Wednesday, July 01, 2015 8:09 PM To: [email protected] Subject: [Dspace-tech] Changing embargo dates in DSpace 5.2 Hi... How do people handle changing the Embargo dates in DSpace 5.2? As far as I can tell, once an item has been submitted as embargoed, it can only be changed by manually modifying the resourcepolicy table. Am I wrong of is there a programmatic way to change the dates? George Kozak Digital Library Specialist Cornell University Library Information Technologies (CUL-IT) 218 Olin Library Cornell University Ithaca, NY 14853 607-255-8924 -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ Message: 11 Date: Thu, 02 Jul 2015 10:51:16 +0200 From: Ruben <[email protected]> Subject: [Dspace-tech] Dspace scripts not works in 1.7.2 To: "[email protected]" <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset=windows-1252; format=flowed Hi all, Yesterday I noticed that dspace scripts are not working well in my DSpace 1.7.2 (preproduction environment), and I don't know why because they worked previously. The error message showed is: java.lang.IllegalArgumentException: Resource path [/projectes/recercat/dspace/bin/dspace] does not denote a directory at org.springframework.core.io.support.PathMatchingResourcePatternResolver.retrieveMatchingFiles(PathMatchingResourcePatternResolver.java:563) at org.springframework.core.io.support.PathMatchingResourcePatternResolver.doFindMatchingFileSystemResources(PathMatchingResourcePatternResolver.java:543) at org.springframework.core.io.support.PathMatchingResourcePatternResolver.doFindPathMatchingFileResources(PathMatchingResourcePatternResolver.java:526) at org.springframework.core.io.support.PathMatchingResourcePatternResolver.findPathMatchingResources(PathMatchingResourcePatternResolver.java:342) at org.springframework.core.io.support.PathMatchingResourcePatternResolver.getResources(PathMatchingResourcePatternResolver.java:263) at org.dspace.servicemanager.config.DSpaceConfigurationService.loadInitialConfig(DSpaceConfigurationService.java:375) at org.dspace.servicemanager.config.DSpaceConfigurationService.<init>(DSpaceConfigurationService.java:60) at org.dspace.servicemanager.DSpaceKernelImpl.start(DSpaceKernelImpl.java:145) at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:51) Failed to startup the DSpace Service Manager: failure starting up spring service manager: Parser configuration exception parsing XML from class path resource [spring/spring-dspace-applicationContext.xml]; nested exception is javax.xml.parsers.ParserConfigurationException: Unable to validate using XSD: Your JAXP provider [org.apache.xerces.jaxp.DocumentBuilderFactoryImpl@6522d847] does not support XML Schema. Are you running on Java 1.4 with Apache Crimson? Upgrade to Apache Xerces (or Java 1.5) for full XSD support. Failure during filter init: Failed to startup the DSpace Service Manager: failure starting up spring service manager: Parser configuration exception parsing XML from class path resource [spring/spring-dspace-applicationContext.xml]; nested exception is javax.xml.parsers.ParserConfigurationException: Unable to validate using XSD: Your JAXP provider [org.apache.xerces.jaxp.DocumentBuilderFactoryImpl@6522d847] does not support XML Schema. Are you running on Java 1.4 with Apache Crimson? Upgrade to Apache Xerces (or Java 1.5) for full XSD support.:java.lang.RuntimeException: Failed to startup the DSpace Service Manager: failure starting up spring service manager: Parser configuration exception parsing XML from class path resource [spring/spring-dspace-applicationContext.xml]; nested exception is javax.xml.parsers.ParserConfigurationException: Unable to validate using XSD: Your JAXP provider [org.apache.xerces.jaxp.DocumentBuilderFactoryImpl@6522d847] does not support XML Schema. Are you running on Java 1.4 with Apache Crimson? Upgrade to Apache Xerces (or Java 1.5) for full XSD support. Exception in thread "main" java.lang.IllegalStateException: Failure during filter init: Failed to startup the DSpace Service Manager: failure starting up spring service manager: Parser configuration exception parsing XML from class path resource [spring/spring-dspace-applicationContext.xml]; nested exception is javax.xml.parsers.ParserConfigurationException: Unable to validate using XSD: Your JAXP provider [org.apache.xerces.jaxp.DocumentBuilderFactoryImpl@6522d847] does not support XML Schema. Are you running on Java 1.4 with Apache Crimson? Upgrade to Apache Xerces (or Java 1.5) for full XSD support. at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:66) Caused by: java.lang.RuntimeException: Failed to startup the DSpace Service Manager: failure starting up spring service manager: Parser configuration exception parsing XML from class path resource [spring/spring-dspace-applicationContext.xml]; nested exception is javax.xml.parsers.ParserConfigurationException: Unable to validate using XSD: Your JAXP provider [org.apache.xerces.jaxp.DocumentBuilderFactoryImpl@6522d847] does not support XML Schema. Are you running on Java 1.4 with Apache Crimson? Upgrade to Apache Xerces (or Java 1.5) for full XSD support. at org.dspace.servicemanager.DSpaceServiceManager.startup(DSpaceServiceManager.java:224) at org.dspace.servicemanager.DSpaceKernelImpl.start(DSpaceKernelImpl.java:150) at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:51) Caused by: java.lang.IllegalStateException: failure starting up spring service manager: Parser configuration exception parsing XML from class path resource [spring/spring-dspace-applicationContext.xml]; nested exception is javax.xml.parsers.ParserConfigurationException: Unable to validate using XSD: Your JAXP provider [org.apache.xerces.jaxp.DocumentBuilderFactoryImpl@6522d847] does not support XML Schema. Are you running on Java 1.4 with Apache Crimson? Upgrade to Apache Xerces (or Java 1.5) for full XSD support. at org.dspace.servicemanager.DSpaceServiceManager.startup(DSpaceServiceManager.java:208) ... 2 more Caused by: org.springframework.beans.factory.BeanDefinitionStoreException: Parser configuration exception parsing XML from class path resource [spring/spring-dspace-applicationContext.xml]; nested exception is javax.xml.parsers.ParserConfigurationException: Unable to validate using XSD: Your JAXP provider [org.apache.xerces.jaxp.DocumentBuilderFactoryImpl@6522d847] does not support XML Schema. Are you running on Java 1.4 with Apache Crimson? Upgrade to Apache Xerces (or Java 1.5) for full XSD support. at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:412) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:342) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:310) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:212) at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:113) at org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:80) at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:123) at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:422) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:352) at org.dspace.servicemanager.spring.SpringServiceManager.startup(SpringServiceManager.java:185) at org.dspace.servicemanager.DSpaceServiceManager.startup(DSpaceServiceManager.java:205) ... 2 more Caused by: javax.xml.parsers.ParserConfigurationException: Unable to validate using XSD: Your JAXP provider [org.apache.xerces.jaxp.DocumentBuilderFactoryImpl@6522d847] does not support XML Schema. Are you running on Java 1.4 with Apache Crimson? Upgrade to Apache Xerces (or Java 1.5) for full XSD support. at org.springframework.beans.factory.xml.DefaultDocumentLoader.createDocumentBuilderFactory(DefaultDocumentLoader.java:102) at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:70) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:396) ... 15 more Caused by: java.lang.IllegalArgumentException: No attributes are implemented at org.apache.xerces.jaxp.DocumentBuilderFactoryImpl.setAttribute(DocumentBuilderFactoryImpl.java:98) at org.springframework.beans.factory.xml.DefaultDocumentLoader.createDocumentBuilderFactory(DefaultDocumentLoader.java:99) ... 17 more Anyone knows why this functionality suddenly no longer works? Thanks -- ........................................................................ Rub?n Boada T?cnic de C?lcul i Aplicacions Consorci de Serveis Universitaris de Catalunya (CSUC) Gran Capit?, 2 (Edifici Nexus)?08034 Barcelona T.93 551 62 [email protected] www.csuc.cat ?Twitter @CSUC_info?Facebook?Linkedin Subscriu-te al butllet?; (www.csuc.cat/butlleti) ........................................................................ ------------------------------ Message: 12 Date: Thu, 2 Jul 2015 03:38:11 -0700 (PDT) From: euler <[email protected]> Subject: Re: [Dspace-tech] Dspace 3.2 to 5.2 To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=us-ascii Hi Lewatle, Just my hunch, in your previous DSpace instance before the upgrade, do you have controlled vocabulary enabled? Based on my experience, items with authority controlled metadata were not indexed if the current instance of DSpace does not have the authority control enabled . Looking at the logs, you would likely see this error (assuming you have your dc.subject authority controlled): ERROR org.dspace.discovery.SolrServiceImpl @ No choices plugin was configured for field "dc_subject". If this is not the case, then I'm wrong. Regards, euler -- View this message in context: http://dspace.2283337.n4.nabble.com/Dspace-3-2-to-5-2-tp4678653p4678667.html Sent from the DSpace - Tech mailing list archive at Nabble.com. ------------------------------ Message: 13 Date: Thu, 2 Jul 2015 11:19:13 +0000 From: Lewatle Phaladi <[email protected]> Subject: Re: [Dspace-tech] Dspace 3.2 to 5.2 To: euler <[email protected]>, "[email protected]" <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset="us-ascii" Hi Euler, At the moment I am trying any suggested solution to solve this problem, what command do I have to run to make sure that all relevant data is indexed properly? Regards, Lewatle -----Original Message----- From: euler [mailto:[email protected]] Sent: 02 July 2015 12:38 PM To: [email protected] Subject: Re: [Dspace-tech] Dspace 3.2 to 5.2 Hi Lewatle, Just my hunch, in your previous DSpace instance before the upgrade, do you have controlled vocabulary enabled? Based on my experience, items with authority controlled metadata were not indexed if the current instance of DSpace does not have the authority control enabled . Looking at the logs, you would likely see this error (assuming you have your dc.subject authority controlled): ERROR org.dspace.discovery.SolrServiceImpl @ No choices plugin was configured for field "dc_subject". If this is not the case, then I'm wrong. Regards, euler -- View this message in context: http://dspace.2283337.n4.nabble.com/Dspace-3-2-to-5-2-tp4678653p4678667.html Sent from the DSpace - Tech mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette <table width="100%" border="0" cellspacing="0" cellpadding="0" style="width:100%;"> <tr> <td align="left" style="text-align:justify;"><font face="arial,sans-serif" size="1" color="#999999"><span style="font-size:11px;">This communication is intended for the addressee only. It is confidential. If you have received this communication in error, please notify us immediately and destroy the original message. You may not copy or disseminate this communication without the permission of the University. Only authorised signatories are competent to enter into agreements on behalf of the University and recipients are thus advised that the content of this message may not be legally binding on the University and may contain the personal views and opinions of the author, which are not necessarily the views and opinions of The University of the Witwatersrand, Johannesburg. All agreements between the University and outsiders are subject to South African Law unless the University agrees in writing to the contrary. </span></font></td> </tr> </table ------------------------------ Message: 14 Date: Thu, 2 Jul 2015 04:23:19 -0700 (PDT) From: euler <[email protected]> Subject: Re: [Dspace-tech] Dspace 3.2 to 5.2 To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset=us-ascii Hi Lewatle, Did you checked your dspace log for errors? If you have this error: "ERROR org.dspace.discovery.SolrServiceImpl @ No choices plugin was configured for field", my suggestion is that you have to enable the authority control settings in your dspace.cfg. I am assuming that this is likely the reason why items with metadata that have authorities were not indexed even if you do an index discovery -b. I have experienced this also so maybe this might help you. Regards, euler -- View this message in context: http://dspace.2283337.n4.nabble.com/Dspace-3-2-to-5-2-tp4678653p4678669.html Sent from the DSpace - Tech mailing list archive at Nabble.com. ------------------------------ Message: 15 Date: Thu, 2 Jul 2015 13:27:27 +0000 From: Graham Faulkner <[email protected]> Subject: Re: [Dspace-tech] dc.date.accessioned incorrect setting To: Arthur Sady Cordeiro Rossetti <[email protected]>, "[email protected]" <[email protected]> Message-ID: <90A0D9B5099A414EADC0F0514A2D2C33A3A7D40A@connmbx02> Content-Type: text/plain; charset="utf-8" Hi Arthur, We have been looking at this issue too, so perhaps I can shed some light. Here is an old discussion about how to change the displayed dates in JSPUI: http://sourceforge.net/p/dspace/mailman/message/29889171/. However, we are using XMLUI (Mirage2) in DSpace 5.1, so I experimented with a custom /home/dspace/dspace-source/dspace/modules/xmlui-mirage2/src/main/webapp/themes/Mirage2/xsl/aspect/artifactbrowser/item-view.xsl. Then I added the following namespace info to the <xsl:stylesheet> tag: xmlns:date="http://exslt.org/dates-and-times"; extension-element-prefixes="date" Note: because the XSLT is version 1.0 I could not benefit from XPath 2.0 functions such as adjust-dateTime-to-timezone(). Then I updated the <xsl:template match="dim:field" mode="itemDetailView-DIM"> template where it was displaying the date. I wanted to modify the displayed date for dc.date.accessioned and dc.date.available, so I performed the following test and used date:date-time() to calculate the correct local timezone and displayed it along with a formatted version of the UTC date-time stored in the node(). <td class=?word-break?> <xsl:choose> <xsl:when test="not(@element='date' and @qualifier='accessioned') and not(@element='date' and @qualifier='available')"> <xsl:value-of select="./node()"/> </xsl:when> <xsl:otherwise> <xsl:variable name="dt" select="./node()" /> <!-- cannot use fn:adjust-dateTime-to-timezone because requires XSLT 2.0 --> <!--<xsl:value-of select="fn:adjust-dateTime-to-timezone($dt, '-PT4H')" />--> <xsl:variable name="currDateTime" select="date:date-time()" /> <xsl:variable name="currTimeZone" select="substring($currDateTime,20,25)" /> <xsl:value-of select="date:format-date($dt, 'YYYY-MM-dd HH:mm:ss')" /> <xsl:value-of select="$currTimeZone" /> </xsl:otherwise> </xsl:choose> </td> What I still need to do is perform an actual transformation to the current timezone for the UTC date-time stored in the node(), but at least I am further along in where and how to make the changes. Hope that helps. Graham From: Arthur Sady Cordeiro Rossetti [mailto:[email protected]] Sent: Wednesday, July 01, 2015 9:25 AM To: [email protected] Subject: [Dspace-tech] dc.date.accessioned incorrect setting Hi, Im trying to find the file where Dspace automatically sets the dc.date.accessed variable date which represents the date of submission of the items in de database, because in my instance, even though the machine where its running has the right time configuration and in the right timezone, the value in dc.date.accessed is always set based in the UTC timezone, I changed the computer clock, to compensate and it solved the problem, but this solution is not enough for me because there are other aplications dependant on the computer clock. So does anybody knows where I can find the file where that variable is set, so I can change it? Thanks for the attention -- Arthur Sady C. Rossetti -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ Message: 16 Date: Thu, 2 Jul 2015 08:33:18 -0500 From: Tim Donohue <[email protected]> Subject: Re: [Dspace-tech] Dspace 3.2 to 5.2 To: [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset="windows-1252" Hi Lewatle, DSpace 3.2 is definitely upgradeable to DSpace 5.2. Have you checked for any error messages in your logs? What do you mean by the "Bitstreams/PDF/Images etc are not visible under any collection"? Do you mean that the file links no longer work? Or are all your Items missing? If it's the latter, it may just be that the automatic re-index process hadn't completed. If you stopped Tomcat during the re-index, you can always re-run it manually by starting Tomcat & running "[dspace]/bin/dspace index-discovery -b" - Tim On 7/1/2015 4:08 AM, Lewatle Phaladi wrote: > > Dear Team, > > I have upgraded dspace 3.2 straight to 5.2, I haven?t upgraded to > version 4 , I have just did upgrade to version 5.2, all steps went > well database upgrade also went well, and after the upgrade all > information shows well on XMLUI user interface, and the only part that > is not showing is Bitstrams/PFD/Images etc are not visible under any > collection, I have checked the path in dspace.cfg all indicated well, > I have also asked my colleagues who are developing softwares to team > up with me so that we all check where do we miss the step but we > executed all commands and responded successfully but the PDF?s are not > showing, that is where they have started asking if maybe dspace 3.2 is > not that upgradable to 5.2 although document seems to say it is > upgradable. > > Regards, > > Lewatle > > This communication is intended for the addressee only. It is > confidential. If you have received this communication in error, please > notify us immediately and destroy the original message. You may not > copy or disseminate this communication without the permission of the > University. Only authorised signatories are competent to enter into > agreements on behalf of the University and recipients are thus advised > that the content of this message may not be legally binding on the > University and may contain the personal views and opinions of the > author, which are not necessarily the views and opinions of The > University of the Witwatersrand, Johannesburg. All agreements between > the University and outsiders are subject to South African Law unless > the University agrees in writing to the contrary. > > > > > > ------------------------------------------------------------------------------ > Don't Limit Your Business. Reach for the Cloud. > GigeNET's Cloud Solutions provide you with the tools and support that > you need to offload your IT needs and focus on growing your business. > Configured For All Businesses. Start Your Cloud Today. > https://www.gigenetcloud.com/ > > > _______________________________________________ > DSpace-tech mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dspace-tech > List Etiquette: > https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette > > -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ Message: 17 Date: Thu, 2 Jul 2015 08:40:12 -0500 From: Tim Donohue <[email protected]> Subject: Re: [Dspace-tech] Disable Handle? To: Shannon Meisenheimer <[email protected]>, [email protected] Message-ID: <[email protected]> Content-Type: text/plain; charset="windows-1252" Hi Shannon, While DSpace shows URLs that include the word "handle" by default, the actual handle server is actually not configured by default. It sounds like you may just be wanting the URI that is displayed on Item pages to no longer start with "http://hdl.handle.net/";. If that's the case you can easily tweak that in your "build.properties". It's the "handle.canonical.prefix" setting in that file: https://github.com/DSpace/DSpace/blob/master/build.properties#L148 If you want it to simply be the URL of your Dspace, you can change this setting to be: handle.canonical.prefix = ${dspace.url}/handle/ After changing that setting, you will need to rebuild & redeploy DSpace (which will cause the setting to be propagated to your "live" dspace.cfg file): cd [dspace-src] (i.e. source directory) mvn clean package cd dspace/target/dspace-installer ant update Finally, restart Tomcat. - Tim On 7/1/2015 8:16 AM, Shannon Meisenheimer wrote: > Is it possible to disable handle all together? Our Library is just > wanting to have the DSpace internal URL displaying without the handle > in the Article link and change the URI displayed to the internal > DSpace link. > > Thanks, > Shannon > -- > Mr. Shannon Meisenheimer > Office of Technology > Blackboard and Academic Application Management > University of Central Missouri > Dockery 207A > [email protected] <mailto:[email protected]> > Work Phone: (660) 543-8483 > > > > ------------------------------------------------------------------------------ > Don't Limit Your Business. Reach for the Cloud. > GigeNET's Cloud Solutions provide you with the tools and support that > you need to offload your IT needs and focus on growing your business. > Configured For All Businesses. Start Your Cloud Today. > https://www.gigenetcloud.com/ > > > _______________________________________________ > DSpace-tech mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dspace-tech > List Etiquette: > https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ Message: 18 Date: Thu, 2 Jul 2015 13:44:36 +0000 From: George Stanley Kozak <[email protected]> Subject: Re: [Dspace-tech] Changing embargo dates in DSpace 5.2 To: "Becker, Pascal-Nicolas" <[email protected]>, "[email protected]" <[email protected]> Message-ID: <by2pr0401mb16882778a36f2b75daaabd639f...@by2pr0401mb1688.namprd04.prod.outlook.com> Content-Type: text/plain; charset="us-ascii" Thank you, Pascal. We are using DSpace 5.2 XMLUI Mirage 2 (I should have mentioned that earlier). It would be nice to change the dates in the Admin interface, but this is helpful. I guess my process now will be: 1) Login in as Admin 2) Open and item and edit 3) Click on Authorizations 4) Find the bitstream in the list and note the bitstream ID 5) If I plan to change the Embargo date, then from the command line I will go to psql and do a. update resorcepolicy set end_date=<whatever you want> where resource_id=<bitstream id noted above>; Again, thanks for your help (and to Hilton Gibson, too!) George Kozak Digital Library Specialist Cornell University Library Information Technologies (CUL-IT) 218 Olin Library Cornell University Ithaca, NY 14853 607-255-8924 From: Becker, Pascal-Nicolas [mailto:[email protected]] Sent: Thursday, July 02, 2015 4:44 AM To: [email protected] Cc: George Stanley Kozak Subject: RE: Changing embargo dates in DSpace 5.2 Hi, if you use the JSPUI this should be fixed in DSpace 5.2. See the ticket in Jira describing the problem and its solution: https://jira.duraspace.org/browse/DS-1965. Starting with DSpace 5.2 you should see the date fields in the administrator interface you use to edit authorizations (login as admin, open an item, click on edit, click on edit, click on authorizations, look for the policy you want to change and click on edit). While writing this mail I see that the dates are not part of the table listing all authorizations of an item. We should change this too. I create the ticket DS-2638 and marked it as needs volunteer. Kind regards, Pascal From: George Stanley Kozak [mailto:[email protected]] Sent: Wednesday, July 01, 2015 8:09 PM To: [email protected]<mailto:[email protected]> Subject: [Dspace-tech] Changing embargo dates in DSpace 5.2 Hi... How do people handle changing the Embargo dates in DSpace 5.2? As far as I can tell, once an item has been submitted as embargoed, it can only be changed by manually modifying the resourcepolicy table. Am I wrong of is there a programmatic way to change the dates? George Kozak Digital Library Specialist Cornell University Library Information Technologies (CUL-IT) 218 Olin Library Cornell University Ithaca, NY 14853 607-255-8924 -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ ------------------------------ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech End of DSpace-tech Digest, Vol 111, Issue 2 ******************************************* ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
