| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
|
|
|
| |
via "missed potential license", refs #58
|
|\
| |
| |
| |
| | |
datacite: hard cast possible date value to string
See merge request webgroup/fatcat!59
|
|/ |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
make fulltext-only label clickable
See merge request webgroup/fatcat!58
|
|/ |
|
|\
| |
| |
| |
| | |
better download button links
See merge request webgroup/fatcat!57
|
| |
| |
| |
| | |
Similar to recent change for release download pages.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This will increase index size (URLs are often long in our corpus, and we
have many file entities), but seems worth it.
Initially added `ia_url` as a second field, guaranteed to always be an
*.archive.org URL, but `best_url` defaults to that anyways so didn't
seem worthwhile.
|
| |
| |
| |
| |
| |
| |
| | |
I thought this was the existing behavior, but it looks like we were just
taking the first link from the first file.
In the future may refactor this out even further.
|
|/ |
|
|\
| |
| |
| |
| |
| | |
Manually resolved conflicts:
python/fatcat_tools/harvest/doi_registrars.py
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In the past harvest of datacite resulted in occasional HTTP 400.
Meanwhile, various API bugs have been fixed (most recently:
https://github.com/datacite/lupo/pull/537,
https://github.com/datacite/datacite/issues/1038). Downside of ignoring
this error was that state lives in kafka, which has limited support for
deletion of arbitrary messages from a topic.
|
|\ \
| | |
| | |
| | |
| | | |
harvest: log the failed url
See merge request webgroup/fatcat!55
|
| |/ |
|
|\ \
| |/
|/|
| |
| | |
datacite: fix test docs
See merge request webgroup/fatcat!54
|
|/ |
|
|\
| |
| |
| |
| | |
verify release_stage in ingest importer
See merge request webgroup/fatcat!52
|
| | |
|
| | |
|
|\ \
| |/
|/|
| |
| | |
rename HarvestState.next() to HarvestState.next_span()
See merge request webgroup/fatcat!53
|
|/
|
|
|
|
|
|
|
| |
"span" short for "timespan" to harvest; there may be a better name to
use.
Motivation for this is to work around a pylint erorr that .next() was
not callable. This might be a bug with pylint, but .next() is also a
very generic name.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Gitlab CI is showing lint errors like:
=================================== FAILURES ===================================
6316 _______________________ [pylint] tests/harvest_state.py ________________________
6317 E: 19,11: hs.next is not callable (not-callable)
6318 E: 33,11: hs.next is not callable (not-callable)
6319 E: 19,11: hs.next is not callable (not-callable)
[...]
this is confusing as we use pipenv with a lock, so I should see the
exact same errors locally.
This commit is a hack to try and fix this and unbreak builds until we
can debug further.
|
|
|
|
|
|
| |
I guess we were dumping 3 times originally; already had an earlier
commit that removed one row from this README (that I copypaste to CLI
every time)
|
| |
|
|
|
|
|
| |
It seems to be an inadvertantly ugraded version of pylint saying that
these lines are not-callable.
|
| |
|
| |
|
|\ |
|
| |\
| | |
| | | |
Travis CI: Lint Python code for syntax errors and undefined names
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
One of these (in ingest importer pipeline) is an actual bug, the others
are just changing the syntax to be more explicit/conservative.
The ingest importer bug seems to have resulted in some bad file match
imports; scale of impact is unknown.
|
| |
| |
| |
| |
| |
| |
| | |
Until reviewing I didn't realize we were even doing this currently.
Hopefluly has not impacted too many imports, as almost all ingests use
an external identifer, so only those with identifers not in fatcat for
whatever reason.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is to push a new package version to pypi with the newer codegen.
The immediate motivation for this is to fix keyword errors with "async"
parameters conflicting with "async" as a keyword in Python 3.7.
I guess that means this is probably actually a breaking change to the
python API, though not to the API itself? Hrm.
All the other changes are typo corrections from the fatcat-openapi2.yml
spec document.
|