IGetDBWiki/GettingStarted/EmmaPlugin - Revision history

Admin: 3 revisions

2011-10-26T06:15:42Z

3 revisions

← Older revision	Revision as of 08:15, 26 October 2011
(No difference)

imported>KaiRunte at 13:20, 10 May 2007

2007-05-10T13:20:42Z

← Older revision		Revision as of 15:20, 10 May 2007
Line 3:		Line 3:

	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:		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
			<pre><nowiki>
			./bin/emma_start test_import.pl -p <project> -i IdentifierClashAction=Update,IdentifierRefAction=Reference src/dbshema/IGetDBExport.xml
			</nowiki></pre>


	=== 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.

imported>KaiRunte at 13:18, 10 May 2007

2007-05-10T13:18:29Z

← Older revision		Revision as of 15:18, 10 May 2007
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.

imported>KaiRunte at 13:18, 10 May 2007

2007-05-10T13:18:11Z

New page

__NOTOC__
== 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.