Batch ID Patterns are used to define custom Batch (or Lot) IDs beyond what LUNA CMP pre-populates for users when first starting a batch. Be sure to play around with various Batch ID Patterns and see what works for you!
To set up customized Batch ID Patterns:
Step 1: Click into Settings by hovering over your name in the upper right hand corner of the screen.
Step 2: On the left side menu under the Organization group, click the Batch ID Patterns menu.
Step 3: Here you can define a custom batch ID pattern by stage.
Step 4: Once completed, click Save.
You will see this custom Batch ID Pattern in use immediately when you start a new batch. The Batch ID (or Lot ID) field on any batch started after updates to the pattern have been saved in Settings will automatically be populated with the new pattern for the corresponding Stage.
You can also use a Variety Code that you have defined in the Varieties setup menu. For more info on setting up codes, click here.
VALUES
Values are delimited by '{' and '}' brackets
Available values:
'{start}' > Start date for the batch
'{finish}' > Planned end date for the batch, based on template length
'{variety}' > Variety Name
'{varcode}' > Variety Code (defaults back to name if code is not present on a variety)
'{crop}' > Variety Type
'{facility_code}' > Can be customized in Settings in your Facility Profile
You can include multiple values, repeated values, and other characters. Values can have optional formatting instructions in the form that should be separated by a colon symbol:
'{<value>:<format>}', for example '{start:MMMD}-{variety:3-3}'
DATE FORMATTING
You can use a number of date patterns related to the Start and End dates of the templates. Below are the most common patterns, but click here for a full list of the types of date formatting that can be used. Please note that time patterns are not supported.
DAY
'D' > '4' if the date in question was the 4th of the month, or '12' if it was the 12th.
'DD' > '04' if it was the 4th of the month. It will always be listed as 2 numbers.
'dow' or 'd' > '4' if it was a Wednesday. The days of the week are assigned numbers starting on Sunday (1) through Saturday (7).
'dd' > 'We' if it was a Wednesday.
'ddd' > 'Wed' if it was a Wednesday.
'DDD' > '321' if it was the 321st day of the year. This formatting uses the Julian calendar.
MONTH
'M' > '8' if the month in question is August
'MM' > '08'
'MMM' > 'Aug'
'MMMM' > 'August'
YEAR
'YY' > '21'
'YYYY' > '2021'
WEEK
'W' > '9' if the week in question was the 9th week of the year
'WW' > '09'
The first week of the year starts on the first Monday of the year in question. If January 1st falls on a Saturday, the first week of the year would begin January 3rd.
TEXT FORMATTING
'asis' > No change
'3-3' > The first three letters of each word, separated by a hyphen
'3.3' > The first three letters of each word, separated by a period
'3 3' > The first four letters of each word, separated by a space
'4-4' > The first four letters of each word, separated by a hyphen
'4.4' > The first four letters of each word, separated by a period
'4 4' > The first four letters of each word, separated by a space
'uc' > Uppercased
'lc' > Lowercased
Formats can combine multiple parts, such as '{start: YYYYMMDD}' > '20210205' (if the date in question was February 5, 2021). Please refer to the first screenshot above for visual examples of many different possible Batch ID Patterns and how they would appear on batches.
You can also add in (hardcode) extra symbols or words outside of the values and formatting contained within the { } brackets that will be included in the batch IDs automatically generated. Examples:
'y{start: YY}m{start:MM}d{start:DD}' > 'y21m02d05' if the date in question was February 5, 2021.
'{start: YYMMMD}G-{variety:asis}' > '21Feb5G-Genovese Basil' if you were starting a growth batch of Genovese Basil on February 5, 2021.
Pro tip: Adding/harcoding in letters to the Batch ID pattern for each of your different stages can be a good way to automatically distinguish between whether active or closed batches were Materials, Growth, Packaging, etc.
Comments
0 comments
Article is closed for comments.