> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.smino.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Examples versioning

Below we show you a few examples to illustrate file versioning, how it works and what to look out for.

| Note: There are different file naming schemes according to which smino recognizes newly uploaded files as updates of an already existing file. How the project admin can specify these schemes is explained by the following helparticle => [What kind of file name schemes can I configure?](https://help.smino.com/en/article/what-kind-of-file-name-schemes-can-i-configure-eh1h4k/)

1. if the following rule is enabled: **after the last "\_" (bottom line)**:  

Everything before the last bottom bar is compared, that is, everything after the last bottom bar is excluded for checking. 

Example 1:

old: Bauplan\_V2-20181123.pdf
new: Bauplan\_V3-20202312.pdf
=> "Word stem "Bauplan" is identical => old is replaced by new

Example 2:

old: Bauplan.pdf
new: Bauplan\_V3-20202312.pdf
=> "word stem "Bauplan" is identical => old is replaced by new

Example 3:

old: Bauplan1.pdf
new: Bauplan2.pdf
=> no update (two different root words "Bauplan1" and "Bauplan2") => a new file Bauplan2.pdf is created. You can now see Bauplan1.pdf and Bauplan2.pdf in the folder.

Example 4:

old: Bauplan\_EG.pdf
new: Bauplan\_OG.pdf
=> Attention! Bauplan\_OG.pdf replaces Bauplan\_EG.pdf (root "Bauplan" is identical) => Bauplan\_OG.pdf is the new version of Bauplan\_EG.

Example 5:
old: Bauplan\_EG\_2020\_02\_01.pdf
neu: Bauplan\_EG\_2020\_03\_02.pdf
=> Attention! No update, because root "Bauplan\_EG\_2020\_02" and "Bauplan\_EG\_2020\_03" are different.

Instruction:
Index information must always be placed at the end of the file name and separated from the plan name with a "\_" (bottom bar). Index information must always be present.

|| Tip: Do not use "\_" (bottom lines) in the rest of the file name, but use other characters such as "-" (hyphen).

Example: 
old: Bauplan-0231-EG\_V23
new: Construction plan-0231-EG\_V24

Furthermore, if **several plans are uploaded at the same time**:

Example 1:
Plan 1: Bauplan\_EG.pdf
Plan 2: Bauplan\_OG.pdf
=> Attention! Bauplan\_OG.pdf would immediately update Bauplan\_EG.pdf. System detects this and reports an error. Plans cannot be uploaded.

Example 2:
Plan 1: Bauplan-EG\_2020-01-23.pdf
Plan 2: Bauplan-OG\_2020-01-23.pdf
=> OK! Word root "Bauplan-EG" and "Bauplan-OG" are different and the plans can be uploaded.

2. use other separator / index in front.

The project admin can change the rule, e.g. to: **before the first "-" (hyphen):**.

Then it looks like this:

Example: 
old: 2018\_11\_23-Bauplan\_EG.pdf
new: 2019\_11\_23-Bauplan\_EG.pdf
=> "Word stem "Bauplan\_EG" is identical --> old is replaced by new

3. versioning disabled (for newly created projects this is the default setting):

If versioning is disabled, then the system compares the complete file name:

Example 1:
old: Bauplan\_V220181123.pdf
new: Bauplan\_V220202312.pdf
=> There are now two different files in the folder (Bauplan\_V220181123.pdf and Bauplan\_V220202312.pdf)

Example 2:
old: Bauplan\_EG.pdf
new: Bauplan\_EG.pdf
=> old is replaced by new