Use local DBLP XML dump instead of per-entry live fetches - #18
Merged
Conversation
DBLP is overloaded and per-publication live fetches were getting the import script rate-limited/blocked. Look records up in a local copy of the official DBLP XML dump instead; fall back to a live fetch only for keys missing from the dump (e.g. too recent). Add fetch_dblp_dump.py to download/refresh the dump.
1 task
Contributor
Author
|
This works really well and makes stuff much more reliable and faster—though it does cost a gigabyte on local disk 😬 |
Member
|
Thank you, @thomwiggers, for making these changes! Merging it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
.xmlper publication over the network, which gets the import script rate-limited/blocked (hit a live 503 from DBLP while testing this).import.pynow looks records up in a local copy of the official DBLP XML dump (dblp.xml.gz), streamed withiterparse(no full decompress to disk), with named XML entities resolved fromdblp.dtd.fetch_dblp_dump.pyhelper downloads/refreshes the dump (checksum-verified, skips redownload if already current).Test plan
dblp.dtddblp.xml.gz: looked up real CRYPTO'24 keys (GupteV24,Ostrovsky24,HulsingJMN24,WatersZ24), correct bib keys/titles/entities producedimport.py confYYYYrun against a real conference by a maintainer