<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.5pt;
font-family:Consolas;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:Consolas;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal>I need some advice on the best way to do something. What I
have isn’t working for me anymore.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>A while ago I had asked for a way to get all the properties
associated to a topic and Alexander was nice enough to give me this query:<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoPlainText>{<o:p></o:p></p>
<p class=MsoPlainText> "query" : [<o:p></o:p></p>
<p class=MsoPlainText> {<o:p></o:p></p>
<p class=MsoPlainText>
"master_property" : null,<o:p></o:p></p>
<p class=MsoPlainText> "source" : {<o:p></o:p></p>
<p class=MsoPlainText> "id"
: "topicId"<o:p></o:p></p>
<p class=MsoPlainText> },<o:p></o:p></p>
<p class=MsoPlainText> "target" : {<o:p></o:p></p>
<p class=MsoPlainText> "id"
: null<o:p></o:p></p>
<p class=MsoPlainText> },<o:p></o:p></p>
<p class=MsoPlainText> "target_value" :
null,<o:p></o:p></p>
<p class=MsoPlainText> "type" :
"/type/link"<o:p></o:p></p>
<p class=MsoPlainText> }<o:p></o:p></p>
<p class=MsoPlainText> ]<o:p></o:p></p>
<p class=MsoPlainText>}<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>So, I modified it a bit to look like this:<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoPlainText>{<o:p></o:p></p>
<p class=MsoPlainText> "query" : [<o:p></o:p></p>
<p class=MsoPlainText> {<o:p></o:p></p>
<p class=MsoPlainText>
"master_property" : null,<o:p></o:p></p>
<p class=MsoPlainText> "source" : {<o:p></o:p></p>
<p class=MsoPlainText> "id"
: null,<o:p></o:p></p>
<p class=MsoPlainText> “guid”
: null,<o:p></o:p></p>
<p class=MsoPlainText> “name”
: “Something”<o:p></o:p></p>
<p class=MsoPlainText> },<o:p></o:p></p>
<p class=MsoPlainText> "target_value" :
null,<o:p></o:p></p>
<p class=MsoPlainText> "type" :
"/type/link"<o:p></o:p></p>
<p class=MsoPlainText> }<o:p></o:p></p>
<p class=MsoPlainText> ]<o:p></o:p></p>
<p class=MsoPlainText>}<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>That worked out quite nicely until I started messing around
with locations (and I’m sure locations aren’t unique in this regard).
But, if you send that query to freebase with Kansas as the name, you wind up getting
back 2700 properties. Most of them “/location/location/contains”
but still, 2700. It takes forever if it doesn’t time out on me. (Even
if I send in the exact guid, I still wind up with 2400 properties – 2300 of
which are the /location/location/contains.). <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>What I do with those properties is loop through them, filter
out anything that starts with /guid, /type, /user as well as any duplicates and
create another query to get the values for those properties. <o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>So, my question is this: given what I’m trying to
accomplish, is there an easier way to go about it? Is there a way to get the
properties for the topic, without duplicates, without /type, /guid, /user so I
can then query to get the information I really want about the topic? I don’t
really want to hard code all the properties I want to go after for each and
every type. I know I could use cursors to “page” through the data,
but that would still take forever and I’m trying to make it as fast as
possible.<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Thanks,<o:p></o:p></p>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Kendra<o:p></o:p></p>
</div>
</body>
</html>