On Tue, Jan 26, 2016 at 4:13 AM, Vanjikumaran Sivajothy <[email protected]> wrote:
> > > On Mon, Jan 25, 2016 at 1:35 AM, Isuruwan Herath <[email protected]> > wrote: > >> Hi Lahiru, >> >> On Mon, Jan 25, 2016 at 9:12 AM, Lahiru J Ekanayake <[email protected]> >> wrote: >> >>> Adding isabelle >>> >>> On Mon, Jan 25, 2016 at 8:21 AM, Lahiru J Ekanayake <[email protected]> >>> wrote: >>> >>>> G-Reg/ES Taxonomy Feature >>>> >>>> >>>> *Management console and Publisher Implementation* >>>> >>>> Taxonomy is the hierarchical classification of entities. This will be >>>> a generic model for Enterprise store. End user will able to view >>>> hierarchical >>>> visualization of categories to search and navigate. In here we have three >>>> stages of implementation. *Management Console Implementation *(Define >>>> the available categories)* ,**Publisher visualization and >>>> implementation *(Select categories for an asset) , *Store **visualization >>>> and implementation* (Store is using end uses to search and navigate >>>> through tree structure). >>>> >>>> >>>> Management Console Implementation >>>> >>>> >>>> - >>>> >>>> Only admin is authorized to define categories. Categories will be >>>> stored in the registry as a XML file. >>>> >>>> Since we support one category hierarchy per organization, shouldn't we >> store this XML as a config file? >> > > In that case how do you handle that in the tenant mode? > My understanding was there would be one master taxonomy structure for the deployment. But after discussion, identified use cases of applying taxonomy structures per tenant, since its better to go ahead with registry based config. > >>>> - >>>> >>>> >>>> ex :- >>>> <WSO2> >>>> >>>> <HR></HR> >>>> >>>> <Engineering> >>>> >>>> <G-Reg></G-Reg> >>>> >>>> <IS></IS> >>>> >>>> </Engineering> >>>> >>>> <Marketing></Marketing> >>>> >>>> </WSO2> >>>> [image: Inline image 1] >>>> >>>> - >>>> >>>> Read the categories from XML file and populate category data. >>>> >>>> >>>> Publisher visualization and implementation >>>> >>>> >>>> - >>>> >>>> Implement backend API to get populated category data into >>>> javascript backend . >>>> - >>>> >>>> Front end User Interface. >>>> This will similar to regular tags UI. It will have separate drop >>>> down menu named “category” , below to regular tags. >>>> >>>> Some artifacts already has the field category as an attribute. Should >> we re think the naming of this drop down to avoid confusion? >> >>> >>>> - >>>> >>>> >>>> >>>> - >>>> >>>> Restrict regular tags with “/” symbol. >>>> - >>>> >>>> Load data from populated categories. Categories will be >>>> displayed with “/” symbol. >>>> >>>> - >>>> >>>> populated category data will be rendered inside a combo box, >>>> with auto populate support when typing. >>>> >>>> >>>> /WSO2/Engineering/G-Reg >>>> >>>> /WSO2/Engineering/IS >>>> >>>> /WSO2/HR >>>> >>>> /WSO2/Marketing >>>> >>>> >>>> - >>>> >>>> Save selected category. Categories will be stored same as regular >>>> tags. >>>> *ex :- /wso2/engineering/g-reg* >>>> - >>>> >>>> >>>> *User can select multiple categories for an asset. Similar to tags >>>> selection. * >>>> >>>> >>>> >>>> *Regards* >>>> >>>> -- >>>> >>>> >>>> >>>> *Lahiru J Ekanayake**Software Engineer* >>>> Mobile : +94 (0) 77 8812629 / +94(0) 778509547 >>>> Email : [email protected] >>>> WSO2, Inc.; http://wso2.com/ >>>> lean . enterprise . middleware. >>>> >>>> >>> >>> >>> -- >>> >>> >>> >>> *Lahiru J Ekanayake**Software Engineer* >>> Mobile : +94 (0) 77 8812629 / +94(0) 778509547 >>> Email : [email protected] >>> WSO2, Inc.; http://wso2.com/ >>> lean . enterprise . middleware. >>> >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Isuruwan Herath >> Technical Lead >> >> Contact: +94 776 273 296 >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Vanjikumaran Sivajothy > *Associate Technical Lead* > *WSO2 Inc. http://wso2.com <http://wso2.com/>* > *USA Mobile **+1-925-464-6816* > *Srilanka Mobile:+94-777-219-209* > [image: Facebook] <https://www.facebook.com/vanjikumaran> [image: Twitter] > <https://twitter.com/vanjikumaran> [image: LinkedIn] > <http://www.linkedin.com/pub/vanjikumaran-sivajothy/25/b31/293> [image: > Blogger] <http://vanjikumaran.blogspot.com/> [image: SlideShare] > <http://www.slideshare.net/vanjikumaran> > > This communication may contain privileged or other > confidential information and is intended exclusively for the addressee/s. > If you are not the intended recipient/s, or believe that you may > have received this communication in error, please reply to the > sender indicating that fact and delete the copy you received and in > addition, you should not print, copy, re-transmit, disseminate, or > otherwise use the information contained in this communication. > Internet communications cannot be guaranteed to be timely, secure, error > or virus-free. The sender does not accept liability for any errors > or omissions > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Isuruwan Herath Technical Lead Contact: +94 776 273 296
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
