Pulling data from the JSS for asset management?

I recently went the route that @lisacherie mentioned in her comment above. I setup a RHEL 7 server and installed python-jss on it. I then created a script to do the following:

1. Get a list of computers from the JSS.
2. Iterate through each computer and get the full JSS computer record for that system.
3. Grab the serial number and barcode of the computer from the JSS record.
4. Use this info to query against a website/API that another department of our team created for viewing asset data without using the ITAM product's desktop client.
5. Gather desired details from ITAM record (e.g. asset assignment, location, etc.) and also do comparisons between ITAM data and JSS data and return comparison results. Store these values in a Python dictionary. The key names of each value match up with the names of "text field" extension attributes that I created in the JSS.
6. Iterate through each extension attribute in the JSS computer record and find the extension attributes that the script should populate. When an extension attribute is found, copy it to an XML element tree object that I created before processing.
7. Clear the JSS computer record's contents and replace it with the contents of the aforementioned XML element tree object. This is done to ensure that other values aren't overwritten in the unlikely event that a computer checks in while it is being processed by the script.
8. Save the modified computer record back to the JSS.

Once all of this was complete, I setup a cron job to run this everynight. So far, it has been working out quite well for us.

UPDATE: We decided to build out our asset tracking system using JIRA. Atlassian has an excellent how-to eBook on how to use Jira for asset management, you can find it here: http://atlassian.wpengine.netdna-cdn.com/wp-content/uploads/assetebook.pdf

It's a lot cheaper than a third party solution and it gives us infinite flexibility (including the ability to sync directly to the JSS).

Github URL is now

https://github.com/Oomnitza/oomnitza-connector