[Developers] Property or Document?

[John Giannandrea]

Arthur, you should use whatever works best for your app.  Long  
documents should definitely go in the blob store, but short ones can  
go either way.

 From our side, we much prefer that you put text blobs in the content  
store and use the /common/document type.
The idea is that a document can remain static while its content  
property is versioned.
In general the /common/document schema is intended to mirror RSS and  
Atom, and is the basis for our discussion system.

In addition to search, we also support rich text editing of these in  
our UI.

Being able to mark a text property as equivalent for the article (e.g.  
in autocomplete and such) is a god idea and we will think about it.

-jg


On Jan 25, 2008, at 9:10 AM, Arthur van Hoff wrote:

> Hi,
>
> All our broadcast objects (/user/cotton/default_domain/broadcast)  
> have a summary property of type text which holds a plain text  
> summary for the broadcast. For Podcasts this is the description of  
> the podcast that is retrieved from the RSS feed.
>
> Instead of using the summary field we could also use the /common/ 
> topic/article property to store the summary as an external document.  
> This has the advantage that the summary would be displayed in  
> various lists, and it will be used to improve search.
>
> What is the right solution here? Property or document? Or both?
>
> By the way, I prefer having the summary as a property because it is  
> easier to store and retrieve from the database. Ideally I would want  
> to mark the property in some way so that it is displayed in lists,  
> and used during search.
>
> Have fun,
>
>     Arthur van Hoff
>
> ___________________________________________
> Arthur van Hoff, Dell-ZING, CTO Software and Services.
> W: 650-267-2413, F: 650-267-2498, M: 650-283-0842
>
> _______________________________________________
> Developers mailing list
> Developers at freebase.com
> http://lists.freebase.com/mailman/listinfo/developers