>
> Interested to hear if there's a 4th, best option.
>
I don't know about the broader issue - looking forward to that discussion!
But in this example at least, it seems wrong to be using names as the
identifier at all, because names aren't unique. What happens when you need
a URI for another
es catalogers that I (or my programs) am
responsible for all those edits they don't remember making
If "459" really is your cataloging location (parameter 4), then you're
missing the HoldLocationID (parameter 6), which should be the numerical id
corresponding to what's in your 852 $b.
for matching incoming records to the
database. Or, export the database and compare it with the files, as above.
Andy Kohler / UCLA Library Info Tech
akoh...@library.ucla.edu / 310 206-8312
On Thu, Aug 15, 2013 at 10:11 AM, Michael Beccaria mbecca...@paulsmiths.edu
wrote:
Has anyone had any luck
I agree with Terry: use a database. Since you're doing multiple queries,
invest the time up front to import your data in a queryable format, with
indexes, instead of repeatedly building comparison files.
But of course, it depends... dealing with large amounts of data efficiently
is often best
I don't know about ISO 2709 itself, but the MARC21 implementation of
it refers to octets, aka 8-bit bytes:
http://www.loc.gov/marc/specifications/specrecstruc.html
Characters may be encoded using one or more than one octet, depending
on the character set. All ASCII characters are encoded using
If your library's machines all have www.library.yale,edu as their home
page are you assuming that users actually click links to leave
that home page? User sits at library machine, user sees library home
page, user types url for gmail or youtube or facebook,,, does GA track
those actions?
On
I've found this useful at times:
http://www.itsmarc.com/crs/bib1468.htm
It's apparently not maintained, but lists more fields as obsolete
than the selected ones on the LC list - probably best to use both
together.
--Andy
On Wed, Jan 27, 2010 at 12:23 PM, Jonathan Rochkind rochk...@jhu.edu
Posted to Code4Lib for our HR department; please contact them with questions.
The UCLA Library has initiated recruitment for the Head of Library
Information Technology (Computer Resource Manager III)
The complete posting, which includes the position description,
complete qualifications and
