Discussions on Bug / Feature Request
Filtersonly show threads also posted in:
-
-
We downloaded the films data dump, and found that the value of the netflix ID wasn't present in the films.tsv, even though it appeared as a column in the first row. Any reason for this? Is there any way we can get the netflix ID?
-
The Netflix IDs have been added and updated extensively since the data dump. I would recommend going to filter view (http://www.freebase.com/view/film/film), adding all the columns from the left that you want, including the Netflix ID, and then "Use these results" --> "Save as TSV/CSV" to produce your own version of the latest film data. Please post if you have trouble doing this.
-
So, would this mean that there could be the possibility of certain values being updated, that may not be reflected in the dump? Is there any way of getting this delta as well?
-
The best way to pick up deltas between data dumps would be by using our API; this would be very easy for the case you mention, simply getting Netflix IDs for any that have gained them since the last dump. See our help section for API help.
-
Another way to detect recent changes is to monitor the RSS feed of the history for that type. For example, the Film type history feed is:
http://www.freebase.com/feed/history/all/film/film
This will notify you as soon as someone adds a new film, changes an existing film or deletes a film.
-
-
-
This isn't necessarily a bug, but how can you remove the value in the Gender field from the Person type?
For example, I want to remove the Person type from the Bass Brothers topic, but I need to remove the "Male" from the Gender. But I can't figure out how to do that.
If I clear out the value, it wants me to pick something from the list. I cleared the value and then quickly hit enter, but I don't think the form likes that option as it keeps the value pick list open even when the box is closed :) [of course that disappears as soon as I leave the page]
Is there a way to allow someone to blank out a field for cases like this?
-
Why do you need to remove "Male" from Gender before removing the type? That's not necessary. You can remove the type without clearing the gender first.
-
Oh, good to know. I assumed I had to disassociate all the values before removing the type or there could be a value/space/whatever left hanging on the other end.
-
Well... detyping a type from a topic is not necessarily "clean". If a topic is erronously typed with property values, the cleanest way is to detype is to remove all the property values first and then detype the type. Otherwise, you get property artifacts left behind (the link between the topic and the property/value is not unlinked). As an example. see my topic on sandbox - I typed myself as a location, added a containment, then detyped without removing property values.
We're trying to get clean detyping functionality into the client soon, as well as have backend validators run periodically. However, in the meantime, I advocate removing property values first before detyping.
-
I guess it depends on if the property value is linked with another topic? So it probably doesn't matter for date of birth, but does for employer.
Not sure where gender falls into it, but the problem with removing the value is seems to want a value and there's no obvious way to remove it.
-
Ah, the enumerated type is trying to "force" you to pick a choice. What I do to remove the value is delete the current text in the edit popup, wait for the popup choices appear, then click off of the edit popup. The popup choices will disappear and then you can click save and the value will be disconnected. Definitely not desired functionality - I'll bring it up with client design.
As for removing values, it applies for all properties.
-
-
-
When you import a list of episodes to a tv series or season, once you've reconciled all of the episodes, on the next page it says the episodes will be reconciled with existing episode etc., but all the episode numbers are going to be created as new topics. And on the next page, it says they've been created, and the links go back to the home page.
-
It also seems that when one imports a list of episodes to a season, only existing episodes save the episode number, if you add a new episode, the episode numbers appear to be deleted. And when you import episodes to a TV series, none of the episode numbers are saved.
-
It looks like there are two problems here: one an unclear UI, and the other an actual possible bug.
The bit about creating episode numbers as new is because the episode numbers are just text values, not actual topics; the “1” for the first episode is not going to be reconciled with an existing topic called “1.” The UI should be clearer about what is happening with text and number values, however.
The bit about the episode numbers not taking is a real problem.
I will add both of these issues to our bug tracking system.
-
-
-
When an actor has appeared regularly in more than six seasons of a show, they don't all show up automatically, only the first six show up, you have to press More to see the rest. But this means when you edit them, only the first six appear in the edit box, the others aren't visible. eg. Stargate SG-1 for Richard Dean Anderson
-
It also appears to be a problem on the actor, character and season pages (and presumably any more where they appear), except in those cases, no More button is available, but if you go to Stargate SG-1 Season 8 for example, Richard Dean Anderson is in that season, but on the list he's no in season 7, but if you go to season 7, season 8 isn't listed, if you get my drift.
-
Oooh, that is a problem. I'll report a bug in our internal tracking. Thanks for letting us know.
-
-
-
People are adding bands, tv shows and things like Wikipedia to the Influence domain (which is intended to be restricted to people), which adds the included type 'people' to things that are obviously not people. I'm not policing the domain rigorously, and you're going to end up with junky data. You could have something like a message:
"Wikipedia" is not yet typed as a person (required by Influence Node). Do you want to continue and add Wikipedia as a person?
-
-
-
Usually the auto suggestions are fine, but sometimes there are topcis, particularly common city/town names, where there are more options but the auto-suggest list isn't long enough.
For example, try adding Cambridge, Vermont to a location field and you won't see it (well, not the couple times I tried). And depending on the Type, you may not be able to go into that town topic to add the town in the "back way".
One thing I've noticed while trying to add town names to fields is that the auto-suggest won't use the aka name of a topic. So you can't type "Cambridge, V" to pull up the Vermont specific topic.
Perhaps if we could, then we'd be able to better access these "hidden" topics in the list. I know if we lengthen the list then we can run into other issues (like performance) and we probably can't make certain names/topics give a longer list instead of doing a global lengthen. Otherwise, not sure how we can address this issue.
-
Autosuggest does use the aliases, but it doesn’t currently do well with partial matches. If you actually type out “Cambridge, Vermont” you will get two primary results: the town, and the village. However, anything less than the full name of the state will return no hits; that is definitely not ideal.
-
Ah, I see. I'll start typing out the whole thing then. Thank you
-
OK, I'm having more trouble with this auto suggest list, but in a different way. For some reason I can't get the United States topic to come up when I type it in the Import From in Statistical Region!
I've been able to get it previously (other days), but for whatever reason it doesn't as of now. I've tried it a couple times, and even made sure no one renamed that topic to something weird. I get Boston, Massacheussetts, Colorado, US $, etc, but not the actual topic. And I'm typing the full "United States".
Ideas on how to fix??
-
I just checked that United States topic, and I think something is wrong with it. When you click on it, it goes to a domain, not the topic itself. Did something get screwed up?
-
Oog… yeah, it got mangled. This is a known problem but as yet undiagnosed; the good news is it was a Metaweb employee who did it this time, so we can
waterboardask him how it happened. I’m going to leave it broken for just a little longer so the client team can diagnose it, but it should be fixed soon. -
I've got a similar problem with similar symptoms - it seems at the very least, priority should go to exact name/type matches first, then exact name matches, then approximate matches. This isn't what happens and it causes all sorts of grief if the topic name is a simple word.
For example, I want to link to a Doctor Who TV Episode called "Midnight". If I type the word, the topic I want doesn't appear as an auto-suggest - many other topics mentioning the word appear first, some of which aren't even TV episodes. At this point I have only one choice, create a new topic, and plan to merge it later. Of course, the problem is, I can't submit a merge report either, since I get the exact same auto-suggest list with the entry I want too far down.
At the very least, would it be possible for me to use the guid? I can filter down and find the node from the full search box.
-
This is underdocmented, but you can always enter an ID in the autocomplete box. So once you know that “Midnight” is /guid/9202a8c04000641f8000000008e684ab, you can enter that literally into the autocomplete box.
-
Thank you so much!
-
-
-
If you do a search for "bennington vermont" you'll see the first result appears to be a normal topic. It even shows the wiki description. But when you click into it, you only find the image and its properties. I can't find a real topic for Bennington, VT, and so didn't know if something went wrong with the import of this one, or what happened.
-
-
-
The MQL query editor (http://www.freebase.com/tools/queryeditor) is not able to generatea a functioning permalink for the following query
{"id":"#9202a8c04000641f8000000004f4abbe","name":[],"type":[]}
Contrast this to the sample query (from http://www.freebase.com/view/guid/9202a8c04000641f800000000544e148):
{"albums":{"query":{"album":[],"name":"The Police","type":"/music/artist"}}}
which corresponds to the permalink:
http://www.freebase.com/tools/queryeditor/?q=%7B%22albums%22:%7B%22query%22:%7B%22album%22:%5B%5D,%22name%22:%22The%20Police%22,%22type%22:%22/music/artist%22%7D%7D%7D&read=1
(http://tinyurl.com/5wgz7s)
Perhaps, it's the "#" in the id that is causing the permalink generator problems.
Thanks,
-Raymond
-
-
-
I can't enter a value for the ICAO field under Airports. When I try to save the value I get a message saying I don't have authorization. Is this a bug, or by design?
an example code is FMMI for Ivato Airport in Madagascar
-
Hi evening,
See http://www.freebase.com/discuss/threads/authority/icao/ESSX#/guid/9202a8c04000641f80000000089b3836 . The long and short of it is that we've updated the property to be an property enumeration with a more restrictive permission. We hope to be loading some more airport data soon, so stay tuned! -
Thanks for the info. I'll wait to add smaller airports until the codes come in -- it should make it a lot easier to keep track of (some airports(some have multiple names and it gets confusing!).
-