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  November 2001

METS November 2001

Subject:

Re: Two questions for our next schema discussion

From:

Jerome McDonough <[log in to unmask]>

Reply-To:

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

Date:

Thu, 1 Nov 2001 11:28:39 -0600

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (67 lines)

At 10:14 AM 11/1/2001 -0500, you wrote:
>1) Why do apparently administrative attributes such as CREATED,
>MIMETYPE, SIZE, and OWNERID survive in the file inventory, rather than
>being relegated to the amdSec like the old USE attribute? Is there some
>philosophy behind the assignment of attributes to the inventory vs the
>administrative metadata bucket? I know that the CREATED attribute allows
>for a degree of version control, which is useful in the inventory, but
>are there similar rationales for the others?

For CREATED/SIZE/OWNERID, it's helpful to think of this in terms of data
normalization (as in relational databases).  In MOA2, we tried to take
information
that applied to a whole bunch of files (storage formats, data capture
descriptions)
and put them in a separate section.  That way, you list the information once,
and have a whole bunch of files link to it.  Putting the
information in a separate section and having files link to it saves you storage
space for the information, as well as ensuring that if the information ever
needs
addition/amendment, you only have to do it in one spot.  However, information
about file creation dates/times, file size, and ownerids are likely to vary
significantly
between files; there's therefore no reason to try to separate out the
information
from the file element.  You could say that information is all
administrative and should
go in the administrative section, but ultimately all that's going to mean
is taking the
file inventory section and making it a subsection of administrative metadata.

MIMETYPE, obviously, is somewhat different, as it is something that is shared
across files.  Rick can correct me if I'm wrong on this, but my recollection is
that we put the MIMETYPE attribute on the file element because it made it
way faster to process that information in a useful way in the MOA2 browser.
So, no real theoretical justification, just a practical one.

>2) Now that xlink is valid for both mptr and FLocat (thank you!) we're
>starting to wonder if there's still a functional or philosophical reason
>to keep <mtpr> as distinct from <ftpr>?  The definition of <mptr> seems to
>get at two principles:  a) that it points to METS files, and b) that such
>files are not inventoried, and these seem to be separable issues.
>It's not obvious why it's METS-ness justifies a separate element instead
>of using the usual fptr/FLocat pair. Are there cases where you really
>shouldn't bother with an inventory entry and just use an <mptr> alone?
>Are we just trying to be flexible here?

I'd say it's more a matter of historical cruft than flexibility.  The
original mptr
used a very different model than <FLocat>.  Now that they're identical, there's
probably not a good reason to keep mptr around.  Although if we ditch <mptr>,
we might want to add an optional METS attribute of type xsd:boolean to the
<file> element
to make it clear whether an external file is a METS document or not.  That,
or we
could declare a new MIME type for METS and just store it that
way..."application/x-mets"?



Jerome McDonough
[log in to unmask]
Digital Library Development Team Leader
Elmer Holmes Bobst Library, New York University
70 Washington Square South
New York, NY 10012
(212) 998-2425

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

February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
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
https://listserv.loc.gov/cgi-bin/wa?A2=ind0111&L=METS&D=0&P=621
listserv.loc.gov
crawl=CC-MAIN-2020-10
56060
application/http; msgtype=response
sha1:UY3JR5UY62QE2EPPRL2HNQP4ACO7HZOA
<urn:uuid:3357f45a-c4e2-4f53-bff4-229457ecd1e2>
2020-02-20T10:31:43Z
140.147.55.47
text/html
sha1:ECBIEVZA42UNUEH6LEGWE7T2VYDPAPQB
<urn:uuid:5f1f8bcb-f0f6-4d20-a335-1f7be083cdc0>
https://listserv.loc.gov/cgi-bin/wa?A2=ind0111&L=METS&D=0&P=621
response
<urn:uuid:366314f9-7b5e-400b-84f6-3bd6cd56dfbf>
isPartOf: CC-MAIN-2020-10
publisher: Common Crawl
description: Wide crawl of the web for February 2020
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-128.ec2.internal
software: Apache Nutch 1.16 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/