Page Comparison

columnnavmap

Sectioninfo

icon

false

home

cellWidth

...

cellHeight

Section

20

title

Project Home

Column
homeImage Added
Navigation Map
sprints
cellWidth	200
wrapAfter	1
cellHeight	20
title	Events
sprints
Navigation Map
overteam
cellWidth	200
wrapAfter	1
cellHeight	20
title	Overarching Teams
overteam
Navigation Map
contentteam
cellWidth	200
wrapAfter	1
cellHeight	20
title	Content Teams
contentteam
Column
EA to Drupal round trip Proposals The one error proposal.docx Technical Framework - Option Common Repository EA to Drupal import.odt Discussion After some deliberation, we decided to currently go with the one-arrow option (detailed in The one error proposal.docx). For the long term, the Technical Framework - Option Common Repository should be the goal. The EA to Drupal import.odt could be an intermediary step to this. Important arguments were We should have only one single authority on the model (single source of information) There is a large amount of information that has to go into the XMI to fully incorporate the information from the drupal Some tasks may be easier in EA than in drupal Specialized skripts can be added to drupal to make these tasks more easy We need a working system as fast as possible, one arrow allows that and does not obstruct the way to the better solutions

Versions Compared