蜜桃成人影片

Policy

The Valdosta State University Archives and Special Collections is committed to the responsible and sustainable management of digital assets.

1. Digital Preservation is a new field where best practices and international standards are still evolving. The Valdosta State University Archives and Special Collections long-term digital preservation policy is based on the Open Archival Information System (OAIS) reference model ISO 14721:2003.
2. Every effort will be utilized to preserved digital formats submitted to the Valdosta State University Archives and Special Collections. When submitting, we recommend following our recommended file formats guide to facilitate long-term preservation.
3. The Valdosta State University Archives and Special Collections will provide long-term access to submitted works, in addition to associated descriptive and administrative metadata, by a combined strategy combining the following:

• Secure Backups
• Storage Media Refreshment (Copying data from one storage medium to another)
• File Format Migration

Presently the Valdosta State University Archives and Special Collections is committed to preserving the bitstream (binary data). Functionality and appearance will be maintained as resources permit.

1. Works submitted to the Valdosta State University Archives and Special Collections will be assigned a if applicable.
2. This policy and other preservation-related activities will be reviewed annually to ensure best practices and techniques are adopted as technology and institutional practices evolve.

   ---

File Naming Conventions

The Valdosta State University Archives and Special Collections recommend the following guidelines for File naming.

Rule 1. Do not use special characters in the file name. Including: /:\*?”<>|(){}[]&,.$, etc…

The characters above are used by various electronic environments. For example, a forward slash identifies folder levels in Microsoft products, while macs use the colon. Periods are used to  denote file formats. Avoid using these characters which could result in file lost or errors.

Rule 2. Use underscores and hyphens instead of spaces.

Spaces are displayed in web environments as %20 and can create broken links and errors as a result. Use underscores to separate themes, descriptions, and other fields in a file name. Use hyphens instead of spaces to link words together.  Examples:  VSU File Naming Guide.docx becomes VSU%20 File%20Naming%20Guide.docx. Instead try: vsu_file-naming-guide.docx. 

Rule 3. Use lower case letters only.

Some operating systems and electronic environments distinguish between upper and lower case letters. As a precaution, use only lower case letters.

Rule 4. File names should be short. Err on the side of brevity.

Long file names are not compatible with older legacy systems. For example, files on a standard CD-ROM can have a maximum of eight characters, including the extension.  Additionally, when transferring data into another directory, the entire file path is counted towards the file name. With exceptionally long names, deep in a directory, files cannot be moved or transferred if they exceed 256 characters, including their file path. Generally, 25 characters should be sufficient. Remember, filenames do not have to be overly descriptive, that is what metadata is for.

Note: Always use a three-letter extension when applicable. For example .tiff should be .tif.

Rule 5. File names should be unique to an object*.

When objects are copied from their directory they should be identifiable on their own merits. For example if the tiff files under ms54//folklife/turpentine/images/0001.tif and ms899/photos/france/0001.tif were pulled from their directories they would appear identical and could prompt an overwrite. The correct way to name these files would be ms899_photos_germany_0001.tif, or an alpha-numeric code representing these fields. [*note: Digital objects can be made up of multiple files. See below.]

Records with Multiple Format Versions Multiple file formats of the same object should have the same name. For example, pc1928_p082.tif, pc1928_p082.pdf, and pc1928_p082.txt would all represent the same digital object. The first file would be the master tif, a pdf for access and usage, and a plain text document with the ocr data written in UTF-8 encoding.

If a single item has multiple digital objects, for example the front and back of a photograph, use a alpha-numeric system to distinguish linked objects. For example ms899-f101_001a.tif and ms899-f101_001b.tif.

Rule 6.  Include dates and format them consistently.

Use the to display dates. Either YYYY-MM-DD or YYYYMMDD. This format allows for easy sorting and can distinguish different versions of the same record, for example between a draft and a finalized document. You can add the date to the filename itself, or just the metadata. If you are unsure of the specific date use January 1 as the default.

Rule 7.  Be Consistent.

Abbreviations, date formats, and other key info should be agreed upon and utilized by all digital asset creators within a department. An easy way to keep track of this is to simply create "readme.txt" documents in folders explaining the naming format used- if it is unclear.

Rule 8.  Metadata

The Valdosta State University Archives and Special Collections highly recommends embedding metadata into your files. This can easily be done by right-clicking on a file in Windows and selecting “properties” and entering information into the fields and applying. Your can select multiple files at once to speed up the process. Additionally, in most file creation software, “properties” can be found under the “file” menu.  A minimum of author, title, date, and subject are desired.

Subjects and Keywords

The Valdosta State University Archives and Special Collections recommends following the list (LCSH) when possible. For photographs, the is recommended in addition to LCSH. For Geographical locations the (TGN) schema should be followed.  Academic and University related keywords can be found in the . Abbreviations can be found at .

File Formats