Balnaves, Edmund2017-10-132017-10-132017http:/docs.prosentient.com.au/prosentientjspui/handle/703/2909The 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. <br /><br />When you download the xml from within a proxied network it may change the DTD reference at the top of the XML. <br /><br />This is an example of the top 3 lines of an XML export from PubMed:<br /><br /> <?xml version="1.0"?><br /> <b><!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"></b><br /> <PubmedArticleSet><br /> <br /><br /> If you just delete the DOCTYPE line the import should work. You should then have at the top two lines: <br /><br /> <?xml version="1.0"?><br /> <PubmedArticleSet><br /> <br /> <br />Then the import should work OK.TextDSPacePubMedPubmed Import into DSpace fails due to DTD in the xmlFAQDSpace documentation