LISTSERV mailing list manager LISTSERV 16.0

Help for MODS Archives


MODS Archives

MODS Archives


[email protected]


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

MODS Home

MODS Home

MODS  November 2002

MODS November 2002

Subject:

Re: language attributes for MODS element - transliterations

From:

Joe Zeeman <[log in to unmask]>

Reply-To:

Metadata Object Description Schema List <[log in to unmask]>

Date:

Fri, 22 Nov 2002 11:34:19 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (155 lines)

But we already have multiple types of title, each of which may need to be
transliterated.  So transliteration can't be a type of title parallel with
uniform title, etc.  It has to be something else.  We also have names,
publication info, abstract, etc.., which may also need to be
transliterated.

Is a transliterated title a useful access point to anyone other than a
cataloguer?

j.





                    Foster Zhang
                    <fjzhang@STANF       To:     [log in to unmask]
                    ORD.EDU>             cc:
                    Sent by:             Subject:     Re: [MODS] language attributes for MODS element -
                    Metadata              transliterations
                    Object
                    Description
                    Schema List
                    <[log in to unmask]>


                    11/22/2002
                    11:07 AM
                    Please respond
                    to Metadata
                    Object
                    Description
                    Schema List






Title in transliteration is a title in different form for type, it provides
an access point to the record.

It may be easier if transliteration is stored in a separated element with
all necessary attributes to identify the content.

Nest transliteration as an element  in another element will make the
program
logic more difficult than it is in a separated xml element.
You do not need to associate elements together by nesting, you can use name
of the element, and/or type of the element to achieve the same result with
xml data.

Transliterating field as an attribute is not going to work, because you
will
have a situation that you need to describe an attribute with another
attribute.

Foster Zhang
===============================================
Systems Department         (650) 725-7924
Green Library East, 2nd Fl.(650) 723-3038 (fax)
Stanford University        [log in to unmask]
Stanford, CA  94305-6069   library.stanford.edu




-----Original Message-----
From: Metadata Object Description Schema List [mailto:[log in to unmask]]On
Behalf
Of Joe Zeeman
Sent: 2002?11?22?(???) 9:44
To: [log in to unmask]
Subject: Re: [MODS] language attributes for MODS element - transliterations


But how, then, is the transliteration to be linked to the element it is a
transliteration of (assuming there is one in the record)?  In my mind, the
best approach would be to find a way to carry them in the same field.
Possibly a <transliteration> element needs to be available for nesting
inside other elements as needed.

For example:

<titleInfo>
     <title>[a title in Cyrillic]
          <transliteration scheme="Marc21">[transliteration of Cyrillic
title] </transliteration>
     </title>
     <partNumber>[a part number in Cyrillic]
          <transliteration scheme="Marc21">[transliteration of Cyrillic
part number</transliteration>
     </partNumber>
</titleInfo>

It would be unfortunate if we end up needing to use application logic to
link arbitrary fields along the lines of the 880s in MARC, when XML gives
us an opportunity to have an explicit dependency.

An alternative would be to carry the transliteration itself as an
attribute, but this would cause awkwardnesses when the transliteration is
the only data available for the field (as in LOTS of MARC records). Mind
you, in most of those we don't even know that the title is transliterated,
at least not in any way that a mapping algorithm could easily use.

Of course, the easier thing to do would be to ban transliteration
altogether.

Joe Zeeman
Research Libraries Group




                    Karen Coyle
                    <kcoyle@KCOYLE       To:     [log in to unmask]
                    .NET>                cc:
                    Sent by:             Subject:     Re: [MODS] language
attributes for MODS element -
                    Metadata              transliterations
                    Object
                    Description
                    Schema List
                    <[log in to unmask]>


                    11/22/2002
                    06:53 AM
                    Please respond
                    to Metadata
                    Object
                    Description
                    Schema List






I was assuming it to be an attribute on a field. We could cover both pieces
of info (it's a transliteration, and what transliteration scheme) by having
an attribute that is simply:

    transliteration=[pinyin, wade-giles, etc.]

There would have to be a "cop-out" value ("other" and/or "unknown"). There
would have to be an authoritative list of transliteration schemes and we
could limit it to a few very common ones, with everything else being
"other." I think we can justify this in that transliteration, as many have
stated here, should be a thing of the past and this would primarily be used
for older metadata that is being transformed to MODS, not for metadata
being created currently or in the future.

kc

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

December 2023
November 2023
August 2023
July 2023
June 2023
November 2022
October 2022
September 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
May 2021
November 2020
September 2020
August 2020
July 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
October 2019
September 2019
August 2019
June 2019
May 2019
March 2019
February 2019
January 2019
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 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
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
February 2008
January 2008
December 2007
November 2007
October 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager