RDF - Connecting Software and People

An short 30 minute in depth introduction to the Semantic Web for people with some Software engineering background. Presenting the problem ... all » of the Mythical Man Month, this shows how one can use an OWL Ontology, to describe the relation between people and software bugs. Makes the case that the best way to get the Semantic Web going is by opening up a valuable database to a SPARQL end point. presentation and more available at:http://blogs.sun.com/roller/page/bblfish/20060323

Technorati

Technorati Profile

Lucene: How to design your own Web search application ?

Apache Lucene is a high-performance, full-featured text search engine library written entirely in Java. It is a technology suitable for nearly any application that requires full-text search, especially cross-platform.

Apache Lucene is an open source project available for free download. Please use the links on the left to access Lucene.


How to design your own Web search application ?:

"Beef up Web search applications with Lucene"

by Deng Peng Zhou

mplement advanced search with Lucene

"Lucene supports several kinds of advanced searches, which I'll discuss in this section. I'll then demonstrate how to implement these searches with Lucene's Application Programming Interfaces (APIs).

Boolean operators

Most search engines provide Boolean operators so users can compose queries. Typical Boolean operators are AND, OR, and NOT. Lucene provides five Boolean operators: AND, OR, NOT, plus (+), and minus (-). I'll describe each of these operators.

• OR: If you want to search for documents that contain the words "A" or "B," use the OR operator. Keep in mind that if you don't put any Boolean operator between two search words, the OR operator will be added between them automatically. For example, "Java OR Lucene" and "Java Lucene" both search for the terms "Java" or "Lucene."
• AND: If you want to search for documents that contain more than one word, use the AND operator. For example, "Java AND Lucene" returns all documents that contain both "Java" and "Lucene."
• NOT: Documents that contain the search word immediately after the NOT operator won't be retrieved. For example, if you want to search for documents that contain "Java" but not "Lucene," you may use the query "Java NOT Lucene." You cannot use this operator with only one term. For example, the query "NOT Java" returns no results.
• +: The function of this operator is similar to the AND operator, but it only applies to the word immediately following it. For example, if you want to search documents that must contain "Java" and may contain "Lucene," you can use the query "+Java Lucene."
• -: The function of this operator is the same as the NOT operator. The query "Java -Lucene" returns all of the documents that contain "Java" but not "Lucene."

Now look at how to implement a query with Boolean operators using Lucene's API. Listing 1 shows the process of doing searches with Boolean operators.

Full Article : here

by Deng Peng Zhou is a graduate student from Shanghai Jiaotong University. He works as an intern software engineer in IBM Shanghai Globalization Lab and is interested in Java technology and modern information retrieval. You can contact him at zhoudengpeng@yahoo.com.cn.

MySQL 5.0.26 new version

MySQL The world's most popular open source database MySQL 5.0.26 new version has been released...

MySQL software is published under an open source license and is available in two ways:

1. MySQL Community Edition is the freely downloadable version of the world's most popular open source database. It is supported by a huge and active community of open source developers and enthusiasts. MySQL Community Edition uses the GPL License, is released early and often, and includes all features, including the latest features under development.
2. MySQL Network is available for users who want access to our world-class support services, Knowledge Base and certified software. This subscription service is designed to save developers and DBAs time and effort.

Library 2.0 links

" I have done a lot of reading while preparing for my presentation on Blogs and Wikis at the LRSN forum next month. Nearly everything leads me to find out more about the catchphrase “Library 2.0”.

It was only recently that I first heard about this phenomenon so I brought it up at our monthly Librarians’ Forum at Perth this morning – only to find out that, although we had been discussing several ideas that are important to Library 2.0, my colleagues were not aware of the term.

I’ve cobbled together some links to further reading that I have found worthwhile. If we want to be seen as being on top of new ideas then constant awareness of what’s being posted on the web is important and we should all monitor our RSS feeds regularly."

Published in mchabib.blogspot.com by Maeve Everest

Library 2.0 Links

http://mchabib.blogspot.com/2006/08/academic-library-20-concept-models.html

Greenstone 2.71

GLI:
-----
- new Format panel, containing all options relating to collection formatting.
These options don't require a rebuild to take effect. Preview Collection
button now also on this Format panel.
- default indexer for new collections is MGPP
- searchtypes now a format statement instead of a design option.
- new Macros section on Format panel - can edit collection's extra.dm directly.
- redesign of Search Indexes section of Design panel.
- Search indexes now displays options for stem, casefolding and accentfolding
(MG and MGPP only). If selected, the appropriate index will be built.
Search preferences for these options will depend on the appropriate index
being built.
- new Search section in Format panel: can edit display text for search form
drop down lists (indexes, subcollections, levels etc)
- metadata set management now on Enrich panel (Manage Metadata Sets button).
- New collections default to using the Dublin Core metadata set, and no set
prompt is given. This can be changed from the Enrich panel.
- updated help text
- now restarts itself if a new language is selected.
- plugins.dat and classifiers.dat no longer used. Plugin and Classifier
information is dynamically loaded when needed.

GEMS:
-----------
- reimplementation to make a simpler interface
- only one set is now open at a time
- A predefined set of attributes for set/element is provided
- Is launched from GLI to create a new metadata set or edit an existing one

Collection Exporting:
------------------------
- File->Export in GLI. Now supports exporting as Greenstone Archive (GA),
DSpace batch import, Greenstone METS, and MARCXML formats.
- All export types support the use of XSLT to transform resulting XML files.
For example, could export to GA format, then transform to a custom format
using an XSLT file

Export to CDROM:
------------------
- now has a -noinstall option, so that the resulting CDROM doesn't install
anything onto the host computer

MGPP:
------
- maxnumeric support added
- query term truncation (e.g. comput*) with casefolding fixed for non-ascii
query terms
- accent folding support added (thanks to Juan Grigera): Generates a
new index which folds accents, in the same way that case folding
works. Accent folding means that é will match e, and vice versa.
This is turned on by the user via the preferences page.
- Mongolian unicode support

More ....................here

Importing MARC data into DSpace

posted by Steve Thomas in http://stevethomas.blogspot.com/

Monday, August 07, 2006

"For the interest of anyone else working on Institutional Repositories, I’ve written a technical report on how we used MARC record data to build records for import into DSpace.

In brief, we had a couple of collections with documents held in local web servers and a record for each document in our catalogue. So we exported the catalogue records to a MARC file for each collection, then developed Perl scripts to convert the MARC records into the required data structure required to import into DSpace."

You can find the report in our Digital Library, at

http://digital.library.adelaide.edu.au/dspace/handle/2440/14784