Please use this identifier to cite or link to this item: http://docs.prosentient.com.au/prosentientjspui/handle/1/2909
Title: Pubmed Import into DSpace fails due to DTD in the xml
Authors: Balnaves, Edmund
Issue Date: 2017
Description: The BTE import function in DSpace may fail if the DTD element in the pubmed xml does not resolve. A simple solution is to delete the DTD element in the xml prior to using the BTE import.

When you download the xml from within a proxied network it may change the DTD reference at the top of the XML.

This is an example of the top 3 lines of an XML export from PubMed:

<?xml version="1.0"?>
<!DOCTYPE PubmedArticleSet PUBLIC "-//NLM//DTD PubMedArticle, 1st January 2017//EN" "https://dtd-nlm-nih-gov.www.ezpdhcs.nt.gov.au/ncbi/pubmed/out/pubmed_170101.dtd">
<PubmedArticleSet>


If you just delete the DOCTYPE line the import should work. You should then have at the top two lines:

<?xml version="1.0"?>
<PubmedArticleSet>


Then the import should work OK.
URI: http:/docs.prosentient.com.au/prosentientjspui/handle/1/2909
Appears in Collections:DSpace documentation

Files in This Item:
There are no files associated with this item.


Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.