Re: diglib: file naming conventions

[Sara Brownmiller <snb@darkwing.uoregon.edu>]

I think it will be easier to obtain cooperation/compliance if policies
about naming conventions have been adopted by DCC.  So I would support a
discussion of this at a future DCC.  It would be useful to have some
examples of filenames that have created problems and why.

Sara

Sara Brownmiller			University of Oregon Libraries
Director, Library Systems 		1299 University of Oregon
Women's Studies Librarian		Eugene, OR  97403-1299
					541/346-2368 (voice)
snb@uoregon.edu				541/346-3485 (fax)

On Mon, 10 Jan 2005, Carol Hixson wrote:

> We've been having some discussions recently in
> MDLS about appropriate file names and making some
> changes to some file names used for our digital collections.
> We often deal with files created by different units
> and the file names are sometimes problematic.
>
> The MSU Guidelines provide some guidance on
> FOLDER naming conventions for folders on the
> MSU. Those state:
>
>
> "The project manager creates the name for the folder
> following the guidelines that the name should:
>     * Reflect the content of the project.
>     * Be reasonably short (three to fifteen characters)
>     * Use lower case characters.
>     * Not contain blank spaces.
>     * Not contain non-alphanumeric characters (except hyphens). "
> I think it would be useful to have some file naming conventions but
> am not sure that they would be identical to the folder naming
> conventions. For instance, the first one isn't practical when dealing
> with large sets of digital images from the same photograph collection.
>
> Question for the group: do we want to revise the MSU guidelines to
> include some file naming recommendations or should MDLS just
> handle that internally?
>
> Carol
>