- Localized the project page for Kannada Wiki for better collaboration with Community. ಸದಸ್ಯ:Omshivaprakash/ಯೋಜನೆಗಳು/ಕನ್ನಡ_ವಿಕಿಮೀಡಿಯ_ಯೋಜನೆಗಳನ್ನು_ಡಿಜಿಟಲ್_ಲೈಬ್ರರಿಗಳೊಂದಿಗೆ_ಬೆಳಸುವುದು
- Crowd sourcing project pages reviewed to fix the flow.
- Requested community members & external resources to help us review the best books which should have a page in wiki
- Out of copyright books list created to be pushed to wiki source.
- Seeked further information on License issues – DLI and OUDL mark books as OUT_OF_COPYRIGHT which are questionable. Need better source to identify the books copyrights. \
- Initiated tests and activities to push the books to Internet Archive & to Wiki commons
- Requested help from community to get the commons books to wiki source.
- Officially requested Prajavani and other news paper agencies to share the E-Book information under Creative Commons license to build wiki pages effectively.
- Follow-ups done to check the status of content collaboration from news papers.
- Tested article creation on wiki – moved the new page creation to sandbox as stub articles are a big no for Kannada Wiki. Using sandbox would be a best start to train new wikipedians to build a complete page before pushing the articles to main namespace.
- Metadata review has been speeded up.
I will keep this post updated with all info needed to participate in l10n team activities for WordPress in Kannada.
About an year ago, we found that it is almost becoming difficult/worse to search the Kannada books on DLI (Digital Library Of India) and OUDL (Osmania University Digital Library).
- Index found in these digital libraries used latin letters for book names i.e. in Kanglish. It was not easy to type any book name and find them due to the transliteration rule used to come up with these names Ex:
Aitihaasika Kathaaval’i Erd’aneya Bhaaga.
- As the names were not found in Unicode/Native language more than 5000 books in these libraries were hidden from common people who would have loved to read them/use them for research, learning etc.
- Even if we found the the book, it was difficult to read the books as DLI needed a special plugin to view tif files on the browser. Luckily OUDL had books in PDF format.
These reasons were more than enough to encourage ourselves to do something around this. We started a small project to pull the metadata of these libraries and see if we can do something about the books.
We initiated a crowdsourcing project on our community portal http://samooha.sanchaya.net, pushed the metadata that Pavithra had collected from the DLI & OUDL websites and requested people to help us transcribe the book name, publisher name and author names to Kannada in Unicode. Following video demonstrates how crowd sourcing helped us get the metadata transformed into useful information quickly.
We had fun working on the above interface ourself as it was fun seeing the donut graphs turning blue while we downloaded many books which we found interesting or which we had missed to read all these days. It was a same experience for others who joined us from various countries to help us with this crowd sourcing activity. Thanks to Devaraj (Devu) who helped quickly put this module live.
Apart from getting the data, we also worked on getting it validated. More or less same set of people helped going through the books once again to see that we don’t have incorrect information for the metadata.
Now, it was time to let people search these books on Internet without much effort. Atleast they can find the Book names, authors and publishers in Kannada. We made this possible via http://pustaka.sanchaya.net
Above image is just a snapshot. 5000+ books being searched on this platform from 100+ categories.
We had admitted for a while that the work is done, but the queries followed our tweets and blog posts on the above projects. We discovered more issues. People desperately wanted to download some of these books, find some which had different author names, some books did not have the right information as printer name was used as publisher’s name and so on…
Apart from that we had more technical issues which we did over see while working on metadata and other things in early stage of this project. i.e availability of the digital library portals round the clock. DLI & OUDL used to fail serving the pages or files intermittently. OUDL library used to go offline after 5pm just like the government offices shutdown. Writing to concerned people never yielded any results.
I’m writing this whole story because we believe that the work of making these books accessible to all Kannadigas is NOT OVER. We need more work to be done. We thought we should have wiki pages for all these books. Request people to join us writing more about the books, about the authors and the printing presses, publishers. Fellow wikimedians also heard about our idea and helped us write a plan for the same. As a result, I ended up submitting our project plan to Wikimedia Foundation’s Individual Engagement Grant.
Please find the detailed IEG project plan here: Growing Kannada-language Wikimedia projects with a digital library
We have been lucky have been chosen to work on this project along with the other 13 participants who submitted excellent ideas. Read more about the other IEG projects here on Wikimedia Blog.
We are now gearing up to work on the project in full swing. This IEG requires us to teach new wikipedians/wanna be wikipedians to learn about Wiki Editing while working on making the Kannada Books from Digital libraries searchable/made available for learning/research etc.
It’s a challenge to make this happen as it again involves crowdsourcing activities in various stages. Involves understanding how we can control the mass editing on wikipedia while taking care of the edit quality and more.
Looking forward for lots of support and encouragement for us here.
If you’re trying to run rkhunter check on your server and finding expr: syntax error for all binaries, it might be due to outdated file properties database.
Run the following command to fix it:
rkhunter –propupd –update
After updating the file properties database, you must get rkhunter working fine again.
Here is some more information about –propupd option
–propupd [file | directory | Update the entire file properties database,
package]… or just for the specified entries
If you wish to contribute back to this list, please send me a personal message from the contact page to be added as a contributor on hackpad.
Zimbra desktop installation on my system was prompting me to upgrade the installation to the latest 7.2.7 version. I downloaded the installer (zdesktop_7_2_7_ga_b12059_20150629062326_linux_i686.tgz) from Zimbra and found that it was not working. For couple of weeks there was no discussion around this on zimbra forums too.
Looking at the logs displayed the following error:
STARTED Jetty ಸೋ ಆ 3 23:03:55 IST 2015
Error: This Java instance does not support a 32-bit JVM.
Please install the desired version.
STOPPED ಸೋ ಆ 3 23:03:55 IST 2015
This forced me to change the default java version that I’m using on my desktop to and i386 version.
$ sudo update-alternatives –config java
There are 4 choices for the alternative java (providing /usr/bin/java).
Selection Path Priority Status
0 /usr/lib/jvm/java-8-oracle/jre/bin/java 1077 auto mode
1 /usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java 1071 manual mode
* 2 /usr/lib/jvm/java-7-openjdk-i386/jre/bin/java 1070 manual mode
3 /usr/lib/jvm/java-8-oracle/jre/bin/java 1077 manual mode
4 /usr/lib/jvm/java-9-oracle/bin/java 1076 manual mode
Press enter to keep the current choice[*], or type selection number:
This sorted the issue with Zimbra desktop quickly.
Having trouble getting eclipse loaded on your linux machines?
Try the following troubleshooting methods to get that sorted.
First to understand the complete issue, run the eclipse command on your terminal as follows:
Picked up JAVA_TOOL_OPTIONS: -javaagent:/usr/share/java/jayatanaag.jar
Unrecognized VM option ‘MaxPermSize=256m’
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Now, you know that the application is not able to identify the parameter related to Java MaxPermSize. These parameters are loaded via eclipse.ini file which is easy to find it under program files in Windows. But to find this on your linux machine, you should know where eclipse has its installation directory and find .ini under that.
I found the installation directory of eclipse by running the command dpkg -L eclipse-pde
to find it under /usr/lib/eclipse. Commented the lines containing MaxPermSize option to get eclipse working.
Let me know if you find it working for yourself.