[Developers] Too Many Writes Error

[Michael Jones]

Hi Scott,

On 9/7/07, Scott Meyer <sm at metaweb.com> wrote:
>
> > I seem to have reached some sort of quota on writes to Freebase and now
> > get the error :
> >
> > "result status not okay: /api/status/error; error: Too many writes"
> 10,000 graph primitives per day, I believe.  If you have a large amount
> of data to load, the usual procedure is to debug it in the sandbox and
> then get an exemption from the 10K limit when performing the upload.


It's only about 3-400 records, but I am testing an upload script, and ran it
about 15-20 times yesterday, refreshing exisitng objects.  It doesn't seem
like this should have triggered the limit, but it's possible.  Is there a
reason the limit is on total writes and not on instance creations?

> External applications will often have need of grafting their own types
> > onto Freebase instances in order to flag them or add meta data that
> > would not be of interest to the general public browsing Freebase.
>
> Currently, any user can create a type and use it to type existing
> objects.  In fact, we would much rather you do that, than create
> duplicate objects.  Is that what you want?


That is exactly what I want, and I am doing now for a Fantasy Football Draft
simulator I'm building.

I have grafted the type '/user/szaijan/fantasy_football/player' to all of
the instances of type '/american_football/football_player' that I have data
on.  I've also created types and instances for the objects that will support
the application (League, Owner, Team, et. al.)  In addition, I have created
Projection objects, which hold my estimate of a player's performance and
average fantasy draft position over the course of a given season.  My app
will essentially predict each selection of a fantasy draft based on the
point projections and average draft position, then rank the teams.  A lot of
meta data is used in the sorting, and several enumerated types required near
duplicates of types already in the database.

Ideally, I'd like to make sure no one who isn't running my app can see,
change, or add to this data.  There are two reasons for this.  In the case
of enumerated types, I need to control what is available so I can script for
it.  Allowing arbitrary objects to be added could break my app.  In the case
of meta data, most of it does not make sense outside the context of my app,
and it is thus not suitble for public viewing.

I know that one viewpoint is that such data does not belong on Freebase.  My
contention is that allowing for and supporting such data will be of benefit
in encouraging people to develop Freebase powered apps, for the reasons
specified earlier.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freebase.com/pipermail/developers/attachments/20070907/4a65e5bb/attachment.htm