Skip to content
Prev 7332 / 21312 Next

[Bioc-devel] AnnotationHubData Error: Access denied: 530

On 04/10/2015 12:18 PM, Rainer Johannes wrote:
Hi Johannes,

So you have several options actually.  We sometimes store the files in 
S3 and then send them down/cache them as requested and other times the 
hub can just point to an existing ftp site (and files get 
transformed/cached on the fly when users ask for them).  So you have 
three choices here:

1) You could just write a function that takes in one of the processed 
GRanges objects and transforms it into an EnsDb object. This should be 
straightforward and is probably your easiest option since you won't have 
to write a recipe OR have any code included into the AnnotationHub.  You 
can basically just take advantage of the fact that these data are 
already there in the hub waiting to be used.
2) You could write R code that transforms a GTF file into a sqlite file 
and ALSO a recipe to call that (and create metadata) for all the GTF 
files.  This will be more work than #1 since you will have to write both 
a recipe and port any code that you have for generating the DB files.  
But when you are done you would be able to have your resources come 
right out of the AnnotationHub.
3) You could write R code to process a GRanges object into an EnsDb 
object and then also write a recipe so that your data resources can be 
served up directly from the AnnotationHub, but still take advantage of 
what is already there (GRanges).  No new data would need to be added to 
the hub since new metadata records could allow users to transform the 
data into EnsDb objects on the fly.  This is an elegant solution, but it 
will still take more effort than option #1.

If I were you, I would start with option #1.  That way if (after I got 
that working) I still wanted things to be more elegant, then I could 
then add a recipe (thus evolving the strategy into option #3...


  Marc