Amazon EC2: Finding AMIs and Using Command Line Tools

I set up my command line tools with a little help from Robert Sosinski’s blog which I think lays things out a little more clearly than Amazon’s instructions.

I’ve abandoned for now using Elastic Fox, my brain needs to wrap around how the back end really works before I can start using a GUI….that’s just the way I roll I guess. So I started searching around for a good AMI to use. It seems that amazon hasn’t really updated their public AMIs, so the Fedoras are a bit out of date.

I noticed that Sun has OpenSolaris on a few AMIs, it requires you to register but the terms of use don’t seem to ridiculous; essentially it says you’re only going to use OpenSolaris on EC2…which is true…I’m not going to install Solaris on any of my machines. Apparently once Solaris approves my use of the AMI I can start playing around. That seems a bit absurd. But I did find a very basic AMI that’ll I’ll generally be happy with playing around with: AMP stack AMI on OpenSolaris provided by Sun Microsystems, Inc.

So now I’ll just play around with the commandline tools and see what I can get. Hopefully Sun will approve me soon….

Posted in Ideas | Tagged , | Leave a comment

New API for Google Book

Google Book Search has added a new API, the Embedded Viewer API. In addition to being able to call for information about the book’s preview you can create static links to various parts of the book’s preview.

Additionally, Google has also come out with a way to embed the viewer into your webpage. They have a developer guide and a reference guide on how to use the embedded view API; and they created a Preview Wizard which does it for you automatically, that’s how I created this page. They have also provided some samples to help you get started.

You can see how this information, in conjunction with the book data API would come in handy if say you wanted to create your own catalog or use images in your already existing catalog.

Interesting side note: The libraries participating in the Google Book project have decided to work together to create something called the HathiTrust. This trust will keep all the books that Google is scanning in case Google goes belly up (Google provides an electronic copy of each book it scans to the library it scanned it from). They too are developing APIs and what not so that you can get data out of the books, it’ll be interesting to see what they do with all of this data.

Posted in Fun | Tagged , , | Leave a comment

Creating a Constrained TEI Schema

To create a schema you can use Roma. This gives you a graphical interface that allows you to include or exclude elements, include or exclude attributes, and constrain values for attribute values.

A few pointers for using Roma…

  • hit submit every time you make a change. there is a bug that sometimes it doesn’t look like you’ve saved your changes, but in reality you have. and if you don’t hit save, then you’ve definitely not saved your work.
  • give your schema a name that will help you understand what its purpose is for. you can also supply a description of its purpose. one idea is to create a schema and then come back later and modify it as you delve deeper into analyzing your text.
  • save your schema as Relax NG schema (compact syntax). this files gives your xml code a place to go to double check that you are organizing your data properly.
  • save your documentation in html so that you can read what the elements and attributes you can use in your customized schema are.
  • save your customization (aka the ODD file). this is the file that creates the schema (ie .rnc file). if you have any problems with your schema you might want to look at the ODD file to make sure the changes you made are properly reflected in the schema document.

creating a schema allows your coders to reduce the options they can choose from and hopefully reduce the amount of mistakes they can possibly make.

Posted in Work | Tagged , | Leave a comment