Overview

LucidIDs and Collections

Lucid Green stores each LucidID with a set of identifications that allow grouping at various levels.

These structures are called Collections.

After creating one or more LucidIDs, those LucidIDs can be added to any Collection at any point in a Brand, Distributor, or Retailer operational process.

For example, assigning a production run of products to a Metrc batch involves:

  1. Creating a set of LucidIDs

  2. Creating a Collection with the Metrc ID specifying those LucidIDs

When creating a case or package of items, an internal case identifier can be created as a Collection, specifying the set of LucidIDs that are contained within that case or package.

When creating a sub-lot of cases for shipping to a Distributor, the set of internal case identifiers can be specified when creating a collection representing the wholesale order with the Metrc sub-lot being used as the new collection’s identifier.

If needed, additional LucidIDs can be added to a Collection by updating that Collection with the additional LucidIDs.

LucidIDs can be members of any number of Collections, so adding a LucidID to a new or existing Collection doesn’t remove it from any Collection of which it was previously a member.

The creation of LucidIDs, creation of Collections, and management of Collections can all be accomplished using APIs.

Collections and LucidID Relationships

Querying for LucidIDs using a Collection identifier

Lucid Green provides a way to query for the set of LucidIDs that are members of a Collection merely by specifying the Collection identifier.

This capability allows any Collection identifier to be used to retrieve those LucidIDs.

For example, when querying Lucid Green using a Metrc batch ID, all of the LucidIDs for the items that were manufactured from that batch are returned.

Similarly, querying using a Lucid Manifest ID from a Lucid Green Digital Manifest (representing either a wholesale or retail shipment) will be able to return all of the LucidIDs that are part of that shipment. Subsequently querying a LucidID can provide detailed product and brand information.

Retrieving Information about a LucidID

Lucid Green provides a way to query for the detailed information about a specific LucidID. This information contains structured details about the Brand, the product/sku, and the COA test results for the item to which the LucidID is assigned.

Additionally, a list of Collections of which the item is a member is also provided, including for each Collection:

  • The Collection identifier - in the case of using Collections to represent various types of Metrc tags, the identifier is the Metrc tag)

  • The type of Collection - in the case of a Collection representing a Metrc tag, it would be “regulator”

  • The date and time when the LucidID was added to that collection

Information about when the item was produced as part of the manufacturing process and when the item was packaged as part of the batch is included in the batch level data included in the items detailed data structure.

Since Collection membership is “append only”, the list of Collections returned as part of a given LucidID’s data represents a type of historical provenance for the physical item to which the LucidID is assigned.

LucidID URL Format

LucidIDs have the following format:

https://qr.lcdg.io/KiX44KRHZ8355HBCPbjZ9r

  • The domain may be http://lcdg.io or http://lucidgreen.io or any subdomain thereof. No other domains are used.

  • A trailing slash may be present and is NOT part of the ID portion of the url

  • The protocol may be http or https

The ID itself (KiX44KRHZ8355HBCPbjZ9r) is the 22 character UUID at the end.

CaseID URL Format

CaseIDs have the following format:

https://qr.lcdg.io/c/MEjwvA9YoDPWBjbcXcjUki

  • The domain may be http://lcdg.io or http://lucidgreen.io or any subdomain thereof. No other domains are used.

  • A trailing slash may be present and is NOT part of the ID portion of the url

  • The protocol may be http or https

The ID itself (MEjwvA9YoDPWBjbcXcjUki) is the 22 character UUID at the end.