Creating an Asset

Creating your first Asset

An Asset can be anything: a Connected Machine, a Shipping Container, or even a Data Set. It can be any physical or digital object with an associated Name, Description, and Attributes.

Each Asset will have a history of any actions performed upon it by any actor.

You may share Assets and their history with specific stakeholders using permissioned sharing. RKVST also enables you to publicly attest the provenance of your Assets. To learn how, see Public Attestation.

The creation of an Asset is the first Event in its lifecycle. The following steps will guide you in creating your first Asset.

Creating an Asset

Note: To use the YAML Runner you will need to install the jitsuin-archivist python package.

Click here for installation instructions.

  1. Create your Asset.

Using the Sidebar, select ‘Add Asset’.

Adding an Asset

The RKVST YAML runner is executed as a series of steps, each step representing a single operation with an action.

In order to create an asset we use the action ASSETS_CREATE_IF_NOT_EXISTS.

---
steps:
  - step:
      action: ASSETS_CREATE_IF_NOT_EXISTS

Create an empty file, in later steps we will add the correct JSON.

{
  
}
  1. Add details to your new Asset.

You will see an Asset Creation form, where you provide details of your new Asset:

Creating an Asset

Here you can fill out some more metadata about your asset:

  • selector is the identifying attribute the yaml runner will use to check if your asset exists already before attempting to create it, in this case we use arc_display_name which represents the name of the Asset.
  • behaviours detail what class of events in your assets lifecycle you might wish to record; RecordEvidence and Attachments are the standard and recommended behaviours for all assets.
---
steps:
  - step:
      action: ASSETS_CREATE_IF_NOT_EXISTS
      description: Create an asset.
      asset_label: My First Container 
    selector: 
      - attributes: 
        - arc_display_name
    behaviours: 
      - RecordEvidence
      - Attachments

In the file you created earlier, begin adding metadata for your Asset:

  • behaviours detail what class of events in your assets lifecycle you might wish to record; RecordEvidence and Attachments are the standard and recommended behaviours for all assets.
{
    "behaviours": ["RecordEvidence", "Attachments"]
}
  1. At minimum, you will need to add an Asset Name and Asset Type to create an Asset:
  • Asset Name - This is the unique name of the Asset i.e. ‘My First Container’.
  • Asset Type - This is the class of the object; while it is arbitrary, it is best to have consistency amongst the type of Assets you use i.e. if it is a shipping container, the type could be Shipping Container which will then be pre-populated for future Assets to use as their own types.
Adding Asset Details

The RKVST API uses the reserved attributes arc_display_name and arc_display_type to represent Asset Name and Asset Typerespectively.

---
steps:
  - step:
      action: ASSETS_CREATE_IF_NOT_EXISTS
      description: Create an asset.
      asset_label: My First Container 
    selector: 
      - attributes: 
        - arc_display_name
    behaviours: 
      - RecordEvidence
      - Attachments
    attributes: 
      arc_display_name: My First Container 
      arc_display_type: Shipping Container

The RKVST API uses the reserved attributes arc_display_name and arc_display_type to represent Asset Name and Asset Typerespectively.

{
    "behaviours": ["RecordEvidence", "Attachments"],
    "attributes": {
        "arc_display_name": "My First Container",
        "arc_display_type": "Shipping Container",
    }
}
  1. At this point, you may wish to add other details to your Asset, including extended attributes or attachments such as PDFs or Thumbnail Images.

Extended Attributes are user-defined and can be added to each unique Asset.

Not all Assets of a specific type need to have the same Extended Attributes, but in most cases it is better to do so for consistency.

To add a new Attribute to an Asset, enter your key-value pair.

For Example:

Select ‘Add Attribute’, and add your key-value pairs.

Asset Extended Attributes

Extended Attributes are custom key-value pairs, such as Width, Length, and Height you see below.

This example also adds a location to our asset, to find out more about Locations, click here

It’s also good practice to include confirm: true which tells RKVST to finish commiting the asset before moving to the next step.

---
steps:
  - step:
      action: ASSETS_CREATE_IF_NOT_EXISTS
      description: Create an asset.
      asset_label: My First Container 
    selector: 
      - attributes: 
        - arc_display_name
    behaviours: 
      - RecordEvidence
      - Attachments
    attributes: 
      arc_display_name: My First Container 
      arc_display_type: Shipping Container
      arc_description: Originally shipped from Shanghai
      Width: "2.43m"
      Length: "6.06m"
      Height: "2.59m"
    location: 
      selector: 
        - display_name
      display_name: Parkside Junction
      description: Box intersection between Mill Road and East Road
      latitude: 52.2025
      longitude: 0.1311
    confirm: true

Extended Attributes are custom key-value pairs, such as Width, Length, and Height you see below.

This example also adds a location to our asset, to find out more about Locations and how to find your Location ID, click here.

{
    "behaviours": ["RecordEvidence", "Attachments"],
    "attributes": {
        "arc_display_name": "My First Container",
        "arc_display_type": "Shipping Container",
        "arc_description": "Originally shipped from Shanghai",
        "Width": "2.43m",
        "Length": "6.06m",
        "Height": "2.59m",
        "arc_home_location_identity": "locations/<location-id>",
    }
}
  1. Complete your Asset creation.

Click ‘Create Asset’.

Create the Asset

Use the archivist_runner command to run your YAML file!

$ archivist_runner \
      -u https://app.rkvst.io \
      --client-id <your-client-id> \
      --client-secret client_secret.txt \
      my_first_container.yaml

Use the curl command to run your JSON file! See instructions for creating your BEARER_TOKEN_FILE here.

curl -v -X POST \
    -H "@$BEARER_TOKEN_FILE" \
    -H "Content-type: application/json" \
    -d "@/path/to/jsonfile" \
    https://app.rkvst.io/archivist/v2/assets
  1. View your Assets.

Navigate to ‘Manage Assets’ to see your Asset in the UI.

Managing Assets

You can view all Asset data using the ASSETS_LIST action, use the print_response keyword to get the full output.

---
steps:
  - step:
      action: ASSETS_LIST
      description: List all assets.
      print_response: true

You can view all Asset data using the following command.

curl -v -X GET \
     -H "@$BEARER_TOKEN_FILE" \
     https://app.rkvst.io/archivist/v2/assets
  1. View details of the Asset you created.

To view your Asset, click on the Asset row. You will see the detailed history of your Asset.

Viewing an Asset

The ASSETS_LIST action can be filtered using identifying attrs to view the details of a specific Asset.

---
steps:
  - step:
      action: ASSETS_LIST
      description: Display Asset named My First Container.
      print_response: true
    attrs:
      arc_display_name: My First Container

Details of a specific asset can be retrieved using identifying attrs, such as name, type, or presence of a certain field.

curl -g -v -X GET \
     -H "@$BEARER_TOKEN_FILE" \
     https://app.rkvst.io/archivist/v2/assets?attributes.arc_display_name=My%20First%20Container

Here we see all details entered: The Extended Attributes and a history of Events recorded on the Asset.

Note: To update the details of your Asset after it has been created, you must create an event containing Asset Attributes.

For more information on creating events, click here.

The first Event will always be the Asset Creation. In the next section, we will cover how to create your own Events for your Asset.

Edit this page on GitHub