UM Transfer metadata import - Revision history

Courtney at 00:37, 15 January 2014

2014-01-15T00:37:55Z

Courtney at 23:47, 30 September 2013

2013-09-30T23:47:52Z

Courtney at 23:47, 30 September 2013

2013-09-30T23:47:31Z

Evelyn at 19:15, 3 June 2013

2013-06-03T19:15:32Z

Courtney at 20:27, 30 April 2013

2013-04-30T20:27:18Z

Courtney at 20:19, 30 April 2013

2013-04-30T20:19:22Z

Courtney: Created page with "Main Page > Documentation > User manual > User manual 0.10 > Transfer > Metadata import This page documents the workflow and METS ..."

2013-04-30T20:09:56Z

Created page with "Main Page > Documentation > User manual > User manual 0.10 > Transfer > Metadata import This page documents the workflow and METS ..."

New page

[[Main Page]] > [[Documentation]] > [[User Manual|User manual]] > [[User manual 0.10]] > [[UM_transfer|Transfer]] > Metadata import

This page documents the workflow and METS content for lower-level metadata import - i.e. metadata to be attached to subdirectories and files within a SIP.

==Workflow==

#For simple objects, the user places files in the objects directory, with or without intervening subdirectories. The imported metadata are attached to each object.
#For compound objects, the user creates one or more subdirectories in the objects directory, each containing the files that form a compound object. The imported metadata are attached to each subdirectory.
#*The subdirectory names must not contain spaces or other forbidden characters.
#The user adds a csv file to the metadata folder for the transfer entitled ''metadata.csv''
#*The first row of the csv file consists of field names. Field names must not include spaces.
#*Dublin Core field names must contain the "dc" element in the name, eg "dc.title"
#*Each subsequent row contains the complete set of field values for a single directory or file
#*For multi-value fields (such as dc.subject), the entire column is repeated and each column contains a single value
#*If the metadata are for simple objects, the csv file must contain a "filename" column listing the filepath and filename of each objects: eg "objects/BrocktonOval.jp2"
#*If the metadata are for compound objects, the csv file must contain a "parts" column listing the names of the directories containing the items that form the compound object: eg "objects/Jan021964"
#*Note that filenames can be duplicates of filenames in other subdirectories if desired. For example, the name "page01.jp2" can occur in multiple subdirectories.
#At the generate METS micro-service, Archivematica parses the metadata in ''metadata.csv'' to the METS file, as follows:
#*All Dublin Core elements are used to generate a dmdSec for each directory or file with MDTYPE="DC"
#*All non-Dublin Core elements are used to generate a dmdSec for each directory or file with MDTYPE="OTHER" OTHERMDTYPE="CUSTOM"
#*The dmdSecs are linked to their directories or files in the structMap

</br>

==Simple objects==

This section provides csv file and METS file examples for simple objects - i.e. individual files that are not pages in a compound object such as a book or a newspaper issue.

===CSV file===

'''Sample headings and values'''

{| border="1" cellpadding="10" cellspacing="0" width="100%"
|-
!'''filename'''
!'''dc.title'''
!'''dcterms.issued'''
!'''dc.publisher'''
!'''dc.contributor'''
!'''dc.subject'''
!'''dc.subject'''
!'''dc.date'''
!'''dc.description'''
!'''notes'''
!'''dcterms.isPartOf'''
!'''repository'''
!'''dc.rights'''
!'''project_website'''
!'''dc.format'''
|-
|objects/BrocktonOval.jp2
|Stanley Park in December
|1996-01-17
|Riley Studios, Vancouver BC
|Don Langfield, photographer
|Vancouver (B.C.)--Parks
|Landscapes
|1992/12/04
|Image shows Brockton Oval after light snowfall
|Originally part of series entitled "Winter in Vancouver"
|Riley Studios collection
|New Caledonia Public Library
|Copyright held by Riley Studios
|http://www.ncpl/donlangfieldphotographs.ca
|image/jp2
|-
|objects/QE Park sunset.jp2
|Sunset in Queen Elizabeth Park
|
|Riley Studios, Vancouver BC
|Don Langfield, photographer
|Vancouver (B.C.)--Parks
|
|1994/07/13
|
|
|Riley Studios collection
|New Caledonia Public Library
|Copyright held by Riley Studios
|http://www.ncpl/donlangfieldphotographs.ca
|image/jp2
|-
|}

</br>

===METS file===

[[File:mets_1g.png|980px|thumb|center|]]
[[File:mets_2g.png|980px|thumb|center|]]
[[File:mets_3g.png|980px|thumb|center|]]

==Compound objects==

This section provides csv file and METS file examples for compound objects - i.e. multi-page digital objects such as newspapers and books.

===CSV file===

'''Sample headings and values'''

{| border="1" cellpadding="10" cellspacing="0" width="100%"
|-
!'''parts'''
!'''dc.title'''
!'''alternative_title'''
!'''dc.publisher'''
!'''dates_of_publication'''
!'''dc.subject'''
!'''dc.date'''
!'''dc.description'''
!'''frequency'''
!'''dc.language'''
!'''forms_part_of'''
!'''repository'''
!'''project_website'''
!'''digital_file_format'''
|-
|objects/Jan021964
|Coast News, January 02, 1964
|Sunshine Coast News
|Fred Cruice
|1945-1995
|Gibsons (B.C.)--Newspapers
|1964/01/02
|Serving the Growing Sunshine Coast
|Weekly
|English
|British Columbia Historical Newspapers collection
|Sunshine Coast Museum and Archives
|http://historicalnewspapers.library.ubc.ca
|image/jp2
|-
|objects/Jan091964
|Coast News, January 09, 1964
|Sunshine Coast News
|Fred Cruice
|1945-1995
|Gibsons (B.C.)--Newspapers
|1964/01/09
|Serving the Growing Sunshine Coast
|Weekly
|English
|British Columbia Historical Newspapers collection
|Sunshine Coast Museum and Archives
|http://historicalnewspapers.library.ubc.ca
|image/jp2
|-
|}

</br>

</br>

===METS file===

[[File:mets_4g.png|980px|thumb|center|]]
[[File:mets_5g.png|980px|thumb|center|]]
[[File:mets_6g.png|980px|thumb|center|]]

__NOTOC__

@@ Line 1: / Line 1: @@
 [[Main Page]] > [[Documentation]] > [[User manual 0.10|User manual]] > [[UM_transfer|Transfer]] > Metadata import
-This page documents the workflow and METS content for lower-level metadata import - i.e. metadata to be attached to subdirectories and files within a SIP.
+This page documents the workflow and METS content for lower-level metadata import for DIP upload to AtoM. - i.e. metadata to be attached to subdirectories and files within a SIP.
 ==Workflow==

← Older revision		Revision as of 23:47, 30 September 2013
Line 1:		Line 1:
−	[[Main Page]] > [[Documentation~~]] > [[User Manual\|User manual~~]] > [[User manual 0.10\|User manual]] > [[UM_transfer\|Transfer]] > Metadata import	+	[[Main Page]] > [[Documentation]] > [[User manual 0.10\|User manual]] > [[UM_transfer\|Transfer]] > Metadata import

	This page documents the workflow and METS content for lower-level metadata import - i.e. metadata to be attached to subdirectories and files within a SIP.		This page documents the workflow and METS content for lower-level metadata import - i.e. metadata to be attached to subdirectories and files within a SIP.

← Older revision		Revision as of 23:47, 30 September 2013
Line 1:		Line 1:
−	[[Main Page]] > [[Documentation]] > [[User Manual\|User manual]] > [[User manual 0.10]] > [[UM_transfer\|Transfer]] > Metadata import	+	[[Main Page]] > [[Documentation]] > [[User Manual\|User manual]] > [[User manual 0.10\|User manual]] > [[UM_transfer\|Transfer]] > Metadata import

	This page documents the workflow and METS content for lower-level metadata import - i.e. metadata to be attached to subdirectories and files within a SIP.		This page documents the workflow and METS content for lower-level metadata import - i.e. metadata to be attached to subdirectories and files within a SIP.

@@ Line 7: / Line 7: @@
 #For simple objects, the user places files in the objects directory, with or without intervening subdirectories. The imported metadata are attached to each object.
 #For compound objects, the user creates one or more subdirectories in the objects directory, each containing the files that form a compound object. The imported metadata are attached to each subdirectory.
-#*The subdirectory names must not contain spaces or other forbidden characters.
+#*'''The subdirectory names must not contain spaces or other forbidden characters.'''
 #The user adds a csv file to the metadata folder for the transfer entitled ''metadata.csv'' ('''figure 1''')
-#*The first row of the csv file consists of field names. Field names must not include spaces. ('''figure 2''')
+#*The first row of the csv file consists of field names. '''Field names must not include spaces.''' ('''figure 2''')
 #*Dublin Core field names must contain the "dc" element in the name, eg "dc.title"
 #*Each subsequent row contains the complete set of field values for a single directory or file

@@ Line 20: / Line 20: @@
 #*All non-Dublin Core elements are used to generate a dmdSec for each directory or file with MDTYPE="OTHER" OTHERMDTYPE="CUSTOM"
 #*The dmdSecs are linked to their directories or files in the structMap
 </br>