{"action":"opened","issue":{"url":"https://api.github.com/repos/Utah-Data-Science/dimensional/issues/2","repository_url":"https://api.github.com/repos/Utah-Data-Science/dimensional","labels_url":"https://api.github.com/repos/Utah-Data-Science/dimensional/issues/2/labels{/name}","comments_url":"https://api.github.com/repos/Utah-Data-Science/dimensional/issues/2/comments","events_url":"https://api.github.com/repos/Utah-Data-Science/dimensional/issues/2/events","html_url":"https://github.com/Utah-Data-Science/dimensional/issues/2","id":162032958,"number":2,"title":"`search` and `info` Command Line Arguments","user":{"login":"rosenbrockc","id":7817795,"avatar_url":"https://avatars.githubusercontent.com/u/7817795?v=3","gravatar_id":"","url":"https://api.github.com/users/rosenbrockc","html_url":"https://github.com/rosenbrockc","followers_url":"https://api.github.com/users/rosenbrockc/followers","following_url":"https://api.github.com/users/rosenbrockc/following{/other_user}","gists_url":"https://api.github.com/users/rosenbrockc/gists{/gist_id}","starred_url":"https://api.github.com/users/rosenbrockc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rosenbrockc/subscriptions","organizations_url":"https://api.github.com/users/rosenbrockc/orgs","repos_url":"https://api.github.com/users/rosenbrockc/repos","events_url":"https://api.github.com/users/rosenbrockc/events{/privacy}","received_events_url":"https://api.github.com/users/rosenbrockc/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-06-23T21:58:01Z","updated_at":"2016-06-23T21:58:01Z","closed_at":null,"body":"These are probably helpful to clear up right from the start. When the script is supposed to search the available combinations of datasets, where does it look? This will define how we organize the recipes for combining column-level ETLs in the repo.\r\n\r\nI like the way that homebrew and melpa have the brews/recipes just as separate files. @davidrichards mentioned this in Slack as well. So `search` would just scan the list of files in a folder called `??` and return those based on a `fnmatch` of the search string the user gave. This can be implemented in 5 lines easily. Speaking of which, do we want to separate out the file managament/searching etc. to a separate module in the package, or just keep it in the `cli.py`?\r\n\r\nFor `info`, we would grab details from the specific recipe file. But we need to decide what metadata to include in that file. Using a version of `Dataset` of @jpotts18, we could extract most of the relevant information. Should we just serialize those fields that contribute to obvious metadata into a JSON string to store in the recipe file? Then we could just grab it off the first line after a comment char and return a pretty-printed version of it to the terminal."}}
{"actor":{"display_login":"rosenbrockc"}}