MOAI 1.0.6

What does it do?

The MOAI software can aggregate content from different sources, transform it and store it in a database. The contents of this database can then be published in many separate OAI feeds, each with its own configuration.

The MOAI software has a very flexible system for combining records into sets, and can use these sets in the feed configuration. It also comes with a simple yet flexible authentication scheme that can be easily customized. Besides providing authentication for the feeds, the authentication also controls the access to the assets.

Why MOAI

MOAI has been specifically developed for universities, and contains a lot of hard-earned wisdom. The software has been in production use since 2007, and new features have been continually added. In late 2008, the software was completely refactored and packaged under the name “MOAI”. You can read more about this on the MOAI History page.

MOAI is a standalone system, so it can be used in combination with any repository software that comes with an OAI feed such as Fedora Commons, EPrints or DSpace. It can also be used directly with an SQL database or just a folder of XML files.

The MOAI project takes the philosophy that every repository is different and unique, and that an institutional repository is a living thing. It is therefore never finished. Metadata is always changes, improving, and evolves. We think this is healthy.

Because of this viewpoint, the MOAI software makes it as easy as possible to add or modify parts of your repository (OAI) services stack. It tries to do this without sacrificing power, and encouraging the re-use of components.

Features

MOAI has some interesting features not found in most OAI servers. Besides serving OAI, it can also harvest OAI. This makes it possible for MOAI to work as a pipe, where the OAI data can be reconfigured, cached, and enriched while it passes through the MOAI processing.

More specifically MOAI has the ability to:

• Harvest data from different kinds of sources

• Serve many OAI feeds from one MOAI server, each with their own configuration

• Turn metadata values into OAI sets on the fly, creating new collections

• Use OAI sets to filter records shown in a feed, configurable for each feed

• Work easily with relational data (e.g. if an author changes, the publication should also change)

• Simple and robust authentication through integration with the Apache webserver

• Serve assets via Apache while still using configurable authentication rules

In the coming period we will be adding more features and updating this page accordingly.

MOAI 1.0.6 (2009-08-12)

• Fixed metadataPrefix value in didl:Resource URL. This was using didl instead of nl_didl

MOAI 1.0.5 (2009-08-12)

• Unicode bug in Fedora provider

• Added support for mods:location/url Make url prefered identifier in oai_dc:identifier instead of uri

• Update method of Content Objects can now return False to prevent further processing of the object. The object will be logged as ignored

MOAI 1.0.4 (2009-07-15)

• Fixed misspelled mimeType attribute in DIDL metadata prefix

MOAI 1.0.3 (2009-06-23)

Bugs Fixed

• Bug in ListMetadataFormats when using nl_didl prefix

• Added simple dc example profile

MOAI 1.0.2 (2009-05-20)

Bugs Fixed

• Location in mod_python config is dynamicly extracted from Metro Server class.

MOAI 1.0.1 (2009-05-19)

Bugs Fixed

• Fixed URL error in didl metadata prefix

• Seperated darenet specific didl extensions in nl_didl prefix

MOAI 1.0 (2009-05-04)

New Features

• Improved documentation

• Added description to Identify header

• More complete mods name roles

• Require newer pyoai version that gives better error responses when wrong datatime values are used in OAI requests

MOAI 0.9.x (2009-02-01)

MOAI 0.9 (2008-11-18)

• Initial development borrowing code and ideas from RepubXML, a repository environment build for the Erasmus Univiersity Rotterdam