Automatic part numbering

[grd]

Automatic part numbering ¹, lets call this APN, is a very nice to have feature. In many companies they use APN but not in all. APN most of the times come together with a custom versioning scheme ².

For instance we can use the json file format to implement APN. When a file that is called AutoPartNumber.json is placed inside the directory vaults/.data/yourvault then (after this feature is implemented) it should work³.

An example looks like this:

{
  “prefix”: “4022-077-”,
  “with_zero”: ”yes”, // otherwise it would use the space character
  “number_digits”: 5,
  “starts_with”: 500,
}

This generates the number (after renaming the file) 4022-077-00500.fcasm, 4022-077-00501.fcdrw, 4022-077-00502.fcprt, and so on.

A different example:

{
  “with_zero”: ”yes”, // otherwise it would use the space character
  “number_digits”: 6,
  “special_character”: [
    {
      “index”: 2,
      “character”: “ “
    },
    {
      “index”: 4,
      “character”: “-“
    },
  ],
}

This generates the number 00 00-00.fcasm, 00 00-01.fcdrw, 00 00-02.fcprt, and so on.

Keywords

• prefix [string] ⁴
• suffix [string] ⁴
• with_zero [bool] // otherwise it would use the space character
• number_digits [int]
• starts_with [int]
• index [int]
• character [char]

What are your thoughts?

Footnotes

1. https://www.buyplm.com/plm-good-practice/part-numbering-system-software.aspx ↩

2. We will also put a custom versioning scheme issue here. See Custom Versioning scheme #93 ↩

3. To put this file there you first need to chmod the vault and then the .data and after that the yourvault directories. Type chmod yourdir 0777 in the server ↩

4. There is a magic word with the name " variable". This means that you can put your text into there. ↩ ↩²