Open Access News

News from the open access movement

Wednesday, August 22, 2007

Two useful demo services tap DOAJ data

Eric Lease Morgan has launched two demos to show how Notre Dame’s MyLibrary software can make use of journal and article data from the DOAJ:

  1. Article Index.  From the about page:

    ...Article Index serves two purposes: 1) to illustrate ways DOAJ content can be re-used and repurposed, and 2) to demonstrate how MyLibrary can be used to support digital library collections and services.

    DOAJ is an OAI-PMH data repository. It supports at least two different data sets: 1) metadata regarding journals, and 2) metadata regarding articles. We here at Notre Dame wrote a simple OAI-PMH harvesting program that pulls down the article-level metadata. We store the data in a MyLibrary database, and then provide searchable/browsable interfaces to the result. The browsable interface is rudimentary, including only publishers, sources (journal titles), and broad DOAJ-specific "subject headings". With more work a browsable author list could be created too. The entire content of the system is...searchable....

    Ideally, if all (scholarly) journal article content were exposed via OAI-PMH, then indexes like this one, or even more specialized ones, could become the norm. A publisher does not need to expose the the articles themselves, just the metadata. The articles themselves could retrievable only via subscribers.

    Article Index is not intended to be a production service. It is only intended to demonstrate ways DOAJ content can be used and reused. It also demonstrates the flexibility of MyLibrary.

  2. Reading List.  From the about page:

    [Reading List serves the same two purposes as Articles Index above, and makes the same disclaimer that it is only a demo.]

    A MyLibrary system consists of: 1) information resources, 2) users, and 3) librarians. In the case of Reading List, the information resources are journal titles. This MyLibrary implementation allows people to create accounts for themselves -- the users. By associating users with journal titles, a list of "my journals" can be created -- a reading list. If users and information resources shared a controlled vocabulary, then relationships between the users and the resources could be created to implement things like, "If you like this, then you might like that." Alas, this implementation does support such functionality, yet....