Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/eln/devices/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,8 @@ Examples for (1): NJ-101; NJ-101-A; NJ-101-5; NJ-101_pure; ABCD-1234-B
Also, if many groups are using the Chemotion ELN, a groupID may help to sort users and therefore their measurements according to a group ID. The measurements should then be named according to examples (2): 2NJ-101; 2NJ-101-A; 2NJ-101-5; 2NJ-101_pure; 2ABCD-1234-B.
Please take care that the hyphen is included!

If the filename contains an elements short label or name, it can be automatically or manually transferred to this elements from the inbox ([Details](../ui/inbox.mdx#moving-files-to-elements)).

### Mail-collector

One of the easiest possibilities to transfer data to a management system such as the Chemotion ELN is to send data per email. The software of some analytical devices support the mailing of measurements to a user defined email address by default. This allows to implement storage routines that are independent of any additional software or hardware on the instrument’s side. The only prerequisite for a use of the MailCollector routine is fulfilled if one can set the email to be send to two addresses, to the Chemotion ELN server associated email address and to the user’s email address registered with the corresponding Chemotion ELN account (Figure 2). This is necessary to identify the target of the mailed information and the corresponding account in the Chemotion ELN. In short, four configuration steps are necessary to fetch the information via email:
Expand Down
53 changes: 51 additions & 2 deletions docs/eln/ui/inbox.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -37,8 +37,57 @@ Regarding the [Data collector](../../eln/devices#datacollectors-for-devices-with

Along with all these, users can manually upload some files in the inbox which they can later use in further analyses.

## Direct import of files from the inbox
## Moving files to elements

You can choose to drag and drop files into `Analyses`, directly from the inbox, when working with datasets.
### Manual import of files from the inbox

When working with datasets, you can drag and drop files directly from the inbox into `Analyses`.

![Drag and Drop](/img/analyses_drag_inbox_files.gif)

Alternatively, you can use the buttons next to the file to open a dialog.
In this dialog, you can select the appropriate element and assign the file to it.
This creates a new `Analysis` with this file.

The list of available elements depends on the file name.
The system automatically searches for elements with matching or partially matching names.

:::note

- Currently, only samples and reactions are supported.
- The buttons must be enabled in the user configuration.

:::

![Move to Sample](/img/inbox_move_to_sample.png)

:::info

The file name (excluding the file extension) should contain:
- The full name of the element or a part of it
- The short label of the element or a part of it (e.g. CU1-1)

:::

### Automatic transfer of files from the inbox

If the filename can be uniquely assigned to an element,
the file will be automatically assigned to that element when uploaded to the inbox.
This creates a new `Analysis` with this file.

:::note

This feature can be disabled in the user configuration.

:::

### Reaction variations link

When you assign a file to a reaction with the filename method and this reaction has one or multiple variations,
the resulting `Analysis` can automatically be linked to a variation.
To enable this, the filename needs to consist of:
1. full name or short label (part)
2. A minus (-) sign followed by **v** + variation index
3. optional file extension

Example name: CU1-R1-**v**1.dat
Binary file added static/img/inbox_move_to_sample.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.