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.
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.
-
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.
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
