Domains & Types » Media Common » Adaptation » Discuss

Discussions on Adaptation

  1.  

    Property for adaptation media?

    1. Hi, I'd like to suggest adding a property to capture the media for which an adaptation is done, like "Adaptation Media" or "Adapted for Media". I'd also suggest checking the "displaying as disambiguator" option for this media property.

      This way, when you're looking at an Adapted Work and there's a list of Adaptations, you can see at a glance the media/format for which they've been adapted, like "Jane Eyre - TV Program", "Iron Man - Film", "High School Musical - Play (aka Musical)", and "V for Vandetta - Book" (adapted from the film adapted from the comic book).

      A secondary type of enumerated "adaptation media" may be created to help guiding user input to the appropriate types. But that's like icing on the cake. I'd be happy just to have cake.

      1. You're already talking about creating a new type, enumeration or otherwise, so in this case the icing and the cake are the same (mousse?). We'd actually have to insert a CVT between "adaptation" and "adapted work" to do this, so I'm a little reluctant to do this unless you have a pressing use case in mind.

      2. It's just that when you're looking at a topic with adaptations, having only their names displayed doesn't really mean much to a user, especially since the adaptations tend to inherit the same name as the original work.

        Take the Jane Eyre book topic, for example. It has eight adaptations listed: "Jane Eyre", "Jane Eyre", "Jane Eyre", "Jane Eyre", "Jane Eyre", "Jane Eyre", "Jane Eyre", "Jane Eyre". A user has to click on every single one to find out which is a film, a tv program, or a play, to find out if any of them is a dup, or to find out if a particular adaptation is already in the list.

        Wikipedia puts diambiguating information into the page title: "Jane Eyre (Book)", "Jane Eyre, Film (1981)", etc. We don't -- because the logic goes we have type information, and a user can figure out what something is by looking at its type(s). Well, if that's the argument, then we should strive to display that type information where disambiguation is needed. I even think adding Date information to adaptations would be useful.

      3. Faye’s primary suggestion, adding a property, doesn’t require a new type. Having a type for creative work medium would make it more robust, but no new types are actually required.

      4. This sounds in some way like more of a client issue than a modeling issue. Should we denormalize the information implied by the type itself by making a property that basically contains the name of the type? Or should the client display this information in some other way? Dates tend to exist already on most of the types that are involved in adaptations, and sometimes as disambiguators. Again, this would be a denormalization to stick this value into a CVT. I'm not sure what the solution is; I understand the problem you're running into, since I've run up against it myself, but I really don't think a CVT is a great idea here.

      5. D'oh!  You're right, Chris. I don't know what I was thinking. I'll try adding a new property on "adapted work" for the medium on sandbox.

      6. http://sandbox.freebase.com/view/en/pride_and_prejudice

        Take a look at this, and let me know what you think. But think quickly, because this will go away in a few hours.

      7. Perfect! Ship it! :)

      8. It's live. Have at it!  I made the list an enum, and populated it with what seemed like likely topics; if I missed any, please add them.