🟣 Meta Data

Meta data can be attached to any analysis by the user and is searchable to permit quick identification of analyses of interest. All meta data is user-defined and there is no limit to the number or complexity of meta data descriptions. Meta data must be added at the time of analysis and cannot be updated later.

Note

Search capability on meta data is not available during the Early Access Program. It will be available when Aplos NCA is available for subscription.

Input for web configuration

Enter a value for the key and value and click the ➕ button. You can click the trash can button to remove a key:value pair you entered.

Tip

Make sure you click the ➕ button after entering your key:value pair. If a trash can does not appear next to your key:value pair, it will not be included in the analysis.

Manual JSON structure

If you are performing analysis using a formatted JSON file, you must structure the meta data using standard JSON structures. You can create arrays (and nested arrays) for the meta data if desired. One example is shown below:

{
  "compound": "IX-123",
  "study": "CL-123-004",
  "project": "psoriasis",
  "type-of-analysis": "interim-analysis",
  "team": [
        {
            "name": "john doe",
            "title": "lead analyst",
            "company": "little pharma"
        },
        {
            "name": "jane doe",
            "title": "consultant",
            "company": "acme consulting"
        }
    ]
}

In the example, there are 5 keys: "compound", "study", "project", "type-of-analysis", and "team". The values after the colon (:) are the values assigned to those keys. The key "team" includes an array of 2 values, each with a set of 3 key:value pairs.

Warning

Do not use spaces in either the keys or the values. Spaces create challenges when searching for information from the database in the future. We recommend using a dash (-) instead of a space.

Recommendations

It is recommended that you attept to standardize on both the keys and values across your organization for the greatest benefit. However, it is impossible to predict every bit of information that might be needed in the future. We recommend development of a key:value guide for users and the preparation of a standard meta data json file that is readily available for all users. Since these values are stored as text, you may need to employ creative searching algorithms to capture inconsistent formatting across multiple users (e.g. IX-123 and IX123 may be used by different individuals)