Archive for June, 2008

ALA 2008 conference notes: ALCTS FRBR Interest Group

Friday, June 27th, 2008 by Galen Charlton

This morning I went to the meeting of the FRBR Interest Group at the American Library Association (ALA) conference in Anaheim, California. For those who like lots of acronyms, the interest group is a part of the Association for Library Collections and Technical Services (ALCTS), a division of ALA.

There were two invited speakers. The first, John Espley from VTLS, discussed a couple projects that VTLS has started to promote FRBR and VTLS’s implementation of it in their Virtua ILS. The first, “Try FRBR, You’ll Like It!”, offers existing VTLS customers the chance to send a small sample of MARC bib records and see how they look after FRBRization.

The second project is of more interest to non-VTLS customers. VTLS has started an experiment to offer Virtua’s FRBRization tools in the form of software as a service (SaaS). A library would send VTLS an extract of all of their bib records. VTLS would then determine which subset of the records would most benefit from FRBRization, then create a Virtua database with the FRBRized set of bibs. The library could then set up their OPAC to link from bib records to the work-sets stored in the Virtua database. That would allow a patron to find a bib for a paperback edition of Tom Sawyer and click on a link to see a list of all editions of that work that the library has. From the work-set page, the patron could in turn travel to one of the individual bibs.

VTLS has a prototype of this service working for one of their Virtua customers, but they intend for the service to work with any ILS. The prototype seems to be quite new — Espley mentioned that it was set up in the past week or so — and during the question and answer session, Espley and the audience identified a number of issues for VTLS to work through. One issue is improving their automated FRBRization tools, as Espley said that some manual cleanup was needed to group together expressions in the prototype and create higher-level entities that VTLS calls “superworks” (under FRBR rules, the book and movie versions of Tom Sawyer are two separate works — a “superwork” puts the two works under a single Tom Sawyer concept). Another is keeping the FRBRized database up to date as the library adds and updates their bib records.

VTLS’s FRBRization service is an interesting idea, and it could complement services such as xISBN and ThingISBN by offering a FRBRization that is customized to a library’s specific collection. I applaud VTLS for undertaking the experiment. Of course, I have concerns about the openness of such a service, and encourage VTLS to think about keeping the service as open as their business model permits, including:

  • Making sure that any web service APIs related to the FRBR service are fully documented so that their customers (and others!) can easily build mashups.
  • Making sure that there are no restrictive licensing terms that would prevent a library from contributing changes they make to improve the FRBRization back to the library community.
  • Publishing details of the VTLS FRBRization algorithm, in particular, to describe how and why it may differ from the OCLC FRBR work-set algorithm.
  • Contributing any bib record enhancement that VTLS may do as part of the service (e.g., by adding uniform title headings) to the library community.

The second speaker was Jennifer Bowen from the eXtensible Catalog project (XC). The XC project aims to create open source tools and services to help libraries improve resource discovery and metadata management.

Part of the planned XC system is a “metadata hub” that would harvest records from a library’s ILS using OAI-PMH. Once in the hub, the MARC records would be mapped to a more flexible schema. Since RDA has not been finalized, XC is devising an interim schema that includes the Dublin Core elements (mapped to FRBR entities) and about 20 elements from RDA. As such, the XC schema will be a testbed for parts of RDA — as Bowen said, an “RDA sandbox”.

How does FRBR fit in? Besides the FRBR entities represented in the XC schema, incoming records will be split into their FRBR components. The proposed schema doesn’t seem to be available on the XC website; I’ll be very interested to see it when it’s published.

There was a brief general discussion after the two speakers finished. Of particular note: somebody asked how she, as a cataloger in a small public library that is not a member of OCLC, can prepare her catalog for FRBRization. This spawned an interesting discussion. One person made the point that catalogers should consider adopting a peer-to-peer model for distributing metadata instead of relying on central repositories to collect all improvements to metadata records. In the case of FRBR, this is important because one way to make a MARC21 bib record more useful for FRBRization is to add a uniform title heading. For such an improvement to be even more useful, it should be contributed the library community, but as someone said at the meeting, “While we are very good about sharing the first version of a bib record, we’re less good about sharing enhancements.”

To close with a bit of shameless self-promotion, I discuss using distributed version control systems as a model for sharing library metadata (and perhaps more importantly, changes to library metadata), in my article in the current issue of the Code4Lib Journal. While big central repositories of metadata such as OCLC and the Open Library are very important, I think a distributed record of record sharing is also needed.

Technorati Tags: , ,

Koha 3.0 RC1 Released

Friday, June 27th, 2008 by Nicole C. Engard

It’s finally here! After tons of hard work, the Koha community has announced the release of Koha 3.0 RC1. This from the many Koha mailing lists:

You can download from the usual location:

http://download.koha.org/koha-3.00.00-stableRC1.tar.gz
http://download.koha.org/koha-3.00.00-stableRC1.tar.gz.sig

You can check the integrity of the package; either by verifying the provided GPG signature (.sig) or by comparing the MD5 checksum:

5cc0914c5e8250c2491f4dbcf27d4301 koha-3.00.00-stableRC1.tar.gz

I’ve also tagged this in Git as “version 3.00.00 stableRC1″ v3.00.00-stableRC1

This is the third packaged release of Koha 3. Prior to the official stable release of Koha 3.0, translations will be updated; additional issues and bugs may be be addressed. A list of these are documented on Koha’s Bugzilla:

http://bugs.koha.org

and organized on the 3.0 RM’s QA notes Wiki page:

http://wiki.koha.org/doku.php?id=en:development:qanotes3.0

The release notes for this RC1 version are pasted in below, and will also on the koha.org website sometime soon.

Cheers,


Joshua Ferraro
Koha 3.0 Release Manager

And as many of you know (well at least those of you on Twitter & Facebook) I have been working on the documentation for this new release and my working draft can be viewed online (hopefully to be moved to a more collaborative medium soon) via LibLime’s Google Sites at http://sites.google.com/a/liblime.com/koha-manual/Home. Feel free to notify me of any changes, suggestions, etc.

Technorati Tags:

Gitting Used to Git

Friday, June 6th, 2008 by Andrew Moore

I have been using git a lot more efficiently recently, and I want to share some of the more advanced things that may help you get used to using git, too.

First, it helps me a lot to have some things in color. I have found these four config changes to make it a lot easier to scan git output quickly. The “diff” one is especially handy.

  • git config –global color.branch auto
  • git config –global color.status auto
  • git config –global color.diff auto
  • git config –global color.interactive auto

Second, I have found “git add –interactive” to be pretty useful. If you have changed several files and only want to commit some of them, this will present a menu-driven interface to let you pick the files to add. Even better, if you have edited a file in two places and only want to include one “chunk” in your commit, this lets you specify that. It’s great if you have added some debug code at the top or bottom that you don’t want to commit.

Next, I’ve been using git rebase –interactive” to be able to re-order and combine my patches to make them more readable. If you have a long sting of small commits that you want to organize better, you can run “git rebase –interactive HEAD~20″. This will open an editor with the last 20 commits in it. You can reorder the lines to reorder the commits. You can also “squash” the lines to merge commits together. This will help you make more readable sets of commits.

Finally, if you have a commit that you want to split up, use “git rebase –interactive” to “edit” it. Then, “git reset HEAD^” to put yourself “back in time” to that spot. Then, you an choose only a subset of the files or patches to commit, commit them, and then optionally commit the rest.

For more help on using git, I have really found the gitcasts to be a tremendous help.

Some of these features require a newish version of git, so if yours doesn’t seem to be working like this, I recommend an upgrade.

git ‘er done!

Koha 3.0 Haiku

Thursday, June 5th, 2008 by Joshua Ferraro

To do my part for
LibLime's bloging policy
here are two haiku

Koha ILS,
we're nearing the 3rd release
watch koha dot org

Code4Lib 2008 Videos

Wednesday, June 4th, 2008 by Nicole C. Engard

If you weren’t able to make it to the conference, you can still see all the great talks!! Check out the videos from the conference at Archive.org.

Also all slides and videos are linked from the conference schedule.

Technorati Tags: ,