Difference between revisions of "Talk:Best Practices for TEI in Libraries"
Jump to navigation
Jump to search
(cleared out all this old stuff) |
(New section: Possible expanded filename recommendations) |
||
| Line 1: | Line 1: | ||
| + | == Possible expanded filename recommendations == | ||
| + | Standardized file naming for a particular encoding project is key for reliable online storage and delivery of these files. Consider the following best practices when determining the file name scheme for your project: | ||
| + | |||
| + | * Each filename should contain an identifier that uniquely specifies a single digital object within the parent collection (e.g., a parent collection of text, images and other related materials) | ||
| + | * Each filename should be fully specified. It should not just be a sequence number that is dependent on location within a directory structure for context | ||
| + | * Filenames should not include spaces | ||
| + | * Filenames should following a predicatble case constructions (e.g., all lowercase, camelCase, etc.) | ||
| + | * The first character of the filename should be an ASCII letter ('a' through 'z' or 'A' through 'Z') to comply with current restrictions on identifiers by many programming and metadata languages such as METS | ||
| + | * The "base" filename may include only ASCII letters ('a' through 'z' and 'A' through 'Z'), ASCII digits ('0' through '9'), hyphens, underscores, and periods. Refrain from using other characters and limit period usage to only once (to separate base name from file extensions). | ||
| + | |||
| + | For those saving files to CD-ROM for storage or file transfer, file naming should follow ISO 9660 conventions: 8-character filenames, 3-character extensions, using A-Z, a-z, 0-9, underscores and hyphens. | ||
Revision as of 00:33, 11 May 2009
Possible expanded filename recommendations
Standardized file naming for a particular encoding project is key for reliable online storage and delivery of these files. Consider the following best practices when determining the file name scheme for your project:
- Each filename should contain an identifier that uniquely specifies a single digital object within the parent collection (e.g., a parent collection of text, images and other related materials)
- Each filename should be fully specified. It should not just be a sequence number that is dependent on location within a directory structure for context
- Filenames should not include spaces
- Filenames should following a predicatble case constructions (e.g., all lowercase, camelCase, etc.)
- The first character of the filename should be an ASCII letter ('a' through 'z' or 'A' through 'Z') to comply with current restrictions on identifiers by many programming and metadata languages such as METS
- The "base" filename may include only ASCII letters ('a' through 'z' and 'A' through 'Z'), ASCII digits ('0' through '9'), hyphens, underscores, and periods. Refrain from using other characters and limit period usage to only once (to separate base name from file extensions).
For those saving files to CD-ROM for storage or file transfer, file naming should follow ISO 9660 conventions: 8-character filenames, 3-character extensions, using A-Z, a-z, 0-9, underscores and hyphens.
