Re: [Dspace-tech] Best practice for adding javascript to avoid jQuery conflicts with other libraries?
On Thu, Jul 25, 2013 at 4:24 AM, Nemiz, Elvi esne...@seafdec.org.ph wrote: I would like to ask for any advice on how to add javascript and avoiding issues of jQuery conflicts. I've seen in some repositories using the jQuery.conflict() mode. I also noticed that some of these conflicts that I've encountered were fixed by rearranging the sequence of imported javascript in sitemap.xmap. What is the best way to add javascript and avoiding jQuery conflicts with other libraries in DSpace? Hi Elvi, this is actually explained very well on the jQuery website: http://learn.jquery.com/using-jquery-core/avoid-conflicts-other-libraries/ Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] DSpace LDAP authentication problem
On Thu, Jul 25, 2013 at 12:42 AM, Keir Vaughan-Taylor k...@usyd.edu.au wrote: LifeH2O is correct in that it is the email address being populated with NULL characters added to the username. Is this the email column or the netid column of the eperson table, or both? Please, also send your whole LDAP configuration. I'm especially interested in your value of id_field. I can see this using the unix command ldapsearch Just to make sure, when you do ldapsearch, are you binding as the same user as dspace? E.g. anonymous search or a particular admin user in both cases? Attributes can have different visibility for different LDAP users. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] Help with enabling mobile site
Hello, Has anyone enabled mobile theme in DSpace 3.1? I followed these instructions: https://github.com/DSpace/DSpace/blob/dspace-3_x/dspace-xmlui/src/main/webapp/themes/mobile/readme.txt, but I can' t get it to work! The mobile site does not appear neither from mobiles, nor from my pc using the mobile address. It can be accessed only through this address: http:///ourdspacesite//?themepath=mobile/ as a theme preview. Please let me explain what I have done so far: - Added two DNS entries. An A record entry for our DSpace (Mirage) site and a CNAME record for the mobile./ourdspacesite/. Both addresses work and point to Mirage. - Added two lines in /my-theme/.xsl to call detectmobile.js and cookies.js scripts. Did not add the View mobile site link in the footer. - Added the mobile./ourdspacesite /address in detectmobile.js - Edited dspace.mobileUrl property in dspace.cfg Do I need to do something else? What am I missing? Thank you in advance. Best regards, Kiriaki -- Kiriaki Roditi Technical Support Engineer EL/i/DOC Systems Services e-mail: krod...@elidoc.gr Phone: +30 210 2588510 -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] Rebuild ....
Hi, how can I rebuild Dspace 3.1 after making some changes like changing the logo? (Windows, tomcat, maven, jpsui) Regards, Jimena -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] FW: Repository Fringe 2013 - Programme Announced / How to Take Part
With apologies for cross-postingŠ On 25/07/2013 14:33, OSBORNE Nicola nicola.osbo...@ed.ac.uk wrote: There is just one week to go until Repository Fringe 2013, which takes place in Edinburgh from 31st July 2013 to 2nd August 2013. You can find out more about the Fringe on the website: http://rfringe13.blogs.edina.ac.uk/ Registration is still open if you would like to secure your place: http://rfringe13.eventbrite.com Programme We are delighted to announce that we have published our programme filled with super presentations, round tables and Pecha Kucha. If you would still like to make a contribution to the programme there is just enough time for submitting a last minute Pecha Kucha, otherwise we are happy to receive updates, ideas, etc. as guest blog posts, videos or other digital materials to be shared on the Repository Fringe website. Joining online If you cannot make the event in person but would like to follow on remotely then please keep an eye on our hashtag #rfringe13 and on the blog. There will be some live blogging and we have volunteer bloggers (and welcome more if you'd like to take part) who will share their reflections throughout the event. We will also be videoing all of the talks (any taking place in Room 1) and these will be shared online as quickly as we can after the event. Developer Challenge If you have registered for the event and are taking part in the Developer Challenge do take the time to take a look at our prizes, our theme for this year, and our rules. If you have indicated that you may be taking part in the Challenge you will also receive an email shortly with a few more details from Muriel Mewissen who is coordinating the Developer Challenge this year. The Developer Challenge is very deliberately at the heart of the Fringe this year. We want there to be lots of opportunities to chat and exchange ideas across the whole event. With that in mine if you would like to be part of the Developer Challenge but cannot make it along in person you can still submit your idea/hack online. Take a look at the Developer Challenge page for more on how to do this. Our dedicated Challenge hashtag is: #rfringe13dev. Thank You We are very much looking forward to seeing some of you in Edinburgh next week. We think this will be another fantastic Repository Fringe! - Nicola Osborne (Chair Repository Fringe 2013) and the Repository Fringe Organising Team Key links for Repository Fringe 2013 - Website: http://repositoryfringe.org/ - Programme: http://rfringe13.blogs.edina.ac.uk/programme/ - Essentials for Presenters: http://rfringe13.blogs.edina.ac.uk/2013/07/19/our-essential-guide-for-repo fringe-presenters/ - Networking Session - what to bring: http://rfringe13.blogs.edina.ac.uk/2013/07/09/coming-to-repository-fringe/ - Developer Challenge: http://rfringe13.blogs.edina.ac.uk/developer-challenge/ - Developer Challenge Rules: http://rfringe13.blogs.edina.ac.uk/developer-challenge/developer-challenge -rules/ - All of our social media links in one place - including our hashtags: http://rfringe13.blogs.edina.ac.uk/contact/ - Beginners Guide to Social Media: http://rfringe13.blogs.edina.ac.uk/2013/07/23/beginners-guide-to-repositor y-fringe-2013-social-media-amplification/ - Connect with us - Flickr: http://www.flickr.com/groups/repofringe13/ - Connect with us - Crowdvine: http://rfringe13.crowdvine.com/ - Connect with us - Lanyrd: http://lanyrd.com/2013/rfringe13/ - Follow us on Twitter: https://twitter.com/#!/repofringe -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] text encoding problem with bitstreams in DSpace 3.1 - resolved
On Thu, Jul 25, 2013 at 03:07:36AM +, Halliday, James Leonard wrote: Hi everyone, I posted about this a while back, and finally found a workaround so I wanted to share. My problem was regarding HTML bitstreams in DSpace 3.1 (XMLUI). In previous versions of DSpace, the encoding for my UTF-8 bitstreams worked just fine, but in DSpace 3.1, the encoding for ONLY the bitstreams was coming out as ISO-8859 instead. After much searching, I finally found a workaround which involved changing a value in the web.xml file, as follows: In the original web.xml are the following lines: filter filter-nameSetCharacterEncoding/filter-name filter-classorg.dspace.app.xmlui.cocoon.SetCharacterEncodingFilter/filter-class init-param param-nameencoding/param-name param-valueUTF-8/param-value /init-param /filter I substituted: filter filter-nameSetCharacterEncoding/filter-name filter-classorg.springframework.web.filter.CharacterEncodingFilter/filter-class init-param param-nameencoding/param-name param-valueUTF-8/param-value /init-param init-param param-nameforceEncoding/param-name param-valuetrue/param-value /init-param /filter So basically I took out the DSpace-specific encoding filter, and substituted the Spring one (which is already included by default). So I had to change only these lines, and my encoding problem was resolved. This tells me there might be a problem in the DSpace encoding filter ... ? Thank you. Interesting. If this works well, then at the least we could just use Spring's filter and stop maintaining our own. I'm thinking that our filter as written could never have done what you expect, and the effect was produced elsewhere. Our filter only sets the request's encoding. Spring's filter is documented to also set the response's encoding when forceEncoding=true. Perhaps BitstreamReader should just set the encoding on the response? -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Machines should not be friendly. Machines should be obedient. signature.asc Description: Digital signature -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] Announcing DSpace 3.2 Release : provides bug and security fixes to 3.x platform
DSpace Community, Today we are proud to announce DSpace 3.2, a new bug-fix / security-fix release for the 3.x platform. DSpace 3.2 addresses a number of issues that were found to affect 3.0 or 3.1. These fixes include: * Several bug fixes to the OAI-PMH interface * Resolved memory leak in JSPUI * Resolved security issue in JSPUI * Several minor configuration / build fixes * Other minor fixes A detailed list of resolved issues can be found at: https://wiki.duraspace.org/display/DSPACE/DSpace+Release+3.2+Notes We recommend that all 3.x JSPUI users upgrade to 3.2 in order to resolve a memory leak and fix a potential security vulnerability. Any 3.x OAI-PMH users are also encouraged to upgrade, as several recently reported OAI-PMH issues have now been resolved. 3.2 Installation and Upgrade instructions: * Installation: https://wiki.duraspace.org/display/DSDOC3x/Installation * Upgrade from 3.x to 3.2: https://wiki.duraspace.org/display/DSDOC3x/Upgrading+From+3.0+to+3.x * Upgrade (general instructions): https://wiki.duraspace.org/display/DSDOC3x/Upgrading+a+DSpace+Installation DSpace would not exist without the hard work and support of the community! We'd like to thank each of you for continuing to use DSpace, support DSpace, test DSpace, and provide feedback to the developers. Sincerely, Tim Donohue, on behalf of the DSpace Committers -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] Announcing DSpace 1.8.3 Release: provides a JSPUI security patch to 1.8.x platform
DSpace Community, Today we'd like to also announce DSpace 1.8.3, a security release for the 1.8.x platform. DSpace 1.8.3 addresses a security vulnerability in the JSPUI. Although there are no known exploits of this vulnerability, we recommend all 1.8.x JSPUI users upgrade to 1.8.3 or 3.2. This JSPUI security fix has been backported to 1.8.3 (from 3.2) as per our current DSpace Software Support Policy [1]. This 1.8.3 release also contains minor improvements that make 1.8.x more Git/GitHub friendly, allowing users to more easily work with 1.8 in Git/GitHub. More details on the 1.8.3 release (including download links) can be found at: https://wiki.duraspace.org/display/DSPACE/DSpace+Release+1.8.3+Notes Recommendations: * We highly recommend that all 1.8.x JSPUI users either upgrade to 1.8.3 or 3.2 to fix the JSPUI security vulnerability. * If you are unable to upgrade at this time, a manual patch has been provided at https://jira.duraspace.org/browse/DS-1603 (you must register to access this ticket) 1.8.3 Installation and Upgrade instructions: * Installation: https://wiki.duraspace.org/display/DSDOC18/Installation * Upgrade from 1.8.x to 1.8.3: https://wiki.duraspace.org/display/DSDOC18/Upgrading+From+1.8+to+1.8.x * Upgrade from 1.8.x to 3.2: https://wiki.duraspace.org/display/DSDOC3x/Upgrading+From+1.8.x+to+3.x * Upgrade (general instructions): https://wiki.duraspace.org/display/DSDOC18/Upgrading+a+DSpace+Installation DSpace would not exist without the hard work and support of the community! We'd like to thank each of you for continuing to use DSpace, support DSpace, test DSpace, and provide feedback to the developers. Sincerely, Tim Donohue, on behalf of the DSpace Committers [1] DSpace Software Support Policy: https://wiki.duraspace.org/display/DSPACE/DSpace+Software+Support+Policy -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] Announcing DSpace 1.7.3 Release: provides a JSPUI security patch to 1.7.x platform
DSpace Community, Today we'd like to also announce DSpace 1.7.3, a security release for the 1.7.x platform. DSpace 1.7.3 addresses a security vulnerability in the JSPUI. Although there are no known exploits of this vulnerability, we recommend all 1.7.x JSPUI users upgrade to 1.7.3 (or 1.8.3 or 3.2). This JSPUI security fix has been backported to 1.7.3 (from 3.2) as per our current DSpace Software Support Policy [1]. This 1.7.3 release also contains minor improvements that make 1.7.x more Git/GitHub friendly, allowing users to more easily work with 1.7 in Git/GitHub. More details on the 1.7.3 release (including download links) can be found at: https://wiki.duraspace.org/display/DSPACE/DSpace+Release+1.7.3+Notes Recommendations: * We highly recommend that all 1.7.x JSPUI users either upgrade to 1.7.3 or 1.8.3 or 3.2 to fix the JSPUI security vulnerability. * Users of previous versions of DSpace (1.6.x or below), who depend on the JSPUI, are also encouraged to upgrade to 1.7.3 or 1.8.3 or 3.2 to fix this vulnerability. * If you are unable to upgrade at this time, a manual patch has been provided at https://jira.duraspace.org/browse/DS-1603 (you must register to access this ticket) 1.7.3 Installation and Upgrade instructions: * Installation: https://wiki.duraspace.org/display/DSDOC17/Installation * Upgrade from 1.7.x to 1.7.3: https://wiki.duraspace.org/display/DSDOC18/Upgrading+From+1.7+to+1.7.x * Upgrade from 1.7.x to 1.8.3: https://wiki.duraspace.org/display/DSDOC18/Upgrading+From+1.7.x+to+1.8.x * Upgrade (general instructions): https://wiki.duraspace.org/display/DSDOC18/Upgrading+a+DSpace+Installation DSpace would not exist without the hard work and support of the community! We'd like to thank each of you for continuing to use DSpace, support DSpace, test DSpace, and provide feedback to the developers. Sincerely, Tim Donohue, on behalf of the DSpace Committers [1] DSpace Software Support Policy: https://wiki.duraspace.org/display/DSPACE/DSpace+Software+Support+Policy -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] text encoding problem with bitstreams in DSpace 3.1 - resolved
Hello, Can you tell me wich file I need to change? Javier Távara 2013/7/25 Mark H. Wood mw...@iupui.edu On Thu, Jul 25, 2013 at 03:07:36AM +, Halliday, James Leonard wrote: Hi everyone, I posted about this a while back, and finally found a workaround so I wanted to share. My problem was regarding HTML bitstreams in DSpace 3.1 (XMLUI). In previous versions of DSpace, the encoding for my UTF-8 bitstreams worked just fine, but in DSpace 3.1, the encoding for ONLY the bitstreams was coming out as ISO-8859 instead. After much searching, I finally found a workaround which involved changing a value in the web.xml file, as follows: In the original web.xml are the following lines: filter filter-nameSetCharacterEncoding/filter-name filter-classorg.dspace.app.xmlui.cocoon.SetCharacterEncodingFilter/filter-class init-param param-nameencoding/param-name param-valueUTF-8/param-value /init-param /filter I substituted: filter filter-nameSetCharacterEncoding/filter-name filter-classorg.springframework.web.filter.CharacterEncodingFilter/filter-class init-param param-nameencoding/param-name param-valueUTF-8/param-value /init-param init-param param-nameforceEncoding/param-name param-valuetrue/param-value /init-param /filter So basically I took out the DSpace-specific encoding filter, and substituted the Spring one (which is already included by default). So I had to change only these lines, and my encoding problem was resolved. This tells me there might be a problem in the DSpace encoding filter ... ? Thank you. Interesting. If this works well, then at the least we could just use Spring's filter and stop maintaining our own. I'm thinking that our filter as written could never have done what you expect, and the effect was produced elsewhere. Our filter only sets the request's encoding. Spring's filter is documented to also set the response's encoding when forceEncoding=true. Perhaps BitstreamReader should just set the encoding on the response? -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Machines should not be friendly. Machines should be obedient. -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
