LISTSERV mailing list manager LISTSERV 16.0

Help for METS Archives


METS Archives

METS Archives


METS@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

METS Home

METS Home

METS  February 2006

METS February 2006

Subject:

Re: METS for transporting of various files

From:

Robert Wolfe <[log in to unmask]>

Reply-To:

Metadata Encoding and Transmission Standard <[log in to unmask]>

Date:

Thu, 23 Feb 2006 12:17:25 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (103 lines)

Hi Jenn,

I second that you're scanned pages are rightly considered descriptive  
metadata, if they can be indexed.

At DSpace, we have also encountered the situation where system  
developers want our METS to point to all files (metadata and content)  
in one place using one mechanism.  I'd prefer to counter this bit of  
laziness, keeping them from ignoring the rich information our METS is  
passing them.  I kind of like what you did as a solution to that  
puzzle.  It allows a METS consumer to decide whether they can use any  
of its meaning.

However, if the problem you want to solve is integrity checking, you  
should look at PREMIS.


Robert Wolfe
Metadata Specialist
MIT Libraries/OpenCourseWare
[log in to unmask]





On Feb 23, 2006, at 11:24 AM, Jerome McDonough wrote:

> On Feb 23, 2006, at 9:48 AM, Riley, Jenn wrote:
>> 2) A <dmdSec> appears representing the set of scanned pages of the
>> program for a concert (not each individual page, but the set of  
>> them).
>> It has an <mdRef> with an xlink:href attribute with the current METS
>> file as its value, and an XPTR attribute pointing to the <fileGrp> in
>> the <fileSec> where the page images are grouped. Saying this is
>> descriptive metadata is a *bit* of a stretch, as the bits making  
>> up the
>> page images aren't descriptive metadata, but their intellectual  
>> content
>> is.
>>
>> 3) Several <techMD>s appear, each representing a technical  
>> metadata file
>> (we have two kinds in this situation), using the same <mdRef>  
>> strategy
>> as in the <dmdSec> to point to the file in the <fileSec> of the METS
>> document.
>>
>
> I don't have a problem with considering the program as a piece of  
> descriptive
> metadata, but if it's really operating as such, I wonder whether  
> you might
> want to at least produce a text transcription so that the  
> "descriptive metadata"
> is indexable/searchable.  If you're going to use <fileSec> to insure
> you can record fixity information for your metadata records, the  
> approach
> you're taking for <dmdSec> and <techMD> records seems OK, but I would
> suggest at least considering whether it might be better to use PREMIS
> to record this type of information, and abandon the slightly kludgy  
> use
> of <fileSec> to record fixity info for your metadata.
>
>
>
>> 4) The audio files in the <fileSec> have AMDID attributes referencing
>> which of the technical metadata files is applicable to this audio  
>> file.
>> They also have DMDID attributes referencing the set of program pages
>> referenced in the <dmdSec>. We reference the set rather than anything
>> more specific because we don't at this point in the project have
>> information about how the page images line up with points in the  
>> audio
>> file.
>>
>> 5) A <structMap TYPE="logical"> appears, listing "tracks" or breaks
>> between musical works in the concert.
>>
>> So does any of this sound like I've gone a bit too far with the  
>> usage of
>> a METS element? Is there anything in this proposal that could be done
>> more simply or elegantly than the way I've described?
>>
>
> I think the use of PREMIS would be a bit more elegant and in keeping
> with the general structure of METS, given that there is no existing
> facility in METS for recording fixity information for a metadata  
> record.
> I do think the board might want to consider whether a change to the
> METS schema to add some sort of fixity information to the mdSecType
> definition is in order.  If we include an attribute for this  
> purpose for
> data files, including one for metadata seems like a reasonable step.
>
> Jerome McDonough, Asst. Professor
> Graduate School of Library & Information Science
> University of Illinois, Urbana-Champaign
> 501 E. Daniel Street, Room 202
> Champaign, IL 61820
> (217) 244-5916
> [log in to unmask]

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

August 2019
May 2019
April 2019
March 2019
November 2018
October 2018
September 2018
July 2018
June 2018
April 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
July 2017
June 2017
May 2017
April 2017
January 2017
October 2016
August 2016
July 2016
June 2016
May 2016
April 2016
January 2016
September 2015
August 2015
June 2015
May 2015
April 2015
March 2015
February 2015
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
January 2014
December 2013
October 2013
September 2013
August 2013
June 2013
May 2013
April 2013
February 2013
November 2012
October 2012
September 2012
August 2012
June 2012
May 2012
March 2012
February 2012
January 2012
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
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
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
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
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
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager