Discussions on Flagging Topics for Merge or Deletion
Start a New Discussion
-
-
Hi.
In the popdown "flag" menu there are just two empty html-list-items where once the merge and split function used to be.
Is this a bug or (the end of a) feature?
-
What topic were you trying to flag?
-
Both of them for merge:
http://www.freebase.com/search?limit=30&start=0&query=Khomaniac
-
I'll bet this is because Musical Tracks are not full-fledged topics in Freebase.
That said -- these are two different tracks. The track on "Deadly Relics" is not the same as the track on "By Inheritance" even though they have the same name.
-
Ok. I already understood that a Track is a recorded "instance" of a song.
I thought that in this particular case the recordings are the same. That would comply with the statement of the Track type schema "A track should be a unique recording, but may appear on multiple albums or releases."
But now I see that according to Wikipedia one track is 06:42 and the other one 06:43 - So it may really be distinct recordings instead of a re-release of the same one. By the way: The freebase entries seem a bit odd to me: "Length (seconds): 401.906 s" - where do the milliseconds come from? any technical CD-timestamp-tick thingy or a rounding error (intel processor's floating point error :D )?
Anyway, the two non-functional
- s in the UI made me think of some bug.
And just for my understanding: A composition is linked to a recording by a "Performed song" for "livemusic" - but what's with never-played-live songs? Or ar they livemusic the moment they are recorded?
Well. Thanks for your quick reply.
-
Whoops. It should read " non-functional s in the UI"
Strange html tag filtering going on here... :D
- Test
-
Strange it filters out html entities but allows me to insert unordered list as html.
All I meant is the html tag for "list item".
and now I'm stopping the spam. (btw. an edit- or remove-function for posts would be nice)
-
The track data in Freebase largely comes from MusicBrainz, including the track lengths; I don't know how they calculate it, though. (Interestingly, although they apparently store the data in milliseconds, they round it up for display on their site.)
Tracks are linked to Compositions via the "Recording of Composition" property. Users are free (and encouraged) to create additional types and properties, which is where the livemusic base comes in.
-
-
-
One good improvement on the present state would be allowing users to merge nodes they have created themselves (and where no other person has been involved yet), without any supervision -- since it's entirely their fault (and perhaps the user interface they at first did not understand), it's only right they get the bits to wipe up the mess they made, if they want to. Adding a manual moderation step there just makes it cumbersome to fix errors.
I base this solely on having myself first added some members to the music ensemble "Visa Röster", then added some photos and marked up those photos with the people featured in them -- and, at that stage, made name duplicates rather than picking the "Member of Visa Röster" person from the pop-down menu. After realizing the error, I tried sweeping up some of the messes by marking some of those duplicates as duplicates, but quickly lost track (since those I had "fixed" were still left in the system), and stopped, since I did not remember which ones were left to do, and quite simply did not have the time.
-
-
-
is there a backend system that automates removing of duplicates and reconciliation?
-
The marking of topics for merge, delete, and split is meant is visible in the API for anyone who cares. Our current efforts are focussed on how to use this information to do "gardening" of the data with high confidence.
-
We are working on this. This is more of a social problem than a technical one. For example, we need to give folks a chance to disagree about merge requests before they happen. When merges should happen automatically is a topic worthy of discussion.
-
