Details
-
Type: Task
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 2.10.0
-
Fix Version/s: 2.10.0
-
Component/s: data retrieval services
-
Labels:None
Description
As far as XML records from ENA go, we'd definitely recommend looking at the ENA service and making sure in your examples you're using an up to database and entry format that they support - they are more
likely to make sure such requests are handled in a timely fashion.
You can find examples at http://www.ebi.ac.uk/ena/browse/data-retrieval-rest
which as you see, are now using emblxml-1.2 which if using dbfetch should be retieved via:
http://www.ebi.ac.uk/Tools/dbfetch/dbfetch?db=ena_coding&id=aah29712&format=emblxml1.2&style=default
(please also note emblcds is out of date - it's now ena_coding)
Attachments
Issue Links
- depends on
-
JAL-2114 Parse GenBank/ENA location specifiers
- Closed
-
JAL-2113 Update EMBL fetch to parse version 1.2 of EMBLXML
- Closed
- related with
-
JAL-1919 import of 3D structure data from flat file and EMBL-PDBe via PDBx/mmCIF
- Closed
-
JAL-2027 EMBL parsing of CDS does not respect 'complement()' operator
- Closed
-
JAL-2748 Uniprot dbfetch returning errors
- Closed
-
JAL-2138 Remove EMBLCDS as a database source
- Open
-
JAL-2628 Review new Uniprot Proteins REST API
- In Progress
-
JAL-2245 (unannounced) changes to ENA 1.2 XML format
- Closed
-
JAL-2113 Update EMBL fetch to parse version 1.2 of EMBLXML
- Closed
-
JAL-1856 Better error handling if DBRefFetcher fails
- Closed