Patrick's suggest is how I usually achieve this, but think for a few minutes on your choice of EnumType.STRING vs EnumType.ORDINAL. How do you think you're application will change with time? Generally I prefer STRING since reordering of your enumeration or removal of values will leave you in a bind (say for an API that you don't control). Either way you're subject to change, but STRING is more versatile in my mind. I all depends on the volatility of your project schema.
Just don't worry about a few bytes here and there since you're now in
the cloud and bytes are not what they seem. For example a boolean is a
4 bytes in GAE DataStore due to word size issues. That's right, 32 bits to store 1 bit (note you can store 2 bools in 4 bytes, but if you have just 1, it's 4 bytes).
Sincerely,
Joseph