Archivematica - User contributions [en]

Significant characteristics

2011-10-11T03:05:06Z

Anarchivist:

[[Main Page]] > [[Documentation]] > [[Media type preservation plans]] > Significant characteristics

== Significant characteristics by media type ==
*[[Significant characteristics of audio files|audio]]
*[[Significant characteristics of presentation files|presentation files]]
*[[Significant characteristics of raster images|raster images]]
*[[Significant characteristics of spreadsheets|spreadsheets]]
*[[Significant characteristics of text files|text]]
*[[Significant characteristics of email|email]]
*[[Significant characteristics of vector images|vector images]]
*[[Significant characteristics of video files|video]]
*[[Significant characteristics of word processing files|word processing files]]

== Definitions ==

Within the Archivematica project, the term 'significant properties' has been superseded by 'significant characteristics' because it has a wider scope, see [http://www.planets-project.eu/docs/papers/Dappert_SignificantCharacteristics_ECDL2009.pdf Significance is in the Eye of the Stakeholder] (Dappert and Farquhar, 2009). It is also more consistent with the terminology used in the [http://planetarium.hki.uni-koeln.de/planets_cms/about-xcl eXtensible Characterization Language]. However, in most instances the two terms ('significant properties' or 'significant characteristics') are largely synonymous and best defined by Andrew Wilson:
* "Significant properties: the characteristics of digital objects that must be preserved over time in order to ensure the continued accessibility, usability, and meaning of the objects, and their capacity to be accepted as evidence of what they purport to record." [http://www.dpconline.org/docs/events/080407sigpropsWilson.pdf Significant Properties of Digital Objects, Andrew Wilson, National Archives of Australia, 2008, p. 15]

Other definitions:

* "Significant Properties: Those technical characteristics agreed by the archive or by the collection manager to be most important for preserving the digital object over time." [http://www.webarchive.org.uk/wayback/archive/20050410120000/http://www.leeds.ac.uk/cedars/guideto/collmanagement/index.html Cedars Guide to: Digital Collection Management, 2002, p. 24]
* "Significant properties are those aspects of a digital record that must be preserved over time in order for it to remain accessible and meaningful." [http://www.significantproperties.org.uk/documents/wp33-propertiesreport-v1.pdf Framework for the definition of significant properties, Gareth Night, 2008 (Inspect Project document), p. 3]
* "Transformational Information Property: An Information Property whose preservation is regarded as being necessary but not sufficient to verify that any Non-Reversible Transformation has adequately reserved information content. This could be important as contributing to evidence about Authenticity. Such Information Properties will need to be associated with specific Representation Information, including Semantic Information, to denote how they are encoded and what they mean. (The term ‘significant property’, which has various definitions in the literature, is sometimes used in a way that is consistent with its being a Transformational Information Property)." [http://public.ccsds.org/sites/cwe/rids/Lists/CCSDS%206500P11/Attachments/650x0p11.pdf OAIS Draft Recommended Standard Pink Book, August 2009, p. 1-15]

== Research ==
[http://www.significantproperties.org.uk/ InsPECT: (Investigating the Significant Properties of Electronic Content over Time)]
*[http://www.significantproperties.org.uk/documents/wp33-propertiesreport-v1.pdf Framework for the definition of significant properties, Gareth Night, 2008]

[http://planetarium.hki.uni-koeln.de/planets_cms/about-xcl XCL - eXtensible Characterisation Language]
*[http://www.springerlink.com/content/c20150x260758r11/ Significant Characteristics to Abstract Content: Long Term Preservation of Information]

[http://www.planets-project.eu/ PLANETS (Preservation and Long-Term Access through Networked Services)]
*[http://www.planets-project.eu/publications/?l=s Significance is in the Eye of the Stakeholder, Angela Dappert and Adam Farquhar (British Library), October, 2009]

[http://www.jisc.ac.uk/whatwedo/programmes/preservation/2008sigprops.aspx JISC]
*[http://www.jisc.ac.uk/media/documents/programmes/preservation/vector_images.pdf The Significant Properties of Vector Images. Mike Coyne, David Duce, Bob Hopgood, George Mallen, Mike Stapleton 2007]
*[http://www.jisc.ac.uk/media/documents/programmes/preservation/spmovimages_report.pdf The Significant Properties of Moving Images, Mike Coyne and Mike Stapleton, 2008]
*[http://www.jisc.ac.uk/media/documents/programmes/preservation/spelosfinal.pdf Significant Properties of e-Learning Objects (SPeLOs), Kevin Ashley, Richard Davis, Ed Pinsent, 2008]

Other research
*[http://www.ijdc.net/index.php/ijdc/issue/view/7 Data Without Meaning: Establishing the Significant Properties of Digital Research, Gareth Night, Maureen Pennock, The International Journal of Digital Curation, vol. 4, no. 1, 2009]
*[http://fclaweb.fcla.edu/uploads/Lydia%20Motyka/FDA_documentation/documentMD.pdf Document Metadata: Document Technical Metadata for Digital Preservation, Florida Digital Archive and Harvard University Library, 2009]

Significant characteristics of word processing files

2011-10-11T02:59:27Z

Anarchivist:

[[Main Page]] > [[Documentation]] > [[Media type preservation plans]] > [[Significant characteristics]] > Significant characteristics of word processing files

*"[T]he essential characteristics of a word processing document may include the textual content; formatting such as bolded text, font type and size; layout; bulleting; colour and embedded graphics." [http://www.naa.gov.au/Images/An-approach-Green-Paper_tcm2-888.pdf An Approach to the Preservation of Digital Records, National Archives of Australia, 2002]
*[http://fclaweb.fcla.edu/uploads/Lydia%20Motyka/FDA_documentation/documentMD.pdf Document Metadata: Document Technical Metadata for Digital Preservation, Florida Digital Archive and Harvard University Library, 2009]: this document suggests technical metadata for textual records which "can be used to verify the result of document transformations, ensuring the properties of the original document are preserved and properly transformed to the new document format." The metadata in this table are adapted from that source:

{| border="1" cellpadding="10" cellspacing="0" width=90%
|-
|- style="background-color:#cccccc;"
!style="width:10%"|'''Semantic unit'''
!style="width:30%"|'''Description'''
!style="width:10%"|'''Obligation'''
!style="width:20%"|'''Characteristic'''
!style="width:50%"|'''Note'''
|-
|PageCount
|Total number of pages in the document
|Mandatory
|Structure
|
|-
|WordCount
|Total number of words in the document
|Optional
|Structure
|This element is included in this schema because it can be valuable for evaluating the completeness of the content after transformations. Caution must be used with this element, however, because tools and applications that can determine the number of words in a document do not always use the same algorithm for determining this value.
|-
|CharacterCount
|Total number of characters in the document
|Optional
|Structure
|See note for WordCount, above
|-
|ParagraphCount
|Total number of paragraphs in the document
|Optional
|Structure
|See note for WordCount, above
|-
|LineCount
|Total number of lines in the document
|Optional
|Structure
|See note for WordCount, above
|-
|TableCount
|Total number of tables in the document
|Optional
|Structure
|See note for WordCount, above
|-
|GraphicsCount
|Total number of graphics in the document
|Optional
|Structure
|See note for WordCount, above
|-
|Language
|A language identifier specifying the natural language used in the document
|Optional
|Content
|
|-
|Fonts (FontName, isEmbedded)
|A list of fonts used in the document; An indication of whether or not a font is embedded in a document
|Mandatory
|Content, Appearance
|This element allows a repository to store the names of all fonts used in a document. Some repositories may choose to store only the non-embedded fonts. It is recommended that repositories record at least the non-embedded fonts to assist in identifying the documents with potential long-term preservation risks.
|-
|Features
|Additional document features as follows: hasLayers, hasTransparency, hasOutline, hasForms, has Annotations
|Optional
|
*hasLayers: appearance
*hasTransparency: appearance
*hasOutline: behaviour, appearance
*hasForms: content
*hasAnnotations: content
|
|}

Micro-services

2010-10-06T03:51:35Z

Anarchivist: Undo revision 2684 by Sefsefsef (talk)

[[Main Page]] > [[Overview]] > Micro-services

[[File:Archivematica-architecture-7May2010-2.png|thumb|right|600px|Archivematica architecture - May 2010]]

The Archivematica [http://www.cdlib.org/services/uc3/curation/ micro-services] are based on the project's [[OAIS Use Cases|use case]] and [[UML Activity Diagrams|workflow]] analysis of the ISO-OAIS functional model. Each service is available to a conceptual entity that is equivalent to an OAIS information package:
*Submission Information Package (SIP)
*Archival Information Package (AIP)
*Dissemination Information Package (DIP)

These packages are moved from one service to the next using the [http://en.wikipedia.org/wiki/Pipeline_%28Unix%29 Unix pipeline] design pattern implemented with a combination of Bash and Python scripts. Each service is provided by one or more of the open-source [[Release_0.6-alpha|software]] utilities and applications bundled in the Archivematica system.

In early iterations of the Archivematica system, some of the workflow controls (e.g. event triggering, error reporting, etc.) are handled via the Thunar file manager (e.g. drag-and-drop, desktop notifications). As the system approaches beta maturity all of the micro-services workflow will be managed via a web-based [[Dashboard]] application.

==Archivematica Micro-services==

{| border="1" cellpadding="10" cellspacing="0" width=40%
|-
|- style="background-color:#cccccc;"
!'''Category'''
!'''Micro-service'''
|-
|-
|receiveSIP
|
*verifyChecksum
|-
|reviewSIP
|
*extractPackage
*assignIdentifier
*parseManifest
*cleanFilename
|-
|quarantineSIP
|
*lockAccess
*virusCheck
|-
|appraiseSIP
|
*identifyFormat
*validateFormat
*extractMetadata
*decidePreservationAction
|-
|prepareAIP
|
*gatherMetadata
*normalizeFiles
*createPackage
|-
|reviewAIP
|
*decideStorageAction
|-
|storeAIP
|
*writePackage
*replicatePackage
*auditFixity
*readPackage
*updatePackage
|-
|provideDIP
|
*uploadPackage
*updateMetadata
|-
|monitorPreservation
|
*updatePolicy
*migrateFormat
|}