-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Obtain fulltext from sciencedirect #12161
Comments
I looked into the detailed debug logs, this appears to be a cookie handling issue:
Full debug logs for reference: |
JabRef version
5.15 (latest release)
Operating system
Windows
Details on version and operating system
22H2
Checked with the latest development build (copy version output from About dialog)
Steps to reproduce the behaviour
When trying to obtain the fulltext from sciencedirect, it does not find it. For example taking this DOI: https://doi.org/10.1016/j.ndteint.2023.102990
I am able to add it to the library, but the fulltext does not resolve, although it is clearly available.
Appendix
Logs:
2024-11-07 16:22:10 [JavaFX Application Thread] org.jabref.gui.JabRefDialogService.notify()
INFO: Deleted 1 entry(ies)
2024-11-07 16:22:43 [JavaFX Application Thread] org.jabref.gui.JabRefDialogService.notify()
INFO: Looking for full text document...
2024-11-07 16:22:43 [JabRef CachedThreadPool] sun.util.logging.internal.LoggingProviderImpl$JULWrapper.log()
ERROR: Invalid cookie for https://linkinghub.elsevier.com/retrieve/pii/S0963869523002050:
2024-11-07 16:22:44 [JabRef CachedThreadPool] sun.util.logging.internal.LoggingProviderImpl$JULWrapper.log()
ERROR: Invalid cookie for https://www.sciencedirect.com/science/article/pii/S0963869523002050:
2024-11-07 16:22:45 [JabRef CachedThreadPool] org.jabref.logic.importer.fetcher.SemanticScholar.findFullText()
INFO: Fulltext PDF found @ SemanticScholar. Link: https://doi.org/10.1016/j.ndteint.2023.102990
2024-11-07 16:22:45 [JavaFX Application Thread] org.jabref.gui.JabRefDialogService.notify()
INFO: No full text document found for entry Cosarinsky2024.
The text was updated successfully, but these errors were encountered: