Although many properties are self-explanatory, others are mysterious to the casual editor. It would be great if each property's pulldown menu in the topic viewer had a way to get more information on what the property is and how best to use it.
more
Each property should have help text
We can tell you that Each property should have help text is a
If you know more about Each property should have help text, you can add more facts here »
Similar topics in Freebase
-
App-friendly authentication API
In thinking about applications I'd like to build, I'd don't want to make people authenticate through my app. There's no reason for people to trust me with their pasword, and I'd rather not even know it, so that I can't possibly leak it.In the web links, I've included a couple of links to auth APIs... -
Link dialog in description editor should be prefilled with selected text
When editing a description, to add a link I highlight text and click the "link" icon. Usually I end up having to immediately retype the text I just selected into the metaweb link field. Seems like it might make sense to pre-fill that field with the selected text to save time (or even... -
Add a 'report bug' link in the header
I understand, that there's the 'Feedback' link at the page bottom. But this part of the page is often not visible without scrolling. At least during Alpha and Beta stages, it's important to make it as simple as possible to give feedback.The feedback page is nice and lean. You might make a... -
Usability of type selection dropdown list
In some cases, the autocomplete entry can be frustrating to use.For instance, if "Web Site Category" has been selected as a type, and I want to correct it to "Web Site", then I cannot just delete the word "Category" and hit enter -- this just re-selects "Web Site Category". I need to delete... -
Query editor too tall
The query editor is too tall to fit without scrolling even when maximized on my 1400x1050 screen using normal browser settings. It should at least fit on a 1280x1024 screen, and it would be great if the layout were flexible enough to accommodate a variety of window sizes. -
Can't link to users in text editor, favorite topics
I'd like to be able to link to users as internal Metaweb links. But at least when I try it for my two accounts ("/user/william" and "/user/querybuilder_bot") the autocomplete can't find them, both in the text editor link tool and in the "favorite topics" autocomplete. -
Mass Import
It would be great to be able to have some kind of mass import functionality when we are setting up our profile pages. For example, using the API tie into Last.FM to grab your favorite artists (just as an example), and maybe something similar for movies. Alternatively, it would just be nice to be... -
Query editor should not resort query by key
Although key order doesn't make any difference to the API, you can see in the docs that changing key order can make the query clearer. Unfortunately, the query editor automatically sorts the keys in alphabetical order on submission. In addition to making the query more confusing to a novice, it... -
Better bug report UI
The edit box that pops up when creating a software ticket is confusing since it is not clear what to type in it (the name of the bug). Once, they do figure that out, it really not clear to most users what to do with Ticket type, Category, etc.Ordinary users need a simpler way to report bugs. -
MQL/JSON comments
Hello --As a newbie to the wonderful world of MQL, JSON and freebase, please excuse if this is a silly request.In putting together and/or reading nested MQL queries, I often find myself wishing for the ability to add english-language comments to the query, to keep track of where I am and what I am...