Multiple naming convention in one project (ISO 19650)

[olivierbayle4523]

Hello,

Since few month, you developed ISO 19650 for BIM 360 and Autodesk Docs, great but this naming convention is applied  for the whole project.

Could you take in consideration to integrate multiple naming convetion in one project. Example below :

* Folder 1 = Naming 1

* Folder 2 = Naming 1

* Folder 3 = Naming 1

* Folder 4 =Naming 2

* Folder 5 =Naming 2

Thanks

Olivier

[alexandrem]

This is essential, many customers asked for having multiple naming conventions for one project, if a project covers different phases, in most cases each phase requires a different naming convention.

[Chad-Smith]

And, within those naming conventions, we need optional attributes. Even if that means it's only the last shown attribute that can be designated as optional.

This way we can define a very strict ISO naming convention, while allowing the very last attribute to be an optional 'descriptor'.

[gareth.spencer1]

I can see where you are coming from here but I would be questioning why we need multiple naming standards especially for the same client. This is first thing I implemented when I was client side to have all files named accordingly to one naming standard.

[olivierbayle4523]

hello @gareth.spencer1 ,

We need multiple naming convention in one project, to answer to project steps: 

* conceptual phase

* Review phae

* execution phase

* xxxx phase

For each phase, we need a naming convention to differentiate them

[gareth.spencer1]

Hi @olivierbayle4523,

That is easy just add an additional attribute with the type as a drop-down list called project phase which can be selected when the file is uploaded. I assume this would be included in the filename, but if not, it could be selected once the file is uploaded.  

[Trent_Field]

I would also love the ability for the naming convention to be smart enough to recognise a folder name and list appropriate document types, discipline names etc, especially for document types I don't want my users to have to scroll through a whole list of doc types that aren't necessary for their type of work, such as modelers having reports, letters, calculations etc.

[chris_kim]

We need more than one naming standard. We have many different types of documents in a single project, all organized in different folders, and you can't expect all of them to have the same naming standard.