Re: [CODE4LIB] date fields

[Karen Miller]

And don't forgot to check the MARC 264$c as well. That's the field that we use 
with RDA and you'll find it in newer records.

Karen

Karen D. Miller
Monographic Cataloger/Metadata Specialist
Northwestern University Libraries
Northwestern University
1970 Campus Drive
Evanston, IL 60208
www.library.northwestern.edu
k-mill...@northwestern.edu
874.467.3462


-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Trail, 
Nate
Sent: Monday, July 11, 2016 2:24 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] date fields

Don't forget that it might be duplicative of the 260 but the 008 has "machine 
readable" date info that may be less specific than the 260 but more uniformly 
entered (or that's the only place there is a date associated with 
publication/release).
Nate

==
Nate Trail
LS/ABA/NDMSO
Library of Congress
n...@loc.gov



-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Joy 
Nelson
Sent: Monday, July 11, 2016 3:19 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] date fields

Hi Eric-
Are you planning on storing the 'normalized' dates for ever in the MARC?
i.e. leave the c1900 in the 260$c and have 1900 in another place?

I think what you do depends on your ILS and tools.  My first reaction would be 
to stash the date in an unused subfield in the 260.  If your system allows you 
to add 'non standard' subfields, you could use 260$z to stash it.

But, then I start to think that might rankle some catalogers to have 'non 
standard' date data in the 260 (or 264).  I would probably then look at using 
one of the local use tags.  901-907, 910, or 945-949.  You could be the date in 
$a and even a brief description in a second subfield.
901$a1900$bnormalized date for project XYZ -initials/date

-Joy

On Mon, Jul 11, 2016 at 12:51 PM, Eric Lease Morgan  wrote:

> I’m looking for date fields.
>
> Or more specifically, I have been given a pile o’ MARC records, and I 
> will be extracting for analysis the values of dates from MARC 260$c.
> From the resulting set of values — which will include all sorts of 
> string values ([1900], c1900, 190?, 19—, 1900, etc.) — I plan to 
> normalize things to integers like 1900. I then want to save/store 
> these normalized values back to my local set of MARC records. I will 
> then re-read the data to create things like timelines, to answer 
> questions like “How old is old?”, or to “simply” look for trends in the data.
>
> What field would y’all suggest I use to store my normalized date content?
>
> —
> Eric Morgan
>



--
Joy Nelson
Director of Migrations

ByWater Solutions 
 Support and Consulting for Open Source Software
Office: Fort Worth, TX
Phone/Fax (888)900-8944
What is Koha? 

Re: [CODE4LIB] Representing geographic hiearchy in linked data

[Karen Miller]

Ethan, have you considered Getty's Thesaurus of Geographic Names?  It does 
provide a geographic hierarchy, although the data for Athens they provide isn't 
quite the one you've described: 

http://www.getty.edu/vow/TGNHierarchy?find=athensplace=nation=prev_page=1english=Ysubjectid=7001393

This vocabulary is available in XML here:

http://www.getty.edu/research/tools/vocabularies/obtain/index.html

I have looked at it but not used it; it's a big tangled mess of XML.

MODS mimics a hierarchy (the subject/hierarchicalGeographic element has these 
children: continent, country, province, region, state, territory, county, city, 
island, area, extraterrestrialArea, citySection). The VRA Core location element 
provides a similar mapping.

I try to stay away from Dublin Core, but I did venture onto the DC Terms page 
just now and saw TGN listed in the vocabulary encoding schemes there, so 
probably someone has implemented it.

Karen


Karen D. Miller
Monographic/Digital Projects Cataloger
Bibliographic Services Dept.
Northwestern University Library
Evanston, IL 
k-mill...@northwestern.edu
847-467-3462




-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Ethan 
Gruber
Sent: Thursday, April 05, 2012 12:49 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: [CODE4LIB] Representing geographic hiearchy in linked data

Hi all,

I have a dilemma that needs to be sorted out.  I'm looking for an ontology that 
can describe geographic hierarchy, and hopefully someone on the list has 
experience with this.  For example, if I have an RDF record that describes 
Athens, I want to point Athens to Attica, and Attica to Greece, and so on.  The 
current proposal is to use dcterms:partOf, but the problem with this is that 
our records will also use dcterms:partOf to describe a completely different 
type of relational concept, and it will be almost impossible for scripts to 
recognize the difference between these two uses of the same DC term.

Thanks,
Ethan

[CODE4LIB] Northwestern University Library Librarian Vacancy Announcement

[Karen Miller]

Northwestern University Library
Librarian Vacancy Announcement

Northwestern University Library invites nominations and applications for the 
position of Assistant Head of the Digital Collections Department, which is a 
unit of the library organization that advances the University's teaching and 
research mission by providing digitization services and support to Northwestern 
faculty and graduate students.  The assistant head is responsible for 
conceptual development and execution of digital library projects and related 
services. The assistant head supervises staff engaged in digital conversion and 
digital project management and assists with implementation of digital archiving 
and curation services. For more information about this position, go to 
http://www.library.northwestern.edu/about/library-administration/jobs.  

QUALIFICATIONS INCLUDE:  Masters degree from an ALA accredited program in 
library and information science or equivalent combination of education and 
relevant library experience.  At least 3 years of experience working in an 
academic library setting, specializing in digital libraries, information 
services, repository services, or a related area. Supervisory experience and 
project management experience. Excellent interpersonal, communication, and 
collaboration skills. 

TO APPLY:  Send letter of application, resume or vita, and names of three 
references to the attention of Roxanne Sellberg, Associate University Librarian 
for Administrative Services, electronically to library-personnel at 
northwestern.edu. Applications received by October 30, 2011 will receive first 
consideration. Northwestern University is an equal opportunity/affirmative 
action employer. Employment eligibility verification required upon hire.


Karen D. Miller
Monographic/Digital Projects Cataloger
Bibliographic Services Dept.
Northwestern University Library
Evanston, IL 
k-miller3 at northwestern.edu
847-467-3462

Re: [CODE4LIB] LCSH and Linked Data

[Karen Miller]

OK, as a cataloger who has been confused by the jurisdictional/place name
distinction, I'm going to jump in here. 

Whether England means the free-floating geographic entity or the country
is not quite unknowable -- it depends on the MARC codes that accompany it. 

The brief answer is this: a field used in a 651$a or a $z should match a 151
in the LC authorities.

If the MARC field is 151 or 651 (let's just say x51), then the $a should
match a 151 in the authority file.
MARC subfield z ($z) is always a geographic subdivision and should match a
151.

Here's where it gets tricky: 
If the MARC field is a x10 (110, 610, 710 – corporate bodies), then the $a
should match a 110 or a 151 in the authority file. If the first indicator of
such a MARC field is a 1, then it will probably match a 151 – first
indicator 1 means that a heading is jurisdictional and may match a 151.

For  example:

110 1_ United States. ‡b Dept. of Agriculture

There is a 

151 United States 

in the LC authorities, but no 

110 United States

yet it can be used as a corporate body name in a bib. record with a 110
field. 

This is further confused by the VIAF, in which some national libraries have
established the United States as a corporate body (110).

At the risk of confusing things, I'd suggest looking at countries like the
United States, Kenya or Canada as examples. England is not a great example
because it's not a current jurisdiction name - there is a note in the LC
authority record that reads Heading for England valid as a jurisdiction
before 1536 only. Use (England) as qualifier for places (23.4D) and for
nongovernment bodies (24.4C2). It is established as a 110 because it *used
to be* a jurisdiction name and would be valid for works issued by the
government prior to 1536. Obviously this note is of no use to a machine, but
it explains why we aren't seeing it used as a jurisdiction (a corporate
body) with subordinate bodies.

I hope I'm not pointing out the obvious, but the use of names that appear in
151 fields in the authority file as 110 fields in bibliographic records
confused me for a very long time; our authorities librarian explained it to
me at least twice before the proverbial light bulb went on for me. 

Karen

Karen D. Miller
Monographic/Digital Projects Cataloger
Bibliographic Services Dept.
Northwestern University Library
Evanston, IL 
k-mill...@northwestern.edu
847-467-3462


-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Bill
Dueber
Sent: Friday, April 08, 2011 1:40 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] LCSH and Linked Data

On Fri, Apr 8, 2011 at 1:50 PM, Shirley Lincicum shirley.linci...@gmail.com
 wrote:

 Ross is essentially correct. Education is an authorized subject term
 that can be subdivided geographically. Finance is a free-floating
 subdivision that is authorized for use under subject terms that
 conform to parameters given in the scope notes in its authority record
 (680 fields), but it cannot be subdivided geographically. England is
 an authorized geographic subject term that can be added to any heading
 that can be subdivided geographically.


Wait, so is it possible to know if England means the free-floating
geographic entity or the country? Or is that just plain unknowable.

Suddenly, my mouth is hungering for something gun-flavored.

I know OCLC did some work trying to dis-integrate different types of terms
with the FAST stuff, but it's not clear to me how I can leverage that (or
anything else) to make LCSH at all useful as a search target or (even
better) facet.  Has anyone done anything with it?