Partner logo on corporate website via a Drupal block

[rchards]

As a Partner level member I can see my logo at the bottom of the landing page and on the supporters list so I can get maximum brand value.

[JeniT]

Can pull in the logos through Javascript into the website. Logos can be stored on the 'directory' server and the URL put into CapsuleCRM. May need to crop etc logos.

[rchards]

Scale preserving resizing is far more preferable. We will need to preserve people's brands/logos.

[Floppy]

JSON sample:

GET http://directory.theodi.org/members.json?level=member

{
  version: "0.1",
  profile: "http://schema.theodi.org/membership",
  memberships: [
    {
      url: "http://member-directory.dev/members/XZ4895SM",
      membershipId: "XZ4895SM",
      role: {
        url: "http://schema.theodi.org/membership/member",
        name: "Member"
      },
      member: {
        type: "http://schema.org/Organization",
        name: "Logos R Us",
        description: "Bacon ipsum dolor sit amet short loin frankfurter tri-tip pastrami turkey. Capicola beef ribs corned beef brisket, short ribs ribeye pork chop turducken tenderloin. T-bone drumstick chuck prosciutto pig beef swine pork pork belly spare ribs ribeye shoulder shankle pork chop short ribs. Beef ribs ground round corned beef pork chop. Biltong sausage spare ribs meatloaf. Turkey andouille capicola ground round, fatback pork chop flank drumstick. Flank frankfurter ground round brisket cow boudin pork belly. Spare ribs prosciutto bresaola jowl pig, kielbasa sirloin. Sirloin beef beef ribs, doner pastrami hamburger prosciutto swine bresaola bacon drumstick boudin sausage filet mignon. Chicken filet mignon pig pork belly bresaola tri-tip t-bone. Short ribs corned beef ribeye pork belly pork. Turducken pastrami pancetta biltong chicken salami. Pork belly pork chicken leberkas shoulder short loin meatball beef turkey ground round sausage bacon doner. Shank swine meatloaf, jowl pork loin gro",
        url: "http://google.com",
        logo: [
          {
            type: "http://schema.org/ImageObject",
            description: "Original",
            contentUrl: "http://1817e92590778e7949b4-f5b82e124b2bfe7571304195e288c24b.r43.cf3.rackcdn.com/logos/XZ4895SM/headshot1.jpg",
            thumbnail: {
              type: "http://schema.org/ImageObject",
              contentUrl: "http://1817e92590778e7949b4-f5b82e124b2bfe7571304195e288c24b.r43.cf3.rackcdn.com/logos/XZ4895SM/square.png",
              height: 100,
              width: 100
            }
          },
          {
            type: "http://schema.org/ImageObject",
            description: "Rectangular",
            contentUrl: "http://1817e92590778e7949b4-f5b82e124b2bfe7571304195e288c24b.r43.cf3.rackcdn.com/logos/XZ4895SM/rectangular.png",
            height: 100,
            width: 200,
            thumbnail: {
              type: "http://schema.org/ImageObject",
              contentUrl: "http://1817e92590778e7949b4-f5b82e124b2bfe7571304195e288c24b.r43.cf3.rackcdn.com/logos/XZ4895SM/square.png",
              height: 100,
              width: 100
            }
          }
        ]
      }
    }
  ]
}

[tomheath]

I think contentUrl is a horrible bit of modelling. Or to be more specific, if the url property can refer to either the object itself or a landing page about the object then it should be split up and renamed accordingly. Given that the scope notes for url describe it as "URL of the item" and contentUrl is nasty, could we stick with plain url?

[Floppy]

I'm definitely open to better ways of doing this. schema.org defines contentUrl, so I was just going with that in this case.

[tomheath]

This is relevant: http://lists.w3.org/Archives/Public/public-vocabs/2011Oct/0070.html

Can see the intention, but the solution is nasty.

[pezholio]

It's worth being mindful of IP restrictions on use of logos. Maybe not worth doing it automagically. Will just have a block in Drupal which is manually managed.

[pezholio]

Thinking about making a new content type for partners with the following fields:

• Name
• Image
• Url

This can then all be pulled in via a block. We will resize the height on the server, but won't do any cropping, any other resizing will have to be done by the end user, rather than on the server, so we make sure we follow the partner's branding guidelines.

[pezholio]

OK, so, this is what I've got so far:

@rchards - comments?

[JeniT]

@rchards we need you to approve this so that we can close the story.

[rchards]

Someone should close this.