Planet Cataloging

May 13, 2008

Catalogablog

Non-Latin Data in Name Authority Records

From LC:
As previously announced, MDS- Name Authority records will be enhanced with non-Latin script data in 4XX fields and selected notes beginning June 1, 2008, (see earlier announcements at http://www.loc.gov/catdir/cpso/nonroman_announce.pdf and http://www.loc.gov/catdir/cpso/nonlatin_whitepaper.html for additional information.) An additional FAQ related to the project will be posted at http://www.loc.gov/aba/ shortly.

An effort to automatically pre-populate existing authority records with non-Latin references by OCLC, Inc. will also begin in early June 2008. The initial rate of pre-population will be limited to several hundred records per week, and will grow to a rate of approximately 25,000 records per week. Note that other clean-up projects that have recently increased the volume of name authority records (http://www.loc.gov/cds/notices/2008-02-14.pdf ) will be suspended during this pre-population effort. It is estimated that approximately 400,000 pre-population records will be distributed over a number of months.

CDS is making available a file of name authority test records containing non-Latin script data. The file of 110 test records can be found on the Library of Congress rs7 server under the /emds/test subdirectory with file names of names.nonlatintest.records for the MARC 8 version and names.nonlatintest.records.utf8 for the UTF8 version.

by noreply@blogger.com (David) at May 13, 2008 06:12 PM

Spam

I've been blasted with comment spam. So I've had to turn on the comment moderation function.

It is a shame how these few folks can ruin things for all. A few years back a e-card was a fun thing to receive and send. now so many are spam, I've stopped sending and opening them. Open comments seem ready to go the same way.

by noreply@blogger.com (David) at May 13, 2008 05:14 PM

025.431: The Dewey blog

Oil Prices

High prices for crude oil have been in the news recently, e.g., “Supply Fears Push Oil beyond $126” and “Oil Price Resumes Its Record Run.” 

Among the Relative Index entries for prices are:
Prices   338.52   
Prices—economics   338.52 
Prices—mineral industries   338.23 

The comprehensive economics number (also the interdisciplinary number) for prices is 338.52 Prices.  The class-elsewhere note under 338.5 General production economics, “Class production economics of specific kinds of industries in 338.1-338.4,” has hierarchical force; consequently, the price of crude oil is classed in the appropriate subdivision of 338.1-338.4 Specific kinds of industries, specifically under 338.2 Extraction of minerals.  The scatter note under 338.52 Prices, “For a specific aspect of prices not provided for here, see the aspect, e.g., effects of prices on the whole economy 339.42,” also indicates that oil prices will not be classed in 338.52 Prices

Among the Relative Index entries for oil are:
Oil (Petroleum)       553.282
Oil (Petroleum)—economic geology       553.282
Oil (Petroleum)—extractive economics       338.27282

At 338.27 Products is the add note that explains how to build 338.27282 Extractive economics of oil (338.27 Products plus 282 from 553.282 Oil). There are also two class-elsewhere notes that should be considered: “Class supply in storage, shortages, surpluses, demand, and projections of these in 333.8; class specific elements of production applied to specific products in 338.23-338.26.”  The first class-elsewhere note would be relevant for a work about the effect of oil prices on supply in storage, shortages, surpluses, and demand; by the rule of application, works about the influence of the price of crude oil on something else are classed with the thing influenced.  The first note is not, however, relevant for comprehensive works on oil prices.  The second class-elsewhere note leads to 338.23 Financial aspects of extraction of minerals, which has the note, “Class here . . .  prices.”

Comprehensive works on prices of crude oil are classed in 338.23282 Financial aspects of extraction of oil (built with 338.23 Financial aspects of extraction of minerals plus 282 from 553.282 Oil, following instructions at 338.23), e.g., Oil Markets and Prices:  The Brent Market and the Formation of World Oil Prices

by Juli at May 13, 2008 03:34 PM

Z666.7.L364 (www.jenniferlang.net)

Planet Cataloging, Take 2

The email address to send comments, requests, etc., is:

info@planetcataloging.org

{sigh}

by Jennifer Lang at May 13, 2008 12:20 PM

Planet Cataloging

Imagine my dismay when I received the following email last Sunday (sent to my Princeton email address):

“The Planet Cataloging email address box is full, so suggestions can’t get through (like mine; see below). Thought the maintainers ought to know in case someone wants to do anything about it.”

Yikes.

For some reason (only known and forgotten by me), I thought I’d set The Planet emails to be forwarded automatically to my personal email address. See what happens when I think?!

Anyway, if you sent suggestions, requests, or comments but haven’t noticed any changes to Planet Cataloging, info@planetcataloging.org is once more a functioning email address, so please re-send your emails; my apologies for the inconvenience.

Thanks for reading, and thanks for your support!!!

Jennifer (and Kevin, even though I didn’t tell him about this latest glitch…)

by Jennifer Lang at May 13, 2008 11:19 AM

repositories for the rest of us

Musing on role of librarian in the cyberinfrastructure

For each step two steps forward, there is the requisite step back.Last week's two steps forward: the Rockefeller Press announcement (via Issues in Scholarly Communication) and the Harvard Law School joining the Harvard Faculty of Arts and Sciences in unanimously adopting an OA mandate (via same).

Last week's step back: Thompson-ISI puts restrictions on how authors using ResearchID (via Disrupted Library Technology Jester).

Thompson-ISI isn't high up on my fave vendor list because of their abysmal treatment of ISSNs within Web of Knowledge (don't get me started on the difficulties I encounter administering links to WoK within SFX). To their credit they're working on that. But this ResearchID thing makes it very obvious how they're developing their market -- they want to lock up author identifiers so only they can create web services with them. They've lost their monopoly on citation analysis now that Google, Scopus etc. are in the game. Makes me think that academic libraries better get on the ball with developing author identifier tools for their repositories and/or institutions. This is something I've been thinking about. I would love to make authority files for each faculty member and research group on campus and OpenID them or some such so that doing bibliographic citation analysis becomes more rationalized.

That's in keeping with a lively discussion the librarians at MPOW had with John Wilbanks of Science Commons during lunch last Monday. Wilbanks talked about the economic issues involved in creating and maintaining namespaces, largely who is to be responsible for long term funding and support. Wilkins said he believes that this is the type of work where librarians will find their niche as the academy moves towards cyberinfrastructure/eScience what-have-you.

Maybe. There's a big gap between the idea of librarians doing server/database/webby stuff and the reality of the technology skills of librarians on the front lines. I sure as heck don't know how to install and configure a namespace server. There are research and commercial interests which are way ahead of us on providing those types of services. Why should a researcher go to his librarian for help with managing his online identity if ResearcherID-type services already exist?

I don't know how to bridge that gap when it comes to what type of things I should be working on as professional development. Is it worth the energy to bootstrap myself into managing the technology behind semantic-webified authorities? That takes not only time but day-to-day projects with which to practice skills.

And technical services librarians are enmeshed in economically unsustainable models of cataloging and electronic resource maintenance anyway. For example, I've had to fix all the records for Proceedings of the Royal Society at each single place I've ever worked (hey, 300 odd years of title changes and splits makes for hard slogging managing the 78Xs and OpenURLs). This is the forest in which we toil and the trees are fading from view.

My only means of dealing with it is to partner with public service librarians to liaise with researchers, do user needs assessment for cyberinfrastructure services that we're capable of developing and delivering, then develop pilot projects from which to learn the requisite skills.

I fear that this type of work is too little too late for academic librarians. Yet, what choice do we have other than to persevere?

by Laura (noreply@blogger.com) at May 13, 2008 10:36 AM

The FRBR Blog

Johnston, FRBR and Time-Based Media

Pete Johnston posted FRBR & “Time-Based” Media, Part 1 and FRBR & “Time-Based” Media, Part 2: Clips/Segments and perhaps more will follow. Go give them a read.

Suppose I develop a machinima-based tutorial video introducing some of the features of Second Life for use by undergraduate students new to the application. I might make my tutorial available for streaming using my institution’s streaming server, both in Windows Media Video format and in QuickTime format. And I might make a QuickTime version available for download as an alternative to streaming. I might also make a second copy of that QuickTime file - exactly the same content, quality, size etc - available for download from my personal Web site.

From a FRBR viewpoint, I think this would be represented as a single FRBR Work (W01), realized in a single Expression (E01), embodied in three different Manifestations (streamed Windows Media Video (M01), streamed QuickTime (M02) and downloadable QuickTime (M03)), with the first two of these Manifestations each exemplified in a single Item, and the last exemplified in two Items.

And then it gets complicated!

by William Denton (wtd@pobox.com) at May 13, 2008 03:08 AM

May 12, 2008

Bibliographic Wilderness

Search hints/related search?


So google and Yahoo both sometimes offer “related” searches, in a nice AJAXy popup.

I don’t have time to find an example to show you, but I think most of you have seen it with Google at least. The firefox google opensearch toolbar for instance. I put in “library” and in a popup it suggests “library of congress; librarything; library thing; library journal” etc. Maybe that wasn’t the best example, but sometimes this is useful.

It strikes me that it would be really nice to have a similar feature in our various library search functions (including catalog and federated search?). First thought is, gee, can I just use the Yahoo and/or Google apis to do this? But I seriously doubt that would be consistent with either of their Terms of Service, to use this service for something that has nothing to do with google/yahoo and isn’t going to lead to a search of google/yahoo, but instead use these suggestions for search of our own content.

So, that gets me thinking, how do you do this? Obviously Google and Yahoo are coming up with these suggestions by analyzing their own data—either their corpus of indexed stuff, their query logs, or likely a combination of both. Anyone know if there are any public basic algorithms for doing this kind of thing? Anyone have enough “information retrieval” knowledge to hazzard a guess as to what sorts of algorithms are used for this? How would we go about adding this to our own apps?

Update: It also occurs to me that this would be ANOTHER natural service for OCLC to provide. To provide “related search” suggestions well, you need a good corpus and some data mining. OCLC has a giant corpus of not only book metadata, but search query history from their database offerings.  An OCLC “search suggestion” API where you give it a query, and it gives you search suggetsions, which you are licensed to use in any search your library has? I’d reccomend my library pay for that, if the price was right.  Natural service from OCLC.

by jrochkind at May 12, 2008 03:57 PM

Terry's Worklog

RLG Tools Form (May 8th, Boston Public Library)

So, as folks might have gathered from a few of my posts over the last week, I had a few engagements that have keep me on the east coast over the past week.  One of the events that I had attended during the week was the RLG Tools forum at the Boston Public Library.  This event is the first (of hopefully what will become a reoccurring) event put on by RLG to help promote and inform RLG members of tools being developed within the library community that deal with specific facets of creating, managing and preserving objects within a library.  For this first tools forum, RLG focused on tools primarily developed to facilitate the metadata creation and maintenance process.  For that reason, I was invited to present MarcEdit…but I’ll get to that shortly.

So how was the trip.  Good.  I actually like Boston, and even though I didn’t get a whole lot of time to visit the city (simply because I was busy), I did find ways to get out and sample multiple varieties of my favorite soups, creaming Boston Clam Chowder and a creamy Lobster bisque.  It’s likely a good thing that I don’t live in a city were these types of creamy delights are always available — because I’d likely find a way to have them about everyday (which can’t be healthy).  But I’m getting ahead of myself a little.

For this trip, because I was traveling to multiple cities and multiple airports before my trip was done, I decided to buy a lot of one way tickets (partly because it worked out to be cheaper).  And because of that, I got to try out the airport in Salem, Oregon.  Salem, which had a municipal airport years ago before commercial service was abandoned, is getting a second chance at commercial airline service.  Delta provides a handful of flights out of Salem into Salt Lake City, so I decided to give the airport a try since I generally fly out of PDX, about 2+ hours from my house, depending on traffic.  So the good — its only 15 minutes from my house, which definitely has it’s pluses.  Of course, being a small airport, parking is very limited, so you really need someone that can drop you off, or, as I chose, take a cab from somewhere in Salem [note, this is where having only one car can be a pain.  I took a 6 AM flight, and to have my wife drop me off, she would have had to have driven with me (and woke up the boys), around 4:30 am.  Not something I would ask them todo.  Because of that, it actually almost costs more (depending on how I make the trip), for me to fly out of Salem, since I can rent a car through Enterprise and simply drop it off at PDX.  Odd how that works out].

So the airport — it’s small.  Only one terminal, but staff were nice and attentive.  Security took forever to get through, simply because their is only one security gate and all people are processed through it about 40 minutes before the flight.  You basically spend that time in line (unless you can be first through).  Secondly, for a small airport like this — they really need to offer passengers something — wifi would be a good start — a Starbucks or something with some food or pastries would be a second.  Since the terminal is so small, I found myself doing a bit of thumb twiddling.  Had I been at PDX, I would have gotten myself a hot chocolate and been reading the news or playing a little online chess.  Also, I’m not sure I like Salt Lake as a hub.  The airport is actually very nice (Salt Lake), but it made for a very long flight to Boston.  Generally, from PDX, I end up getting a short layover in Cincy or Chicago, which makes for a nice stretch break, and a shorter second flight.  So, I’m pretty sure PDX is going to remain my primary airport for the foreseeable future, though I hope the Salem continues to be an option.

So the tools meeting — that went surprisingly well.  I’m always happy to hear from folks that have used MarcEdit and found it useful and there I found a little of both.  Also, I got to talk to a number of people about MarcEdit for the first time (or, tell people about functionality that they might not have otherwise been aware of it).  I think most people still see MarcEdit as primarily a MARC editing package — though throughout the last couple of years, the program really has been expanded to include a number of functions that make data harvesting, metadata packaging, etc. a much simpler process.

For my part, I got to check out a number of tools myself.  I think that my favorite and the one that I’m going to take a much closer look at is Archon [http://www.archon.com], an EAD delivery and management system.  At present, OSU is making use a number of tools to store and display finding aids.  There’s the NWDA’s website (a group that might be interested in this software as well, since it’s open source, free and looks to be fairly well supported.  Certainly could free up a number of funds currently be spent to license their current software solution), OSU’s CONTENTdm instance as well as just PDF representations of the data.  I’m not sure if Archon can replace any of those interfaces, but I certainly think it’s worth taking a closer look.  Additionally, there was a metadata management tool shared by the University of North Texas Libraries that demonstrated a customized process used by the institution to metadata loaded into their digital systems (which could be interesting if uncoupled from University of North Texas’s workflows) as well as a MOD’s Editor built from XFORMS developed by Brown University, which I find amazing simply due to the simplicity of design.  However, there were lots of other tools that were shown off.  Those with URLs are as follows:

So was the forum worth it?  From my prospective, as a tools developer, it was.  One of the challenges, even for someone who has been doing this for a while, it finding new ways to interact with one’s user community.  I think MarcEdit is likely unique among many tools in that it’s not a university project.  While Oregon State University certainly has been great in allowing me time to work on this project, as well as grow and support the user community — I do all development on my own time.  And the program isn’t developed specifically for OSU.  In fact, development is really community driven, in that new features are basically added at user request — so for me, interacting with users is really one of the most important ways that I can get a better idea of what people are waiting out of the program.  And for that, the RLG tools forum was very useful.  As an attendee, this meeting exposed me to a number of tools that I certainly wasn’t aware of before.  How we will be able to make use of some of these tools, well, that’s still in the air, but I think that forums like this are important.  There are a lot of people within the library community creating a lot of really interesting projects — as well as a lot of overlapping projects being developed.  I think forums like this might be able to have an affect of getting like projects together and maybe help to reduce some of the duplication being done on campuses across the country — and that would certainly be a good thing.

So, after Boston, I made a trip to NY to visit the Geneseo library and my good friend, Cyril Oberlander.  They are doing some fantastic work with ILLIAD and document/article delivery.  If you want to read a little more about their project, see http://oregonstate.edu/~reeset/blog/archives/522.  But I certainly enjoyed the opportunity to get to hear about their work and give them some feedback and some ideas as they look to make the service more widely available to organizations outside of the SUNY group.  And of course, this trip wasn’t all work as well.  On Saturday, I drove out to the Letchworth State Park — also referred to as the Grand Canyon of the East.  It’s a gorgeous area — with some great hiking and scenery.  There are basically 4 falls areas that you can hike to.  I got a lot of great pictures (which I might post, maybe not), seen lots of deer and basically spend 8 hours hiking in the woods.  I loved the quiet and a chance to get unconnected for a little while.  Of course, while I was there, one place that I didn’t visit was Inspiration Point.  My impression of the place is that it’s kindof a couples hangout, so I decided to add that as a place to visit with my wife, next time we find ourselves in the Rochester/Geneseo area.  :)

The only real bummer with the trip has been the travel home.  This is the first time in a long time that I haven’t been at home for Mother’s day.  Fortunately, my oldest son (Kenny) picked up the slack for me.  My wife told me that he’d been planning a secret all week and that this morning, he got up at 7 am and snuck into the our bedroom with gifts.  He left them on the bed and then gave her a kiss on the cheek and wished her a happy mother’s day before disappearing back into his room with his brother.  Not sure what the secret Kenny present was (apparently, I have loose lips because I told me he wasn’t telling me either), but I’m sure it was great.  And now I’m hoping that I’ll be able to get home before mother’s day ends.  The joys of airline travel in the 21st century.  I should just about be at PDX right now (9 pm), but thanks to an extended period on the runway (for who knows why), I’ve still got at least another hour before landing (10 pm).  Speaking of joys of airline travel. [soapbox]I personally have no problem with airlines moving to the al cart model that many have started to embrace.  If they want to charge for food, entertainment, extra bags, etc — I’m fine with that.  On a 6 hour flight, like the one I’m on now — it would be nice to be tossed a bag of peanuts now and then, but I know the score and pack accordingly so I’m generally prepared.  All I ask of an airline is two things…1) that both my bags and I get to the city at the same time (something that I’ve had few problems with considering the amount I travel) and 2) that I arrive on time.  Both are important to me, but it seems that arriving ontime is becoming a much rarer event.  Since February, I’ve been on roughly 7 flights.  Going east bound, I’ve found average arrival time has been about a 1/2 late, going west bound, my arrival at PDX has been nearly always ontime (today is actually a bit of an anomaly), but my layover flights (generally to O’Hare) have been exercises in futility as I’m always finding myself landing and then sprinting between terminally only to arrive at my gate and trying to talk myself onto a flight that is preparing to leave.  Fortunately, I’ve had a lot of understanding gate agents, but the increased frequency of delays and tardiness is something that I’ve definitely been noticing.[/soapbox]

 

–TR

 

** Update — didn’t make it.  Got home at 12:03 am in the morning.  Loooonnnnngggg day.

by Administrator at May 12, 2008 02:56 PM

panlibus

JISC & SCONUL Talk with Talis about Library Management System Study

Rachel Bruce of JISC and Anne Bell of SCONUL join me in the latest Talking with Talis podcast to discuss the recently published JISC & SCONUL Library Management Systems Study - An Evaluation and horizon scan of the current library management systems and related systems landscape for UK higher education.

We discuss the report, the reasons for commissioning it, how it will inform the on going debate about the future of academic libraries, and how libraries could use it.

During the conversation we reference the following resources:

This conversation was recorded on Friday 9th May  and edited on a Mac with Garageband.

Rachel Bruce of JISC and Anne Bell of SCONUL join me in the latest Talking with Talis podcast to discuss the recently published JISC #38; SCONUL Library Management Systems Study - An Evaluation and horizon scan of the current library management systems and related systems landscape for UK higher education. We discuss the report, the reasons for commissioning it, how it will inform the on going debate about the future of academic libraries, and how libraries could use it. During the conversation we reference the following resources: JISC SCONUL JISC #38; SCONUL Library Management Systems Study [pdf] JISC Information Environment Libraries of the Future This conversation was recorded on Friday 9th May#160; and edited on a Mac with Garageband. Technorati Tags: JISC, SCONUL, Academic Libraries, Library Management Systems, LMS, ILS, Talking with Talis, Podcast.

by richard.wallis@talis.com at May 12, 2008 01:15 PM

Metalogger

neilgodfrey


Continuing here to share my “education in metadata” — and since I’m still discussing the early months, the post may be of interest to other peoples beginning their metadata journeys too . . . .

An easy MARC intro for a cataloguer into metadata

One good thing about having a library cataloguing background when it came to investigating repositories and seeing how they might be able to talk to each other, was knowing the blunter as well as some of the finer points of MARC. Some have argued that MARC is not really a metadata schema itself but a format for encoding metadata. And that’s one reason it works particularly well as a crosswalk for discrete bits of data from one schema to another.

Migration

I had cut my teeth with an EPrints repository, but when it finally osmosed into me that I had to mind my big P’s and my little p’s (learning that ePrints with a big P was a TM for a particular software package, and eprints with a little p was as often as not used as a generic term for electronic print collections, except when different users said that was only half true), it also became apparent that no institution could assume that once it chose a particular repository it would always have that particular brand of repository.

Currently the different configurations and software bases of repositories mean choosing one is like choosing a car: each make of car has some things one likes but not all, etcetera. And once one make and model is selected for one’s needs now, in a few years one’s circumstances are likely going to mean a different car would be more appropriate, or even necessary.

So given the current state of repository software, one needs to be sure that if one stores all one’s digital resources into one particular make of repository now, one will be able, with little effort or complication, transfer that data to another repository in the future.

I have since learned that some promoters of proprietary repositories promise their repositories will do this for clients, but it’s a topic that’s quickly glibbed over and a little digging shows the promise may not be all it seems. Yes, the data may all be put in a neat package and given back to the library when they cease to use a particular repository, but at least in one case I know it will be stripped of its configurations and be a complete mess. The soft boiled egg will be returned scrambled, leaving repository managers finding staff, workflows and money to reconstruct the original soft boiled egg.

So one has to expect that one’s institution will one day, or just might one day, want to migrate data from one repository to another. And MARC is one handy tool, an old well-known favourite of librarians, that is complex and versatile enough to carry out most migration tasks. By mapping data in a repository to MARC one can then map from that MARC record to the new data format of the new repository.

That is one solution. Librarians know what MARC is capable of conveying as discrete units of data. And thus how granular the migration process can be from one repository to another.

Moving beyond MARC

But there is more. The demands being placed upon repositories are leading them into data configurations that have no traditional counterpart in the normal library cataloguing of resources.

For example: it may be desirable, eventually obligatory, for a repository to differentiate preprints from postprints; articles submitted for publication, articles published, and articles written but not published or submitted; an author’s (different?) affiliations with different publications; whether a particular article or paper, as opposed to a journal or other collation, is peer-reviewed or not; and more.

MARC is good, it can and will continue to do most things. But it will not be able to do everything, at least not easily. One other possibility in certain circumstances is METS, a container for carrying a number of different schema-clumps of data. MARC cannot easily link multiple affiliations to respective authors. But the MODS schema can. And either a MODS schema and/or a MARC one can be carried by a METS package. But not all repositories will support the embedded structure carried by MODS. At least not yet. Plan for change.

But MARC is still going to be good for a while yet with a most vital day to day purpose of the repositories — Open Archive (OAI) Harvesting. That is, migrating the data that is essential for one’s resources being discovered on the internet.

Grappling with standards clashes and confusions over harvesting

Part of our repository evaluation process in RUBRIC was to compare their OAI harvesting functionalities. The easiest way to do this was to migrate data from one repository to another with MARC. Only a few data elements (title, author, date, subject etc) are used for OAI harvesting, and these are easily handled by MARC.

MARC was not the end product as it usually is in a catalogue record. For our repository purposes it was only the half-way house between data destinations. The final destination for harvesting is the Simple Dublin Core schema. Its elements are basic. Cataloguers used to MARC will first wonder how on earth such a blunt instrument can be useful for anything. But recall that library searchers do mostly search by title, author, subject, date, anyway. The more complex data is not lost. It can be kept in reserve (not in Simple Dublin Core but some other schema) till a particular resource is discovered. And then it can go into action and show its stuff as required.

This (OAI harvesting) was one of the hardest aspects of repository functions to come to terms with. Contradictions abounded. The Dublin Core standard insisted that the DC term “identifier” must only refer to the digital resource itself and not to the metadata record describing that resource. So why did EPrints use the DC term “identifier” to point to the metadata record instead? I sent off an email to EPrints to ask. They were as helpful as they could be, but we were all talking from different perspectives and not immediately understanding what each other knew/didn’t know/needed to know. I think I spoke to a technician who knew that by using “identifier” for the metadata page EPrints worked. Blank! when I tried to raise the DCMI stipulation. “Will look into it for next version.”

It was not easy for a newbie like myself to immediately discover that although OAI-PMH harvesting used the DC schema, this OAI protocol had to make its own rules in how to use that DC schema to make harvesting work. I asked harvesters for an explanation also. For some reason I interpreted their responses as something like an ad hoc “making do” with how things worked.

The problem was not with the DC schema. It was with the repository institutions. The institutions did not, from the pureness of their hearts, simply want users having direct access to their resources. Reputations, and the necessary finances and career advancements that reputations attracted, were part of the game. Users had to be directed first to the institution’s repository, with full professional header branding, as the gateway to the resources. The user needed to be taken first to the metadata page — where the branding decorating the details of the resource hit them in the eyes.

Repositories could not be sold in universities otherwise. So the OAI-PMH harvesting had to break the DCMI regulation for the use of the “identifier” element.

I wish I understood that from the very beginning! As it was, this basic piece of information only came to me when it came time for the RUBRIC tech team to test the nitty gritty of OAI harvesting with VTLS’s VITAL repository.

Next

There are several other issues that arise from the simplicity of the simple DC for harvesting, yet to be discussed.

But I can see a quite different set of issues relating to interoperability on the horizon. OAI-PMH and DC will still be basic tools, — especially if/when URI’s can be assigned to each piece of data, one for an author name, another for an affiliation, etc.

One can begin to see the importance of choosing a repository with an established and proficient support base, and to have a planning agenda to sustain whatever is chosen until the next choice has to be made, whether to upgrade or change platforms completely.

by neilgodfrey at May 12, 2008 12:16 PM

repositories for the rest of us

Monday 4M


lemonpoppyseed.JPG
Originally uploaded by laurasmart.
This week's muffin (vegan as always): Lemon poppyseed

This week's movies: Part 4 of Diane Hillman's Metadata Standards & Applications: Relationship Models

Talis' Rob Styles on Finding Relationships in MARC

by Laura (noreply@blogger.com) at May 12, 2008 07:11 AM

The FRBR Blog

Eadie, Towards an Application Profile for Images

Mick Eadie, Towards an Application Profile for Images, from Ariadne 55 (April 2008). A quote:

However, after much investigation and consultation, it was decided ultimately that FRBR did not address our requirements for the IAP [Images Application Profile]. In essence what is being done by FRBR is not the modelling of the simple image and its relationships, but rather an attempt to model the artistic / intellectual process and all resultant manifestations of it. We decided this was inappropriate for the IAP for number of reasons. While possible, an application profile of this complexity would require detailed explanation that could be a barrier to take-up. Moreover, it strays from the core remit of the IAP to facilitate a simple exchange of image data between repositories. While the FRBR approach attempts to build relationships between objects, e.g. slides, photographs, objects and digital surrogates, this facility already exists in, for example, the Visual Resources Association Core (VRA) schema. Our intention was not to reinvent or in any way replicate existing standards that are robust and heavyweight enough to deal with most image types. Rather our intention was to build a lightweight layer that could sit above these standards, and work with them, facilitating a simple image search across institutional repositories.

by William Denton (wtd@pobox.com) at May 12, 2008 03:11 AM

Lorcan Dempsey's weblog

Tagging at the network level

There is a fascinating entry by Seb Chan of the Powerhouse Museum in Sydney documenting experiences one month into their participation in the Commons on Flickr. The Powerhouse Museum has been alert to various ways of combining professional and audience metadata in its services. It was an early comer to the Commons, joining the Library of Congress.

Our experiment with the Commons on Flickr continues and barring a few hours delay we have managed to keep to our promise of 50 new images a week. We’re up to 400 images now with the most recent 50 going live this morning. 158 of these have been geotagged. [fresh + new(er) » Blog Archive » Commons on Flickr - one month later]

A couple of things struck me about his note. First, the volume of activity:

... our images have been viewed 39,685 times to yesterday. That’s more than an entire year on the old Tyrrell website (which, incidentally, has more images and is better indexed by Google) [fresh + new(er) » Blog Archive » Commons on Flickr - one month later]

And second, he talks about the volume and quality of tagging activity:

Tonnes of tags have been added and they have been of a quality that we’ve not experienced in our other tagging projects. I am firmly of the belief that the quality is a result of the Flickr environment (lets call it ‘culture’) and its userbase. [fresh + new(er) » Blog Archive » Commons on Flickr - one month later]

It will be interesting to see the promised three-month report. It seems to me that this shows the long-tail dynamic I have discussed elsewhere. A large part of the long tail effect is about better matching supply and demand by aggregating each in a network environment. Flickr aggregates supply: it provides a critical mass of pictures and community structure for sharing at the network level. It also aggregates demand by attracting large numbers of users, and creates value for them through its sharing structures. An individual institution has difficulty mobilizing this audience.

Related:

Dempsey, Lorcan. Libraries and the Long Tail: Some Thoughts about Libraries in a Network Age. D-Lib Magazine, April 2006, Volume 12 Number 4.

Quick Bookmarks: del.icio.us  Digg   Google  Reddit   Furl

May 12, 2008 12:47 AM

May 11, 2008

Terry's Worklog

MarcEdit update

Sorry I haven’t gotten this up — I’ll post it tonight.

–TR

by Administrator at May 11, 2008 06:57 PM

Geneseo Resource Sharing project

For the first time, in a really long time, I won’t be home on Mother’s Day.  A trip to Boston last week was extended to include some time in NY to talk to friends and the Geneseo library about the resource sharing project that they are working on.   I was really impressed by the work that had currently been done on this project.  Their work to integrate ILLIAD instances to work towards unmediated article sharing within their partners as well as their ability to generate workflow reports generating time spent on each part of the request and delivery process (seeing information about both the borrowing and lending institutions) was pretty cool.  At this point, this group is looking to expand their current work into a very ambitious open source project that could potentially help both their own consortia, but also provide an open tool that could be utilized by other Interlibrary Loan offices to deal with issues relating to publisher licensing guidelines, as they relate to lending digital articles.  If anyone happens to be working on something like that, they should contact Cyril Oberlander.  At this point, they are starting work on their next implementation of this project and are interested in knowing if anyone else is working a project like this.

 

–TR

by Administrator at May 11, 2008 06:56 PM

Lorcan Dempsey's weblog

Boxed in: a set of search boxes

Libraries have major challenges in developing their websites. Think just of the information resources they provide access to. There are locally managed resources: a catalog, a repository or two, informational pages, and so on. And there are many remote resources: licensed databases, links to web pages, and so on. And there are pages which try to pull these together: resources organized by subject or department, for example.

These resources may be different in scope (reference, discovery, full-text or other content, ...), in type of content, in terms and conditions, in specialization, and so on.

Abstracting up to that single - or small number of - search boxes that are presented as a goal is not straightforward. And indeed it is still common to see various searches/entry points offered: the catalog, metasearch, a list of databases, a search of the library website, ....

In this context I was interested to see Suzanne Chapman's "search box round-up".

She does a nice job of commenting on several approaches, and has a companion Flickr set of search box pics.

Incidentally, over time I reckon that 'single search' alternatives to 'metasearch' for general article access will emerge. By this I mean that services will consolidate article level metadata to facilitate access. This is not to say that there will not be target markets where niche databases continue to exist, rather that alternative solutions for general article searching seem inevitable. And of course, we are also seeing integrated search solutions for local resources emerge, Primo for example. In this way, the multiple resource challenge may get simpler, but will continue to exist in some form.

Related entries;

Quick Bookmarks: del.icio.us  Digg   Google  Reddit   Furl

May 11, 2008 04:29 AM

May 10, 2008

Bibliographic Wilderness

Tagging and motivation in library catalogs?


Eh, this comment was long enough I might as well post it here too, revised and expanded a bit. (I’ve been flagging on the blogging lately). Karen Schneider thinks about “tagging in a workflow context

Tagging in library catalogs hasn’t worked yet for a number of reasons…

Karen goes on to discuss much of the ‘when’ of tagging, but I still think the ‘why’ of tagging is more relevant. Why would a user spend their valuable time adding tags to books in your library catalog?

I think the vast majority of succesful tagging happens when users tag to aid their OWN workflow. Generally to keep track of things. You tag on delicious to keep track of your bookmarks. You tag on librarything to organize your collections. The most succesful tagging isn’t done to help _other_ people find things, but to keep track of things yourself–at least not at first, not the tagging that builds the successful tag ecology. Most cases of a successful tagging community where people do to tag to help others find things–I’d suggest it would be because it somehow benefits them personally to help people find things. Such as, maybe, tagging your blog posts on wordpress.com because you want others to find your blog posts–still a personal benefit.

A succesful tag ecology is generally built on tagging actions that serve very personal interests which do not need the succesful tagging ecology on top of it. Interests served even if you are the only one who is tagging. The succesful tagging ecology which builds out of it–and which goes on to provide collective benefit that was not the original intent of the taggers–is an epiphenomenon.

Amazon might be a notable exemption to this hypothesis, perhaps because it such a universally used service before tagging already. (Unlike our library catalogs).  I would be interested to understand what motivates users to tag in Amazon. Anyone know of anyone who’s looked into this? It’s also possible that if amazon’s tags are less useful, it is in fact because of this lack of personal benefit from tagging.

So what personal benefit can a user get in tagging in a library catalog? If we provided better ’saved records’ features, perhaps, keep tracks of books you’ve checked out, books you might want to check out, etc. But I’m not sure if our users actually USE our catalogs enough to find this useful, no matter how good a ’saved records’ feature we provide. In an academic setting, items from the catalog no longer neccesarily make up a majority of a user’s research space.

To me, that suggests, can we capture tags from somewhere else? My users export items to refworks. Does refworks allow tagging yet? If it did, is there a way to export (really re-import) these tags BACK to the catalog, when a user tags something? But even if so, it would be better if Refworks somehow magically aggregated tags from _different_ catalogs, of the same work. But that relies on identifier issues we haven’t solved yet. If our catalogs provide persistent URLs (which they don’t usually, which is a tragedy), users COULD tag in delicious if they wanted to. Is there a way to scan delicious for any tags including your catalogs url, and import those back in?

In addition to organizing one’s research and books/items of interest, are there other reasons it would serve a patron’s interest to tag, other things they could get out of it?  A professor might tag books of interest for their students, perhaps (not that most professors are looking for more technological things to spend time on helping students, but some are).   And librarians themselves might tag things with non-controlled-vocabulary topic areas they know would be of use to a particular class or program or department, with terms of use to those classes or programs or departments.  Can anyone think of any other reasons tagging could be of benefit to a user (not whether a successful tagging ecology would be of collective benefit–but benefits an individual user can get from assigning tags in a library catalog).

Worldcat covers a much larger share of my academic users’ research universe than my own catalog. And worldcat has solved the “aggregating different copies of this work from different libraries” problem to some extent. Which is why it would make so much sense for worldcat to offer a tagging service–which can be easily incorporated into your own local catalog for both assigning and displaying tags (if not for searching) ala library thing. It is astounding to me that OCLC hasn’t provided this yet. It seems to be a very ‘low hanging fruit’ (a tagging interface on worldcat.org with a good API is not rocket science) that is worth a try.

by jrochkind at May 10, 2008 11:04 PM

panlibus

CILIP Podcasts Syndicate Library 2.0 Gang

I was delighted to see that via the newly launched Podcasts area of the CILIP Communities site they are syndicating the Library 2.0 Gang.

The combined feed of podcasts that CILIP have launched, is a great service to CILIP members and a recognition that the traditional ways of learning and keeping up to date are being powerfully supplemented by blogs and podcasts.  I will be interested to see how this develops.

As the monthly round table listen for those that are interested in libraries and the technologies that influence them, I am eager to make it available to all that will benefit from the the insights and opinions from the librarians, vendors, journalists, and commentators that join the Gang.

To that end, whilst welcoming CILIP’s recognition of the Gang, I also invite others in different sectors and geographies that are interested in enriching their site by adding value for the visitors to it,  by syndicating the Library 2.0 Gang series, to drop me a line librarygang@talis.com.

I was delighted to see that via the newly launched Podcasts area of the CILIP Communities site they are syndicating the Library 2.0 Gang. The combined feed of podcasts that CILIP have launched, is a great service to CILIP members and a recognition that the traditional ways of learning and keeping up to date are being powerfully supplemented by blogs and podcasts.#160; I will be interested to see how this develops. As the monthly round table listen for those that are interested in libraries and the technologies that influence them, I am eager to make it available to all that will benefit from the the insights and opinions from the librarians, vendors, journalists, and commentators that join the Gang. To that end, whilst welcoming CILIP's recognition of the Gang, I also invite others in different sectors and geographies that are interested in enriching their site by adding value for the visitors to it,#160; by syndicating the Library 2.0 Gang series, to drop me a line librarygang@talis.com. Technorati Tags: CILIP, Podcasts, Library 2.0 Gang, Talis, Library

by richard.wallis@talis.com at May 10, 2008 08:03 AM

Metalogger

neilgodfrey


I did not come into RUBRIC cold. I was involved in the planning stages of the implementation of an EPrints repository, and then as a cataloguer I was the one responsible for testing how the data entries and outputs worked.

The point was to understand how and where the repository data stood in relation to the rest of the library’s resources, and in relation to the needs and interests of the various university departments and academics who would be using the repository.

We began low-key. Not with award winning research papers or datasets embedded with configurations for their re-use. Rather, it was decided to make our first entries in the repository all the fourth year engineering projects. New students wanted to consult these, and lecturers encouraged the study of them. We would soon learn that once in the repository they would acquire a sizable audience beyond our university, too.

But low-key soon made its voice heard loudly if not immediately very clearly. It was a low key beginning in one respect, but to make it all work I quickly found myself visiting the head and other academics in the engineering department in order to confidently assess the metadata requirements for this sort of resource material. Dewey, USMARC, AACR2, the LOC and OCLC sites all left me high and dry with some of my the metadata needs for this new type of database.

On the technical side, some of the files accompanying some the projects were simply too big or formatted in a way that would not fit in the repository, let alone be viewable to users. Some files were uselessly battened down with password-only access. Some MSWord documents that we wanted to convert to PDF contained formatting that made that process extremely difficult and time-consuming. Most of these issues were solvable or postponable at that stage.

But on the metadata side, academics used a standard research classification code to classify their works. But when I looked into that code (the RFCD component of ASRC) it emerged that this research classification served a different purpose from the descriptive subject classifications such as LCSH. It was not a descriptive discovery classification scheme at all, but a classification scheme for grants and policy reviews. Yet it was the schema known among and used by academic institutions. For starters, there were too many “XYZ not elsewhere classified” entries in it to be of real use as a true subject finding aid.

It appeared from a library cataloguer’s perspective that with our repository we were trying to make a square peg fit into a round hole.

I was yet to learn that the repository was not going to be simply a quantitative extension of traditional library resource services. The repository was not just an enhancement of our services. It was going to be something quite qualitatively different, heading in a direction hitherto alien to libraries, and we needed to start thinking of ways traditional library services themselves could start working with it.

The outcomes from a metadata perspective of this exploratory testing were three documents in particular. The first was a manual of best practice for metadata entry procedures for our EPrints 2.(X) repository. Not just a do/don’t list, but a guideline that explained rationales so that the principles could be applied with a bit of thought and understanding for whoever was to do the data entry, and to know how to work through the inevitable curly questions that come along with data entry.

But that was the easy bit. Much of the fun and frustration of this exploratory work was trying to figure out how to handle all the exceptions to the rules.

Did the exceptions matter? Was it important to standardize repository and library catalogue data? If there was no immediate need, what of the future? What function(s) did each bit of data serve and to what extent could the software take care of our needs, and to what extent were data entry guidelines required?

To help work through these questions I compiled a list of all the potential metadata issues, from the big and fat to the nit-picky or even possibly illusory. This was constructed in 3 columns. The first was a description of each issue. The second was a comparison of that issue with what was understood from normal library practice. And the third was for comments on what the real or imaginary implications might be in the longterm for each “issue”.

This helped focus and prioritize the issues, and eventually I produced a more formal thesaurus of metadata exceptions for USQ’s Eprints repository.

The attempted goal in compiling those documents was to sift through known and true library standards and best practices and to see how these could be applied, if at all, to repository metadata. And where no normal library data standards did apply then to try to assess what a standard or best practice should look like. This sometimes meant attempting to extrapolate from a rule in cataloguing and seeing if it could or should be justified in the repository context.

I have no doubt that given what I have learned since I would change some, possibly much, of what I wrote in those documents. But one has to start somewhere.

I was still very green when it came to broader issues such as OAI harvesting. And we were only working at this stage with pdf documents.

But will elaborate in future meta-reflections . . . . .

by neilgodfrey at May 10, 2008 01:04 AM

May 09, 2008

Catalogablog

Metadata for Learning Resources

Metadata for Learning Resources: An Update on Standards Activity for 2008 by Sarah Currier appears in the latest issue of Ariadne.
The major areas of development covered in this article are:
  1. LOM Next: plans for the next version of the IEEE LOM
  2. The Joint DCMI/IEEE LTSC (Learning Technology Standards Committee) Taskforce: bringing together the two major metadata standards used for learning resources, and providing an RDF translation for the LOM
  3. DC-Education Application Profile (DC-Ed AP): a modular application profile purely looking at educational aspects of resources, based on community requirements
  4. The United Kingdom’s Joint Information Systems Committee Learning Materials Application Profile (JISC LMAP) scoping study: working alongside a number of similar projects looking at application profiles for repositories in other areas, e.g. images.
  5. International Standards Organisation Metadata for Learning Resources (ISO MLR): based primarily in Canada, this international standards body is devising a new international standard for educational metadata, in response to perceived limitations of the IEEE LOM
  6. The European Commission’s PROLEARN Harmonisation of Metadata project: a study into the issues and challenges of achieving harmonisation in metadata, given the heterogeneous landscape

by noreply@blogger.com (David) at May 09, 2008 05:20 PM

Metalogger

neilgodfrey


Before I start my next job I’ve decided it’s time to look back on the things I’ve learned, where I’ve succeeded and where I did not (and why), in working as a “metadata specialist” for two years and 2 months with RUBRIC, and before that working in various capacities (mostly as a cataloguer/editor) with an EPrints repository.

RUBRIC was a project funded by a national government department to assist university libraries to implement repositories. The acronym stands for Regional Universities Building Repository Infrastructure Collaboratively.

There was a “RUBRIC Central”, consisting of a technical team, a planning and PR person, and project manager and myself, the metadata specialist, and this Central team worked as per the acronym collaboratively with repository managers in different universities. How this worked can be seen in a PowerPoint presentation by Kate Watson and Vicki Picasso, both involved repository managers, titled The RUBRIC Project: the benefits of collaboration through partnerships. This is linked on the IDEA 2006 page.

So my introduction into the nitty gritty of metadata and repositories with RUBRIC was in the context of working with several universities, each with different library practices, priorities and infrastructure, most of whom did not yet have repositories. The requirement was to help each get started with a “first generation” repository. The couple that did have repositories were still in their neophyte stages and welcoming of professional assistance to help establish themselves on the right footing.

The first step was to evaluate different repository systems so each university could better assess the one most suited to their situation. We investigated DSpace, VTLS’s VITAL and the University of Queensland’s Fez (two Fedora based repositories), and I also had had experience with EPrints.

This evaluation meant working closely with the technical team of programmers. This involvement consisted of weekly meetings where goals and needs were raised and assessed, and sitting beside them in the same workroom so we could regularly talk the issues through together.

It also, most importantly, meant regular communication and prioritization and troubleshooting through TRAC, wikis and teleconferences.

So the technical skills of the programmers was combined with my library cataloguing skills and understanding of library terminology needs.

So I was put in a rare and enviable position of being able to begin studying metadata issues in the context of:

  1. a variety of repository systems
  2. different universities with different needs and resources
  3. close daily liaison with computer technicians and regular liaison with project partners
  4. and a well resourced and coordinated team and collaborative partnership that kept us all focussed on the issues

Unfortunately the weather can change and towards the end of the project some of the above started to fade, and in hindsight I can see where I could have been more alert to have worked to compensate or correct that, and how I could have improved on some of what I attempted, but that’s hindsight. I’ll discuss that side of it when the time comes for that particular meta-reflection.

It was a great start. I needed to understand metadata not just for one institution, but for eight universities, and how metadata would or could work in four different repository systems, with a marriage of technical and metadata specialists.

Subsequent discussions with more experienced repository managers who were not part of the RUBRIC project began to help me understand just how well positioned I was to help new repository managers avoid certain pitfalls and risks — and to help me acquire an expanding awareness of what future needs would be and the broader environment our partners would be entering.

Next post will begin to discuss the first metadata specifics that needed exploration and solutions.

by neilgodfrey at May 09, 2008 01:41 PM

Cataloging Futures

Martha Yee's new article - cataloging et al.

Martha Yee has a new article available at the UC eScholarship repository, Cataloging, Compared to Descriptive Bibliography, Abstracting and Indexing Services and Metadata.

Cataloging is compared to descriptive bibliography, to enumerative bibliography and abstracting and indexing services as well as to metadata created by Web search engines or by nonprofessionals at sites such as Amazon.com. These four types of metadata are compared with regard to object of the description, functions, scope, number of copies examined, collective vs. individual creation, standardization, authority control, evidence, amount of descriptive detail, degression, time span the data is intended to last, and degree of evaluation.

by Christine Schwartz at May 09, 2008 11:11 AM

JSC April meeting outcomes now available

Important reading for keeping up with the development of the new cataloging content standard, Resource Description and Access (RDA):

The Joint Steering Committee for the Development of RDA (JSC) has just issued outcomes from their most recent meeting. The meeting was held in Chicago in April 2008.

by Christine Schwartz at May 09, 2008 10:49 AM

New book: Radical Cataloging: Essays at the Front

I've been waiting for this one. Radical Cataloging: Essays at the Front edited by K.R. Roberto is now available in paperback.

This collection of critical and scholarly essays addresses the state of cataloging in the world of librarianship. The contributors, including Sanford Berman, Thomas Mann, and numerous front-line library workers, address topics ranging from criticisms of the state of the profession and traditional Library of Congress cataloging to methods of making cataloging more inclusive and helpful to library users. Other essay topics include historical overviews of cataloging practices and the literature they generate, first-person discussions of library workers' experiences with cataloging or metadata work, and the implications behind what materials get cataloged, who catalogs them, and how. Several essays provide a critical overview of innovative cataloging practices and the ways that such practices have been successfully integrated in many of the nation's leading libraries.

by Christine Schwartz at May 09, 2008 10:40 AM

The Serials Cataloger

"Catalog/Cataloging Changes and Web 2.0 Functionality: New Directions for Serials" by Rebecca Kemp

Kemp discusses the organization and presentation of serials data in library catalogs with a particular interest in the relationships between serials. Included is a brief discussion of the application of FRBR concepts to serials and how these concepts along with the use of identifiers (some yet to be created) and superwork records (to fully outline the history of a serial title) could provide a useful framework for the organization of serials data. She also calls for the simplification of cataloging rules, looking to RDA for flexibility for future cataloging needs and citing the CONSER standard record as an improvement currently underway. Outsourcing is another means she cites to simplify the cataloging process. She argues that simpler records have the dual advantage of being more understandable for users and more efficient to create. Another aspect she considers in catalog design, specifically the implementation of web 2.0 functionality. She briefly addresses mash-ups, user-created metadata (a.k.a. tagging), user reviews, and personalization through recommender services as ways of bringing web 2.0 into library catalogs. She also touches on improvements in search technology such as relevance ranking, metasearching, natural language searching, faceted searching, and clustering. How can these advances help users searching for serials titles or articles? Kemp outlines five scenarios for locating known and unknown items, including mock-ups of catalog results screens. Overall, Kemp attempts to cover a lot of ground in this article and as a result does not provide comprehensive coverage on any of the topics included.

Kemp's article can be found in The Serials Librarian, vol. 53, no. 4 (2008), pages 91-112.


by Lori (noreply@blogger.com) at May 09, 2008 09:55 AM

“Excessive Successive: Time for a Radical Change” by Wendy Baia

Wendy Baia makes an impassioned plea for a return to latest entry cataloging in her article, “Excessive Successive: Time for a Radical Change.” She first provides a brief history documenting her own experiences over a 40-year career with both latest entry and successive entry cataloging. She then uses the example of Organic Gardening to illustrate the differences between what successive entry looks like compared to latest entry cataloging. (She makes a technical error in suggesting that the OG record covering the years 2001-2003 should be marked for deletion—that title change happened prior to the Dec. 2002 implementation of major and minor title changes and so was correct at the time it was cataloged.) [Note: She presents her evidence as 6 records in successive cataloging versus only 1 with latest entry. However successive record #6 was input incorrectly, leaving 5 successive records, and if all those changes had occured after the Dec. 2002 minor title change rules were implemented, there would be only 2 successive entry records.]

The real meat of the article comes in the section, “What’s Wrong with Latest Entry Cataloging?” where Baia presents 13 criticisms of latest entry cataloging and her responses to them. She mentions FRBR, although in my opinion dismisses FRBRized displays as a solution too easily. She also argues that “using one record to represent one serial fulfills the FRBR goal to promote users’ ability to find, identify, select, and obtain resources.” However, I would argue that data elements within records are far more vital to achieving those user tasks than simply the number of records that exist. (See Table 6.3 on pages 93-95 of Functional Requirements for Bibliographic Records.) Even though she hasn’t quite convinced me, overall the article is thought-provoking and well-worth reading as she presents both user-focused reasons for, as well as possible workflow advantages to latest entry cataloging.

You'll find Baia's article in the Serials Librarian, vol. 53, no. 1/2 (2007), pages 57-80.

by Lori (noreply@blogger.com) at May 09, 2008 09:51 AM

“Latest Entry Legacies: Confessions of a Guerrilla Cataloger” by Kevin M. Randall

Kevin Randall looks at the history of serials cataloging practices at Northwestern University, which used latest entry cataloging from the mid-1980s through the mid-1990s ignoring the standard of successive entry cataloging. He discusses some of the problems encountered in using latest entry in addition to its advantages. From the cataloging perspective, he mentions that quick copy-cataloging of successive entry records is often easier than local maintenance with latest entry cataloging. Randall's evaluation of latest entry versus successive entry is more balanced than in the Baia article. He also gives more credit to the potential of FRBR stating,
“If any ideal solution is to be found, it is in more sophisticated OPAC development to utilize data encoded in the MARC records." He goes on to say that it does not matter to the user if one record or several are used, what is important is the display of the data. Randall concludes that successive entry is “our only real hope” in the current environment.

You'll find Randall's article in the Serials Librarian, vol. 53, no. 1/2 (2007), pages 81-91.

by Lori (noreply@blogger.com) at May 09, 2008 09:50 AM

“How Successive Entry Cataloging Stacks Up in Today’s World” by Mary Grenci

Grenci adds another assessment to the successive entry versus latest entry debate. She considers arguments about which method is most practical and efficient for catalogers, noting the difficulties in researching a serial’s history in latest entry cataloging and the time spent creating or editing new records under successive entry. She concludes that both methods require time and effort to determine “what’s going on” on the part of a cataloger. She then considers the user perspective. She provides a rebuttal to the argument that latest entry is best for users, pointing out that most users don’t care about a serial’s history--they simply want to find the title that matches their citation! On the other hand, long browse displays or receiving a large number of hits can be confusing. Latest entry records may result in false hits if portions of the serial run are not owned. Like Randall, she looks to improved catalog displays as the solution to serials confusion. She cites the issuance of the FRBR report as an important step forward and briefly mentions the concept of the “superwork.” While acknowledging arguments on either side, Grenci ultimately advocates for a combination of successive entry cataloging and improved library catalogs as the best option for the future.

Grenci's article can be found in the Serials Librarian, vol. 53, no. 1/2 (2007), pages 93-98.

by Lori (noreply@blogger.com) at May 09, 2008 09:49 AM

“Building Connections: A Review of the Serials Literature 2004 through 2005” by Cecilia Genereux

Genereux covers three major aspects of serials trends in her literature review for 2004-2005: cost, management, and access. Serials catalogers will be particularly interested in her coverage of access issues. Specific topics addressed include: FRBR and serials; new rules for major and minor title changes; aggregator-neutral records for online serials; changing roles and responsibilities of serials catalogers brought on by the proliferation of e-journals; cataloging of new types of continuing resources such as zines, e-zines, and blogs; and serials holdings records. As with any literature review, readers will want to consult the original works to learn more about the topics.

Genereux’s article can be found in Library Resources & Technical Services, vol. 51, no. 4 (Oct. 2007), pages 293-304.

by Lori (noreply@blogger.com) at May 09, 2008 09:49 AM

"Single, Separate, or Something in Between: Results of a Survey on Representing Electronic Serials in the Catalog" by Abigail C. Bordeaux

Volume 7, Issue 3/4 (2007) of the Journal of Internet Cataloging includes Bordeaux's article on the single vs. separate record debate concerning the cataloging of electronic serials. I first discovered this article as a pre-print a couple months ago while doing research on the topic. While a number of articles already address the debate, Bordeaux's article provides a fresh perspective by using a survey to find out what libraries are doing in the real world. While her survey showed no clear preference in practice, those using separate records were more likely to have the majority (76-100%) of their electronic serials represented in the online library catalog. Also notable is the similar perception of patron satisfaction between libraries using the single record approach versus the separate record approach.

by Lori (noreply@blogger.com) at May 09, 2008 09:48 AM

“Confessions of a Correspondent from the Choice-of-Entry War: Review of Responses to a Set of Informal Opinion Surveys” by Andrew D. Shroyer

Shroyer’s article is the fourth in a quartet on the latest entry versus successive entry debate. He surveyed both catalogers and public services librarians, using separate survey instruments for each group, in his exploration of the topic. Both raw data and evaluative summaries of his survey findings are provided in the article. Both groups leaned more towards latest entry cataloging leading him to conclude, “a fresh exploration of the rules governing choice of entry, in terms of both principles and practicalities, would be timely and could be productive.”

Shroyer’s article can be found in the Serials Librarian, vol. 53, no. 1/2 (2007), pages 99-123.

by Lori (noreply@blogger.com) at May 09, 2008 09:48 AM

Fred 2.0

Should such a thing exist

“Data organization.” “Human Information  Organizing Behavior.” “Knowledge Organization Systems.”  What would characterize a “Wisdom Organization  System?”   

by ses at May 09, 2008 08:45 AM

Terry's Worklog

Quick MarcEdit FYI

I’ll be posting an update this weekend that includes an updated bootloader to deal with a problem identified when installing on Vista 64-bit, as well as including enhancements to the Z39.50 Extended Services support and the OAI Harvester (making it more fault tolerant).

Also, I reharvested the UMich. Google Books records and will be posting the set (for those interested in a testing set, etc) this weekend as well, likely Friday night as I’ll be spending a good deal of time tomorrow on the road.

–TR

by Administrator at May 09, 2008 02:38 AM

May 08, 2008

Fred 2.0

Repo-Rat

Self Archiving has failed. Stealth Archiving is the answer.

An ordinary person spends there time getting out avoiding tense situations. A repo-rat spends his time getting in to tense situations.

Never broke into an office. Never wire-tapped an office. Kid. I never broke into a laptop. I shall not corrupt a file northe contents thereof. Nor through inaction let that file or the digital contents thereof come to harm. That’s what I call the repo code kid. Don’t forget it etch it in your brain. Not many people got a code to live by anymore.

(nodding to Wisconsin)

by ses at May 08, 2008 10:17 PM

Cataloging Futures

Letter from Deanna Marcum on RDA

A letter from Deanna Marcum was just posted to the AUTOCAT list. It provides the joint statement of the Library of Congress, the National Library of Medicine, and the National Agricultural Library on Resource Description and Access. Some excerpts:

The three national libraries agreed on the following approach: First, we jointly commit to further development and completion of RDA. Second, following its completion, a decision to implement the rules will be based upon the positive evaluation of RDA's utility within the library and information environment, and criteria reflecting the technical, operational, and financial implications of the new code. This will include an articulation of the business case for RDA, including benefits to libraries and end users and cost analyses for retraining staff and re-engineering cataloging processes.

Together, we will:

  • Jointly develop milestones for evaluating how we will implement RDA
  • Conduct tests of RDA that determine if each milestone has been reached; paying particular attention to the benefits and costs of implementation
  • Widely distribute analyses of benefits and costs for review by the U.S. library community
  • Consult with the vendor and bibliographic utility communities to address their concerns about RDA

Included among the tests that will be developed to assist in formulating implementation decisions:

  • Usability testing with cataloging staff, i.e. librarians and technicians, experienced and newer staff from the three national libraries in consultation with representatives from the U.S. library community (including OCLC and library vendors) about its participation in the process
  • Testing of records for a broad array of materials created during usability studies to determine compatibility with existing record sets and ensuring records are usable and understandable for our end users
  • Testing the feasibility of integrating this new cataloging standard into all relevant technology systems

The three institutions agreed that these steps will be followed and, if there is a decision to implement RDA, that the implementation would not occur before the end of 2009.

UPDATE: Letter and joint statement [pdf] now available on the LC Working Group website.

by Christine Schwartz at May 08, 2008 04:41 PM

Bibliographic Wilderness