Hello Andrew, Thank you for your time and suggestions. Received new/updated marc.xml from library, now able to load both title and batch successfully. -----Original Message----- From: Data, API, website, and code of the Chronicling America website [mailto:[log in to unmask]] On Behalf Of Gearhart, Andrew Sent: 25 March 2019 17:49 To: [log in to unmask] Subject: Re: Unable to load new marc.xml Hey there Subramanian! Looks like you're using ChronAm as your xml data source, but the LCCN coded xml file that you're looking for "2018270203" doesn't exist on the chroman servers (404). There are a couple different possible reasons... * it could be that your batch " batch_nbu_2018sample_ver0001" is coded for the wrong LCCN. * the batch that you've encoded isn't a "newspaper" by the standard for ChronAm (and, therefore, the title information in marc.xml format isn't on the ChronAm servers) * some other cataloging error has occurred and resulted in the marc.xml not making it through oclc and/or loc to chroman Some options: * Correct your batch if the LCCN is wrong. * Correct your title information through cataloging > oclc/loc * Change your data source to use something other than the title information in loc. This is handled in ChronAm here: https://github.com/LibraryOfCongress/chronam/blob/d76d9dd75653b94ade4c67e85d91de737e5c1788/core/batch_loader.py#L257 * If you're using OpenONI, this is handled with the MARC_RETRIEVAL_URLFORMAT variable. You can find that here: https://github.com/open-oni/open-oni/blob/master/onisite/settings_base.py#L214 Hope that helps. Best regards, +A On 3/22/19, 04:31, "Data, API, website, and code of the Chronicling America website on behalf of Subramanian Sadasivam" <[log in to unmask] on behalf of [log in to unmask]> wrote: We got below error when we try to load specific batch [2019-03-18 20:33:52,953 INFO chronam.core.batch_loader] creating symlink /data3/ndnp/batch_nbu_2018sample_ver0001/ -> /opt/chronam/data/batches/batch_nbu_2018sample_ver0001 [2019-03-18 20:33:52,953 INFO chronam.core.batch_loader] loading batch: batch_nbu_2018sample_ver0001 [2019-03-18 20:33:53,306 INFO root] attempting to load marc record from https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchroniclingamerica.loc.gov%2Flccn%2F2018270203%2Fmarc.xml&data=02%7C01%7Candrew%40psu.edu%7C1df28a41a2ec47ea9e1108d6aea0becd%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C636888402772412540&sdata=945%2FFsV3j0dEIRe2AkyDlpQj1Bpp%2Ff0ibXFBtrOfsFY%3D&reserved=0 [2019-03-18 20:33:53,476 INFO chronam.core.title_loader] loading titles from: https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fchroniclingamerica.loc.gov%2Flccn%2F2018270203%2Fmarc.xml&data=02%7C01%7Candrew%40psu.edu%7C1df28a41a2ec47ea9e1108d6aea0becd%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C636888402772412540&sdata=945%2FFsV3j0dEIRe2AkyDlpQj1Bpp%2Ff0ibXFBtrOfsFY%3D&reserved=0 [2019-03-18 20:33:55,156 ERROR chronam.core.batch_loader] unable to load batch: HTTP Error 404: NOT FOUND [2019-03-18 20:33:55,156 ERROR chronam.core.batch_loader] HTTP Error 404: NOT FOUND Traceback (most recent call last): File "/opt/chronam/core/batch_loader.py", line 165, in load_batch issue = self._load_issue(mets_url) File "/opt/chronam/core/batch_loader.py", line 262, in _load_issue Hence tried to load received new marc.xml file using below command but unable to load. $django-admin.py load_titles /opt/chronam/data/lib/worldcat_titles/lccn/2018270203.xml Error message: [2019-03-21 13:24:52,963 INFO chronam.core.title_loader] loading titles from: /opt/chronam/data/bib/worldcat_titles/lccn/2018270203.xml [2019-03-21 13:24:53,031 ERROR chronam.core.title_loader] Code , not found in language table. [2019-03-21 13:24:53,099 INFO chronam.core.management.commands.load_titles] indexing new titles Could you please suggest, this is only to specific title and able to load remaining titles successfully without any issue. Could you please help us to fix the issue. The information contained in this electronic message and any attachments to this message are intended for exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Apex immediately and destroy all copies of this message and any attachments. The views expressed in this E-mail message / Attachments, are those of the individual sender.