Meeting 23.07.2014 - question and notes

[alberskib]

Questions:

• refactoring
• ncbiTaxonomy.name

[eparejatobes]

• [x] put item for hash-only tables @laughedelic
• [x] attributes vs properties in tabula @laughedelic
• [ ] write something about using attributes from scarph in table schema, and in general the use of vertexTable, EdgeTable etc @alberskib
• [x] what happened with dd writing @alberskib
• [ ] finishing refactoring @alberskib
• [x] blog post @alberskib
• [ ] review dd writing @evdokim
• [ ] review docs @eparejatobes
• [ ] what to do with the ENA @eparejatobes

[alberskib]

Notes:

• We should get rid of passing arguments to the table layout. Currently for each table we add set of attributes for it - this is duplication with scarph model. Each type of the Edge, Vertex ie(GoTermType) contains definition os attributes- we should reuse it. For those attributes which are specific for table layout we should define them in abstract type for tables i.e EdgeTables
• After switching implementation of writers to tabula it will be easy just to extend Dynamograph with support for new Dataset (docs will covert this issue)
• We should use consequently Set of Items - in other words eveyrwhere where we are using Map[String,AttributeValue] we should replace it with Set of Items ie. AnyDynamoEdge, AnyDynamoVertex
• Blog post should be written by friday - repo: bio4j/bio4j.github.com
• After providing support for ncbiTaxonomy I should concentrate on ENA - more information will provide @eparejatobes
• @laughedelic will introduce PutItemRequest int tabula for HashKeyTables
• @evdokim will help me with troubles connected with ec2, s3 etc

[laughedelic]

my part in tabula is done: 94e98bf920f8f3ed013acd1ca363a1b8e5649e95 and aa774fe3d0a57106d0474077b92b8cbd1028d491

it's pushed to master and and published under the 0.1.0-SNAPSHOT version. let me know if you will have any problems with migration

[alberskib]

@eparejatobes Could yuo confirm instruction for saving blog post:

0. Do not change anything in master branch
1. In source branch under source/_posts create file with content of the blog

[laughedelic]

Correct. Once you push your changes, the website will be updated (with some delay). You can also try to use octopress rake stuff for preview, if you're not afraid of dealing with ruby mess

[eparejatobes]

@alberskib yes but open a pull request, do not push to source directly

[alberskib]

@bio4j/dynamograph I push branch with post - please take a look on it.