Archivematica - User contributions [en]

Adobe Extensible Metadata Platform

2009-12-09T16:21:17Z

Paul Jordan:

[[Main Page]] > [[Documentation]] > [[Format-specific preservation issues]] > Adobe Extensible Metadata Platform

===Also Known As===
Adobe XMP

===File Extension===
.xmp

===Format Registry===
Not part of PRONOM

===Preservation Issues===
* Xena incorrectly guesses xmp files to be comma separated files. During the normalization, xml code is added to the xmp file, likely rendering it unintelligable to those software programs seeking to draw change information from it.
* Xena also does not incorporate the changes described in the xmp file into the raw image before normalizing the image. This results in the loss of all post-production work.

===More information===
* Further information about XMP can be found on the Adobe website: [http://www.adobe.com/products/xmp/]

Adobe Extensible Metadata Platform

2009-12-09T16:18:50Z

Paul Jordan:

[[Main Page]] > [[Documentation]] > [[Format-specific preservation issues]] > Adobe Extensible Metadata Platform

===Also Known As===
Adobe XMP

===File Extension===
.xmp

===Format Registry===
??

===Preservation Issues===
* Xena incorrectly guesses xmp files to be comma separated files. During the normalization, xml code is added to the xmp file, likely rendering it unintelligable to those software programs seeking to draw change information from it.
* Xena also does not incorporate the changes described in the xmp file into the raw image before normalizing the image. This results in the loss of all post-production work.

===More information===
* Further information about XMP can be found on the Adobe website: [http://www.adobe.com/products/xmp/]

Adobe Extensible Metadata Platform

2009-12-09T16:17:42Z

Paul Jordan:

===Also Known As===
Adobe XMP

===File Extension===
.xmp

===Format Registry===
??

===Preservation Issues===
* Xena incorrectly guesses xmp files to be comma separated files. During the normalization, xml code is added to the xmp file, likely rendering it unintelligable to those software programs seeking to draw change information from it.
* Xena also does not incorporate the changes described in the xmp file into the raw image before normalizing the image. This results in the loss of all post-production work.

===More information===
* Further information about XMP can be found on the Adobe website: [http://www.adobe.com/products/xmp/]

Adobe Extensible Metadata Platform

2009-12-09T15:29:34Z

Paul Jordan: Created page with 'Also Known As Adobe XMP File Extension .xmp Format Registry ?? Preservation Issues * Xena incorrectly guesses xmp files to be comma separated files. During the normalization, …'

Also Known As
Adobe XMP

File Extension
.xmp

Format Registry
??

Preservation Issues
* Xena incorrectly guesses xmp files to be comma separated files. During the normalization, xml code is added to the xmp file, likely rendering it unintelligable to those software programs seeking to draw change information from it.
* Xena also does not incorporate the changes described in the xmp file into the raw image before normalizing the image. This results in the loss of all post-production work.

More information
* Further information about XMP can be found on the Adobe website: [http://www.adobe.com/products/xmp/]

Format policies

2009-12-09T15:22:54Z

Paul Jordan:

[[Main Page]] > [[Documentation]] > Format-specific preservation issues

Normalization is one preservation strategy that can be implemented using Archivematica.

Archivematica uses the National Archives of Australia's Xena (XML Electronic Normalising for Archives) software to convert certain file formats to xml-based formats on ingest.

A full list of the file types Xena can normalize is available at [http://xena.sourceforge.net/help.php?page=normformats.html http://xena.sourceforge.net/help.php?page=normformats.html].

However, some formats cannot be normalized by Xena. Also, it may be desirable to adopt format-specific preservation plans for certain types of files based on institutional requirements and preferences.

Follow the links below for further discussion of these issues for each file format.

{| border="1" cellpadding="10" cellspacing="0" width=90%
|-
|- style="background-color:#cccccc;"
!style="width:20%"|'''Format'''
!style="width:20%"|'''Also known as'''
!style="width:20%"|'''File extension(s)'''
!style="width:20%"|'''Xena support'''
|-
|[[Microsoft Excel Workbook]]
|
*Microsoft Excel
*Binary Interchange File Format (BIFF)
|.xls
|supported
|-
|[[Microsoft Office Word]]
|MS-WORD
|.doc
|supported
|-
|[[Nikon Electronic Format]]
|
*Nikon Image Format
*Nikon Digital SLR Camera Raw Image File
|.nef
|not supported
|-
|[[Adobe Extensible Metadata Platform]]
|
*Adobe XMP
|.xmp
|not supported
|-
|[[Rich Text Format]]
|
|.rtf
|supported
|-
|[[Tagged Image File Format]]
|
|.tiff, .tif
|supported
|-
|}<br />

Format policies

2009-12-08T20:28:59Z

Paul Jordan:

[[Main Page]] > [[Documentation]] > Format-specific preservation issues

Normalization is one preservation strategy that can be implemented using Archivematica.

Archivematica uses the National Archives of Australia's Xena (XML Electronic Normalising for Archives) software to convert certain file formats to xml-based formats on ingest.

A full list of the file types Xena can normalize is available at [http://xena.sourceforge.net/help.php?page=normformats.html http://xena.sourceforge.net/help.php?page=normformats.html].

However, some formats cannot be normalized by Xena. Also, it may be desirable to adopt format-specific preservation plans for certain types of files based on institutional requirements and preferences.

Follow the links below for further discussion of these issues for each file format.

{| border="1" cellpadding="10" cellspacing="0" width=90%
|-
|- style="background-color:#cccccc;"
!style="width:20%"|'''Format'''
!style="width:20%"|'''Also known as'''
!style="width:20%"|'''File extension(s)'''
!style="width:20%"|'''Xena support'''
|-
|[[Microsoft Office Word]]
|MS-WORD
|.doc
|supported
|-
|[[Nikon Electronic Format]]
|
*NEF
*Nikon Image Format
*Nikon Digital SLR Camera Raw Image File
|.nef
|not supported
|-
|[[Tagged Image File Format]]
|TIFF
|
* .tiff
* .tif
|supported
|-
|[[XLS]]
|
|.xls
|not supported
|-
|[[Rich Text Format]]
|
|.rtf
|supported
|}<br />

Nikon Electronic Format

2009-12-08T20:26:54Z

Paul Jordan: /* Preservation Issues */

[[Main Page]] > [[Documentation]] > [[Format-specific preservation issues]] > Nikon Electronic Format

===Also known as===
*NEF
*Nikon Image Format
*Nikon Digital SLR Camera Raw Image File

===File extension(s)===
.nef

===Format Registry Information===
[http://www.nationalarchives.gov.uk/PRONOM/Format/proFormatSearch.aspx?status=detailReport&id=927 PRONOM]

===Preservation Action Plan===
*Possible normalization to Adobe Digital Negative (DNG) format
**Library of Congress states that [http://www.digitalpreservation.gov/formats/fdd/fdd000188.shtml Adobe Digital Negative (DNG), Version 1.1] may be emerging as a standard preservation format for raw camera images. Adobe provides a free (but not open-source) [http://www.adobe.com/products/dng/ Adobe DNG Converter] designed for downloading to Windows or Mac computers.

===Preservation Issues===
*Xena incorrectly guesses the file type as TIFF and normalizes as it would a TIFF, with the result that a very large file (e.g. 70 MB) is normalized to a very small one (eg. 250 KB) with considerable loss of data. Changes to the raw file (ie: alterations done in image editing software) are stored in a separate XMP file, which Xena also does not recognize, and does not normalize together. This means that any edits added by the creator are removed.
*NEF is a proprietary format with an unpublished specification.
*NEF files can be very large - 70 MB or more.

===More information===
*NEF is a raw (i.e. pre-processed) image format produced by Nikon cameras.
*Information on NEF files is available at [http://www.digitalpreservation.gov/formats/fdd/fdd000241.shtml Library of Congress Sustainability of Digital Formats: Camera Raw Formats].

__NOTOC__