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  August 2004

METS August 2004

Subject:

Re: Agent role in metsHdr

From:

Karen Coyle <[log in to unmask]>

Reply-To:

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

Date:

Mon, 30 Aug 2004 13:41:31 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (174 lines)

Jerry,

I had no intention to drive you to drink! [coffee]

Thanks for the explanation. I've been looking at roles in relation to
depositing resources in an archival repository. I've mainly been
concerned with roles relating to rights, but those seem to overlap with
roles relating to the archival/conservator function.

For rights, it seems that we have at least these roles:

- Rights holder (can be a copyright notice off of a published item, or
anyone who has obtained rights through a license or contract, or the
rights could be split between parties.)

- Rights "asserter" -- the person or institution that making a statement
about the rights (this assumes that somewhere in the METSRights record
there will be, as there is today, a statement that the item is
copyrighted, in the public domain, licensed, etc.) For example, if a
library has an archive of 19th manuscripts, whoever determined that the
items were indeed unpublished and in the public domain (either the
archive or the legal department or the digitizing department) would be
the one who asserts the rights. This is who you would go to to determine
if they had done the proper "due diligence" in relation to the rights
statement.

- Rights contact -- who you would contact for questions about rights and
possible uses. This probably is usually the archive or the institution's
licensing office.

Now the question in my mind is if there are roles relating to the
resources that aren't "rights" roles. For example, the agent role of
"ownership" of the material. In the analog world you can own the
material without owning the rights, as is the case for most books in the
library, and for works of art in a museum (where the artist retains some
IP rights). You can also be the creator of a resource and not be its
owner or IP holder (as in works for hire).

So you see how this can get very complicated, very quickly. However, to
get clarity for myself on what roles I'd like to see in the Rights
section, it would be ideal to have clarity on the roles that are
relevant for other sections. Right now the only roles I see are in the
METS Header section. It seems that some administrative roles that are
not specifically rights roles would be appropriate - yes?

kc

On Mon, 2004-08-30 at 12:14, Jerome McDonough wrote:
> I should really not answer e-mail before I've had my fifth
> cup of coffee.
>
> So, I'll try to clarify my take on this, and if anyone else on the
> editorial
> board wants to jump in, they may feel free.  The metsHdr really is
> intended to
> be about the METS document itself, and not the complete
> digital object.  As noted in the original question, the METS schema
> provides slots for recording descriptive and administrative metadata for
> the digital files included in the digital object; the metsHdr should
> in theory be used only for CREATOR/EDITOR/IPOWNER etc. with regards
> to the METS document itself.
>
> That being said, it's fairly obvious that someone entrusted with
> preservation responsibilities for the METS document is probably
> also going to have preservation responsibilities for the rest of
> the files composing the complete digital object.  If an organization
> wants to use such roles as PRESERVATIONIST, DISSEMINATOR,
> ARCHIVIST, etc. as a shorthand way of indicating that someone has
> responsibility
> for both the METS file and associated files in a digital object, I
> don't think
> anyone is going to morally censure them for it.  Moreover, some folks
> may be using the <FContent> element to embed the content bitstreams
> inside of the METS document itself, in which case saying someone has
> preservation responsibility for the METS file would of necessity imply
> preservation responsibility for the embedded bitstreams.  So, the
> metsHdr documentation stating that the <agent>s should be responsible
> for the "METS document" is actually more inclusive than it might sound
> on its face.
>
> But using the metsHdr to indicate someone has roles/responsibilities
> for digital content files in an object when they do *NOT* have
> responsibility for the METS
> file itself would be, to my mind, a mis-use of the specification.  If
> someone
> has an agent role with respect to digital files that they do not also
> play
> with respect to the METS file, that should be recorded somewhere in a
> dmdSec or
> an amdSec with the <file> element(s) linked to the information using
> the DMDID
> and ADMID attributes.  So, officially, <metsHdr> should be used to
> record
> metadata for the METS file itself, and if you want to use <metsHdr> to
> record
> information about agent roles for the METS file *and* associated data
> files,
> probably no one will give you grief, although it would be a *very* good
> idea
> to indicate that in the <note> element for that agent.  But if someone
> has a role with respect to content files that they do not have with
> respect
> to the METS file itself, you should keep that out of the <metsHdr>.
>
> Does that help any, or do I need a sixth cup of coffee?
>
>
> On Aug 30, 2004, at 2:19 PM, Karen Coyle wrote:
>
> > OK, then I need a bit more of an explanation of the other agent roles
> > in
> > the metsHdr, in particular:
> >
> > ARCHIVIST
> > PRESERVATION
> > CUSTODIAN
> >
> > It seems to me that the inherent meaning of these implies not just the
> > METS document but also the digital resources. I can see where CREATOR
> > and EDITOR can refer to the METS document alone, but with the others
> > I'm
> > having a hard time giving them that semantic.
> >
> > kc
> >
> > On Mon, 2004-08-30 at 08:15, Jerome McDonough wrote:
> >> On Aug 30, 2004, at 10:48 AM, Evan Owens wrote:
> >>
> >>> I read the documentation to say that the agent roles in the <metsHdr>
> >>> are roles in connection with the METS file, not the digital object
> >>> that
> >>> the METS file documents.  Thus for example agent role "IPOWNER" means
> >>> IP
> >>> owner of the METS file, not the digital object described by METS
> >>> file.
> >>> Information about the IP owner for the digital object would go in the
> >>> rights MD section of the administrative MD.
> >>>
> >>> Is that a correct reading of the standard?
> >>>
> >>
> >> Yes.
> >>
> >>
> >> Jerome McDonough
> >> Digital Library Development Team Leader
> >> Elmer Bobst Library, New York University
> >> 70 Washington Square South
> >> New York, NY 10012
> >> (212) 998-2425
> > [log in to unmask]
> > --
> > -------------------------------------
> > Karen Coyle
> > Digital Library Specialist
> > http://www.kcoyle.net
> > Ph: 510-540-7596 Fax: 510-848-3913
> > --------------------------------------
> >
> Jerome McDonough
> Digital Library Development Team Leader
> Elmer Bobst Library, New York University
> 70 Washington Square South
> New York, NY 10012
> (212) 998-2425
[log in to unmask]
--
-------------------------------------
Karen Coyle
Digital Library Specialist
http://www.kcoyle.net
Ph: 510-540-7596 Fax: 510-848-3913
--------------------------------------

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 2021
November 2021
November 2020
October 2020
September 2020
July 2020
May 2020
April 2020
March 2020
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