LISTSERV mailing list manager LISTSERV 16.0

Help for PIG Archives


PIG Archives

PIG Archives


[email protected]


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

PIG Home

PIG Home

PIG  July 2006

PIG July 2006

Subject:

Re: PREMIS METS example - An example from National Library of Australia

From:

"Morgan V. Cundiff" <[log in to unmask]>

Reply-To:

PREMIS Implementors Group Forum <[log in to unmask]>

Date:

Fri, 21 Jul 2006 08:53:06 -0400

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (137 lines)

Bronwyn,

Can you point us to the METS file for the item?

Thanks,
Morgan Cundiff


On Fri, 21 Jul 2006, Bronwyn Lee wrote:

>
> This is very timely, as we have also just developed a PREMIS METS
> example to go with a profile we are drafting for use within the
> Australian Partnership for Sustainable Repositories (APSR).
>
> Our example is a bit more complicated, being a piece of sheet music
> consisting of a front cover, two pages and a back cover. There are three
> representations covered in the METS document: an archival master copy
> consisting of four TIFF files, a display or access copy consisting of
> four JPEG files and a print copy consisting of a single PDF file which
> was created from the access copies. This is a real example from the
> National Library of Australia's Digital Collections Manager (DCM) system
> and the presentation of it can be seen at
> http://nla.gov.au/nla.mus-an5631356
>
> The scenario the profile addresses is use of the METS document to
> transfer custody of an item from one repository to another because this
> scenario requires the most metadata for the master copy. As a general
> principle we have included all available metadata rather than linking to
> it hence for example the full catalogue record is included as well as a
> MODS record.
>
> In the example technical metadata is included for the access copies as
> well but we agree it is not essential.
>
> Our approach is similar to Rebecca's but the main difference is that we
> have one amdSec for each file (rather than all files' metadata under one
> amdSec) because we thought it was desirable to keep all the information
> about a file together. We also had only one digiprov for each file (we
> only included digiprov for the master files). An advantage of Rebecca's
> approach is that metadata for an agent only has to occur once, not once
> for each file involved.
>
> I'd be interested to hear what people think. Our approach makes the
> document potentially longer but (in my opinion anyway) easier to follow
> as you don't have to jump round as much. But as systems will generate
> these documents, and process them, perhaps neither the jumping round nor
> the length matters, although I think it helps if the documents ARE human
> readable (by the way I'm not in favour of codes e.g. MIX's ColorSpace
> "2" instead of "RGB"). We would go along with the consensus in any case.
>
> This is still very much a draft and has not been published to a website
> yet, so I'm attaching both the draft profile notes (it won't be put into
> the METS profile xml schema until it's firmer) and the METS example. The
> METS example is a .txt file as the PIG list rejected the .xml file.
>
> Bronwyn Lee
> Australian Partnership for Sustainable Repositories (APSR)
> http://www.apsr.edu.au
> National Library of Australia
> [log in to unmask]
>
> -----Original Message-----
> From: PREMIS Implementors Group Forum [mailto:[log in to unmask]] On Behalf Of
> Rebecca S. Guenther
> Sent: Friday, 21 July 2006 12:29 AM
> To: [log in to unmask]
> Subject: [PIG] PREMIS METS example
>
> This is being sent to both the PREMIS Implementors' Group list and the
> METS list. Sorry for the duplication.
>
> In preparation for a PREMIS tutorial that Priscilla Caplan and I just
> did in Glasgow (sponsored by Digital Curation Centre), I spent a lot of
> time trying to figure out the best approach for using PREMIS with METS.
> Thanks especially to Morgan Cundiff at LC and Tom Habing at UIUC for
> helping me with this. I have made available a sample document to
> illustrate the approach that we came up with and solicit comments about
> it. It is at:
> http://www.loc.gov/standards/premis/louis.xml
>
> Some notes on the approach.
>
> 1. There is one administrative metadata with multiple techMD and
> digiProvMDs. The ADMID on <file> of course links to the appropriate
> techMD or digiProvMD.
>
> 2. PREMIS object metadata is in techMD and premis:event is in digiProv.
> If we had premis:rights it would be in rightsMD.
>
> 3. If there are elements in PREMIS that are also in METS, they are
> encoded redundantly. We thought that there was no harm in this and
> perhaps safer.
>
> 4. If there is MIX, generally the data that is in PREMIS is in the
> PREMIS section and only the additional elements that are file specific
> are included in the MIX section. Note that this is based on the older
> version of MIX; MIX is in the process of revision because of the Z39.87
> revision to harmonize the element names with PREMIS where they are the
> same.
>
> 5. If there is an agent, it is in a separate digiProvMD or rightsMD
> section depending upon which metadata it's related to. In this case we
> haven't included a rightsMD section. We do have 2 events in digiProv.
> Then we have repeated digiProv with an agent and both events link to the
> same agent and the one agent is associated with both events in the file
> section.
>
> 6. This example adds to a METS object we already had in our digital
> library. I am considering this METS object an intellectual entity (in
> PREMIS terms); thus the link to the presentation of it in the PREMIS
> linkingIntellectualEntity.
> see:
> http://lcweb2.loc.gov/cocoon/test-ihas/loc.natlib.gottlieb.09601/default
> .html
>
> 7. We have not included PREMIS metadata for the service copies, because
> we consider them throwaways.
>
> I would welcome any comments on this approach. Also any discussion so
> that we can all start thinking about best practices for PREMIS/METS/MIX
> together.
>
> Rebecca
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> ^^ Rebecca S. Guenther ^^
> ^^ Senior Networking and Standards Specialist ^^
> ^^ Network Development and MARC Standards Office ^^
> ^^ 1st and Independence Ave. SE ^^
> ^^ Library of Congress ^^
> ^^ Washington, DC 20540-4402 ^^
> ^^ (202) 707-5092 (voice) (202) 707-0115 (FAX) ^^
> ^^ [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

February 2024
January 2024
December 2023
August 2023
July 2023
June 2023
March 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
May 2022
April 2022
January 2022
December 2021
October 2021
August 2021
July 2021
June 2021
April 2021
March 2021
January 2021
December 2020
September 2020
August 2020
July 2020
June 2020
April 2020
February 2020
December 2019
November 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 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
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
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

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager