Main | July 2007 »

June 28, 2007

Updated MODS Records from UM

We finally got around to updating the MODS records for our two collections we're data providing through MODS -- History of Math and Michigan Counties. The latter is in the Aquifer portal:
(search "The University of Michigan, University Library")

Mostly these were tweaks to conform to the new-ish Aquifer Guidelines. However, we are planning to do something interesting with the call numbers in the original MARC records we're mapping to MODS. We plan on attaching High-Level Browse topics, based on these call numbers, to the MODS records. If anyone has suggestions for what MODS field to place these topics in, that would be much appreciated. We were originally thinking Genre, but that doesn't seem quite right.

** See High-Level Browse in action at UM:

Posted by khage at 01:00 PM | Comments (0)

June 26, 2007

UM Best Practices Wiki Available!

We have the UM Best Practices Wiki available, finally. I've done a lot of monkey work getting the paths to work correctly, weed out bad characters, re-upload files from the NSDL wiki, etc.

Now folks will take a look, and hopefully pretty soon we can allow NSDL to take down the current wiki.

Posted by khage at 06:42 PM | Comments (0)

June 20, 2007

Web Stats for DLF Aquifer Portal

I added a Wiki page to the Core group describing the web stats to date. You'll see that June 2007 has been our busiest month to date!

Posted by khage at 01:53 PM | Comments (0)

June 19, 2007

Steps to Add an Aquifer Set

So, this is my attempt to list what it takes on my end to add records to the Aquifer portal. There are a bunch of stand-alone files, and if nothing else, perhaps this will encourage Chick and Tom to make this more invisible/automatic!

1. Assuming a successful harvest of the MODS records, I look to see what the set ID is, and if I need to modify the name (I try to avoid set IDs with a dash or underline in them).

2. I add the set ID and appropriate set name (not necessarily what the data provider has indicated is the set name) to a couple of stand-alone files. One file associates the set ID with the set name, so that the left-hand column in the results list will be populated correctly. The second file associates the set IDs with the set names for the purpose of running the transform tool.

3. Once the files are populated, I run the MODSTransform tool. This runs very quickly, and I get a report of which records are in the file system, which records have URLs (i.e., those that end up being included in the portal), any data conditioning/massaging that needed to happen, etc.

4. I move the resulting [setID]_bib.xml file to the appropriate place in the filesystem, concatenate all set XML files and index the concatenated file.

5. While it's indexing, I change the web files so that they describe the new set added, and update the number of records and data contributors.

6. I rdist (move) all these files to the production server.

Posted by khage at 09:46 AM | Comments (0)

June 15, 2007

Institutions interested in creating MODS records

I was wondering how many institutions have shown interest in creating MODS records. We currently have 7: Digital Colls at UM, OCLC, Indiana, LoC, U of Chicago, Deep Blue at UM and Celebration of Women Writers at UPenn. Who has heard of others who are waiting on the finalization of the Aquifer MODS profile to create MODS records?

Can we encourage folks to create MODS records even if they are not perfectly conforming to the profile? I would imagine that the big hurdle is finding (or creating) the appropriate mapping and finding time to make sure the mapping is appropriate for a collection. Once the metadata is created, fitting into the profile at a level of conformance would seem a smaller hurdle. I know that's the case at UM.

Interested in your thoughts.

Posted by khage at 02:35 PM | Comments (6)

June 11, 2007

EDIT: Collection Solicitation Draft

Folks, I've edited the Collection Solicitation draft using the comments of the collection submission advisory group (Tim, Sarah, Jenn, Perry, me). Please comment: go ahead and just comment on this blog entry.

Edits for later: The Best Practices wiki URL will change at some point in the near future. Also, we might wish to point instead to the published versions on the DLF site.

Also, we need to determine who will be responsible for ingestion of collection submissions. I think we can hash that out at Friday's meeting.

DLF Aquifer seeks material that fits within an American culture and life theme, broadly defined. The Aquifer Collections Working Group will evaluate the metadata to determine whether it is in the Aquifer scope.

The current method for gathering material is by metadata harvesting using OAI-PMH. We ask data providers to make MODS records available according to the Digital Library Federation/Aquifer Implementation Guidelines for Shareable MODS Records. In addition, potential data providers may find the OAI Best Practices useful, in particular the Shareable Metadata and Data Provider Implementations sections.

We understand that many libraries and cultural heritage organizations have metadata in other formats and we are investigating the possibility of providing mapping support for transformations from MARC, EAD and possibly VRA formats to Aquifer style MODS. The Aquifer team is modeling workflows for ingesting new collections and would be glad to work with collection providers and their technical contacts to create flexible methods to add content with metadata in other formats. We strongly recommend that these formats be as rich or richer than MODS or MARC, in keeping with our efforts to provide as much detail as possible. It also bears noting that a requirement of OAI-PMH is that data providers make the oai_dc (simple Dublin Core) format available.

As per the Aquifer mission, the metadata we collect should point to digital objects. These digital resources should also be made available for additional purposes within our framework, e.g., as thumbnails for Asset Actions services; for manipulation of the resources themselves.

For organizations without OAI data providers or plans to set one up, we are also considering offering a Static Repository setup service. We welcome the opportunity to discuss this idea with collection providers. For those interested in this avenue, the requirement is XML-enabled metadata.

When collections are submitted, we ask that the provider insure the continued availability of the resources through Aquifer by signing a submission agreement. The agreement also outlines the Digital Library Federation's right to use the digital material and metadata within the Aquifer project.

Send expressions of interest and questions to need group/individual.

Posted by khage at 04:05 PM | Comments (1)