[Developers] Editing longer text fields.

[Arthur van Hoff]

The indexing of text properties has only been functional since fairly
recently. However, the other reason to create the article is to
disambiguate the topic during a search. So we'll keep using the article
and use the summary for a short plain text description. Thanks!

> -----Original Message-----
> From: developers-bounces at freebase.com [mailto:developers-
> bounces at freebase.com] On Behalf Of Faye Li
> Sent: Tuesday, March 25, 2008 4:39 PM
> To: For discussions about MQL,Freebase API and apps built on Freebase
> Subject: Re: [Developers] Editing longer text fields.
> 
> Hi Arthur,
> 
> All properties of type /type/text are already being indexed for
> search.
> There's no need to copy the summary into the article if that's the
> only
> reason for doing so.
> 
> -- Faye
> 
> 
> Arthur van Hoff wrote:
> > Hi Faye,
> >
> > The summary is a non-html description of a broadcast that we can
> display
> > in our environment (which does not support html). We have to copy
> it
> > into the article so that it is indexed for search.
> >
> > We've asked if it was possible to add an option to the schema which
> > flags the summary for indexing. That way we would not have to put a
> copy
> > in the article.
> >
> > Using a separate article of type text/plain is possible, but it
> adds a
> > lot of complexity since we can't simply request the content using a
> MQL
> > query.
> >
> > Have fun,
> >
> >     Arthur van Hoff
> >
> >
> >> -----Original Message-----
> >> From: developers-bounces at freebase.com [mailto:developers-
> >> bounces at freebase.com] On Behalf Of Faye Li
> >> Sent: Tuesday, March 11, 2008 4:26 PM
> >> To: For discussions about MQL,Freebase API and apps built on
> Freebase
> >> Subject: Re: [Developers] Editing longer text fields.
> >>
> >> Hi Arthur,
> >>
> >> A little off-topic as I'm trying to understand your data model and
> >> see
> >> if there's a better way to support that. At least for this topic,
> I
> >> see
> >> that the content of the Summary (/type/text) is identical to that
> of
> >> the
> >> Description (/common/topic/article). So my questions are:
> >>
> >> 1) What's the purpose of the Summary property, and how is it
> >> different
> >> from that of the topic article, if at all?
> >> 2) If it tends to contain sentences instead of short phrases,
> would
> >> it
> >> serve your purpose better to set the expected type as
> >> /common/topic/article if that can be handled well by the Freebase
> >> app?
> >>
> >> Dan,
> >> I recall that the idea of allowing/supporting multiple articles on
> a
> >> topic came up last year. Was a definitive decision made on that?
> >>
> >> Thanks,
> >> -- Faye
> >>
> >>
> >> Dan Milbrath wrote:
> >>
> >>> agreed. we'll try to address this in the next release or two.
> >>> thanks.
> >>>
> >>> - Dan
> >>>
> >>> ----- Original Message -----
> >>> From: "Arthur van Hoff" <AVH at zing.net>
> >>> To: "For discussions about MQL, Freebase API and apps built on
> >>>
> >> Freebase" <developers at freebase.com>
> >>
> >>> Sent: Tuesday, March 11, 2008 3:27:33 PM (GMT-0800)
> >>>
> >> America/Los_Angeles
> >>
> >>> Subject: [Developers] Editing longer text fields.
> >>>
> >>> _______________________________________________
> >>> Developers mailing list
> >>> Developers at freebase.com
> >>> http://lists.freebase.com/mailman/listinfo/developers
> >>>
> >>> _______________________________________________
> >>> Developers mailing list
> >>> Developers at freebase.com
> >>> http://lists.freebase.com/mailman/listinfo/developers
> >>>
> >>>
> >>>
> >> _______________________________________________
> >> Developers mailing list
> >> Developers at freebase.com
> >> http://lists.freebase.com/mailman/listinfo/developers
> >>
> > _______________________________________________
> > Developers mailing list
> > Developers at freebase.com
> > http://lists.freebase.com/mailman/listinfo/developers
> >
> >
> 
> _______________________________________________
> Developers mailing list
> Developers at freebase.com
> http://lists.freebase.com/mailman/listinfo/developers