search

ddavisqa / google-refine

Automatically exported from code.google.com/p/google-refine
0 stars 0 forks source link

Add Columns From Freebase dialog should support constraints #92

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
This feature would allow constraints to be placed on the data imported from 
Freebase.  It would affect the extend-data-preview-dialog page.

Original issue reported on code.google.com by iainsproat on 23 Jun 2010 at 4:24

GoogleCodeExporter commented 8 years ago 
Iain, it does support constraints right now: after you've added a property and 
the preview gets updated, the corresponding column header has Remove | 
Constraint. It certainly needs design work.

Original comment by dfhu...@gmail.com on 18 Jul 2010 at 1:19

GoogleCodeExporter commented 8 years ago

Original comment by dfhu...@gmail.com on 18 Jul 2010 at 1:19

GoogleCodeExporter commented 8 years ago

Original comment by dfhu...@google.com on 27 Sep 2010 at 10:03

GoogleCodeExporter commented 8 years ago 
Hello, I want to add population values for each country in my table but as I 
guess you know when you try to add a new column from Freebase choosing the 
"Population number" property you get that value for ten different years for 
each country but, in my case, I want only the last value. 
I saw the constraint option in the preview dialog and I changed the default 
JSON query which is as the following one:
({
  "limit": 10
})
putting 1 instead of 10 but unfortunately this does not perform what I want 
because anything has been modified.

Original comment by perrone...@gmail.com on 23 Dec 2011 at 10:57

GoogleCodeExporter commented 8 years ago 
Refine has supports constraints in this context now (not sure what version they 
were introduced in).  

re: comment 4 - A late change added for v2.5 was the ability to use the "sort" 
keyword in constraints (it was filtered before).  To get the latest population 
figure which is within the last 5 years, you could do something like

{"year>":"2006",
 "year<":"2012",
 "sort":"-year",
 "limit":1
}

The "year<":"2012" is necessary because some projected future population data 
(e.g. for the year 2025) have been added to Freebase by users.

Original comment by tfmorris on 27 Dec 2011 at 8:42