it would be nice to have the License field of Tracks (and hopefully Albums) displayed with an image that links to the license. the obvious example is using a CC logo and linking it to the appropriate standard CC page.

there are already some modules that handle this for CC at least:

https://drupal.org/project/creativecommons seems the most promising and complete and i have played with it successfully.

or we could simply define a simple Field, Field Collection, Entity Type, etc. that allows an optional logo and link to be associated as a menu? i assume this is done in code for a Field, though perhaps Field Collection or Entity Construction Kit could be used as well?

the end result for the user would be similar to current UX: when adding Album/Track content, simply select the license from a predetermined select list. the only cool "advanced" option would be having an admin interface to add/remove/edit licenses (i.e. change logo, links, hover text, etc.).

finally, this would require a change of the core License Field Type. can this be done via a Feature?

any thoughts?

peace

Comments

waynedpj’s picture

after playing with the Pushtape License field a bit more, i see that one can add some basic HTML, including images, to the Select List labels:

cc_a|<a href='http://creativecommons.org/licenses/by-nc-sa/3.0/deed.en_US' title='Creative Commons: Attribution'><img src='/sites/local.dev.in-giro.org/files/by.svg' title='Creative Commons: Attribution'/></a>

which helps with having an icon and link for the displayed license as i requested in this feature. however, there are a few issues:

  • the "Creative Commons:" is being removed from the <img> & <href> title attribute?!
  • the label in the select list is blank since now there is no text to display

perhaps these are just limitations of the core Select List? or hopefully old problems that have been already solved? i was hoping to somehow make the Widget for the Select List use the title attribute of the img or a tag, but so far my research has turned up no solutions. maybe the experts have some ideas?

thanks

zirafa’s picture

Is there any reason this can't be achieved using plain CSS (background images)?

waynedpj’s picture

do you mean something like this:

http://css-tricks.com/examples/ImageReplacement/

? i never heard of this before but it seems possible, depending on what kind of browser support you want.

however, for the non-technical musician use case coming to Pushtape, requiring them to edit the theme's CSS (which i assume is how this would have to be done) to have icons for licenses seems like too much. also, will this trick work for the links as well (i.e. can you replace the license text with an image that is hotlinked to the actual license)?

in addition, the referenced module Creative Commons also supports (or plans to support) license metadata via RDFa. i think this is important for having content correctly indexed (and thus discoverable) by users searching for media using a certain license (e.g. i am searching for music to use for my video that is CC BY-SA).

even if this module is not ready for use in Pt (again, i have used it and it seems to work well) because of its alpha status or because it only supports CC and All Rights Reserved licenses (though perhaps it could be extended to allow additional licenses to be defined), i think having a simple license type (perhaps an Entity Type?) that allows a icon and link would be useful improvement over the current text only license. this way, we can provide some default licenses (CC, all rights reserved, etc.) that a musician using Pt can simply choose, or if need be create a new license by entering a name, optional link and optional image. would there be any interest in something like this replacing the simple text license field?

in summary, though the CSS trick may work in the short term, it feels limiting and too difficult for the non-technical user who wants to stick with UI screen configuration of Pt.

peace, w

zirafa’s picture

Status: Active » Closed (won't fix)

I think the CSS solution is the most straightforward answer, since this is primarily a style issue.