Transaction Logs and Focus Groups as Data Collection Methods

Research on library science has several problems, but one thing in common is data collection. Qualitative and quantitative information supporting actual questions is necessary to verify needs or phenomena or trends (Wildemuth, 2009). Transaction logs and focus groups are two useful data collection techniques. Transaction Log Different types of information are automatically collected in the transaction log each time someone logs in and starts using the computers in the library (Jansen, 2006).

For additional information on transactions, you can check the event log. Normally, transactions contain logs that contain additional data - but not all transactions can do this, but depending on other transactions it may be written to multiple event logs. To display the event log of the registerTicker method, return to the transaction information screen you confirmed earlier and click the Event Log (1) tab. You will be taken to the screen shown above where you can see the data in the event log. Since the data of the transaction record is defined by the developer of the smart contract, the above contents may differ from contract to contract. By default, all values ​​are displayed in hexadecimal, but you can also select and change the way each value is displayed. Because the display may be different for each specific event (item arranged in different order), it is difficult to distinguish the data field you are looking for.

The event is an inherited contract member. When they are called, they store the parameters in the transaction log (a special data structure in the block chain). These logs are associated with contract addresses and merged into block chains and remain there as long as the block is accessible. Logs and event data can not be accessed from the contract (they can not be accessed from the contract that created them). Solidity supports multiple inheritance (including polymorphism) by copying the code. All function calls are virtual functions. That is, unless the contract name is explicitly specified, it means calling the function with the most derived function. Once a contract is inherited from multiple contracts, only one contract is created on the block chain, and all contract codes are copied to the created contract. The general inheritance system is very similar to Python, especially including multiple inheritance.