Metadata - Revision history

Kgmatheny at 16:41, 19 December 2012

2012-12-19T16:41:13Z

←Older revision		Revision as of 16:41, 19 December 2012
Line 31:		Line 31:

	* '''Descriptive metadata''' is the most common type of metadata, the one that most people have used. It is data that describes and identifies digital objects whether they were orginally physical artifacts or born digitally. After combining the metadata currently in use for all of our collections, we wound up with an 87-field spreadsheet template: ([[Image:DescriptiveMetadata.xls]]). We are currently mapping all these fields ([[Image:MASTER_LIST_for_Metadata_Fields_in_CONTENTdm_(instructions).docx‎]]) to MODS, and then will be transforming each item's metadata to a MODS XML file for both online delivery and long-term storage. The current mapping can be found on the following page, with each spreadsheet column name in place of the contents of that column's field for an item: [[MODS_Mockup]]		* '''Descriptive metadata''' is the most common type of metadata, the one that most people have used. It is data that describes and identifies digital objects whether they were orginally physical artifacts or born digitally. After combining the metadata currently in use for all of our collections, we wound up with an 87-field spreadsheet template: ([[Image:DescriptiveMetadata.xls]]). We are currently mapping all these fields ([[Image:MASTER_LIST_for_Metadata_Fields_in_CONTENTdm_(instructions).docx‎]]) to MODS, and then will be transforming each item's metadata to a MODS XML file for both online delivery and long-term storage. The current mapping can be found on the following page, with each spreadsheet column name in place of the contents of that column's field for an item: [[MODS_Mockup]]
-
-
-	[[Instructions]]
-
-
	* '''Administrative metadata''' is used to manage and administer. It is an umbrella term for the following:		* '''Administrative metadata''' is used to manage and administer. It is an umbrella term for the following:
	** '''[[Technical metadata]]''' provides specifications that describes the generation of the digital object including reformatting history. It is used to manage and migrate digital objects.		** '''[[Technical metadata]]''' provides specifications that describes the generation of the digital object including reformatting history. It is used to manage and migrate digital objects.
Line 54:		Line 49:

	[[Descriptive metadata\|List of Our Standardized Descriptive Metadata Fields]]		[[Descriptive metadata\|List of Our Standardized Descriptive Metadata Fields]]
		+
		+	[[Instructions\|Instructions for creating metadata, if none is supplied]]

	[[Collection_Information\|Creating collection xml file]]		[[Collection_Information\|Creating collection xml file]]

Jlderidder: /* Manuscripts Manuscript Collections */

2012-12-18T16:36:14Z

Manuscripts Manuscript Collections

←Older revision		Revision as of 16:36, 18 December 2012
Line 78:		Line 78:
	====[[Photo Collections Metadata\|Photo Collections]]====		====[[Photo Collections Metadata\|Photo Collections]]====

-	====[[Manuscripts Manuscript Collections]]====	+	====[[Manuscripts \|Manuscript Collections]]====

	===Templates===		===Templates===

	Metadata for all collections are entered using the same template in EXCEL. Not all of the fields will be used for one collection. Fields (columns) in the EXCEL template may be hidden to facilitate data entry. By hiding fields, the template specifications can be made for one type of object (manuscripts, photographs, audio recordings, etc.). This is specially helpful when a collection only has one type of object. For collections that contain a variety of types, it is best to use the template without any hidden fields.		Metadata for all collections are entered using the same template in EXCEL. Not all of the fields will be used for one collection. Fields (columns) in the EXCEL template may be hidden to facilitate data entry. By hiding fields, the template specifications can be made for one type of object (manuscripts, photographs, audio recordings, etc.). This is specially helpful when a collection only has one type of object. For collections that contain a variety of types, it is best to use the template without any hidden fields.

Jlderidder: /* Manuscript Collections */

2012-12-18T16:35:50Z

Manuscript Collections

←Older revision		Revision as of 16:35, 18 December 2012
Line 78:		Line 78:
	====[[Photo Collections Metadata\|Photo Collections]]====		====[[Photo Collections Metadata\|Photo Collections]]====

-	====[[Manuscripts ~~Metadata\|~~Manuscript Collections]]====	+	====[[Manuscripts Manuscript Collections]]====

	===Templates===		===Templates===

	Metadata for all collections are entered using the same template in EXCEL. Not all of the fields will be used for one collection. Fields (columns) in the EXCEL template may be hidden to facilitate data entry. By hiding fields, the template specifications can be made for one type of object (manuscripts, photographs, audio recordings, etc.). This is specially helpful when a collection only has one type of object. For collections that contain a variety of types, it is best to use the template without any hidden fields.		Metadata for all collections are entered using the same template in EXCEL. Not all of the fields will be used for one collection. Fields (columns) in the EXCEL template may be hidden to facilitate data entry. By hiding fields, the template specifications can be made for one type of object (manuscripts, photographs, audio recordings, etc.). This is specially helpful when a collection only has one type of object. For collections that contain a variety of types, it is best to use the template without any hidden fields.

Kgmatheny: /* Procedures and Policies */

2012-09-12T17:01:29Z

Procedures and Policies

←Older revision		Revision as of 17:01, 12 September 2012
Line 55:		Line 55:
	[[Descriptive metadata\|List of Our Standardized Descriptive Metadata Fields]]		[[Descriptive metadata\|List of Our Standardized Descriptive Metadata Fields]]

-	[[Collection_Information]]	+	[[Collection_Information\|Creating collection xml file]]

	[[Linking out from EADS]]		[[Linking out from EADS]]

Scpstu32 at 19:38, 19 August 2010

2010-08-19T19:38:41Z

←Older revision		Revision as of 19:38, 19 August 2010
Line 31:		Line 31:

	* '''Descriptive metadata''' is the most common type of metadata, the one that most people have used. It is data that describes and identifies digital objects whether they were orginally physical artifacts or born digitally. After combining the metadata currently in use for all of our collections, we wound up with an 87-field spreadsheet template: ([[Image:DescriptiveMetadata.xls]]). We are currently mapping all these fields ([[Image:MASTER_LIST_for_Metadata_Fields_in_CONTENTdm_(instructions).docx‎]]) to MODS, and then will be transforming each item's metadata to a MODS XML file for both online delivery and long-term storage. The current mapping can be found on the following page, with each spreadsheet column name in place of the contents of that column's field for an item: [[MODS_Mockup]]		* '''Descriptive metadata''' is the most common type of metadata, the one that most people have used. It is data that describes and identifies digital objects whether they were orginally physical artifacts or born digitally. After combining the metadata currently in use for all of our collections, we wound up with an 87-field spreadsheet template: ([[Image:DescriptiveMetadata.xls]]). We are currently mapping all these fields ([[Image:MASTER_LIST_for_Metadata_Fields_in_CONTENTdm_(instructions).docx‎]]) to MODS, and then will be transforming each item's metadata to a MODS XML file for both online delivery and long-term storage. The current mapping can be found on the following page, with each spreadsheet column name in place of the contents of that column's field for an item: [[MODS_Mockup]]
		+

	[[Instructions]]		[[Instructions]]

Scpstu32: /* Full template */

2010-08-19T19:37:54Z

Full template

←Older revision		Revision as of 19:37, 19 August 2010
Line 82:		Line 82:

	Metadata for all collections are entered using the same template in EXCEL. Not all of the fields will be used for one collection. Fields (columns) in the EXCEL template may be hidden to facilitate data entry. By hiding fields, the template specifications can be made for one type of object (manuscripts, photographs, audio recordings, etc.). This is specially helpful when a collection only has one type of object. For collections that contain a variety of types, it is best to use the template without any hidden fields.		Metadata for all collections are entered using the same template in EXCEL. Not all of the fields will be used for one collection. Fields (columns) in the EXCEL template may be hidden to facilitate data entry. By hiding fields, the template specifications can be made for one type of object (manuscripts, photographs, audio recordings, etc.). This is specially helpful when a collection only has one type of object. For collections that contain a variety of types, it is best to use the template without any hidden fields.
-
-	====Full template====

Scpstu32 at 19:37, 19 August 2010

2010-08-19T19:37:11Z

←Older revision		Revision as of 19:37, 19 August 2010
Line 78:		Line 78:

	====[[Manuscripts Metadata\|Manuscript Collections]]====		====[[Manuscripts Metadata\|Manuscript Collections]]====
-
-	====[[Audio Collections Metadata\|Audio Collections]]====

	===Templates===		===Templates===

Jlderidder at 15:39, 28 January 2010

2010-01-28T15:39:00Z

←Older revision		Revision as of 15:39, 28 January 2010
Line 31:		Line 31:

	* '''Descriptive metadata''' is the most common type of metadata, the one that most people have used. It is data that describes and identifies digital objects whether they were orginally physical artifacts or born digitally. After combining the metadata currently in use for all of our collections, we wound up with an 87-field spreadsheet template: ([[Image:DescriptiveMetadata.xls]]). We are currently mapping all these fields ([[Image:MASTER_LIST_for_Metadata_Fields_in_CONTENTdm_(instructions).docx‎]]) to MODS, and then will be transforming each item's metadata to a MODS XML file for both online delivery and long-term storage. The current mapping can be found on the following page, with each spreadsheet column name in place of the contents of that column's field for an item: [[MODS_Mockup]]		* '''Descriptive metadata''' is the most common type of metadata, the one that most people have used. It is data that describes and identifies digital objects whether they were orginally physical artifacts or born digitally. After combining the metadata currently in use for all of our collections, we wound up with an 87-field spreadsheet template: ([[Image:DescriptiveMetadata.xls]]). We are currently mapping all these fields ([[Image:MASTER_LIST_for_Metadata_Fields_in_CONTENTdm_(instructions).docx‎]]) to MODS, and then will be transforming each item's metadata to a MODS XML file for both online delivery and long-term storage. The current mapping can be found on the following page, with each spreadsheet column name in place of the contents of that column's field for an item: [[MODS_Mockup]]
		+
		+	[[Instructions]]
		+
		+
	* '''Administrative metadata''' is used to manage and administer. It is an umbrella term for the following:		* '''Administrative metadata''' is used to manage and administer. It is an umbrella term for the following:
	** '''[[Technical metadata]]''' provides specifications that describes the generation of the digital object including reformatting history. It is used to manage and migrate digital objects.		** '''[[Technical metadata]]''' provides specifications that describes the generation of the digital object including reformatting history. It is used to manage and migrate digital objects.

Malexand: /* Templates */

2009-12-16T21:46:30Z

Templates

←Older revision		Revision as of 21:46, 16 December 2009
Line 77:		Line 77:
	====[[Audio Collections Metadata\|Audio Collections]]====		====[[Audio Collections Metadata\|Audio Collections]]====

-	====Templates====	+	===Templates===

	Metadata for all collections are entered using the same template in EXCEL. Not all of the fields will be used for one collection. Fields (columns) in the EXCEL template may be hidden to facilitate data entry. By hiding fields, the template specifications can be made for one type of object (manuscripts, photographs, audio recordings, etc.). This is specially helpful when a collection only has one type of object. For collections that contain a variety of types, it is best to use the template without any hidden fields.		Metadata for all collections are entered using the same template in EXCEL. Not all of the fields will be used for one collection. Fields (columns) in the EXCEL template may be hidden to facilitate data entry. By hiding fields, the template specifications can be made for one type of object (manuscripts, photographs, audio recordings, etc.). This is specially helpful when a collection only has one type of object. For collections that contain a variety of types, it is best to use the template without any hidden fields.
		+
		+	====Full template====

Malexand: /* Templates */

2009-12-16T21:45:06Z

Templates

←Older revision		Revision as of 21:45, 16 December 2009
Line 79:		Line 79:
	====Templates====		====Templates====

-	Metadata for all collections are entered using the same template. Not all of the fields will be used. Fields (columns) in the EXCEL template may be hidden to facilitate data entry. By hiding fields, ~~you may make a~~ template ~~facilitate data entry~~ for ~~collections that are comprised of~~ one type of object (manuscripts, photographs, audio recordings, etc.)	+	Metadata for all collections are entered using the same template in EXCEL. Not all of the fields will be used for one collection. Fields (columns) in the EXCEL template may be hidden to facilitate data entry. By hiding fields, the template specifications can be made for one type of object (manuscripts, photographs, audio recordings, etc.). This is specially helpful when a collection only has one type of object. For collections that contain a variety of types, it is best to use the template without any hidden fields.