MDL API DATA

1.MDL_API_DATA

MDL_API_DATA data gathering using API keys its used for chatbot.

DataBase : gun_bro
Source : Api keys
Table name : MDL_API_DATA

API 1:

http://diafirearms.azurewebsites.net/api/View_Reference_Best_Uses

First API1 Response:

(sample set)

BestUse : "Informal Recreation Shooting"

BestUseID : "6000"
BestUseToolTip : "Plinking, backyard clays, tin cans,etc
GeneralUse : "Shooter"
GeneralUseID : "3000"
GeneralUseToolTip : nil="true"
SpecificUse : "None"
SpecificUseID : "9000"
SpecificUseToolTip : nil="true"
UseFullPath Shooter : "Informal Recreation Shooting"
UseFullPathID : "3000:6000:9000"

API2 :

Accessing Second API with SpecificUseID for getting the ModelID

Sample set

http://diafirearms.azurewebsites.net/api/View_Lookup_Models_Specific_Use/getmodelid/
9005
Second API2 Response:

ModelID : "1479"
SpecificUseID : "9005"

API 3:

Accessing third api with ModelID For getting the Specification of Firearms
Sample set

http://diafirearms.azurewebsites.net/api/firearmsmdl/modeliddetails/1012

Attributes
https://docs.google.com/spreadsheets/d/1hrMbT80v3Aw6Lqfu-
9HuSjCINsPYVMuRFs5yjK71XXY/edit?ts=5aeab367#gid=0

MDL_API_DATA_APCOH

1.MDL_API_DATA_APCOH

MDL_API_DATA_APCOH data gathering using API keys used for app cohesion

DataBase : gun_bro
Source : Api keys
Table name : MDL_API_DATA_APCOH

API1:

http://diafirearms.azurewebsites.net/api/firearmsmdl

1.Extracting MDL_ID From first response

eg:1067876

API2:

http://diafirearms.azurewebsites.net/api/firearmsmdl/mdlid/1067876/details
1.MDL_ID passing through the second api for all data response.

Attributes
https://docs.google.com/spreadsheets/d/1hrMbT80v3Aw6Lqfu-
9HuSjCINsPYVMuRFs5yjK71XXY/edit?ts=5aeab367#gid=0

FirearmsKapow

FirearmsKapow

Firearms kapow contains data of 30 different firearm manufacturers.

DataBase : gun_bro
DB Name : FirearmsKapow
Source : Manufacturer sites(Firearms)

1.Create robot for extracting the attributes from each manufacturer site.
2.Following the same structure of MDL data.
3.Extra information available in manufacturer sites are stored in a column named
AllAttributesJSON in JSON format.

Attributes
https://docs.google.com/spreadsheets/d/1hrMbT80v3Aw6Lqfu-
9HuSjCINsPYVMuRFs5yjK71XXY/edit?ts=5aeab367#gid=0

MDL_DATA_OCT

Table Name : MDL_data_oct

DB Name : gun_bro
Source : CSV file

Description: MDL_data_oct contains firearms data provided by the client as a csv file
through mail.

Attributes
https://docs.google.com/spreadsheets/d/1hrMbT80v3Aw6Lqfu-
9HuSjCINsPYVMuRFs5yjK71XXY/edit?ts=5aeab367#gid=0

Comparison

It is the data comparison of grabbed manufacturer data stored in FirearmsKapow and MDL data
stored in MDL_data_oct.

Purpose: Need to check firearms data contained in MDL_data_oct is correct or updated as

per the manufacturer site data.

SS_holster

Table Name : SS_holster

DB Name : gun_bro
Source : CSV file

Description: SS_holster table contains holster data provided by sports south

distributor,used for association (fit information).It contains all the details of a holster like
part number,UPC, Brand etc ..