Closed IAmGrootel closed 6 years ago
Hi Alex,
ECS: The paper for ECS are very old and they do not have the Full HTML content. Our parser was build to deal with the Full Text link where we obtain the HTML content. In the case of ECS, we do not store the full page, but we store the relevant part of the webpage, i.e: ''<div class=\"article fulltext-view\">''
RSC: Regards to Journal and Keywords, we store this information in a separate database with the DOI, then do not worry about it. However, you should include the DOI during the parser step. About the content of the page, for RSC we just pass to the parser the: ''<div id=\"wrapper\"> of the full article HTML.''
Anything, let me know. Best,
Thanks for the clarification!
@eddotman @zjensen262 We pulled a branch from master and tried running the ECS parsers using:
Where ECS_htmls is a list of html strings.
But we get an error:
This was tried on the following dois: 10.1149/1.3492151, 10.1149/1.3492174, 10.1149/1.3492188. The html files could be opened on Chrome and looked like it was parsed properly there.
With RSC we were able to run :
data = RSCSoup.parse(RSC_htmls[0])
Here we get an issue with empty entries in data. DOI, Journal, and Keywords which are all empty. We tried this on the DOIs: 10.1039/B210215C, 10.1039/B210393C , 10.1039/C000028KSo for the ECS parser we were wondering if this error has a fix. And for the RSC parser we wanted to check in to see if the missing entries is expected behavior or whether we should be attempting to extract that information from htmls.