LISTSERV mailing list manager LISTSERV 16.0

Help for MODS Archives


MODS Archives

MODS Archives


MODS@LISTSERV.LOC.GOV


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  July 2009

MODS July 2009

Subject:

Re: geospatial information in MODS - call for use cases

From:

Rebecca S Guenther <[log in to unmask]>

Reply-To:

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

Date:

Fri, 24 Jul 2009 12:09:15 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (106 lines)

Now my response to Jenn's message about geospatial in MODS.

There needs to be extensibility for the cartographics element and also any of its subelements to be able to use any XML, such as that in geonames.

I would like to see probably the same granularity in MODS coordinates as we have in MARC 034. We are engaged in a project here at LC where we will be populating authority records for geographic places with coordinates in field 034, so the granularity will be the same as MARC, i.e. separate subfields for west, east, north south. Currently MODS just outputs coordinates as a string of course.

The use case is that we are going to be doing some metadata remediation-- for now on some of our American Memory collections. We are going to be generating coordinates for items that have a place associated and using the authority record (once we have the 034s in the records) to match geographic place and extract the coordinates. We are using MODS for remediated records, which will be converted from their source format (which varies) into MODS. So it would really be helpful if we don't have to convert the data that we will have in the MARC authority record into a string but can retain the granularity in coding. 

We could also make a case for parsing out scale as it is in the bibliographic 034:
http://www.loc.gov/marc/bibliographic/bd034.html 
And I am not sure whether any of the data in the other subfields in the authority or bibliographic 034 (e.g. declination, ascension, g-ring, etc.) might also be helpful to have available in MODS.

As we all know, people are really into geographic approaches to data these days, which justifies to me giving more granularity in MODS. We plan to use this data to develop interfaces to the resources, like clicking on parts of a map to get, for example, civil war photographs of a certain town.

Rebecca

Rebecca S. Guenther                                                       
Senior Networking and Standards Specialist                  
Network Development and MARC Standards Office     
Library of Congress   
101 Independence Ave. SE                                                                                      
Washington, DC 20540-4402                                          
(202) 707-5092 (voice)    
(202) 707-0115 (FAX)           
 [log in to unmask]

>>> "Riley, Jenn" <[log in to unmask]> 7/21/2009 3:14 PM >>>
Dear MODS/MADS Community,

This is a reminder the MODS/MADS Editorial Committee is looking for use cases for geospatial information in MODS. Please send any use cases you have to the MODS list - we'd like MODS to evolve to handle this type of information in a way that's useful to you.

Thanks,

Jenn Riley
Chair, MODS/MADS Editorial Committee

> -----Original Message-----
> From: Metadata Object Description Schema List [mailto:[log in to unmask]] On
> Behalf Of Riley, Jenn
> Sent: Monday, June 29, 2009 9:19 PM
> To: [log in to unmask] 
> Subject: [MODS] geospatial information in MODS - call for use cases
>
> Dear MODS/MADS community,
>
> In considering changes for future versions of MODS, the MODS/MADS
> Editorial Committee is starting to think about how to better handle
> geospatial information. Detailed geospatial information in the form of
> coordinates, etc. is becoming more and more common and can promote many
> innovative user interactions with resources. Currently MODS has poor
> support for this information.
>
> The committee would like to bring together use cases for supporting
> geospatial access to resources from MODS and/or MADS implementations.
> We are interested both in use cases that you already have in your
> MODS/MADS implementation and that any local geospatial experts you have
> access to can provide, to help us inform how MODS and/or MADS should
> evolve to better handle this information. It should be noted this
> discussion came to the Editorial Committee from the more specific
> geospatial elements (latitude/longitude,
> equinox/epoch) in RDA, although we want to look beyond RDA for guidance
> in this decision.
>
> So far, we have identified the following use cases for geospatial data:
>
> - To allow resources with a geospatial component (interpreted widely)
> to be plotted on an interactive map-based interface
> - Interactively overlaying different maps, including aerial
> photographs, digitized historic maps, and current maps in a GIS
> environment
> - To index coordinate data about the geographic coverage of a resource
> for retrieval purposes
> - To index coordinate data about the geographic origin of a resource
> for retrieval purposes
>
> What others can you provide?
>
> Are there more specific use cases both for geospatial *coverage* (what
> a resource is about or represents) and geospatial *origin* (where a
> resource is from, for example, a soil sample)? This distinction seems
> important but it would be useful to understand what is done differently
> in each case.
>
> There is some question as to whether the appropriate place for this
> information is MODS or MADS - thoughts on this issue? Should MODS/MADS
> be looking to embedding or referencing other standards for this
> information, and, if so, which and where? What is the best balance
> between functionality (and potentially complexity) and ease of
> creation/maintenance/use?
>
> We look forward to hearing discussion on this issue - it's a complex
> but important one that will benefit from community contribution.
>
> Jenn Riley, Chair, MODS/MADS Editorial Committee
>
> ========================
> Jenn Riley
> Metadata Librarian
> Digital Library Program
> Indiana University - Bloomington
> Wells Library W501
> (812) 856-5759
> www.dlib.indiana.edu 
>
> Inquiring Librarian blog: www.inquiringlibrarian.blogspot.com

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

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