[Bioc-devel] Idea for improved visibility of Bioconductor packages
Dan Tenenbaum
dtenenba at fredhutch.org
Tue Nov 3 02:05:52 CET 2015
----- Original Message -----
> From: "Jiří Hon" <xhonji01 at stud.fit.vutbr.cz>
> To: "bioc-devel" <bioc-devel at r-project.org>
> Sent: Thursday, October 29, 2015 7:05:57 AM
> Subject: Re: [Bioc-devel] Idea for improved visibility of Bioconductor packages
> The implementation of Open Graph protocol should solve this, at least
> for LinkedIn and Facebook. See
> https://developer.linkedin.com/docs/share-on-linkedin (at the bottom of
> the page).
I've tweaked the package landing pages so their HTML contains (for example, for the EBImage package):
<meta property="og:title" content="EBImage" />
<meta property="og:type" content="website" />
<meta property="og:site_name" content="Bioconductor" />
<meta property="og:description" content="EBImage provides general purpose functionality for image processing and analysis. In the context of (high-throughput) microscopy-based cellular assays, EBImage offers tools to segment cells and extract quantitative cellular descriptors. This allows the automation of such tasks using the R programming language and facilitates the use of other tools in the R environment for signal processing, statistical modeling, machine learning and visualization with image data." />
<meta property="og:url" content="http://bioconductor.org/packages/EBImage/" />
<meta property="og:image" content="http://bioconductor.org/images/logo/jpg/bioconductor_logo_rgb.jpg" />
This should cause sites that implement the Open Graph Protocol (like LinkedIn and Facebook) to extract these elements from the page.
Adding a custom image for each package will need to wait for another iteration. We need to decide on some standard for declaring these images, either a field/url in the DESCRIPTION file, and/or a standard location within the package.
Dan
>
> Jiri Hon
>
> Dne 29.10.2015 v 14:59 Jim Hester napsal(a):
>> It seems to be pulling it from an invisible `#tooltip` div on the page.
>> This happens to be the first `<p>` block on the page, which is probably why
>> it is being used by linkedin.
>>
>> ```html
>> <div class="tooltip2" id="tooltip">
>> <p>To install this package, start R and enter:</p>
>> <pre>## try http:// if https:// URLs are not supported
>> source("https://bioconductor.org/biocLite.R")
>> biocLite("biobroom")</pre>
>> <p> In most cases, you don't need to download the
>> package archive at all.</p>
>> </div>
>> ```
>>
>> Probably these results could be improved by moving this tooltip block below
>> the package description, or annotating it with some metadata to exclude it
>> from the linkedin summary (I don't know what that would be).
>>
>> On Thu, Oct 29, 2015 at 9:50 AM, Kasper Daniel Hansen <
>> kasperdanielhansen at gmail.com> wrote:
>>
>>> For people like me who might be a bit behind on social media, it might be
>>> nice to identify where the blurb is generated from. Is it the first
>>> sentence of the description or ...?
>>>
>>> Best,
>>> Kasper
>>>
>>> On Thu, Oct 29, 2015 at 9:48 AM, Andrzej Oleś <andrzej.oles at gmail.com>
>>> wrote:
>>>
>>>> Hi Thomas,
>>>>
>>>> thank you for sharing your idea!
>>>>
>>>> One possibility would be to include a package icon/logo next to the
>>> package
>>>> name if the package provides one. This file could be saved as
>>> inst/logo.png
>>>> or vignettes/logo.png, e.g. see
>>>> https://github.com/aoles/EBImage/blob/master/vignettes/logo.png
>>>>
>>>> Best,
>>>> Andrzej
>>>>
>>>> On Thu, Oct 29, 2015 at 2:27 PM, Thomas Lin Pedersen <
>>> thomasp85 at gmail.com>
>>>> wrote:
>>>>
>>>>> I just sat down to write a linkedIn update about my recent package and
>>>>> noticed that a thumbnail styled summary was added once I put in the URL
>>>> for
>>>>> my package (this is probably old news - I’m not much of a social media
>>>>> guy). The summary was a bit dull though, and I was wondering if it was
>>>>> possible to change something on the package landing pages to spice
>>> these
>>>>> thumbnails up a bit, so they would appear more exciting when people
>>> share
>>>>> their work on Facebook/linkedIn/Twitter…
>>>>>
>>>>> Don’t know how much work this entail - it is definitely in the
>>>>> nice-to-have rather than need-to-have pile of feature requests
>>>>> _______________________________________________
>>>>> Bioc-devel at r-project.org mailing list
>>>>> https://stat.ethz.ch/mailman/listinfo/bioc-devel
>>>>
>>>> [[alternative HTML version deleted]]
>>>>
>>>> _______________________________________________
>>>> Bioc-devel at r-project.org mailing list
>>>> https://stat.ethz.ch/mailman/listinfo/bioc-devel
>>>>
>>>
>>> [[alternative HTML version deleted]]
>>>
>>> _______________________________________________
>>> Bioc-devel at r-project.org mailing list
>>> https://stat.ethz.ch/mailman/listinfo/bioc-devel
>>>
>>
>> [[alternative HTML version deleted]]
>>
>> _______________________________________________
>> Bioc-devel at r-project.org mailing list
>> https://stat.ethz.ch/mailman/listinfo/bioc-devel
>>
>
> _______________________________________________
> Bioc-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/bioc-devel
More information about the Bioc-devel
mailing list