Hello,
I'm trying to implement Vault Data Standard in our company's Vault to enhance our custom numbering scheme management. Being new to VDS, I'm not entirely sure if it's the best solution for our needs.
One of the aspects I find particularly appealing about VDS is its capability to automatically upload files to Vault at their very first save, without the need for users to manually check them in to let colleagues know that a specific file "exists", thereby streamlining the process.
Our file naming convention is as follows:
- Parts: ABC.Z1234.DEF
- Assemblies: ABC.A1234.DEF
- Drawings: inherit the same filename as their corresponding 3D file.
Details of the filename components:
- ABC can be derived from the first three characters of the folder where the file is saved.
- A or Z is automatically assigned based on the 3D file extension.
- 1234 is an incremental number, dependent on the prefix only, but can have different suffix (see example below)
- DEF is selected by the user according to the machine for which the part is being designed the first time.
For instance, within the ABC folder, you might find files such as:
- ABC.A0001.DEF.iam
- ABC.Z0001.DEF.ipt
- ABC.Z0002.JKL.ipt (same prefix, different suffix: the incremental number keeps increasing)
My aim is for users to only need to select the Vault path and the suffix, thereby dedicating their time to input other valuable data. However, I honestly don’t know where to start. I’ve read numerous topics on this forum, studied Marcus’s GitHub content and his sample plugin, and looked at AU contents, but I’m still missing the bigger picture. Any guidance or advice on how to proceed would be greatly appreciated.
