Kristina Neumann, one of our PhD candidates in the Department of Classics at UC, will be giving a presentation soon on her work with the Google Earth database mentioned here earlier. She has done amazing things with this database and created a series of KML files that allows her to express the reach of Antioch coinage in a stunning way.
This paper is part of the joint AIA/APA meetings in Chicago happening now. See it in session 5D at 12:30 on Saturday January 4.
In ancient times, much like now, authorities determined which foreign currency was accepted in a community. For Neumann, this made coins an ideal representation of a political relationship among cities. For example, if lots of Antiochene coins were discovered in a neighboring city, it’s likely a political agreement existed between the two governments.
Coins were also a data-rich resource for Neumann. In addition to tracking where the coins were found, she cataloged critical information about a coin — such as when it was minted and under whose authority it was made — that has been derived from the images and inscriptions imprinted on it. Other artifacts, like pottery, were less likely to have such identifiers.
Neumann uses Google Earth to convert the vast information in her coin database into a visual representation of Antioch’s political borders. She analyzes how the software plots which coins were found where and in what quantity across different historic time periods. This way she can follow the transformation of Antioch’s political influence as it was absorbed by the Roman empire.
She has found Antioch’s civic coins were spread farther out than previously theorized, and they were particularly abundant along a known trade route. Neumann can scan centuries of change in seconds with Google Earth to show the overall contraction of Antioch’s political authority but also its continued and evolving influence in selected regions and cities — and eventually its greater integration within the empire.
Google Earth allows Kristina Neumann to track change in Antioch as it was absorbed by the Roman Empire.
Her talk is already getting some news attention, which I have been tracking here.
For 2014, the CAA conference is in Paris (not Texas). The conference itself runs from 22-25 April. The call for papers deadline is October 31.
They have a list of sessions available.
You have until October 1, 2013.
Award for Outstanding Work in Digital Archaeology
Digital technologies are driving important changes in archaeology. Despite the increasing acceptance of digital technology in daily life, however, determining how to assess digital scholarship has proved difficult: many universities remain unsure about how to evaluate digital work along side more traditional forms of print publication when faced with tenure and promotion decisions. Recognizing the value of digital scholarship, and aiming to encourage its practice, the AIA offers this award to honor projects, groups, and individuals that deploy digital technology in innovative ways in the realms of excavation, research, teaching, publishing, or outreach.
Criteria for Selection
Nominations of projects and individuals are welcome. Nominations may be made by anyone, including the project director or the principal members of the team responsible for the digital creation. Nominations of collaborative projects are encouraged. At least one member of the leadership team, or any individual nominee, must be a member in good standing of the AIA. Please submit the AIA membership number(s) with the nomination.
Due Date for Nomination
September 15, 2013 Extended to October 1, 2013
With iOS 7 arriving tomorrow, Apple is extending some love to the owners of older iOS devices that have been left behind. New compatibility features, first spotted on Reddit, will now kick into action if you attempt to download an app that is not supported by your current firmware. Instead, the company now asks if you’d like to install the last compatible version, which, for some apps, can be over a year old.
I could have used this during the past summer when I had to reset a first-gen iPad but couldn’t install OmniGraffle.
According to FileMaker there is an issue between iOS 7 (due to be released on Sept 18) and FileMaker Go that affects the creation of a unique UUID number, which has the potential to wreak havoc on databases that rely on that unique number for syncing. This bug hits our own databases, as well as the copy of the database that is hosted at this blog.
Syncing from multiple copies of a database requires that each record have a very unique number. This is more than a straight serial number, since two separate copies of the database can each create a record in the same table which would give them the same serial number. Instead, our database relies on something more specific, a UUID which is generated from several types of information.
The UUID that we use is a custom function written by Jereme Bante a few years ago named UUID.New. It creates a unique number for each record based on:
- recid (an internal number generated by FileMaker)
- the NIC (or MAC) address of the device that created the record
This is stored as a custom function to allow all tables in the database access to it.
According to FileMaker, all iOS devices under iOS 7 will return the same NIC address,. This can theoretically return the same UUID for two records if two devices created a new record in the same table at the exact same time.
I am not very worried about this myself. The odds of two records returning the same UUID are pretty small. Also the syncing scripts that I have use items other than the UUID for matching. For instance each new record is given _DeviceCreated and a _DeviceModified fields. Those are set to auto-enter a calculation [Get ( SystemPlatform ) & "-" & Get ( HostName )]. So unless both devices are iPads and are both named the same (which shouldn’t happen), they won’t supply the same data.
If you are worried about this bug you can switch from using the UUID.New function to another of Jereme Bante’s functions named UUID.Random which replaces the NIC portion of the UUID to a set of random numbers. Switching to this function won’t affect your old records and won’t require that you wait for FileMaker to fix FMGo.