IGetDBWiki/GettingStarted/EmmaPlugin: Difference between revisions
Jump to navigation
Jump to search
imported>KaiRunte No edit summary |
imported>KaiRunte No edit summary |
||
| Line 5: | Line 5: | ||
./bin/emma_start test_import.pl -p <project> -i [[IdentifierClashAction]]=Update,[[IdentifierRefAction]]=Reference src/dbshema/IGetDBExport.xml | ./bin/emma_start test_import.pl -p <project> -i [[IdentifierClashAction]]=Update,[[IdentifierRefAction]]=Reference src/dbshema/IGetDBExport.xml | ||
== Updating the IGetDB-exporter for EMMA === | === Updating the IGetDB-exporter for EMMA === | ||
The script above takes also care of the case that there was an older version of IGetDB-exporter installed. In this case, however, you need to log into EMMA, remove the old pipeline and re-install it with the updated pipeline module. | The script above takes also care of the case that there was an older version of IGetDB-exporter installed. In this case, however, you need to log into EMMA, remove the old pipeline and re-install it with the updated pipeline module. | ||
Revision as of 14:18, 10 May 2007
Setting up the IGetDB-exporter for EMMA
It might be possible that the IGetDB-exporter for EMMA was not set up for the specific project you are working with. To do so, execute the following script from the EMMA CVS checkout: ./bin/emma_start test_import.pl -p <project> -i IdentifierClashAction=Update,IdentifierRefAction=Reference src/dbshema/IGetDBExport.xml
Updating the IGetDB-exporter for EMMA
The script above takes also care of the case that there was an older version of IGetDB-exporter installed. In this case, however, you need to log into EMMA, remove the old pipeline and re-install it with the updated pipeline module.