Naming Conventions

Hi
“Which is the best practice Naming Conventions for MediaBin
Folders and Assets or Digital Assets Management System”.
Thanks
Vin

Find more posts tagged with

Comments

Migrateduser

That's a very open ended question and I think that every business will do it a different way. Ubisoft has a full time digital librarian who organizes their data and provides their own standards.

For our company, we organize our containers in the following order because we have created a lot of home grown automated tools on the back end.

1. Data is inserted into containers "By Tool" (meaning how the original got into the system)
2. Then by Product Groups
3. By Products

We have several other back end systems for accounting, billing, contract, payments, and licensing. It's very important for us to link our images to that information. We name our images in MediaBin based on an ID in our content management system, this way we can make the association between MediaBin and our systems. This empowers us to generate detailed reports.

I'm interested to hear what other people do in their systems.

engelluk

Hi,

In our product images file naming guidelines we maintain follows metadata<>filename relations

article number
product view
image style
usage purpose

Article number is pretty simple (always six characters)

Product view is self-explaining

“_F” means front view
“_B” means back view
…

Image style describes let’s say the standardized photography style like:

“_beauty” means Beauty
“_torso” means 3D Torso style
“_flat” means Flat style
…

and so on.

A final name could look as follows:

123456_B_torso.psd

Of course all this metadata is maintained within the database so it’s ease to search for such product views.

As it can happen that two version of for example 123456_B_torso.psd exists something like a sequential number is also needed F/F2/F3 an so on.

As our filenames are based on metadata something like a “File naming Tool” integrated in to a ingest task could be fantastic as the system will automatically take care about the right filename

Regards
Lukas

Migrateduser

There is one aspect to consider if you plan on uploading or downloading folders via the web client. These operations are restricted to 256 characters for the full path to the web client's transfer folder as defined in the file global.asa. Therefore, you may want to consider this when planning the length of asset and folders names used.
As of 4.6, the web client supports applet or non-applet based files transfers. In both cases, when using archives to transfer folder trees, the entire tree is replicated under the web client's transfer folder so the path may become quite long and exceed the 256 character limit, which generates an error. Archives are not required when using applet based file transfers to upload folder trees. The tree is flattened in the transfer folder, with additional subfolders created only to handle name collisions. This helps alleviate the max path limit issue somewhat.
At any rate, the length of your folder and asset names might be something to keep in mind.