Hi Shankar

 I started new thread called "Data Mapping User Stories" and added this
story , will update that thread adding more stories in the future

Thanks
/jasintha


On Tue, Apr 1, 2014 at 10:40 PM, Jasintha Dasanayake <[email protected]>wrote:

> Hi Shankar
>
> I have already crated this user story and shared with the team for final
> cut , Will share it publicly asap
>
> Thanks and Regards
> /Jasintha
>
>
> On Tue, Apr 1, 2014 at 7:46 PM, Selvaratnam Uthaiyashankar <
> [email protected]> wrote:
>
>>
>>
>>
>> On Tue, Apr 1, 2014 at 10:26 AM, Susinda Perera <[email protected]> wrote:
>>
>>> Hi All,
>>>
>>> Please find the below mentioned points which discussed at the meeting
>>> held on 31/03/2014 regarding Visual DataMapper.
>>>
>>> *Participants*: Sanjiva, Isabelle, Shankar, Srinath, Shiroshika,
>>> Jasintha, Viraj, Susinda, AsankaS, Sohani, Kawith
>>>
>>> *Points*:
>>>
>>>    - Remove the (.js) type from the file, users might edit this if it
>>>    is .js, but we don't want this to edit.
>>>    - User should be able to start a datamapper config without having to
>>>    create a registry resource first.
>>>    - When creating the new registry resource for datamapper (do not ask
>>>    to create registry resource, it has to be a data mapping configuration)
>>>    - For the concat operator give user to select the separator (_ or
>>>    <space> or etc) in the property window. We discussed to maintain this as 
>>> a
>>>    property in the operator
>>>    - Without using the constant operator if there is a prefix (not
>>>    something coming from input) have to handle this in concat operator.
>>>    - Improve UI (font, anchors, font sizes etc), Connections have to
>>>    have more area to easily connect
>>>    - There was an issue in config generation for operators and that has
>>>    to be fixed.
>>>    - Instead of save the datamapper config and input/output schema in
>>>    gov:/<customLocation> ,  think of having a place for the project in the
>>>    registry (per project basis)
>>>    - Create more operators focusing on different functionalities like
>>>    one_to_N, N_to_one and etc
>>>    - UI related improvements will be hold for the moment and have to
>>>    focus on implementing core functionalities and usability features.
>>>    - As per discussed UI improvements will again looked once above
>>>    mentioned functionality improvements is done.
>>>
>>> *Next Review*
>>>
>>>    - Make an end to end user-story. Salesforce to google spreadsheet is
>>>    a good one to start.
>>>
>>>
>> @Jasintha, others: Did you folks work on the user stories? Can you share
>> the user stories?
>>
>> Regards,
>> Shankar
>>
>>
>>
>>>
>>>    -
>>>    - Make the datamapper configuration creation and deploying a simple
>>>    set of steps.
>>>    - Show the above mentioned use case as a demo on next meeting (on
>>>    next Monday).
>>>
>>>
>>>
>>> Thanks and Regards,
>>> Susinda
>>>
>>>
>>> --
>>> *Susinda Perera*
>>> Software Engineer
>>> Mobile:(+94)716049075
>>>
>>> WSO2 Inc. http://wso2.com/
>>> Tel : 94 11 214 5345 Fax :94 11 2145300
>>>
>>>
>>> _______________________________________________
>>> Architecture mailing list
>>> [email protected]
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> S.Uthaiyashankar
>> VP Engineering
>> WSO2 Inc.
>> http://wso2.com/ - "lean . enterprise . middleware"
>>
>> Phone: +94 714897591
>>
>
>
>
> --
>
> *Jasintha Dasanayake *
>
> *Software EngineerWSO2 Inc. | http://wso2.com <http://wso2.com/> lean .
> enterprise . middleware*
>
>
> *mobile :- 0711368118*
>



-- 

*Jasintha Dasanayake*

*Software EngineerWSO2 Inc. | http://wso2.com <http://wso2.com/>lean .
enterprise . middleware*


*mobile :- 0711368118*
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to