Global Address Object:Best Practices: Difference between revisions
Jump to navigation
Jump to search
Created page with "==International Address Data Storage== In considering the storage of international address data the fielding concern should be looked at in two groups: data at the locality/po..." |
No edit summary |
||
| Line 1: | Line 1: | ||
[[Global Address Object|← Global Address Object]] | |||
{{CustomTOC}} | |||
==International Address Data Storage== | ==International Address Data Storage== | ||
In considering the storage of international address data the fielding concern should be looked at in two groups: data at the locality/postal code level and data at the thoroughfare/premise level. Considerations should also be given as to the alphabet(s) and language(s) in which the data may need to be stored. In Appendix X there are some useful address field definitions with suggested field lengths that could be useful in deciding how best to store your global address data. | In considering the storage of international address data the fielding concern should be looked at in two groups: data at the locality/postal code level and data at the thoroughfare/premise level. Considerations should also be given as to the alphabet(s) and language(s) in which the data may need to be stored. In Appendix X there are some useful address field definitions with suggested field lengths that could be useful in deciding how best to store your global address data. | ||
Latest revision as of 22:12, 9 August 2017
International Address Data Storage
In considering the storage of international address data the fielding concern should be looked at in two groups: data at the locality/postal code level and data at the thoroughfare/premise level. Considerations should also be given as to the alphabet(s) and language(s) in which the data may need to be stored. In Appendix X there are some useful address field definitions with suggested field lengths that could be useful in deciding how best to store your global address data.