Issue link: http://digital.copcomm.com/i/1279181
M OT I O N P I CTU R E S O U N D E D I TO R S I 29 fi le was created for a particular project, show, or library. Using abbreviations here also keeps the length of the fi lename manageable while allowing for scripting to generate complete descriptions using lookup tables. Example of a Basic Filename: AMBPubl_Getty Museum Afternoon Busy Crowd_TN_DORY.wav This reads as a Category/ SubCategory of AMBIENCE/ PUBLIC PLACE. It is a recording of a busy crowd at the Getty Museum in the afternoon, recorded by Tim Nielsen for the fi lm Finding Dory. Running a brief script within your library management software may be able to autofi ll all the pertinent information to the relevant metadata fi elds within your library. Allowing you to quickly and easily sort and drill down into your effects library. This function is working and available in Soundminer, and they hope to bring it to other databasing software as well. An advanced fi le-naming scheme is also available, allowing for additional chunks of information: UserCat, UserData, and VendorCat. Each of these are optional but allow for greater description within the fi lename and subsequently greater metadata information. More information about this fi lename system is available on their YouTube channel in a video dedicated to explaining the system. Who's In? Due to Justin Drury's initial involvement regarding language translations, Soundminer will offer full integration of the Universal Category System in their products. An offi cial release is expected shortly that will adhere to the UCS v8.0 public release and is currently available in the advanced Filename Structure As an addendum to the Universal Category System, Nielsen and his team of volunteers highly recommend the adoption of a universal fi lename structure. While not required to be considered UCS- compliant, libraries that adopt this well-thought and proven system will prepare their sound effects fi les (and their customers) in a manner that will make the global exchange of sound effects easier. The basic UCS Filename Structure includes four parts (blocks), laid out in the following order: CatID_ FXName_CreatorID_SourceID In the fi rst position, the CatID functions just as within the UCS- compliant naming scheme, defi ning the Category and SubCategory a sound is classifi ed under. FXName is the title of the sound effect and should simply clarify the question, "What is this sound?" Best practices keep the description brief, less than 25-30 characters ideally. Detailed notes about the sound should be reserved for the Description metadata fi eld. The notion of the FXName is that an editor should be able to comprehend exactly what the sound fi le contains simply by looking at the FXName chunk in a folder on a hard drive. CreatorID provides a place to determine "Who made this sound?" Whether it be yourself, another editor at your facility, or a vendor name, the use of abbreviations in this third block is recommended. Lookup tables within your library management software may be able to expand abbreviations into full descriptions in your database. SourceID should answer the question, "Why was this sound made?" Here the creator should indicate if the sound They explained that the Universal Category System (UCS) sought to become an industry-standard classifi cation for all sound e ects in the hopes of making the organization and global portability of sound fi les faster, simpler, and more user-focused.