Re: [Dspace-tech] Search problems with special characters and diacritics
Hi Bruna Typical problems with diacritic searches comes from the ausence of an specific filterm ISOLatin1AccentFilter in the DSPace configuration of the Lucene engine. You must try to change DSAnalyzer.java adding two lines: import org.apache.lucene.analysis.ISOLatin1AccentFilter; result = new ISOLatin1AccentFilter(result); You will also need to recompile DSPACE AND rebuilt the indexes best luck Emilio El 05/04/2012 1:30, Bruna Fagundes Rócio escribió: Hi folks, We are using DSpace as the base for our objetc repository at UDESC (Joinville, Brazil). But, now, we notticed a problem with search with diacritics and special characters (acents, etc). For example: in portuguese the correct spelling for the word critic is crítico. In the DSpace Documentation we have the information that the search ignores this signs, however, if we search for critico without acent, we don't have the same results when we use crítico. It doesn't work for searching Author, Title, Subjects... and doesn't work for XMLUI neither JSPUI. Thanks for the help! *Bruna Fagundes Rócio* -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Problems with official git repo?
All, I'm happy that DSpace is now hosted officially on github, it's a great place for code to live! I'm having a problem with my normal git routine, though... I set out to test upgrading our DSpace 1.7.x to 1.8.x and I noticed that there are some continuity issues in the history between branches[2]; on clean clone of the official DSpace repo[1], I cannot merge 1.8.x changes into 1.7.x without getting hundreds of merge conflicts: git clone https://github.com/DSpace/DSpace cd DSpace git checkout -b 1.8.2-test origin/dspace-1_7_x git merge origin/dspace-1_8_x Maybe Peter or someone else more involved in the SVN - git transition can comment about? If this is a known issue with no fix, maybe I should just rebase our local changes on top of 1.8.x? Thanks! [1] http://github.com/DSpace/DSpace [2] graphical view of branches: http://img6.imagebanana.com/img/0bcnxp6y/gitkDSpace_010.png -- Alan Orth alan.o...@gmail.com http://alaninkenya.org http://mjanja.co.ke I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone. -Bjarne Stroustrup, inventor of C++ -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Problems with official git repo?
After looking deeper into your situation, your problem is not that 1.7.x and 1.7.2 are diverged, but that 1.7.x and 1.8.x and trunk/master are all diverged. This is fine, thats the shape of the tree. if you scroll back long enough you'll see common branch/split points between each version. I didn't see anything that makes me think the git repo is having issues. So Alan, I did clone your repo because I think thats the only way to fully understand this. And three cheers for providing the perfect example to help us get through these transition pains. User Story: Alan has customized his DSpace repository they were on the 1.7.x branch, but would now like to upgrade to 1.8.x. He's noticed that he wants to get his changes on 1.7 into the 1.8 work, so that they can use 1.8 and continue development off of 1.8. The Problem: Alan's first attempt was to merge 1.7.x into 1.8.x git checkout -b 1.8.2-test origin/dspace-1_7_x git merge origin/dspace-1_8_x That will create a new commit that will have two parents - The commit sitting at 1.7.x - The commit sitting at 1.8.x It will also result in a massive conflict as Alan only wants his changes (mostly to XMLUI theme stuff), but he's carrying all of the modifications between 1.8 and 1.7 into the situation. Git is just trying to do as its told and create a new version of every file in 1.8 and 1.7 that accommodate all the changes in 1.8 and 1.7. The Really Easy Solution: git cherry-pick SHA1-parent-of-first-commit..SHA1-latest-Commit-Of-Yours You can grab just the commits that your local repository customization team has created on 1.7.x, (cherry pick them), and apply those changes on-top of the 1.8.x branch. The result is that you now have a 1.8.x branch with several dozen new commits that are all your local customizations. A bit more detail into how I solved this. You have to find the range of commits you'd like to cherry-pick. In Alan's case, he's got a branch called development with 30 or so commits, that started from dspace-1_7_x. Find the sha1ID of his latest commit: (xmlui: Clean up the CCAFS banner) : 3d15c2ea [image: Inline image 2] Then, find the parent commit, of his first commit. His first commit is: (Add ignores for webapp build folders) 570fdb, but we don't want that commit ID. We need the parent. The parent to his first commit is e320ebd8 ([maven-release-plugin] prepare release dspace-1.7.2) [image: Inline image 3] So now that we know his last commit is 3d15c2ea and the parent of his first commit is: e320ebd8 we have our range. So we checkout to where we want these cherry-picks to end up. git checkout dspace-1_8_x And perform the cherry-pick operation. git cherry-pick e320ebd..3d15c2e After starting the cherry pick, git will do a whole lot of magic applying all of your modifications to the end your current branch (dspace.1_8_x in this case). Best of all, in Alan's example, there were no commit conflicts, because their changes were just creating new XMLUI themes. If he happened to have modified some core files that are likely to have also been modified between 1.8 and 1.7, then you might run into some easy enough to resolve conflicts. Peter Dietz On Thu, Apr 5, 2012 at 2:45 AM, Alan Orth alan.o...@gmail.com wrote: All, I'm happy that DSpace is now hosted officially on github, it's a great place for code to live! I'm having a problem with my normal git routine, though... I set out to test upgrading our DSpace 1.7.x to 1.8.x and I noticed that there are some continuity issues in the history between branches[2]; on clean clone of the official DSpace repo[1], I cannot merge 1.8.x changes into 1.7.x without getting hundreds of merge conflicts: git clone https://github.com/DSpace/DSpace cd DSpace git checkout -b 1.8.2-test origin/dspace-1_7_x git merge origin/dspace-1_8_x Maybe Peter or someone else more involved in the SVN - git transition can comment about? If this is a known issue with no fix, maybe I should just rebase our local changes on top of 1.8.x? Thanks! [1] http://github.com/DSpace/DSpace [2] graphical view of branches: http://img6.imagebanana.com/img/0bcnxp6y/gitkDSpace_010.png -- Alan Orth alan.o...@gmail.com http://alaninkenya.org http://mjanja.co.ke I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone. -Bjarne Stroustrup, inventor of C++ -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Better than sec? Nothing is better
Re: [Dspace-tech] Localization inside config files?
Hi all, This i18n discussion has been bouncing around in my head for a while, so I felt it's time to chime in. First off, it is very important to keep this discussion rolling. Most, if not all, of the developers/committers will readily admit that DSpace i18n processes are currently a bit broken. The main issue here is not that we don't want to fix them. Rather, it's that we are a bit stuck in how to improve the processes for the translators while keeping development moving forward. So, these discussions are extremely helpful! To this end, I've attempted to summarize what I've read in this thread into a new Proposal page on our wiki: https://wiki.duraspace.org/display/DSPACE/i18n+Improvements+Proposal It's highly possible that I've misrepresented a major point (or missed something along the way). So, I'd recommend others read through this, enhance it, and add your own comments or suggestions. You can add brainstorms directly to the Wiki page (with your name after it), or express them on this list (and we can eventually 'capture it' on the wiki page later as needed) The goal of this wiki page is *not* to take discussion away from this listserv. Rather, it's to provide a summary of this discussion, so that we can begin brainstorming from that summary and look towards developing (or trying out) possible solutions to each of these frustrations. I've added some brainstorms of my own to the wiki page itself on many of these key points/frustrations that have been expressed by Christian helix84. I definitely don't claim to have the answers here though. These are merely brainstorms. All in all, I feel strongly that we need to find ways to ease the job of translators, simplify the installation of i18n files, and avoid complicating development processes. This may be a delicate balancing act, but it is an important one. - Tim -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] DSpace-tech Digest, Vol 72, Issue 9
Hi Emilio, It works perfectly! Thank u! You helped us a lot! From: emilio lorenzo elore...@arvo.es Subject: Re: [Dspace-tech] Search problems with special characters and diacritics To: dspace-tech@lists.sourceforge.net Message-ID: 4f7d3f01.2020...@arvo.es Content-Type: text/plain; charset=iso-8859-1 Hi Bruna Typical problems with diacritic searches comes from the ausence of an specific filterm ISOLatin1AccentFilter in the DSPace configuration of the Lucene engine. You must try to change DSAnalyzer.java adding two lines: import org.apache.lucene.analysis.ISOLatin1AccentFilter; result = new ISOLatin1AccentFilter(result); You will also need to recompile DSPACE AND rebuilt the indexes best luck Emilio El 05/04/2012 1:30, Bruna Fagundes R?cio escribi?: Hi folks, We are using DSpace as the base for our objetc repository at UDESC (Joinville, Brazil). But, now, we notticed a problem with search with diacritics and special characters (acents, etc). For example: in portuguese the correct spelling for the word critic is cr?tico. In the DSpace Documentation we have the information that the search ignores this signs, however, if we search for critico without acent, we don't have the same results when we use cr?tico. It doesn't work for searching Author, Title, Subjects... and doesn't work for XMLUI neither JSPUI. Thanks for the help! *Bruna Fagundes R?cio* -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- next part -- An HTML attachment was scrubbed... -- -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev -- ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech End of DSpace-tech Digest, Vol 72, Issue 9 **-- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] About Google Scholar
Hi everybody. We're currently have about 10.000 items within our repository, but google scholar only index about 1/3 of them though all items are identical in dublin core format. I don't know how to tell google scholar to index and recognize all items of the repository. Does anyone face similar problem ? -- TRUONG HOANG DUNG* **Librarian Researcher **Information and Library Centre Mobile: 0121.411.5322 Email: dun...@hpu.edu.vn* *Hai Phong Private University* http://lib.hpu.vn -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
