Organization of completed content for long-term storage - Revision history

Jlderidder: /* OTHER SUBFOLDERS IN EACH OF THE ABOVE */

Jlderidder — Tue, 24 Jul 2012 18:30:58 GMT

OTHER SUBFOLDERS IN EACH OF THE ABOVE

←Older revision		Revision as of 18:30, 24 July 2012
Line 39:		Line 39:
	''We have since decided that OCR text is not archival content, since it can be generated by script, and since OCR software keeps improving. If we correct the OCR by hand (changing the extension from ".ocr.txt" to simply ".txt" and retaining it in the Transcripts directory at the applicable level) then the human-corrected transcript is worth archiving and will be kept. The OCR, however, will be only kept in the delivery system.''		''We have since decided that OCR text is not archival content, since it can be generated by script, and since OCR software keeps improving. If we correct the OCR by hand (changing the extension from ".ocr.txt" to simply ".txt" and retaining it in the Transcripts directory at the applicable level) then the human-corrected transcript is worth archiving and will be kept. The OCR, however, will be only kept in the delivery system.''

-	===C) Metadata===	+	===C) Supplemental===
		+	* Electronic Theses and Dissertations, and Undergraduate Research Papers, are often submitted with supplemental files. These aren't component files, although they are named as if they are "pages" within the item. Since, however, they are supplemental files for the item itself, the Supplemental directory normally resides at the item level, and these "page" numbered files are deposited within that directory. This provides the delivery system with additional information to inform rendering, and it also provides clarity for those reconstructing our content as to what files are supplemental to what level of content.
		+
		+	===D) Metadata===
	* If a METS file is available to organize the metadata and tag it with appropriate namespaces, that is ideal. This METS file should have xlinks to the archival quality bitstreams. Within the metadata folder, filenames should be adapted according to the type of metadata they contain: type followed by underscore, followed by version. The following shorthand is to be used:		* If a METS file is available to organize the metadata and tag it with appropriate namespaces, that is ideal. This METS file should have xlinks to the archival quality bitstreams. Within the metadata folder, filenames should be adapted according to the type of metadata they contain: type followed by underscore, followed by version. The following shorthand is to be used:
	** qdc for qualified Dublin Core		** qdc for qualified Dublin Core

Jlderidder: /* B) Transcripts */

Jlderidder — Tue, 09 Feb 2010 14:56:14 GMT

B) Transcripts

←Older revision		Revision as of 14:56, 9 February 2010
Line 35:		Line 35:
	* Within the Transcripts folder, files should be named for the item transcribed and should be in ASCII text or UTF-8 text. If the file is OCR, include .ocr before the .txt extension. For example, u0003_0000580_0000002.ocr.txt would be the OCR for item 2 in the Hoole Manuscripts (u0003) MSS 580 collection (0000580). Transcripts should be stored at the level to which they belong, just like metadata -- that is, if this is the transcript for item 2, it should be in item 2's directory, in a subdirectory named Transcripts.		* Within the Transcripts folder, files should be named for the item transcribed and should be in ASCII text or UTF-8 text. If the file is OCR, include .ocr before the .txt extension. For example, u0003_0000580_0000002.ocr.txt would be the OCR for item 2 in the Hoole Manuscripts (u0003) MSS 580 collection (0000580). Transcripts should be stored at the level to which they belong, just like metadata -- that is, if this is the transcript for item 2, it should be in item 2's directory, in a subdirectory named Transcripts.

		+	'''NOTE:'''
		+
		+	''We have since decided that OCR text is not archival content, since it can be generated by script, and since OCR software keeps improving. If we correct the OCR by hand (changing the extension from ".ocr.txt" to simply ".txt" and retaining it in the Transcripts directory at the applicable level) then the human-corrected transcript is worth archiving and will be kept. The OCR, however, will be only kept in the delivery system.''

	===C) Metadata===		===C) Metadata===

Jlderidder at 16:00, 19 November 2009

Jlderidder — Thu, 19 Nov 2009 16:00:09 GMT

←Older revision		Revision as of 16:00, 19 November 2009
Line 1:		Line 1:
	As we expand our holdings to multiple collections, and content from different sources beyond Hoole, we need to organize files and folders in a systematic manner. The following solution follows a simple rule: '''replace the underscore in a file name with a forward slash, to determine the appropriate directory location for the file'''.		As we expand our holdings to multiple collections, and content from different sources beyond Hoole, we need to organize files and folders in a systematic manner. The following solution follows a simple rule: '''replace the underscore in a file name with a forward slash, to determine the appropriate directory location for the file'''.
		+
		+	[[Image:Figure_1.jpg]]

	Based on the [[File_naming_schemes\|File Naming Schemes]] we selected,		Based on the [[File_naming_schemes\|File Naming Schemes]] we selected,

Jlderidder: /* 4) By sequence for delivery */

Jlderidder — Thu, 19 Nov 2009 15:59:21 GMT

4) By sequence for delivery

←Older revision		Revision as of 15:59, 19 November 2009
Line 20:		Line 20:
	In the 5th level (within the folders on the 4th level), folders will be named according to the 4th set of numbers in the filename: after the 3rd underscore, and preceding the 4th underscore or the period and filename extension. This is the number assigned to the sequence of delivery for the files within the item. In the file name u0004_0002061_0000345_0003.tif, "0003" indicates the 3rd image in a sequence, so the directory /u0004/0002061/0000345/0003/ will contain this tiff and all information associated with it.		In the 5th level (within the folders on the 4th level), folders will be named according to the 4th set of numbers in the filename: after the 3rd underscore, and preceding the 4th underscore or the period and filename extension. This is the number assigned to the sequence of delivery for the files within the item. In the file name u0004_0002061_0000345_0003.tif, "0003" indicates the 3rd image in a sequence, so the directory /u0004/0002061/0000345/0003/ will contain this tiff and all information associated with it.
	* note that if there are subpages, such as in a scrapbook, there will be an additional level beneath this one, using the same reasoning.		* note that if there are subpages, such as in a scrapbook, there will be an additional level beneath this one, using the same reasoning.
		+
		+	[[Image:Figure_5.jpg]]

	== OTHER SUBFOLDERS IN EACH OF THE ABOVE ==		== OTHER SUBFOLDERS IN EACH OF THE ABOVE ==

Jlderidder at 15:57, 19 November 2009

Jlderidder — Thu, 19 Nov 2009 15:57:46 GMT

←Older revision		Revision as of 15:57, 19 November 2009
Line 41:		Line 41:
	** ead for EAD (Encoded Archival Description)		** ead for EAD (Encoded Archival Description)

-	Versions of metadata will be tracked in the database (saved as flat file regularly in the top set of directories.	+	Versions of metadata will be tracked in the database (saved as flat file regularly in the top set of directories).

	Note that the metadata record is stored at the appropriate level: an EAD would be stored at the collection level, as it is a collection level record.		Note that the metadata record is stored at the appropriate level: an EAD would be stored at the collection level, as it is a collection level record.
		+
		+	[[Image:Figure_7.jpg]]
		+

	Thus, /u0004/2061/Metadata/ may contain u0004_2061.mods.xml and u0004_2061.ead.xml and u0004_2061.dc.xml each containing collection-level metadata about collection 2061.		Thus, /u0004/2061/Metadata/ may contain u0004_2061.mods.xml and u0004_2061.ead.xml and u0004_2061.dc.xml each containing collection-level metadata about collection 2061.

Jlderidder at 22:38, 4 November 2009

Jlderidder — Wed, 04 Nov 2009 22:38:01 GMT

←Older revision		Revision as of 22:38, 4 November 2009
Line 28:		Line 28:
	This directory holds administrative information.		This directory holds administrative information.

-	===B) ~~Text~~===	+	===B) Transcripts===
-	* Within the ~~text~~ folder, ~~subfolders~~ should be named ~~"ocr"~~ for ~~ocr text in ascii or unicode; "~~transcribed~~" for transcribed text in ascii or unicode. All text~~ should be ~~stored either as xml~~ or ~~plain~~ text (.txt ~~files~~).	+	* Within the Transcripts folder, files should be named for the item transcribed and should be in ASCII text or UTF-8 text. If the file is OCR, include .ocr before the .txt extension. For example, u0003_0000580_0000002.ocr.txt would be the OCR for item 2 in the Hoole Manuscripts (u0003) MSS 580 collection (0000580). Transcripts should be stored at the level to which they belong, just like metadata -- that is, if this is the transcript for item 2, it should be in item 2's directory, in a subdirectory named Transcripts.
-	~~This will enable us to identify text which may~~ be ~~poor as opposed~~ to ~~better quality.~~ ~~If the text~~ is ~~ocr text which has been remediated~~, it should be ~~stored as "transcribed"~~.	+

	===C) Metadata===		===C) Metadata===

Jlderidder at 21:13, 1 July 2009

Jlderidder — Wed, 01 Jul 2009 21:13:26 GMT

←Older revision		Revision as of 21:13, 1 July 2009
Line 1:		Line 1:
	As we expand our holdings to multiple collections, and content from different sources beyond Hoole, we need to organize files and folders in a systematic manner. The following solution follows a simple rule: '''replace the underscore in a file name with a forward slash, to determine the appropriate directory location for the file'''.		As we expand our holdings to multiple collections, and content from different sources beyond Hoole, we need to organize files and folders in a systematic manner. The following solution follows a simple rule: '''replace the underscore in a file name with a forward slash, to determine the appropriate directory location for the file'''.

-	Based on the [[~~http://intranet.lib.ua.edu/wiki/digcoll/index.php/~~File_naming_schemes\|File Naming Schemes]] we selected,	+	Based on the [[File_naming_schemes\|File Naming Schemes]] we selected,

	Within a specified directory on a slow server (to reduce risk of damage and corruption by access):		Within a specified directory on a slow server (to reduce risk of damage and corruption by access):

Jlderidder: /* I propose the following organization for materials that we have already digitized: */

Jlderidder — Wed, 10 Jun 2009 21:02:42 GMT

I propose the following organization for materials that we have already digitized:

←Older revision		Revision as of 21:02, 10 June 2009
Line 2:		Line 2:

	Based on the [[http://intranet.lib.ua.edu/wiki/digcoll/index.php/File_naming_schemes\|File Naming Schemes]] we selected,		Based on the [[http://intranet.lib.ua.edu/wiki/digcoll/index.php/File_naming_schemes\|File Naming Schemes]] we selected,
-	~~==I propose the following organization for materials that we have already digitized:==~~	+
	Within a specified directory on a slow server (to reduce risk of damage and corruption by access):		Within a specified directory on a slow server (to reduce risk of damage and corruption by access):

Jlderidder: /* B) text */

Jlderidder — Wed, 10 Jun 2009 21:02:25 GMT

B) text

←Older revision		Revision as of 21:02, 10 June 2009
Line 28:		Line 28:
	This directory holds administrative information.		This directory holds administrative information.

-	===B) ~~text~~===	+	===B) Text===
	* Within the text folder, subfolders should be named "ocr" for ocr text in ascii or unicode; "transcribed" for transcribed text in ascii or unicode. All text should be stored either as xml or plain text (.txt files).		* Within the text folder, subfolders should be named "ocr" for ocr text in ascii or unicode; "transcribed" for transcribed text in ascii or unicode. All text should be stored either as xml or plain text (.txt files).
	This will enable us to identify text which may be poor as opposed to better quality. If the text is ocr text which has been remediated, it should be stored as "transcribed".		This will enable us to identify text which may be poor as opposed to better quality. If the text is ocr text which has been remediated, it should be stored as "transcribed".

Jlderidder: /* A) documentation */

Jlderidder — Wed, 10 Jun 2009 21:02:14 GMT

A) documentation

←Older revision		Revision as of 21:02, 10 June 2009
Line 23:		Line 23:
	== OTHER SUBFOLDERS IN EACH OF THE ABOVE ==		== OTHER SUBFOLDERS IN EACH OF THE ABOVE ==
	Each of the levels above may contain any or all of the following folders:		Each of the levels above may contain any or all of the following folders:
-	===A) ~~documentation~~ ===	+	===A) Documentation ===
	* Note: All documentation needs to be in unicode or ascii xml or plain text.		* Note: All documentation needs to be in unicode or ascii xml or plain text.