Industry Tracker takes shape

In a recent post I have introduced you to the LMeve Industry Tracker. It’s a web app, which I’m writing for my corp.

Some time has passed, and despite a hard drive failure, the app is already taking shape. The most important part I have described in the previous post, the API poller, is nearly complete. And it’s been working stable for more than a month, which is additional boon. I have decided not to parse all-and-every available api feed (do we seriously need that medal data?), but instead I have chosen to poll the most often used ones. This way I can start working on the GUI, which at this time is the most important thing for us. Of course there is nothing stopping me from adding all other API calls later on.

The following feeds are currently being parsed and loaded to the database:

• global: ConquerableStationList.xml
• global: ErrorList.xml
• global: RefTypes.xml
• evecentral: eve-central.com/marketstat.xml
• corp: AccountBalance.xml
• corp: APIKeyInfo.xml
• corp: AssetList.xml
• corp: ContactList.xml
• corp: ContainerLog.xml
• corp: CorporationSheet.xml
• corp: FacWarStats.xml
• corp: IndustryJobs.xml
• corp: KillLog.xml
• corp: MarketOrders.xml
• corp: MemberTracking.xml
• corp: StarbaseList.xml
• corp: WalletJournal.xml
• corp: WalletTransactions.xml

Each feed is cached according to the API documentation, and if a permanent error is returned, the poller will not attempt to read that feed again.

Me and TheAhmosis (Aideron Technologies’ CEO) have decided, which modules have to be up-and-running before we can start using the app for the corp:

• Timesheet – so we know how much money we owe to our employees (yes, Aideron Technologies is paying their members; wanna become a part of the famous Aideron Industry Program and get paid? Apply now!)
• Wallet – so we know how much ISK we have made (or lost)
• Tasks – so every employee knows what to make (and when)

I have added one thing on top of that: role based rights management. My old PHP framework is only using two levels of rights currently: admin and user. In this project however, we would like our corp members to be able to register themselves by using their API keys, so we need a more granular security solution. This way we will also be able to match app username to in-game characters, and display the task list only for characters of that corp member.

Pics, or it didn’t happen?

Sure thing: