The Inbox Concept

If an agent transferred data to an application server, the client software requires some functionality to view and use these data. One solution is the concept of a generic inbox. Similar to an e-mail inbox, this feature allows receiving converted files sent from a software agent in the client application. 

The inbox concept is particularly interesting for documentation systems, like ELNs. According to paper laboratory notebook rules, a scientist is not permitted to write to another notebook besides his own. The same applies to ELN software An external system like an agent will not be able to insert data into an electronic scientific document without user interaction. The inbox plays here the role of a database cache in between an external system and the secured notebook database. The scientist can take a look at the inbox items and can decide which item he wants to insert into his document. 

The idea behind the inbox concept is to provide a very easy mechanism for transferring data to a notebook, much as it works with a paper notebook. Let us consider an example of how we would insert spectral data into a notebook in a paper-based laboratory  

Request a spectrum for a sample from the spectroscopy laboratory, usually by filling out some form with details about the sample and the measurement conditions. 

Receive the spectrum as paper printout from the laboratory. 

---