File Naming Conventions

Per PARADISEC file naming rules, file names should be uppercase.  File extensions should be lowercase. Hyphens are special operators, used to separate the parts of the file name so should not be used. The two hyphens contained in the following examples illustrate their use as special operators for PARADISEC. If you must use a separator, an underscore is acceptable ( _ ). Do not use spaces. More information on file-naming conventions can be found following the above link to the PARADISEC website.


Additional examples of item organization and file naming

Below is an example of a set of recordings collected to address multilingualism in the village of Bimadbn, PNG. The collection will include wordlist data for lexical and phonetic comparison, sociolinguistic interviews, and natural speech in the form of narratives, personal histories, procedurals, etc., in 4 different languages spoken in the village. Information on the subject and content languages will appear in the relevent metadata item description fields; it is unnecessary to have that information in the file name. I have chosen to use very basic item names: 001, 002, 003, knowing that the specific information of the content will be contained in the metadata. 


Why careful file naming is important

Files are automatically sent to specific locations within our archive structure. The first part of the file name (JCM1) tells our system that these files are to be sent to the collection JCM1. Similarly, the second part of the name (001) will direct files to item 001 in our archive structure. Items will have already been created in the catalog by the depositor before sending any files to PARADISEC. The third part of the file name (F45) distinguishes it from other files under that item. Distinctive names avoids conflicts and errors for our automated system.

  • Australian Government
  • The University of Queensland
  • Australian National University
  • The University of Melbourne
  • Western Sydney University