MAPS-L Archives

Maps-L: Map Librarians, etc.

MAPS-L@LISTSERV.UGA.EDU

Options: Use Forum View

Use Monospaced Font
Show HTML Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Paige G. Andrew" <[log in to unmask]>
Reply To:
Maps-L: Map Librarians, etc.
Date:
Tue, 6 Jan 2015 15:37:40 -0500
Content-Type:
multipart/alternative
Parts/Attachments:
text/plain (3024 bytes) , text/html (9 kB)
Rick, 

I haven't used the 006 field in a long time, so I had to go look up which types of data can appear in this field for cartographic resources, and you are correct that there is a position for projection code. Now...if one were to use your proposed technique I don't know if it would be helpful or not. In particular, how would one know that the code in the Proj: fixed field matched one of the maps and then the one in the 006 matched the other one? Ken? 

Paige 

----- Original Message -----

From: "Rick Grapes" <[log in to unmask]> 
To: [log in to unmask] 
Sent: Monday, January 5, 2015 4:05:32 PM 
Subject: Re: Cataloging quesiton, fixed field 



Paige and everyone else, 



I’ve been away for Christmas and so this question may have been answered already. That said, could the addition of a 2 nd 006 field which will include the projection code of the 2 nd map, potentially solve this problem, or am I totally off base here? Granted the 2 nd 006 won’t match the fixed fields, but some future computer system may be able to take advantage of the added coding, much like people now take advantage of extra 255 fields. Are there issues with inserting two 006’s that I’m not seeing? 



Thanks, 

Rick Grapes 

BYU Map Collection 




From: Maps-L: Discussion Forum for Maps, Air Photo, Map Librarianship, GIS, etc. [mailto:[log in to unmask]] On Behalf Of Paige G. Andrew 
Sent: Thursday, December 18, 2014 11:21 AM 
To: [log in to unmask] 
Subject: Re: Cataloging quesiton, fixed field 





This sounds like a new situation I've never run into myself Ken. I don't think you have any choice but to follow your own suggestion because the Proj: fixed field only allows for one code. Naturally, make sure that the name of the projection appears in 255$b for each map, so at least our patrons will be able to know what was used when viewing a record. I think your suggestion works the best -- code for the first named map in the title proper. 





Paige 



----- Original Message -----



From: "Ken Grabach" < [log in to unmask] > 
To: [log in to unmask] 
Sent: Thursday, December 18, 2014 11:20:29 AM 
Subject: Cataloging quesiton, fixed field 





Interesting situation has come up, that I have never dealt with in several years of cataloging maps. Two maps on one sheet, both sides, with each having a different projection. Each is titled separately, so would the Fixed Field be coded for the first named title? And not concern myself in the Fixed Field for the other code? 





The map in question is the new ITMB map of Ethiopia & Eritrea, both previously published separately. Ethiopia has Universal Transverse Mercator projection; Eritrea has Lambert Con formal Conic projection. 





I've encountered many with separate scale and coordinate statements in 255 fields, reflected in separate 034 fields. But different projection statements is new for me. 





My inclination is to code for the Ethiopia (first named) map in the Fixed Field. Any other insights are welcome. 





-- 


Ken Grabach 


Maps Librarian 


BEST Library, 219D 


Miami University Libraries 


Oxford, OH 45056 USA 





513-529-1726 






ATOM RSS1 RSS2