LISTSERV mailing list manager LISTSERV 16.0

Help for METS Archives


METS Archives

METS Archives


METS@C4VLPLISTSERV01.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 2009

METS August 2009

Subject:

Feedback request on a METS/PREMIS sample document

From:

Jukka Kervinen <[log in to unmask]>

Reply-To:

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

Date:

Fri, 14 Aug 2009 14:17:32 +0300

Content-Type:

multipart/mixed

Parts/Attachments:

Parts/Attachments

text/plain (190 lines) , mono_v0_53_for comments.zip (190 lines)



(Apologies for crossposting to METS, PREMIS, MIX)
	
Sample METS document of a digitized monograph for comments.

The National Library of Finland is revising the specification for
digitized monographs to include PREMIS metadata and we are requesting
feedback a sample METS document.

The sample document and feedback received will be used to create a METS
profile.

We hope to receive feedback by 28th of August. Feedback can be given
via mail list or directly by email. As an incentive we will be giving
out small gifts to three randomly selected persons providing feedback.


	Jukka Kervinen				
	[log in to unmask]	
	System Analyst				
	National Digitisation Center	

	Karo Salminen
	[log in to unmask]
	System Analyst
	Library Network Services

	National Library of Finland


------------------------------------

Brief summary of the sample document.

The METS document describes a digitized monograph with OCR and
structural markup performed with CCS docWORKS. It is intented to serve
as both the access and the preservation functions. Main emphasis in
PREMIS has been in recording events. Rights metadata is still under
discussion. The basic METS structure comes from schema defined
by MetaE-project and CCS.

The digital object consists of:
- master images in JPEG2000 lossless format
- access images in JPEG format, rescaled to lower resolution and
converted to sRGB
- thumbnail images in JPEG format
- OCRd text in ALTO XML format
- PDF with hidden text layer
- METS xml
	
Representations (PREMIS):
- repr1: master jpeg2000 images + alto files (+ Physical and Logical
Structmap)
- repr2: access jpeg images + alto files (+ Physical and Logical Structmap)
- repr3: thumb images
- repr4: PDF
	
<dmdSec>
METS file contains two dmdSecs with bibliographic record of the digital
version
in MARCXML and MODS formats. MARCXML record is derived from the analog
original's record which is also stored in <sourceMD> of the main amdSec

There also is a <dmdSec> for each chapter and illustration in MODS
format. Identifiers are NBN based URNs.

<amdSec>
METS file contains one amdSec with id main-amd for administrative
metadata that applies to the whole object:
- rightsMD section
- sourceMD section with bibliographic record of the analog original in
MARCXML format.
- digiprovMD sections describing events (mainly document processing
steps) and agents that created the object and apply to the whole object
using premis:event and premis:agent schemas. The events in the sample
document are based on steps of the processing software used and will be
different when another software is used.
	
For each file in the METS package there will be a separate amdSec that
contains technical metadata in <techMD> and event metadata in
<digiprovMD>. <techMD> contains a premis:object with MIX and JHOVE
output in objectCharacteristicExtension.
	
Agents are referenced from main <amdSec>
	
<fileSec>
Filegroup contains five <fileGrp>s for image, alto-xml and PDF files.
	
<structMap>
Document has Physical and Logical structMaps detailing the structure.
There are also additional structMaps for different representations.

Note:
Identifier types used in PREMIS are fictitious, used only for
demonstration purposes. Date fields do not contain actual values.

---------------------------------------

All comments regarding the sample are welcome. We identified a need of
feedback on the following points:

MODS:

- MODSQ-01: MARC21slim2MODS3-3.xsl translates
<MARC:datafield tag="856" ind1="4" ind2="0">
<MARC:subfield code="u">http://urn.fi/URN:NBN:fi-fd2009-000001
</MARC:subfield>
</MARC:datafield>
to <MODS:identifier type="uri">
http://urn.fi/URN:NBN:fi-fd2008-000001</MODS:identifier>.
Would <MODS:location>
<MODS:url>http://urn.fi/URN:NBN:fi-fd20081</MODS:url>
</MODS:location> be more appropriate?
					
PREMIS:
   General
- Are there any significant gaps from long term preservation point of view?

- Do you consider saving JHOVE output in full reasonable?
What is the practice in existing PREMIS implementations?
(Sample includes JHOVE output for master image and PDF in
premis:objectCharacteristsExtension)

- Currently the content of representations are described in additional
structMaps. Do you find flaws in this implementation?

- What are your thoughts in general on recording events related to
digitization in PREMIS?

Specific (use find to locate from XML)

- PREMISQ-01: edtfSimpleType: We would like to record datetime range but
it is not accepted per v2.0 schema as shown example
(20050705T0715-0500/20050705T0720-0500) in the PREMIS data dictionary

- PREMISQ-02: We propose adding a new semantic unit to Agent entity,
agentNote to PREMIS data dictionary. It might be used for describing
software and its components in detail.

- PREMISQ-03: We record source relationship for the source image(s)
created temporarily for processing. Do you find this reasonable?
We also record the barcode of the scanned book in the scanning event
(img0001-master-event001)

- PREMISQ-04: Should METS IDs and PREMIS identifierValues be identical?

- PREMISQ-05: Comment: According to PREMIS-v2-0.xsd
<premis:objectCharacteristicsExtension> can not be repeated in
<premis:objectCharacteristics>.
This means that to have more than one external schemas for a file, in
this case a image file with MIX and JHOVE metadata,
<premis:objectCharacteristics> has to be repeated with identical
information.

The Data Dictionary seems to indicate that repeating
objectCharacteristicsExtension should be possible.
					
MIX:

- MIXQ-01: <mix:formatVersion> Is there a format version for JPEG 2000?

- MIXQ-02: Colorspace and ColorProfile with embedded scanner profiles
We will be using embedded device ICC profiles in the archive images.
What would be the appropriate way to indicate that in <mix:colorSpace>
and <mix:ColorProfile>.
     - colorSpace in master images with embedded profiles? RGB,
DeviceRGB, ICCBased?
    - Can embedded icc-profiles be marked in MIX?
					
- MIXQ-03: Targets. In our planned workflow targets (resolution,color)
are scanned once a shift and a separate digital object will be created
for the scans. These target objects are then referenced from MIX.
					
Recording multiple targets in MIX seems problematic. While the NISO spec
allows for listing of several targets validating against schema  gives error
					
Instead of trying to reference several targets contained in the target
object in MIX  would it be feasible to just reference the target object
itself.
		
- MIXQ-04: Archived master images are 2nd generation images ie. cropped
and deskewed versions of the scanner originals. Should the scanner
details be nested in PreviousImageMetadata? There are two versions of
MIX in the sample document. One with scanner data in the main data and
another with scanner data in PreviousImageMetadata.
		


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

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