Hi Daniel,

I posted our efforts along these lines yesterday.  It was buried in one of my typically long posts, so I'll repeat that section here:

url  (for fulltext)
We wanted to split the urls for full text from other urls for a resource (e.g. urls for table of contents).   We achieved this with a combination of the 2nd indicator value in an 856 and some string matching.

I am happy to share the code, the test code, and the test data I created.  It was implemented for the solrmarc import.  

We don't have our holdings info yet, but we'll want to get URLs from there as well, if we have them.

If you go further with this work, I'd be very interested in your code.

- Naomi

On Jul 31, 2008, at 10:27 AM, Lovins, Daniel wrote:

Has anyone tried to exploit the MARC21 856 tag subfield $3 ("Material specified") or $z ("Public note") in order to identify what type of URL is embedded there (cf.http://www.loc.gov/marc/856guide.html)? It seems these subfields are ignored in VuFind, and the link text is always: "Get full text", i.e., even if its only pointing to a table-of-contents, finding aid, publisher's web site, etc.. For example, in the following list view excerpt, both records say "Get full text" when in fact they are referring to microfilm guides.
By contrast, here's what the code generates in WebVoyage:
Here the underlying MARC of the second record
I'd be interested in collaborating on a solution (if there isn't one out there already).
Also-- has anyone tried to reveal within VuFind URLs that are derived from MARC *holdings* records? We at Yale sometimes use this technique for, say, a digitized rare book that serves as an "added copy" as it were, to the original artifact.
Thanks for your help.
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
VuFind-General mailing list

Naomi Dushay