Google Earth: “The Immortal Game”

 

1851 was the year of the Great Exhibition in London (England not Ontario). The chess community marked the event by staging the first international chess tournament which brought in the best players of Europe.

An exciting game played during the event became tagged ‘The Immortal Game’. The opponents were Adolf Anderssen, the eventual winner of the tournament, and Lionel Kieseritsky. If Pyrrhus, son of Achilles, had not already given his name to a type of battle in which victory was gained despite incurring heavy losses, then we might today have used the name of Anderssen with the same meaning, for he sacrificed many pieces to get one bishop and two knights into a winning position.

 

chess.jpg 

Anderssen was much the more aggressive player but the rate of attrition was high. He lost a pawn early on when his King’s Gambit was accepted. Then a bishop fell, and another pawn, then both castles. Finally, he forced checkmate by sacrificing his queen even while Kieseritsky thought he was doing well to have Anderssen’s king on the run as his queen and a bishop controlled row 1 of the board.

So, why the animation in Google Earth? Colin said:

“I imagined the game as a battle between two armies, that’s easy enough to do, but I also wanted to tell a story. As well as being fun to create, the animation is intended to illustrate not only the chess game but also a story in which an embedded reporter watches the raging battle and the bloodshed all around from the position of the King’s Pawn. I’ve written a short story which now forms the bones of a longer novel.

It took a while to find the right place on Earth to set the battle. I needed high ground as defensive positions for Kieseritsky and a landscape that would match the story. I found this in the mountains and valleys of the English Lake District, one of my favourite places and destination of many camping trips.

I created the chess pieces using Google SketchUp and that was a fun exercise in itself. I exported the pieces from SketchUp as 3D models which I could then place and animate in Google Earth. The latest version uses the gx:Tour features of KML; previously I had animated the game using set positions after each move, but that doesn’t flow so well. I’m pleased with the way the pieces now glide over the ground.”

You can view it yourself in Google Earth by using this KML file.

Google Places: Onsite “Review Stations”

 

Onsite “Review Stations” AOK with Google

Several weeks ago, I attended a Google GetYourBusiness online seminar and I was surprised to hear the speaker strongly encouraging SMBS to install a computer at their places of business to use as a station where clients, immediately upon completing a transaction, could easily leave a review on their Google Place’s page.

Clearly if training, sales and support at Google all say it is OK, then it must be OK to have on site workstations for the purpose of generating reviews. And one can infer from all of this is that the review filter would not block the review based on location (IP) alone.

Implications

Yelp and Tripadvisor long ago put in place bans on reviews generated onsite from the place of business. In the case of Yelp, the reviews get filtered. TripAdvisor goes so far as to flag/punish the business with a Red notice questioning the integrity of the hotel. Avvo will allow the practice by prior approval and an explanation as to the need. Google’s policy is clearly contrary to the industry norms. Allowing and even encouraging the behavior of using a review station is questionable at best.

While there is nothing against practice in the Google Places review guidelines it is a practice that I have discouraged in my consulting and writings.

Firstly it seems coercive. If a customer is in your store, they can’t very easily say no and more importantly, they might not feel free to leave a fully honest or negative review. It is on the business owners turf and it creates an unequal power dynamic that seems contrary to the spirit of fair, honest and useful reviews.

Secondly, the practice of allowing these reviews make abuse by business owners even easier and more likely.

Apparently, Google doesn’t agree with me. For now, at least with Google, you can solicit reviews in your place of business without worry of losing them to the filter if they are otherwise ok.

Your business

Should you gather reviews from a work station on your premises? That depends on a number of factors specific to your business. Despite Google allowing the practice, I am not comfortable with it in many situations. Because of ethical concerns and the obvious, location centric footprint I have never suggested the idea to clients.

There may be reasons why it makes sense for your business. Here are some things to consider:

-Certainly all of the ethical issues are at play and if you do encourage the use of an internal workstation you need to take them into consideration.

-There will still be logistic issues with user accounts and the likely need for the business to provide many users with help.

-I have said it before and I will say it again, DO NOT put all of your review eggs in one basket. This should not be the only way you gather reviews and Google should not be the only site you ask for reviews on. They could easily change their mind on this policy and all of the reviews gathered this way could disappear in a puff of smoke.

Conclusion

I think it an error on the part of Google to encourage reviews be captured in this way. Regardless of whether it is an intentional act on their part or an oversight in their policy, I think it will further degrade the quality of reviews in Google Places and make spamming easier and more likely to occur.

Neither you nor I have the ability to change which way the winds blow. If at the end of the day it makes sense for your business to implement the practice, do so cautiously. Recognize that any benefit may be short lived and the reviews may go more quickly than they came. Most importantly of all, respect the customer and their needs in the transaction.

Google Summer of Code: Write code and save lives with OpenMRS

Earlier this year OpenMRS participated in Google Summer of Code, a worldwide program organized by Google’s Open Source Programs Office to expose university students to the world of free and open source software, and encourage those students to become long-term contributors to projects that interest them. OpenMRS is a web-based medical record system originally designed for use in the developing world, and is now used on every continent on the globe. OpenMRS is used in all kinds of health care environments, from research laboratories to hospitals to small clinics in remote villages, and even via mobile devices that collect data door-to-door.
OpenMRS has been participating in Google Summer of Code every year since 2007, and our 5th year was arguably our most successful yet. This year, 15 motivated students successfully completed projects to focus or extend the OpenMRS health care IT platform in ways that will have significant impact for our global community of users. Throughout the summer our students became full contributors in good standing in the OpenMRS community. They presented their projects’ work in progress to other developers and users and often contributed their code to our software releases to support health care professionals saving lives around the world. Unlike many other summer internships that students may have during the summer, our students were responsible for planning and delivery of “real-life projects” that came from needs and requests from people installing and using OpenMRS.
Some projects were dedicated to improving the core OpenMRS platform, and some built add-on modules to support specific types of clinical activities. There were projects focused on making the installation of OpenMRS easier, and others focused on helping improve collaboration for our volunteer community. And if the presentations our students made this semester were any indication, all of the projects were exciting ways to write code and save lives. There’s not space here to describe each project in detail, but we encourage you to check out our students and their projects on the OpenMRS Wiki and learn more about them:
  • Balachandiran Ajanthan created an add-on module to deploy reusable “SMART” health care apps inside OpenMRS.
  • Christopher Zakian reimagined a “universal” search within OpenMRS that allows users to search for any system data from anywhere within the system
  • Gaurav Paliwal created an add-on module to allow OpenMRS users to provide application feedback to their system administrators and the larger open source community.
  • Gauthami Pingili improved both the UI of the OpenMRS Patient Matching module and improved its accuracy of finding duplicate patients.
  • Goutham Vasireddi helped make it faster and easier for developers to write add-on modules for OpenMRS by creating a “wizard” for Maven.
  • Jelena Skorucak reworked the attributes a person has within OpenMRS, giving clinics the flexibility to record more information about the persons.
  • João Portela made significant improvements to our HTML Form Entry editor, allowing non-programmers to create more detailed, useful data collection forms for health care.
  • Piotr Bryk enhanced our Metadata Sharing module to make it easier to manage the export and import of OpenMRS system configurations.
  • Rahul Akula’s work helped make it possible for OpenMRS to interoperate with external laboratory information systems.
  • Sai Manohar Nethi worked to create a framework for a comprehensive Human Resource add-on module for OpenMRS, allowing the system to help manage clinic personnel.
  • Sreya Janaswamy created a way for OpenMRS users to translate phrases used by the application into other languages, inside the application itself.
  • Sriskandarajah Suhothayan created a way for the OpenMRS Notifiable Condition Detector module to watch for certain large-scale patterns and send notifications to clinicians via SMS or e-mail.
  • Suranga Kasthurirathne created a new way for OpenMRS to store clinical observations that reference other people or locations.
  • Taras Chorny built a system to allow OpenMRS to be installed and upgraded using a variety of languages.
  • Victor Chircu built an “Atlas” add-on module that allows OpenMRS users to opt-in to report their location, type of clinic, and number of patients on a shared map to represent the active OpenMRS community.
Since we started participating in Google Summer of Code, we’re very proud that so many of our students have stayed active in the OpenMRS community and continued to contribute their talents after the program ended. In fact, three of our students have gone on to become full-time OpenMRS developers paid by various organizations involved in our community.
We continue to be more and more impressed with the students who are interested in our work, and are proud to welcome them into the OpenMRS family! In fact, this year, 2011 Google Summer of Code student Suranga Kasthurirathne was able to join us in October for our annual OpenMRS implementers meeting in Kigali, Rwanda. Suranga provided some excellent feedback about his involvement in Google Summer of Code this year, and about his experience meeting the OpenMRS community face to face. Read his blog post for more of his thoughts.
Once again, this year we were blown away by our amazing students during Google Summer of Code.