Linking information for external database
|
Last Updated: December 2003 FlyBase currently accepts external database link data to gene reports in a simple spreadsheet table (tab-delimited, 4 columns), plus a summary record for each external DB with link info and name. This format may change. Most likely we will continue supporting this, but add an XML format that includes these tabular fields plus the database summary record. Update processing from data providers as well as stale-link checks will become automated.
The current update mechanism is to email to linkout The link tableThe link table looks like this:
#FlybaseID DbName DbID DbUrl (relative to base DBurl)
FBgn0000011 BDGPisx 8078 ab
FBgn0000011 IFly FBgn0000011 ../neural/abrupt.htm
FBgn0000014 IFly FBgn0000014 ../segment/abdmla1.htm
FBgn0000014 KWgx FBgn0000014 FBgn0000014
FlybaseID: valid FlyBase ID, currently only FBgn is supported but others can be. '^FB\w\w\d+\t' is required for valid data line DbName: some unique/standard name for external database. Alpha-numeric only (\w+) DbID: external database object id (any opaque string) DbUrl: relative link to external database web report (this is the essential one, appended to Base DbURL for making hyperlink). Each link table should have a common base-url, but you can provide as many tables as base-urls, with base summary record. Database summary recordThe database summary record looks like this, for Base-url, one per DbName ( == DBID here).
OPVR
BURL|http://www.fruitfly.org/cgi-bin/ex/bquery.pl?qtype=report&searchfield=symbol&find=
NAM|BDGP in situ Gene Expression Database
LKNA|BDGP in situ
ICO|http://www.fruitfly.org/images/logo.gif
LKHE|BDGP in situ Expression Report with images
LKFL|flybase-data-field-here XML Database summary recordThis summary record can also be provided as XML:
<OPVR> An Example database summary:
OPVR OR ---
<OPVR> |
|
flybase.net