You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "BJ Freeman (JIRA)" <ji...@apache.org> on 2006/07/21 21:41:14 UTC
[jira] Created: (OFBIZ-100) Addressing Verification
Addressing Verification
-----------------------
Key: OFBIZ-100
URL: http://issues.apache.org/jira/browse/OFBIZ-100
Project: OFBiz (The Open for Business Project)
Issue Type: New Feature
Components: party
Reporter: BJ Freeman
Priority: Minor
When the POSTALADDRESS entity is created or updated it will go thru verification, if availible.
I suggest POSTALADDRESSVERIFICATION entity to handle the additional data, instead of modifying the POSTALADDRESS .
POSTALADDRESS would be modified to add the vericationprocessed and verified flag and ID to the POSTALADDRESSVERIFICATION entiy.
The reason for the two flag is speed and if the verified flag is false, then further processing of the POSTALADDRESSVERIFICATION can be done.
POSTALADDRESSVERIFICATION may have a range of address that are valid but do not match the address.
if may have address1 matches but not the City or zip.
the Address Element Correction (AEC) service would thn do its best to validate and/or correct the address.
when the AEC is run it will create Task for the user to fix manually, since AEC does not alway work.
The Upper level Verification will see the Verified Flag false and create an event.
For Ecommerce this would alert the buyer that there address is not deliverable and allow them to see the choices and correct thier address.
For Orderentry it would allow the sales person to verify the address with the customer.
For addresses that imported, via webtools, a service will run nightly to validate all address.
I have included proposed service changes and new service as an example.
this changes the Create and Update POSTALADDRESS in the
applications/party/script/org/ofbiz/party/contact/ContactMechServices.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (OFBIZ-100) Addressing Verification
Posted by "BJ Freeman (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/OFBIZ-100?page=all ]
BJ Freeman updated OFBIZ-100:
-----------------------------
Attachment: PostalAddressServiceChange.xml
This show changes to CREATE and UPDATE of postalAddress to do verification.
This is not to me correct but to be a example of implementation, for comment.
> Addressing Verification
> -----------------------
>
> Key: OFBIZ-100
> URL: http://issues.apache.org/jira/browse/OFBIZ-100
> Project: OFBiz (The Open for Business Project)
> Issue Type: New Feature
> Components: party
> Reporter: BJ Freeman
> Priority: Minor
> Attachments: PostalAddressServiceChange.xml
>
>
> When the POSTALADDRESS entity is created or updated it will go thru verification, if availible.
> I suggest POSTALADDRESSVERIFICATION entity to handle the additional data, instead of modifying the POSTALADDRESS .
> POSTALADDRESS would be modified to add the vericationprocessed and verified flag and ID to the POSTALADDRESSVERIFICATION entiy.
> The reason for the two flag is speed and if the verified flag is false, then further processing of the POSTALADDRESSVERIFICATION can be done.
> POSTALADDRESSVERIFICATION may have a range of address that are valid but do not match the address.
> if may have address1 matches but not the City or zip.
> the Address Element Correction (AEC) service would thn do its best to validate and/or correct the address.
> when the AEC is run it will create Task for the user to fix manually, since AEC does not alway work.
> The Upper level Verification will see the Verified Flag false and create an event.
> For Ecommerce this would alert the buyer that there address is not deliverable and allow them to see the choices and correct thier address.
> For Orderentry it would allow the sales person to verify the address with the customer.
> For addresses that imported, via webtools, a service will run nightly to validate all address.
> I have included proposed service changes and new service as an example.
> this changes the Create and Update POSTALADDRESS in the
> applications/party/script/org/ofbiz/party/contact/ContactMechServices.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (OFBIZ-100) Addressing Verification
Posted by "Jacopo Cappellato (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/OFBIZ-100?page=comments#action_12435405 ]
Jacopo Cappellato commented on OFBIZ-100:
-----------------------------------------
Hi BJ,
if you want I can reopen this issue so that you can attach to it your work (but please attach a diff patch instead of the whole modified files).
Jacopo
> Addressing Verification
> -----------------------
>
> Key: OFBIZ-100
> URL: http://issues.apache.org/jira/browse/OFBIZ-100
> Project: OFBiz (The Open for Business Project)
> Issue Type: New Feature
> Components: party
> Reporter: BJ Freeman
> Priority: Minor
> Attachments: PostalAddressServiceChange.xml
>
>
> When the POSTALADDRESS entity is created or updated it will go thru verification, if availible.
> I suggest POSTALADDRESSVERIFICATION entity to handle the additional data, instead of modifying the POSTALADDRESS .
> POSTALADDRESS would be modified to add the vericationprocessed and verified flag and ID to the POSTALADDRESSVERIFICATION entiy.
> The reason for the two flag is speed and if the verified flag is false, then further processing of the POSTALADDRESSVERIFICATION can be done.
> POSTALADDRESSVERIFICATION may have a range of address that are valid but do not match the address.
> if may have address1 matches but not the City or zip.
> the Address Element Correction (AEC) service would thn do its best to validate and/or correct the address.
> when the AEC is run it will create Task for the user to fix manually, since AEC does not alway work.
> The Upper level Verification will see the Verified Flag false and create an event.
> For Ecommerce this would alert the buyer that there address is not deliverable and allow them to see the choices and correct thier address.
> For Orderentry it would allow the sales person to verify the address with the customer.
> For addresses that imported, via webtools, a service will run nightly to validate all address.
> I have included proposed service changes and new service as an example.
> this changes the Create and Update POSTALADDRESS in the
> applications/party/script/org/ofbiz/party/contact/ContactMechServices.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (OFBIZ-100) Addressing Verification
Posted by "BJ Freeman (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/OFBIZ-100?page=comments#action_12435333 ]
BJ Freeman commented on OFBIZ-100:
----------------------------------
is there a time limit on when to submit.
I opened this for comments before final submission.
> Addressing Verification
> -----------------------
>
> Key: OFBIZ-100
> URL: http://issues.apache.org/jira/browse/OFBIZ-100
> Project: OFBiz (The Open for Business Project)
> Issue Type: New Feature
> Components: party
> Reporter: BJ Freeman
> Priority: Minor
> Attachments: PostalAddressServiceChange.xml
>
>
> When the POSTALADDRESS entity is created or updated it will go thru verification, if availible.
> I suggest POSTALADDRESSVERIFICATION entity to handle the additional data, instead of modifying the POSTALADDRESS .
> POSTALADDRESS would be modified to add the vericationprocessed and verified flag and ID to the POSTALADDRESSVERIFICATION entiy.
> The reason for the two flag is speed and if the verified flag is false, then further processing of the POSTALADDRESSVERIFICATION can be done.
> POSTALADDRESSVERIFICATION may have a range of address that are valid but do not match the address.
> if may have address1 matches but not the City or zip.
> the Address Element Correction (AEC) service would thn do its best to validate and/or correct the address.
> when the AEC is run it will create Task for the user to fix manually, since AEC does not alway work.
> The Upper level Verification will see the Verified Flag false and create an event.
> For Ecommerce this would alert the buyer that there address is not deliverable and allow them to see the choices and correct thier address.
> For Orderentry it would allow the sales person to verify the address with the customer.
> For addresses that imported, via webtools, a service will run nightly to validate all address.
> I have included proposed service changes and new service as an example.
> this changes the Create and Update POSTALADDRESS in the
> applications/party/script/org/ofbiz/party/contact/ContactMechServices.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (OFBIZ-100) Addressing Verification
Posted by "BJ Freeman (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/OFBIZ-100?page=comments#action_12423980 ]
BJ Freeman commented on OFBIZ-100:
----------------------------------
originally http://jira.undersunconsulting.com/browse/OFBIZ-219
> Addressing Verification
> -----------------------
>
> Key: OFBIZ-100
> URL: http://issues.apache.org/jira/browse/OFBIZ-100
> Project: OFBiz (The Open for Business Project)
> Issue Type: New Feature
> Components: party
> Reporter: BJ Freeman
> Priority: Minor
> Attachments: PostalAddressServiceChange.xml
>
>
> When the POSTALADDRESS entity is created or updated it will go thru verification, if availible.
> I suggest POSTALADDRESSVERIFICATION entity to handle the additional data, instead of modifying the POSTALADDRESS .
> POSTALADDRESS would be modified to add the vericationprocessed and verified flag and ID to the POSTALADDRESSVERIFICATION entiy.
> The reason for the two flag is speed and if the verified flag is false, then further processing of the POSTALADDRESSVERIFICATION can be done.
> POSTALADDRESSVERIFICATION may have a range of address that are valid but do not match the address.
> if may have address1 matches but not the City or zip.
> the Address Element Correction (AEC) service would thn do its best to validate and/or correct the address.
> when the AEC is run it will create Task for the user to fix manually, since AEC does not alway work.
> The Upper level Verification will see the Verified Flag false and create an event.
> For Ecommerce this would alert the buyer that there address is not deliverable and allow them to see the choices and correct thier address.
> For Orderentry it would allow the sales person to verify the address with the customer.
> For addresses that imported, via webtools, a service will run nightly to validate all address.
> I have included proposed service changes and new service as an example.
> this changes the Create and Update POSTALADDRESS in the
> applications/party/script/org/ofbiz/party/contact/ContactMechServices.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (OFBIZ-100) Addressing Verification
Posted by "BJ Freeman (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/OFBIZ-100?page=comments#action_12439963 ]
BJ Freeman commented on OFBIZ-100:
----------------------------------
I will assume that my implementation Idea meets with everyone, and I can go ahead and code this into the SVN .
The patch will be very large.
> Addressing Verification
> -----------------------
>
> Key: OFBIZ-100
> URL: http://issues.apache.org/jira/browse/OFBIZ-100
> Project: OFBiz (The Open for Business Project)
> Issue Type: New Feature
> Components: party
> Reporter: BJ Freeman
> Priority: Minor
> Attachments: PostalAddressServiceChange.xml
>
>
> When the POSTALADDRESS entity is created or updated it will go thru verification, if availible.
> I suggest POSTALADDRESSVERIFICATION entity to handle the additional data, instead of modifying the POSTALADDRESS .
> POSTALADDRESS would be modified to add the vericationprocessed and verified flag and ID to the POSTALADDRESSVERIFICATION entiy.
> The reason for the two flag is speed and if the verified flag is false, then further processing of the POSTALADDRESSVERIFICATION can be done.
> POSTALADDRESSVERIFICATION may have a range of address that are valid but do not match the address.
> if may have address1 matches but not the City or zip.
> the Address Element Correction (AEC) service would thn do its best to validate and/or correct the address.
> when the AEC is run it will create Task for the user to fix manually, since AEC does not alway work.
> The Upper level Verification will see the Verified Flag false and create an event.
> For Ecommerce this would alert the buyer that there address is not deliverable and allow them to see the choices and correct thier address.
> For Orderentry it would allow the sales person to verify the address with the customer.
> For addresses that imported, via webtools, a service will run nightly to validate all address.
> I have included proposed service changes and new service as an example.
> this changes the Create and Update POSTALADDRESS in the
> applications/party/script/org/ofbiz/party/contact/ContactMechServices.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (OFBIZ-100) Addressing Verification
Posted by "Jacopo Cappellato (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/OFBIZ-100?page=all ]
Jacopo Cappellato closed OFBIZ-100.
-----------------------------------
Resolution: Incomplete
When you'll have a patch for this, please create a new issue (and provide more information about your contribution) and attach the patch to it.
Thanks.
> Addressing Verification
> -----------------------
>
> Key: OFBIZ-100
> URL: http://issues.apache.org/jira/browse/OFBIZ-100
> Project: OFBiz (The Open for Business Project)
> Issue Type: New Feature
> Components: party
> Reporter: BJ Freeman
> Priority: Minor
> Attachments: PostalAddressServiceChange.xml
>
>
> When the POSTALADDRESS entity is created or updated it will go thru verification, if availible.
> I suggest POSTALADDRESSVERIFICATION entity to handle the additional data, instead of modifying the POSTALADDRESS .
> POSTALADDRESS would be modified to add the vericationprocessed and verified flag and ID to the POSTALADDRESSVERIFICATION entiy.
> The reason for the two flag is speed and if the verified flag is false, then further processing of the POSTALADDRESSVERIFICATION can be done.
> POSTALADDRESSVERIFICATION may have a range of address that are valid but do not match the address.
> if may have address1 matches but not the City or zip.
> the Address Element Correction (AEC) service would thn do its best to validate and/or correct the address.
> when the AEC is run it will create Task for the user to fix manually, since AEC does not alway work.
> The Upper level Verification will see the Verified Flag false and create an event.
> For Ecommerce this would alert the buyer that there address is not deliverable and allow them to see the choices and correct thier address.
> For Orderentry it would allow the sales person to verify the address with the customer.
> For addresses that imported, via webtools, a service will run nightly to validate all address.
> I have included proposed service changes and new service as an example.
> this changes the Create and Update POSTALADDRESS in the
> applications/party/script/org/ofbiz/party/contact/ContactMechServices.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (OFBIZ-100) Addressing Verification
Posted by "Jacques Le Roux (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/OFBIZ-100?page=comments#action_12435339 ]
Jacques Le Roux commented on OFBIZ-100:
---------------------------------------
Hi BJ,
I'm not the one who will close Jira but I guess that the time limit is near. Anyway you may copy your comments in http://issues.apache.org/jira/browse/OFBIZ-203 before the end of this Jira
> Addressing Verification
> -----------------------
>
> Key: OFBIZ-100
> URL: http://issues.apache.org/jira/browse/OFBIZ-100
> Project: OFBiz (The Open for Business Project)
> Issue Type: New Feature
> Components: party
> Reporter: BJ Freeman
> Priority: Minor
> Attachments: PostalAddressServiceChange.xml
>
>
> When the POSTALADDRESS entity is created or updated it will go thru verification, if availible.
> I suggest POSTALADDRESSVERIFICATION entity to handle the additional data, instead of modifying the POSTALADDRESS .
> POSTALADDRESS would be modified to add the vericationprocessed and verified flag and ID to the POSTALADDRESSVERIFICATION entiy.
> The reason for the two flag is speed and if the verified flag is false, then further processing of the POSTALADDRESSVERIFICATION can be done.
> POSTALADDRESSVERIFICATION may have a range of address that are valid but do not match the address.
> if may have address1 matches but not the City or zip.
> the Address Element Correction (AEC) service would thn do its best to validate and/or correct the address.
> when the AEC is run it will create Task for the user to fix manually, since AEC does not alway work.
> The Upper level Verification will see the Verified Flag false and create an event.
> For Ecommerce this would alert the buyer that there address is not deliverable and allow them to see the choices and correct thier address.
> For Orderentry it would allow the sales person to verify the address with the customer.
> For addresses that imported, via webtools, a service will run nightly to validate all address.
> I have included proposed service changes and new service as an example.
> this changes the Create and Update POSTALADDRESS in the
> applications/party/script/org/ofbiz/party/contact/ContactMechServices.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira