-
assigned issue to
Add "Open Data" data set
OBI requirements from Dave Tonge.
- Get ATM for the bank (location)
- Get Branches for the bank
- Get products offered by the bank
Something like:
/branches --> returns an array of branch objects {bank_name, bank_id, branch_name, branch_id, street_address, phone, GPS} etc. /atms --> returns an array of atms objects {bank_name, atm_name, atm_id, street_address, phone, GPS, supported_cards, fees, etc. } /products --> returns an array of products
Anoop suggested to extend DDA "Capability" object. Will have to see.
Comments (7)
-
reporter -
After got more details and it is good idea to keep this entity separate as it relates to bank domain entity vs where as capability entities is to get service details.
/branches /atms /products
if any existing examples available interm of data element to cover will be helpful ... as this use case not that prominent in US market not much visibility on data set. Will wait for Henrik to share examples.
-
@Nat looking through the draft API response for products I think we should consider normalising the
Category
,Family
, andSuperFamily
with theAccountType
andAssetClass
from the DDA. -
Dave, Should we open new ticket for category/Family/super family so it can be tracked?
-
reporter I will add this topic to this week's call agenda.
-
reporter - changed component to Part 3: Open Data
-
- edited description
- changed status to wontfix
Data specs no longer being worked on
- Log in to comment
Anoop will share the examples from DDA.
Henrik will share the examples from Denmark.