Alyson Dalby | 16 Apr 03:15 2014
Picon
Picon

Use of authorityURI and valueURI at lower level elements

Hello,

I'm trying to create a MODS framework for a collection of photos of ships, 
and I'm hoping that the user community can help me with the use of the 
authorityURI and valueURI attributes.

The photos can contain multiple ships, each of which has several descriptive 
elements. To achieve this we're mapping along the following lines:

Ship 1:
<subject>
<name></name>
<genre></genre>
<occupation></occupation>
<temporal></temporal>
</subject>

Ship 2:
<subject>
<name></name>
<genre></genre>
<occupation></occupation>
<temporal></temporal>
</subject>

This seems fairly straightforward. Where things get complex is in the 
temporal element.

Each ship has three dates associated with it - the build date, commissioned 
date and the decommissioned date. As there is no display label attribute in 
(Continue reading)

Vicky Phillips | 11 Apr 13:09 2014
Picon

Retaining 035 information during conversion

Hello,
We have a set of MARC records we would like to convert to MODS but would
like to retain the value in the MARC 035 field.  Unfortunately with the
current conversion this is being omitted.  I've looked at the mappings and
none seem to mention the 035.  However it is in the xslt but is specific to
OCLC.  Would it be possible to amend this so that it will retain any
institution value?  For example we have the following in our 035 
<marc:datafield tag="035" ind1=" " ind2=" ">
            <marc:subfield code="a">(WlCaITV)20T02991</marc:subfield>
        </marc:datafield>

and would like this to come across into the MODS as

<identifier type="WlCaITV">20T02991</identifier>

Thanks,
Vicky

Simone Sacchi | 10 Apr 23:48 2014

MODS relatedItem to associate datasets with research publications

Hello,

We are using MODS as the metadata schema for our digital repository,
Academic Commons.  AC contains the scholarly work from Columbia
faculty, students, and staff of Columbia University. Increasingly, we
are receiving data files along with the research publication (e.g. a
conference paper).  We would like to describe these related files in a
relatedItem section of the main record, but none of the existing
relatedItem types appears to fit this case.

The existing types are:

"host"
"isReferencedBy"
"original"
"otherFormat"
"otherVersion"
"preceding"
"references"
"reviewOf"
"series"
"succeeding"

Have other MODS users encountered this issue? If yes, how did you handle it?
Would it be useful to introduce a new type to cover this situation?
MARC  21 includes the 786 (Data Source Entry) for "Information
pertaining to a data source to which the described item is related. It
may contain information about other files, printed sources, or
collection procedures".
There is also dataSource in BIBFRAME. Definition: "Has data source /
(Continue reading)

Jennifer Eustis | 15 Mar 14:08 2014
Picon

Local name authority lists

Hello,

Currently we are building our new version of our digital repository. We have a lot of archival materials
being added. For people and corporate entities, there are no records anywhere. The archivist currently
keeps a local text file in Archivist Toolkit. But this isn't practical for the digital repository. 

How do people handle their local name authorities? Any suggestions are welcome. 

Thanks in advance. 

Jennifer
Marta Bustillo | 10 Mar 11:19 2014
Picon
Picon

Reviewers for "MODS and the Digital Repository of Ireland: A user guide"

Dear all,

I am writing to ask for the help of the MODS community for a project in Ireland. My name is Marta Bustillo, and I
am a metadata cataloguer in the Harry Clarke Studios Demonstrator Project for the Digital Repository of
Ireland (DRI): http://dri.ie/demonstrator-projects/harry-clarke-studios-archive. I am also a
member of the DRI's Metadata taskforce. At present, we are involved in creating metadata guidelines for
institutions depositing collections into DRI. We are not creating any new metadata schema, but we do have
a number of mandatory fields for deposit into our repository. We have just created our first draft of "MODS
and the Digital Repository of Ireland: A user guide", which is aimed at collections using MODS and wanting
to deposit into DRI. We need some external MODS experts, who would be willing to review our guidelines,
point out any errors or inconsistencies in them, and give us some general feedback about their clarity and usefulness.

If anyone on this list is interested in volunteering to become one of our external MODS experts/reviewers,
please contact me off list at the email address below. 

Many thanks in advance for your help,

Marta

-------------------------
Dr. Marta Bustillo
Assistant Librarian
Metadata Cataloguer (Digital Repository of Ireland Demonstrator Project)
Digital Resources and Imaging Services
Trinity College Library
College Street, Dublin 2
Ireland
+353-1-896-2889
http://digitalcollections.tcd.ie/home/
(Continue reading)

Jennifer Eustis | 4 Mar 14:08 2014
Picon

use of publisher element

Hello collective wisdom,

 

Does the publisher element also cover sponsoring bodies?

 

Thanks,

Jennifer

 

 

Jennifer Marie Eustis

Catalog/Metadata Librarian

French & Francophone Studies Librarian

Homer Babbidge Library

University of Connecticut Libraries

369 Fairfield Way Unit 1005B

Storrs, CT 06269-1005B

Tel: 860-486-0384

Email: jennifer.eustis {at} lib.uconn. edu

 

Anila Angjeli | 3 Mar 17:48 2014
Picon

National library of France becomes an ISNI Registration Agency


***Apologies for cross posting****

In January 2014 the Bibliothèque nationale de France (BnF) has become an ISNI Registration Agency.

The aim of the ISNI Registration Agency at the BnF will be to improve data interoperability across communities, both from public and private sector, and to promote trustful data created by libraries on the Web of data.  As ISNI Registration Agency the BnF will first address the identification needs related to the French media content industries and the French cultural heritage collections.

The BnF is a historical partner in the ISNI initiative at international level. Together with the British Library it represents the CENL(Conference of European National Librarians) in the ISNI International Agency (ISNI-IA) - the governing body of ISNI. Both libraries play a key role in the governance of the system, in the quality of the database, but also in supporting its promotion and large diffusion.

See the joint BnF/ISNI-IA press release:
In English:
- on the BnF website http://www.bnf.fr/documents/cp_bnf_isni_en.pdf
- on the ISNI website http://isni.org/content/bnf-becomes-first-national-library-world-become-isni-registration-agency-5
In French:
-on the BnF website http://www.bnf.fr/documents/cp_bnf_isni.pdf

For more information see the BnF professional webpages :
http://www.bnf.fr/en/professionals/isni_about/s.isni_registration_agency.html?first_Art=non


About ISNI:

ISNI - ISO 27729 emerged as a response to the long felt need for a unique, global, cross-domain, standard, persistent identifier for the public identities of persons and organizations. Its primary motivation is the interoperable management of resources in the digital environment. A cross-domain initiative, ISNI is built directly on the functional legacy of library authority files. It started with more than 12 million authority records from VIAF, with data from numerous other contributors added in an on-going process. These include today 25 research organizations, rights management societies, publishers and others, and their number is growing constantly. Therefore ISNI is designed as a “bridge identifier”.

Uniqueness, persistence, and trust are ensured by a centrally governing system managed by the ISNI-International Agency (ISNI-IA) as a cross-domain public private partnership of 6 international organizations. Libraries are major stakeholders in the ISNI system, with the Bibliothèque nationale de France and the British Library representing the CENL, and with OCLC acting as ISNI Assignment Agency and managing the central database for open, global use. The task of providing data review and analysis is entrusted to the Bibliothèque nationale de France and the British Library. Experts from both libraries constitute the ISNI Quality Team.

ISNI official website: http://www.isni.org/


Anila Angjeli
Bibliothèque nationale de France
Département  Information bibliographique et numérique (IBN)
Quai François Mauriac
F-75706 Paris cedex 13
Tél.: 33.(0)1.5379.5395
anila.angjeli-JNLXu3Q5Q9g@public.gmane.org

Exposition De Rouge et de Noir. Les vases grecs de la collection de Luynes - jusqu'au 4 janvier 2015 - BnF - Richelieu

Avant d'imprimer, pensez à l'environnement.

Subirats, Imma (OPCC | 24 Feb 10:34 2014

OR2014 Conference Update: Registration Open; New Scholarship Programme

FOR IMMEDIATE RELEASE

A message from the Open Repositories 2014 Conference organizers

February 21, 2014
Read it online: http://bit.ly/1mwHBZx

Register for Open Repositories 2014
New scholarship programme aims to expand OR participation
 
Helsinki, FI  We are pleased to announce that registration for Open Repositories 2014 is now open. The five-day conference will be held in Helsinki, the capital of Finland, from June 9 to June 13, 2014. You will find full registration information on the following page: http://or2014.helsinki.fi/?page_id=454.

*Open Repositories 2014–registration and fees*

The early registration fee, 320 EUR, will be available until May 4. After May 4, the registration fee will be 400 EUR. The conference dinner will be held on Wednesday, June 11, on Valkosaari Island in Helsinki Harbor (more information here) and is priced separately at 60 EUR. There is also a special Friday evening excursion to Suomenlinna Sea Fortress (more information here) available for those delegates who will be staying in Helsinki until Saturday.

The full conference program is expected to be available in late April once the review process is completed. An early draft version of the schedule (subject to change) is available here: https://www.conftool.com/or2014/sessions.php.

The registration process will be handled by TAVI Congress Bureau. If you have questions related to conference registration, you can contact them directly at or-2014[at]tavicon.fi.

*Pilot scholarship programme* 

A highlight of this year's conference is the availability of delegate scholarships for the first time. The Open Repositories Steering Committee is delighted to announce a pilot Scholarship Programme for OR2014. This programme aims to expand participation by providing registration support for a small number of delegates to this year's conference. The scholarship programme is open to librarians, repository managers, developers and researchers in digital libraries and related fields.

Please note: the OR2014 scholarship programme provides a full discount for conference registration and the conference dinner. It does not cover other costs including accommodation, travel and subsistence. It is anticipated that the applicant's home institution will provide financial support to supplement an OR scholarship award.

Only fully-completed applications will be accepted. The deadline for applications is Sunday, March 14, 2014.

You may apply for funding here: http://or2014.helsinki.fi/?page_id=412

For more information or to nominate someone for a scholarship, please contact the Scholarship Committee chair, William J Nixon (william.nixon <at> glasgow.ac.uk).

All the best,

Imma Subirats

Knowledge and Information Management Officer

OEKC, FAO of the United Nations

Viale delle Terme di Caracalla

00153 Rome (Italy)

 

Meehleib, Tracy | 21 Feb 23:52 2014
Picon

MARCXML to MODS 3.4 -- XSLT 1.0 (Revision 1.94) Announcement

MARCXML to MODS 3.4 -- XSLT 1.0 (Revision 1.94) Announcement

The Library of Congress' MARCXML to MODS 3.4 (XSLT 1.0 Revision 1.94) is now available via the Library of Congress' MODS Web site and at http://www.loc.gov/standards/mods/v3/MARC21slim2MODS3-4.xsl --it incorporates edits made in response to comments received since the release of Revision 1.93--and reflects a recent change in the mapping for the Leader 07 b.

The MODS 3.4 XSLT is based on the MARC to MODS 3.4 mapping made available by the Library of Congress and last updated in February of 2014 <http://www.loc.gov/standards/mods/mods-mapping.html>.

Please note that content standards and practices using MARC vary among institutions, and sometimes within an institution over time or between types of collections or materials. No one stylesheet can deal appropriately with all variations in the use of MARC. The mapping decisions underlying the changes we have made, as well as the decisions underlying the LC stylesheet should be tested on sample records to determine whether the results are as desired or whether the institution needs to modify the stylesheet for a particular collection of records.

General questions about the mapping may be directed to the MODS Editorial Committee members via ndmso-+hwoy1Po9Oc@public.gmane.org. Specific questions about the stylesheet may be addressed to Tracy Meehleib at tmee-+hwoy1Po9Oc@public.gmane.org .

Thank you,

Tracy Meehleib
Network Development and MARC Standards Office
Library of Congress
101 Independence Ave SE
Washington, DC 20540-4402
+1 202 707 0121 (voice)
+1 202 707 0115 (fax)

tmee-+hwoy1Po9Oc@public.gmane.org

 

Stephen Paul Davis | 19 Feb 23:39 2014

Re: Publisher's street address (2)

I think the answer to your question about whether and how to encode a 
publisher's street address depends on the type of material being 
described.   Traditionally, in rare book cataloging at least, when the 
publisher's address appears along with the name of publisher/printer, 
the address is considered part of the "Name of publisher, distributor, 
etc." [[MARC 260 $b].

For example,

"Imprimerie d'E. Duverger, rue de Verneuil, no 4
and
"Printed for T. Cooper, at the Globe in Pater-noster-Row, 1742, and 
reprinted for J. Wilkie, St. Paul's Church-yard."

In MODS the street address would thus appear in the <publisher> element 
in its position following the publisher's name, rather than the <place> 
element.   The "Place of publication, distribution, etc" element 
(<place>) normally includes only the city, state and sometimes country 
of publication.

Changing MODS to include an address in the <place> element and forcing 
it to move out of the publisher element would make it difficult to 
preserve what remains of the "transcriptional" nature of this area in 
standard rare book cataloging.  Note too that for some publications, 
there is more than one publisher and address -- how to link multiple 
pairs of publishers and addressses if they're placed out of order and 
encoded in separate elements?

In the cataloging of modern items I don't think one normally bothers to 
include publishers' addresses if they even appear -- right?  Some 
publications do include the publisher's website address near the name of 
the publisher... Encode??

We should be a little wary of coding data at too detailed a level just 
because it theoretically _could_ be encoded at that level. There should 
be known use cases that support coding at greater detail that are deemed 
to be worth the extra expense of coding, displaying, and parsing the 
content for indexing.

It would be another matter, of course, if you needed to perform special 
retrieval or sorting operations on the street address; in that case you 
would want it structured more for access, delimiting the street number 
separately from the street name and perhaps any cardinal direction.  
This could be done, as Rebecca suggests, in the hierarchicalGeographic 
element, where the information could be recorded in a more highly 
structured way.

/Stephen

On 2/19/2014 12:00 AM, MODS automatic digest system wrote:
> There are 2 messages totalling 284 lines in this issue.
>
> Topics of the day:
>
>    1. Publisher's street address (2)
>
> ----------------------------------------------------------------------
>
> Date:    Tue, 18 Feb 2014 20:38:31 +0000
> From:    "Strong, Marcy" <mstrong@...>
> Subject: Publisher's street address
>
> --_000_7718ED26454BEC44BD89A8FFDE6B003F1CDFC2F4ITSEXCMBP02URRo_
> Content-Type: text/plain; charset="us-ascii"
> Content-Transfer-Encoding: quoted-printable
>
> Hello,
>
> I'm trying to capture the street address of the publisher and there doesn't=
>   appear to be an attribute under <placeTerm> that would allow the recording=
>   of this information.  Does anyone have a suggestion?
>
> Thanks,
> Marcy
>
>
> Marcy A. Strong
> Metadata Creation and Enrichment Librarian
> River Campus Libraries
> University of Rochester
> 755 Library Road
> Rochester, NY  14627-0055
> (585) 273-2325 | mstrong@...<mailto:mstrong@...=
> ster.edu>
>
>
>
> --_000_7718ED26454BEC44BD89A8FFDE6B003F1CDFC2F4ITSEXCMBP02URRo_
> Content-Type: text/html; charset="us-ascii"
> Content-Transfer-Encoding: quoted-printable
>
> <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
> osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
> xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
> //www.w3.org/TR/REC-html40">
> <head>
> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
> <meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
> <style><!--
> /* Font Definitions */
>  <at> font-face
> 	{font-family:Calibri;
> 	panose-1:2 15 5 2 2 2 4 3 2 4;}
> /* Style Definitions */
> p.MsoNormal, li.MsoNormal, div.MsoNormal
> 	{margin:0in;
> 	margin-bottom:.0001pt;
> 	font-size:11.0pt;
> 	font-family:"Calibri","sans-serif";}
> a:link, span.MsoHyperlink
> 	{mso-style-priority:99;
> 	color:blue;
> 	text-decoration:underline;}
> a:visited, span.MsoHyperlinkFollowed
> 	{mso-style-priority:99;
> 	color:purple;
> 	text-decoration:underline;}
> span.EmailStyle17
> 	{mso-style-type:personal-compose;
> 	font-family:"Calibri","sans-serif";
> 	color:windowtext;}
> .MsoChpDefault
> 	{mso-style-type:export-only;
> 	font-family:"Calibri","sans-serif";}
>  <at> page WordSection1
> 	{size:8.5in 11.0in;
> 	margin:1.0in 1.0in 1.0in 1.0in;}
> div.WordSection1
> 	{page:WordSection1;}
> --></style><!--[if gte mso 9]><xml>
> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
> </xml><![endif]--><!--[if gte mso 9]><xml>
> <o:shapelayout v:ext=3D"edit">
> <o:idmap v:ext=3D"edit" data=3D"1" />
> </o:shapelayout></xml><![endif]-->
> </head>
> <body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
> <div class=3D"WordSection1">
> <p class=3D"MsoNormal">Hello,<o:p></o:p></p>
> <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
> <p class=3D"MsoNormal">I&#8217;m trying to capture the street address of th=
> e publisher and there doesn&#8217;t appear to be an attribute under &lt;pla=
> ceTerm&gt; that would allow the recording of this information.&nbsp; Does a=
> nyone have a suggestion?<o:p></o:p></p>
> <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
> <p class=3D"MsoNormal">Thanks,<br>
> Marcy<o:p></o:p></p>
> <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
> <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
> <p class=3D"MsoNormal">Marcy A. Strong<o:p></o:p></p>
> <p class=3D"MsoNormal">Metadata Creation and Enrichment Librarian<o:p></o:p=
>> </p>
> <p class=3D"MsoNormal">River Campus Libraries <o:p></o:p></p>
> <p class=3D"MsoNormal">University of Rochester<o:p></o:p></p>
> <p class=3D"MsoNormal">755 Library Road <o:p></o:p></p>
> <p class=3D"MsoNormal">Rochester, NY&nbsp; 14627-0055<o:p></o:p></p>
> <p class=3D"MsoNormal">(585) 273-2325 | <a href=3D"mailto:mstrong <at> library.r=
> ochester.edu">
> <span style=3D"color:windowtext">mstrong@...</span></a><o=
> :p></o:p></p>
> <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
> <p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
> </div>
> </body>
> </html>
>
> --_000_7718ED26454BEC44BD89A8FFDE6B003F1CDFC2F4ITSEXCMBP02URRo_--
>
> ------------------------------
>
> Date:    Tue, 18 Feb 2014 17:20:41 -0500
> From:    "Guenther, Rebecca" <rgue@...>
> Subject: Re: Publisher's street address
>
> --_000_5483534C5FA8464B881ED2184D98C0F603BD53718ELCXCLMB03LCDS_
> Content-Type: text/plain; charset="us-ascii"
> Content-Transfer-Encoding: quoted-printable
>
> At this point you would have to use a string in <placeTerm> associated with=
>   the city, but there isn't a way to tag it as an address. We have talked ab=
> out enhancing place information in originInfo and aligning it with place in=
> formation under subject (especially being able to use hierarchicalGeographi=
> c under originInfo places). This would need to be done in version 4. Note t=
> hat very recently we discussed changes to hierarchicalGeographic and design=
> ating a type for citySection (including sectionType=3D"street"), which coul=
> d allow for the designation of an address.
>
> Rebecca
>
> Rebecca Squire Guenther
> Network Development & MARC Standards Office
> Library of Congress
> Washington, DC 20540
> rgue@...
>
>
>
> From: Metadata Object Description Schema List [mailto:MODS@...=
> ] On Behalf Of Strong, Marcy
> Sent: Tuesday, February 18, 2014 3:39 PM
> To: MODS@...
> Subject: [MODS] Publisher's street address
>
> Hello,
>
> I'm trying to capture the street address of the publisher and there doesn't=
>   appear to be an attribute under <placeTerm> that would allow the recording=
>   of this information.  Does anyone have a suggestion?
>
> Thanks,
> Marcy
>
>
> Marcy A. Strong
> Metadata Creation and Enrichment Librarian
> River Campus Libraries
> University of Rochester
> 755 Library Road
> Rochester, NY  14627-0055
> (585) 273-2325 | mstrong@...<mailto:mstrong@...=
> ster.edu>
>
>
>
> --_000_5483534C5FA8464B881ED2184D98C0F603BD53718ELCXCLMB03LCDS_
> Content-Type: text/html; charset="us-ascii"
> Content-Transfer-Encoding: quoted-printable
>
> <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
> osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
> xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
> //www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
> =3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
> oft Word 12 (filtered medium)"><style><!--
> /* Font Definitions */
>  <at> font-face
> 	{font-family:SimSun;
> 	panose-1:2 1 6 0 3 1 1 1 1 1;}
>  <at> font-face
> 	{font-family:SimSun;
> 	panose-1:2 1 6 0 3 1 1 1 1 1;}
>  <at> font-face
> 	{font-family:Calibri;
> 	panose-1:2 15 5 2 2 2 4 3 2 4;}
>  <at> font-face
> 	{font-family:Tahoma;
> 	panose-1:2 11 6 4 3 5 4 4 2 4;}
>  <at> font-face
> 	{font-family:"\ <at> SimSun";
> 	panose-1:2 1 6 0 3 1 1 1 1 1;}
> /* Style Definitions */
> p.MsoNormal, li.MsoNormal, div.MsoNormal
> 	{margin:0in;
> 	margin-bottom:.0001pt;
> 	font-size:11.0pt;
> 	font-family:"Calibri","sans-serif";}
> a:link, span.MsoHyperlink
> 	{mso-style-priority:99;
> 	color:blue;
> 	text-decoration:underline;}
> a:visited, span.MsoHyperlinkFollowed
> 	{mso-style-priority:99;
> 	color:purple;
> 	text-decoration:underline;}
> span.EmailStyle17
> 	{mso-style-type:personal;
> 	font-family:"Calibri","sans-serif";
> 	color:windowtext;}
> span.EmailStyle18
> 	{mso-style-type:personal-reply;
> 	font-family:"Calibri","sans-serif";
> 	color:#1F497D;}
> .MsoChpDefault
> 	{mso-style-type:export-only;
> 	font-size:10.0pt;}
>  <at> page WordSection1
> 	{size:8.5in 11.0in;
> 	margin:1.0in 1.0in 1.0in 1.0in;}
> div.WordSection1
> 	{page:WordSection1;}
> --></style><!--[if gte mso 9]><xml>
> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
> </xml><![endif]--><!--[if gte mso 9]><xml>
> <o:shapelayout v:ext=3D"edit">
> <o:idmap v:ext=3D"edit" data=3D"1" />
> </o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
> nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'c=
> olor:#1F497D'>At this point you would have to use a string in &lt;placeTerm=
> &gt; associated with the city, but there isn't a way to tag it as an addres=
> s. We have talked about enhancing place information in originInfo and align=
> ing it with place information under subject (especially being able to use h=
> ierarchicalGeographic under originInfo places). This would need to be done =
> in version 4. Note that very recently we discussed changes to hierarchicalG=
> eographic and designating a type for citySection (including sectionType=3D&=
> quot;street&quot;), which could allow for the designation of an address. <o=
> :p></o:p></span></p><p class=3DMsoNormal><span style=3D'color:#1F497D'><o:p=
>> &nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'color:#1F497D'>=
> Rebecca<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'color:#1F4=
> 97D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'color:=
> #1F497D'>Rebecca Squire Guenther<o:p></o:p></span></p><p class=3DMsoNormal>=
> <span style=3D'color:#1F497D'>Network Development &amp; MARC Standards Offi=
> ce<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'color:#1F497D'>=
> Library of Congress<o:p></o:p></span></p><p class=3DMsoNormal><span style=
> =3D'color:#1F497D'>Washington, DC 20540<o:p></o:p></span></p><p class=3DMso=
> Normal><span
style=3D'color:#1F497D'>rgue@...<o:p></o:p></span></p><p c=
> lass=3DMsoNormal><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p>=
> <p class=3DMsoNormal><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span>=
> </p><p class=3DMsoNormal><span style=3D'color:#1F497D'><o:p>&nbsp;</o:p></s=
> pan></p><div><div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;paddi=
> ng:3.0pt 0in 0in 0in'><p class=3DMsoNormal><b><span style=3D'font-size:10.0=
> pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style=3D'font-s=
> ize:10.0pt;font-family:"Tahoma","sans-serif"'> Metadata Object Description =
> Schema List [mailto:MODS@...] <b>On Behalf Of </b>Strong, Marc=
> y<br><b>Sent:</b> Tuesday, February 18, 2014 3:39 PM<br><b>To:</b> MODS <at> LIS=
> TSERV.LOC.GOV<br><b>Subject:</b> [MODS] Publisher's street address<o:p></o:=
> p></span></p></div></div><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=
> =3DMsoNormal>Hello,<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p=
>> <p class=3DMsoNormal>I&#8217;m trying to capture the street address of the=
>   publisher and there doesn&#8217;t appear to be an attribute under &lt;plac=
> eTerm&gt; that would allow the recording of this information.&nbsp; Does an=
> yone have a suggestion?<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p=
>> </p><p class=3DMsoNormal>Thanks,<br>Marcy<o:p></o:p></p><p class=3DMsoNorm=
> al><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=
> =3DMsoNormal>Marcy A. Strong<o:p></o:p></p><p class=3DMsoNormal>Metadata Cr=
> eation and Enrichment Librarian<o:p></o:p></p><p class=3DMsoNormal>River Ca=
> mpus Libraries <o:p></o:p></p><p class=3DMsoNormal>University of Rochester<=
> o:p></o:p></p><p class=3DMsoNormal>755 Library Road <o:p></o:p></p><p class=
> =3DMsoNormal>Rochester, NY&nbsp; 14627-0055<o:p></o:p></p><p class=3DMsoNor=
> mal>(585) 273-2325 | <a href=3D"mailto:mstrong@..."><span=
>   style=3D'color:windowtext'>mstrong@...</span></a><o:p></=
> o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><o:p=
>> &nbsp;</o:p></p></div></body></html>=
> --_000_5483534C5FA8464B881ED2184D98C0F603BD53718ELCXCLMB03LCDS_--
>
> ------------------------------
>
> End of MODS Digest - 4 Feb 2014 to 18 Feb 2014 (#2014-11)
> *********************************************************
>

Strong, Marcy | 18 Feb 21:38 2014
Picon

Publisher's street address

Hello,

 

I’m trying to capture the street address of the publisher and there doesn’t appear to be an attribute under <placeTerm> that would allow the recording of this information.  Does anyone have a suggestion?

 

Thanks,
Marcy

 

 

Marcy A. Strong

Metadata Creation and Enrichment Librarian

River Campus Libraries

University of Rochester

755 Library Road

Rochester, NY  14627-0055

(585) 273-2325 | mstrong-pJ6Lu2hYgzhpggHy5YhRvdAIK75dWmlW@public.gmane.org

 

 


Gmane