However, the rather frequent changes that these descriptions undergo forced us to develop an automated process capable of retrieving the repository descriptions and generating the metadata files automatically.
Setup phase: The organization admin initializes the public and secret parameters of the system by executing KEYGEN algorithm and preprocesses the data by using SigGen to generate the verification metadata (the information about the connection, the users' accounts).
In this phase, data owner initializes the public and secret parameters of the system by executing KeyGen, and pre-processes the file collection F using BuildMD to generate the encrypted metadata for each file.
In a first attempt, we decided to generate the needed metadata manually.
The organization admin first initializes the setup scheme using KEYGEN [11, 12] algorithm to generate the keys and metadata and then sends them to the CSP.
The entities in the proposed system conduct according to the following sequence: 1 The organization admin first initializes the setup scheme using KEYGEN [11, 12] algorithm to generate the keys and metadata and then sends them to the CSP. 2 The CSP replies to the request from the admin, by using the SINGEN [11, 12] algorithm, to accept the set up scheme.
However, the Codegen transformers that generate the Hibernate XML metadata files follow a single approach which places constraints on the database structure.
When a user inputs a certain product (a television, appliance, phone, laptop, musical instrument, surfboard, etc)., Trov simply needs the make and model to generate all the metadata necessary to insure that item.
The tool then generates the technical metadata needed by the designated repository.
The driver for this development for ChemSpider would be that it would make it much easier to integrate other ELNs to be able to deposit to ChemSpider, rather than writing a separate plugin for each, particularly if the vendors and developers of other ELNs built the ability to generate this metadata into their APIs.
