On Fri, Aug 31, 2012 at 5:24 PM, Amila Jayasekara <[email protected]>wrote:
> Hi Chathuri, > > I guess we also need to have a user table to record user information. > (At least for testing initial developments, till we integrate with a > proper Identity Solution). > +1. For the moment I will add a user table with user_ID and user_name fields. Are there any more fields that need to be added ? I think most of the other information related to a user can be retrieved by other tables. Regards, Chathuri > > Thanks > AmilaJ > > On Fri, Aug 31, 2012 at 5:02 PM, Chathuri Wimalasena > <[email protected]> wrote: > > Hi All, > > > > We had a discussion on how airavata registry data should be categorized > and > > came up with the following structure. > > > > Gateway > > |- Project1 > > | |- Descriptors > > | |- Published workflows > > | |- User A > > | |- unpublished workflows > > | |- experiments > > | |- workflow > > | |- nodes > > | > > | > > | > > | > > |- Project2 > > | |- user A > > | > > | > > > > According to the above structure, below table structure was designed for > > the mysql database which will be replacing existing backend jackrabbit > > database. > > > > Gateway > > gateway_ID > > gateway_name > > > > Projects > > gateway_ID > > project_ID > > > > Public_Workflow > > project_ID > > workflow_name > > version > > content > > published_date > > > > User_Workflow > > project_ID > > user_ID > > workflow_name > > last_update_date > > > > Host_Descriptor > > project_ID > > host_descriptor_ID > > host_descriptor_xml > > > > Service_Descriptor > > project_ID > > service_descriptor_ID > > service_descriptor_xml > > > > Application_Descriptor > > project_ID > > service_descriptor_ID > > host_descriptor_ID > > application_descriptor_xml > > > > Experiment > > project_ID > > user_ID > > experiment_ID > > submitted_date > > > > All suggestions and feedbacks are most welcome. > > > > Thanks and Regards, > > Chathuri >
