JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for LIS-UKBIBS Archives


LIS-UKBIBS Archives

LIS-UKBIBS Archives


LIS-UKBIBS@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

LIS-UKBIBS Home

LIS-UKBIBS Home

LIS-UKBIBS  September 2008

LIS-UKBIBS September 2008

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: UKMARC to MARC21 conversion

From:

"Jardine, Heather" <[log in to unmask]>

Reply-To:

Jardine, Heather

Date:

Tue, 9 Sep 2008 09:11:03 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (221 lines)

 

I agree - now we are using M21 for current cataloguing, we use 245 + 4xx

if each part has a distinctive title; otherwise 245 + 505. But you can't

know when converting which would be the best option for each record, so

we ended up migrating existing multi-part works with subfields n and p.

This leaves you with the job of tidying up when the first few parts in a

multi-part work have been converted (and therefore have subfields n and

p) and you then acquire later parts which you catalogue either with

options 2 or 3 - then do you go back and re-catalogue the earlier parts

so the work is consistent as a whole? We have tried to do so, as we

determined not to carry on using subfields n and p, as not being

standard M21. But it can be a bind, when it involves lots of editing and

fiddling about - and I believe is more honoured in the breach than the

observance by hard-pressed cataloguers, so the inconsistency is only

perpetuated.



Also, be aware (and depending on what system you use) that where you

adopt option 2, whether in retrospective conversion or current

cataloguing, your LMS may expect all items attached to a work to be

identical (it is sort of logical!) and therefore expect that you will

have just one "item" which represents the whole set. This doesn't work

if you want to issue the parts separately, but if you add each part as a

separate item, it may then be impossible to reserve just one part (and

not the others). For example - if you attach parts 1, 2 and 3 of a

spoken language course to a single work, you may be unable to reserve

Part 1 alone. It can also screw your management information - do you

have one copy of the multi-part work described in the bib record, or

three?



I also agree with the rest that careful work ahead of conversion (to

identify and, as far as possible, rectify the errors which all databases

have) is easier and more economic than trying to sort them out

afterwards.



Bon voyage!



Heather Jardine

City of London Libraries.



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

From: Bibliographic standards in UK libraries

[mailto:[log in to unmask]] On Behalf Of Andrew Coburn SLBS LY LS

Sent: 09 September 2008 08:56

To: [log in to unmask]

Subject: Re: UKMARC to MARC21 conversion



Hannah

I would only add to the foregoing that (unless you believe your past

cataloguers were nigh on perfect) you might want to try and get a list

of fields and subfields that are used in your current database and check

out the ones that only appear a couple of times or don't actually exist

in UKMARC. We did that and were able to correct a lot of stuff that

should never have been there and would not have converted sensibly.

On 248 I agree with everyone else.



Andrew Coburn

Acquisitions & Cataloguing Manager

Essex Libraries

Adults, Health and Community Wellbeing

Essex County Council

Goldlay Gardens

tel. 01245 244957

01245 284981 ext 255

minicom 01245 244966

ECC ednet 35255



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

From: Bibliographic standards in UK libraries

[mailto:[log in to unmask]] On Behalf Of Danskin, Alan

Sent: 09 September 2008 08:21

To: [log in to unmask]

Subject: Re: UKMARC to MARC21 conversion



Hannah,



I endorse what Hugh and Michael have said.  Option 1 is the simplest and

most consistent.  We decided that options 2 and 3 could not be applied

with any consistency.  The downside to option 1 is that the conversion

results in a cut off between current and legacy multiparts.  You will

have to instruct staff what to do when processing a new volume for a

legacy multipart.  Do you recatalogue the whole set?  Follow the legacy

pattern (245 n & p) or catalogue as a single volume?



The only advice I have, is make sure you know what elements and

subfields you have in your database.  The mapping may be an opportunity

to do some clean up.  In any case, have a default location such as 887

where you can map stuff that isn't recognised and still retain its

structure.  Finally,  test the conversion thoroughly before going live

with it.



Alan



Alan Danskin

Data Quality & Authority Control Manager, British Library Boston Spa,

Wetherby, West Yorkshire

LS23 7BQ

United Kingdom

 

Tel. +44 (0)1937 546669

Fax. +44 (0)1937 546979

[log in to unmask]





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

From: Bibliographic standards in UK libraries

[mailto:[log in to unmask]] On Behalf Of Hugh Taylor

Sent: 09 September 2008 08:02

To: [log in to unmask]

Subject: Re: UKMARC to MARC21 conversion



Hannah,



I would support everything Michael said. Apart from the errors, the

biggest difficulty you'll have to face is when there are statements of

responsibility in both UKMARC 245 and 248. Whatever else, you don't want

to lose the relationships between the various elements, even if the end

result is "ugly" in MARC 21 terms.



One note of caution, based on our own experience back in 2002. You will

need to drill into the minds of your staff that the resulting

construction is only infrequently going to be appropriate for future

cataloguing. As with so many things, simply seeing so many examples in

your newly-converted database will encourage people to think this is a

pattern that can simply be copied. They need to go back to the rules to

think about what it is they're describing and work out for themselves

what this means in AACR2 terms before deciding how that maps to MARC 21.



Don't start with the MARC 21 and divine the rationale from that! We

found that the most difficult thing of all (perhaps because it involved

more people than writing and testing the conversion spec).



Hugh

--

Hugh Taylor

Head, Collection Development and Description Cambridge University

Library West Road, Cambridge CB3 9DR, England



email: [log in to unmask]   fax: +44 (0)1223 333160

phone: +44 (0)1223 333069 (with voicemail) or

phone: +44 (0)1223 333000 (ask for pager 036)



Michael Emly said - in whole or part - on 08/09/2008 17:09:

> Dear Hannah

> 

> I don't know how your system would handle options 2 or 3 below, but I 

> think they could prove difficult because you then have to identify 

> which discrete records should be merged to form a single bib.  I'd 

> recommend option 1, which is what Leeds did.

> 

> In terms of specification, if your database is clean and compliant, 

> then I wouldn't depart very far from the BL spec - it's tried and 

> tested, even if it isn't perfect.



************************************************************************

**

 

Experience the British Library online at www.bl.uk

 

The British Library's new interactive Annual Report and Accounts 2007/08

: www.bl.uk/knowledge

 

Help the British Library conserve the world's knowledge. Adopt a Book.

www.bl.uk/adoptabook

 

The Library's St Pancras site is WiFi - enabled

 

************************************************************************

*

 

The information contained in this e-mail is confidential and may be

legally privileged. It is intended for the addressee(s) only. If you are

not the intended recipient, please delete this e-mail and notify the

[log in to unmask] : The contents of this e-mail must not be disclosed or

copied without the sender's consent. 

 

The statements and opinions expressed in this message are those of the

author and do not necessarily reflect those of the British Library. The

British Library does not take any responsibility for the views of the

author. 

 

************************************************************************

*



  Click

https://www.mailcontrol.com/sr/GvPzIsJSxjnTndxI!oX7UtTXwRoU2H8XI9PMFPTxe

VxTuIlbg31f+13I5r7HS!X6OEBH4o35jBZaXEW7R1X!lw==  to report this email as

spam.





This email (including any attachments) is intended only for the

recipient(s) named above.  It may contain confidential or privileged

information and should not be read, copied or otherwise used by any

other person unless express permission is given.  If you are not a named

recipient, please contact the sender and delete the email from your

system. It is the recipient's responsibility to ensure that appropriate

measures are in place to check for software viruses. 

 



-----------------------------------------

THIS E-MAIL AND ANY ATTACHED FILES ARE CONFIDENTIAL AND MAY BE
LEGALLY PRIVILEGED.

If you are not the addressee, any disclosure, reproduction,
copying, distribution or other dissemination or use of this
communication is strictly prohibited. If you have received this

transmission in error please notify the sender immediately and then
delete this e-mail. 

Opinions, advice or facts included in this message are given
without any warranties or intention to enter into a contractual
relationship with the City of London unless specifically indicated
otherwise by agreement, letter or facsimile signed by a City of
London authorised signatory. Any part of this e-mail which is
purely personal in nature is not authorised by the City of London.


All e-mail through the City of London's gateway is potentially the
subject of monitoring. All liability for errors and viruses is
excluded. Please note that in so far as the City of London falls
within the scope of the Freedom of Information Act 2000 or the
Environmental Information Regulations 2004, it may need to disclose
this e-mail.

Website: http://www.cityoflondon.gov.uk

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003
2002
2001
2000
1999


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager