Tingle's Technology Notes

I am the Technical Lead for CDL Digital Special Collections, these are some notes of mine, views expressed are my own or the original author's and do not represent my employer. http://btingle.bitbucket.org/
Recent Tweets @tingletech
Posts I Like
Who I Follow
top 100 tags
Posts tagged "google"

Chicago Digital Humanities Plenary Session

Jon Orwant (Google): More Stuff and more things to do with it. A talk with responses by Neil Fraistat (Maryland), and Jeremy York (Michigan)

Brian Tingle’s notes from Jon’s talk [google doc reader] [publish to the web version]

Two stacks

  1. Computation Stack
  2. Linguistic Stack

Computation Stack

Computation

Query

Data

Semantic Stack

ideas

facts, sentences, quotations

parts of speech

structure

letters, punctuation, symbols

text, pictures

pages

Move computing to the data (too much data to move to each researcher)

ex post facto criteria for google DH grants

Is it feasible?

  1. unrealistic requirements for clean data
  2. AI-ex-machin

Is it worthwhile?

  1. someone else doing it?
  2. is it too easy?
  3. is it broad enough?

Can we provide needed assess?

Does it enable other researchers?

Does it illustrate a new style?

  1. refactoring the victorian
  2. what walter holten did

Move up a level in a stack.

Improve level in a stack (reuse-able data set)

Or reasonable using one level as a proxy for a higher level (i.e. structure as a proxy for ideas)

Moving up a level by creating tools (intralanguage translations {early english to modern english})

during the comments from the others this was all I wrote down

corpra space design in bamboo

thedailywhat:

Asaf Hanuka:Google Monster

Drawn to scale.

[superpunch.]

Wave remains an over-engineered and under-designed product that was poorly prepped for general introduction beyond a small developer base, which has become an all-too-familiar Google ritual.
This October 13th, just over one year after dropping NavTeq, the other shoe dropped as well. Google disconnected from Tele Atlas and began to offer maps that were free and clear of either license. These maps are based on a combination of their own data as well as freely available data. Two weeks after this, Google announces free turn-by-turn directions for all Android phones.
Starting today, we’re enabling people everywhere to find and read full text legal opinions from U.S. federal and state district, appellate and supreme courts using Google Scholar.

infoneernet:

The Wall Street Journal added some crucial context to discussion of the revised Google Book Search Settlement announced late Friday: it “would cut the number of works covered by the settlement by at least half by removing millions of foreign works.” (Only works from the United States, the United Kingdom, Australia, and Canada would be included.)

Librarian and consultant Karen Coyle commented, “This greatly changes the value of the institutional subscription for higher education, as well as the value of the ‘research corpus’ (essentially a database of the OCR’d texts that researchers can use for computational research)… As it is, too many Americans are unaware of the world outside of those Anglo-American borders. This will just exacerbate that problem.”

Seen at Library Journal

infoneernet:

Mike started the talk by giving the developers a good laugh: it seems that Google manages its kernel code with Perforce. He apologized for that. There is a single tree that all developers commit to. About every 17 months, Google rebases its work to a current mainline release; what follows is a long struggle to make everything work again. Once that’s done, internal “feature” releases happen about every six months.

Seen at LWN.net

Notable comment:

Posted Oct 21, 2009 5:19 UTC (Wed) by bradfitz (subscriber, #4378)

if you’re going to have a blessed “central” repo anyway, who really cares if that repo is actually git, svn, perforce, etc, as long as you can use your DVCS of choice at the edge?

The alternative is changing years of accumulated tools & checks every time a new VCS comes out and you change your master repo’s storage format.

*shrug*

sameera:

Google is open sourcing a collection of Javascript tools today that will enable developers to build faster, more powerful and more efficient web applications using some of the same code that…