Need Help?

Search our documentation and community forum

Terra is a cloud-native platform for biomedical researchers to access data, run analysis tools, and collaborate.
Terra powers important scientific projects like FireCloud, AnVIL, and BioData Catalyst. Learn more.

it hard to add new tasks to an existing name space

Comments

4 comments

  • Avatar
    Jason

    Hi Andrew Davidson,

    Thanks for writing in. Am I understanding correctly that you are referring to the namespaces in the Broad Methods Repository? https://portal.firecloud.org/#methods

    Kind regards,

    Jason

    0
    Comment actions Permalink
  • Avatar
    Andrew Davidson

    Hi Jason

    I think it would be better if the pull-down was in the "create methods" window. On the methods page, I think it would. be nice if I could sort by namespace.

     

    Kind regards

     

    Andy

     

    0
    Comment actions Permalink
  • Avatar
    Andrew Davidson

    I think Java does a really good job with namespaces. One of the things I think would be helpful is if there was something like the java package statement in the WDL file rather than have the namespace sprayed on in the create form. This would make managing namespace much easier. The convention in java is that you control your domain name. You use your domain name to care out a space you own. that makes it easy to avoid namespace collisions.

    Here is an example from some code I wrote while working at a company with the domain name pws.com. 

     

    ```

    package com.pws.twitterapps.mining;

    import static com.pws.twitterapps.util.TwitterUtil.checkRateLimit;

    public class FollowsDataCollector implements TwitterDataCollector {

      private static final Logger log = LoggerFactory.getLogger(FollowsDataCollector.class);

      private FollowsUserDataRepository repo = null;

     

      public FollowsDataCollector(FollowsUserDataRepository repo) {

        this.repo = repo;

      }

    ```

     

    For my wdl files on terra I would like something like this in my wdl file

    package  "edu.ucsc.kimlab.pancrease.exploration" 

    0
    Comment actions Permalink
  • Avatar
    Jason

    Hi Andy,

    Thanks for elaborating. The Broad Methods Repository is currently configured as a place to store and share full WDLs rather than individual tasks. That said, I'm definitely happy to bring this up with our engineers so they know there is interest in this package-style organization of tasks.

    I'll also flag up the interest in the pulldown menu and in organizing the methods by namespace.

    I'll be happy to follow up on this thread if either change gets implemented!

    Many thanks,

    Jason

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk