28.05.2014 - Meeting questions, notes

[alberskib]

@bio4j/dynamograph Before each meeting I will create similar issue in wich I will write down all questions on which I run into durging development. What is more after each meeting I will create some notes from meeting

[alberskib]

Subject for discussion:

• workflow
• mapping scala objects to dynamoDb values
• user interface

[laughedelic]

:+1: good practice

[alberskib]

Notes:

• there is no need to create additional high level client interface layer - scarph model is good enough
• all commit should be reviewed before merging into master
• after finishing work on issue request for CR should be created
• dynamoDB table model should be divided into static and dynamic part. Dynamic part should synchronise wit actual db state
• writing and reading should be seperated: they should the same intermediate/abstract representation
• persisting data should be divided into front end and back end (like compiler):
  • front end should be responsible for parsing data
  • back end should be responsible for actual uploading data to db
  • more infor could be found on #16
• scarph enable retrieving relationships
• for each tasks/target that should be done before midterm there should be issue created