Freebase
Start typing to get some suggestions
  • Explore
  • Use
  • Build
  • Developers

        Grateful Dead

        Discussions on Grateful Dead

        Domains & Types » Grateful Dead » Discuss

        Start a New Discussion

        Discussion will be posted in:

        • Grateful Dead

        Think this discussion also relates to something else? Cross-post it by adding a new discussion area:

        • General Support,
        • Developer Support
        1.  

          Songs not tracks

          2 posts, latest post: philg, Nov 11, 2008
          Link to discussion
          1. Nov 11, 2008
            bgoldenberg says:

            I think that song links to have expected types of Song, not Musical Track. Musical Track is meant for recorded tracks on albums and has a number of unsuitable properties, such as recorded by. It might make sense to define a new cvt ``Song Performance'' to record information such as guest artists.

            1. philg Metaweb Staff
              Nov 11, 2008
              philg says:

              This is philosophically a little tricky, as I have learned from trying to create a Concert Tour schema with Dead tours as my model. When creating a set list for a show, there are obviously songs performed by the Dead that are from other artists. In this case it does seem to make more sense to have tracks as the expected type, since you do want that "recorded by" information, for example. It also makes sense in this case because it provides a way to link a song in the set list back to an album or live recording on which it appears. 

               

              On the flip side, most of the best-known Dead songs are typed as "compositions" (song, btw, is a generally deprecated type from what I've recently learned), and if you want information such as who wrote it, that's where it comes from. I making set lists I wound up having a mix of "compositions" and tracks.

               

              The thing that's very difficult to capture in our current model is the unreleased track (or movie, or what have you). The weirdness comes about because they are usually recorded, but haven't been released.

               

              So, from my understanding, track is a good expected type if you want to tie into information about what album it's on, when it was recorded, etc. Composition is good if you want to tie into information about who was involved in its creation.  Most things we think of as songs are currently typed as tracks, because of the way in which we got the initial information from MusicBrainz. What I think we really need is a type that's a hybrid of the two, that can capture the composition information, but also peformance information as well (for example, there's currently no way to input which members of the band played what instruments on the track).

          Discussion is posted in:

          • close Grateful Dead

          Think this discussion also relates to something else? Cross-post it by adding a new discussion area:

          • General Support,
          • Developer Support

        Search Discussions

        ©2009  Metaweb
        • Page History
        • RDF
        • Feedback
        • Attribution Policy
        • Terms of Service
        • About Us
        • Jobs
        • Freebase Blog
        Freebase contains information on:
        • Arts & Entertainment
        • Products & Services
        • Science & Technology
        • Society
        • Special Interests
        • Sports
        • Time & Space
        Dev Tools
        Refresh cache | Query Editor | Normal view | Explore | Explore2 | Admin view | View transaction log | Suggest transaction log | Client transaction log | hide (F8) | debug-level
        TID(s):
        Controller: 0.229s
        Template: 0.027s
        Cost: br=2.0, cc=0.288, ch=0.0, cm=0.0, cm+h=0.0, cr=0.0, cs=8.0, cw=4.0, dr=1667.0, dt=0.457, dw=0.0, gqr=0.0, in=975.0, ir=23.0, iw=0.0, mcs=0.004, mcu=0.044, mr=4.0, nivcsw=43.0, nreqs=10.0, nvcsw=21.0, pf=0.0, pr=0.0, stime=0.024, te=0.016, tf=0.174, tg=0.17, tm=0.217, tr=0.014, ts=0.0, tu=0.008, utime=0.264, va=2759.0