aboutsummaryrefslogtreecommitdiffstats
path: root/python/fatcat_tools
Commit message (Collapse)AuthorAgeFilesLines
...
| * datacite: add two more skipable tokensMartin Czygan2020-01-021-1/+1
| |
| * datacite: names can be 'Unav', tooMartin Czygan2020-01-021-1/+4
| |
| * datacite: avoid more None valuesMartin Czygan2020-01-011-4/+4
| |
| * datacite: address 'Unpublished' publisherMartin Czygan2019-12-311-9/+10
| |
| * datacite: ensure name schema is definedMartin Czygan2019-12-311-1/+2
| |
| * datacite: fix typoMartin Czygan2019-12-311-1/+1
| |
| * datacite: isascii was added in 3.7, onlyMartin Czygan2019-12-311-1/+7
| |
| * datacite: skip non-ascii doi for nowMartin Czygan2019-12-311-0/+4
| | | | | | | | | | | | Example of a non-ascii doi: * https://doi.org/10.13125/américacrítica/3017
| * datacite: clean doiMartin Czygan2019-12-311-1/+13
| | | | | | | | | | | | | | address issue with EN DASH DOI. > "external identifier doesn't match required pattern for a DOI (expected, eg, '10.1234/aksjdfh'): 10.25513/1812-3996.2017.1.34–42"
| * datacite: update docsMartin Czygan2019-12-311-9/+9
| |
| * datacite: perform additional checks on contribMartin Czygan2019-12-301-3/+9
| |
| * datacite: check for empty title after cleanMartin Czygan2019-12-291-2/+5
| |
| * datacite: update docs with observed valuesMartin Czygan2019-12-291-1/+3
| |
| * datacite: page number misses are too commonMartin Czygan2019-12-281-1/+2
| | | | | | | | | | | | Should be a level debug, not info. Examples: E675, n/a, 15D.2.1, 15D.2.1, A.1E.1, A.1E.1, ...
| * datacite: suppress debug-like language lookup miss messageMartin Czygan2019-12-281-1/+3
| |
| * datacite: treat untyped names as peopleMartin Czygan2019-12-281-1/+1
| |
| * datacite: include container_name top level key in extraMartin Czygan2019-12-281-7/+21
| |
| * datacite: use clean on field valuesMartin Czygan2019-12-281-2/+28
| |
| * datacite: include doi in error messagesMartin Czygan2019-12-281-8/+8
| |
| * datacite: limit abstract lengthMartin Czygan2019-12-281-0/+6
| |
| * datacite: use iso 639-1 codesMartin Czygan2019-12-281-7/+4
| |
| * address first round of MR14 commentsMartin Czygan2019-12-281-148/+319
| | | | | | | | | | | | | | | | | | | | | | | | | | * add missing langdetect * use entity_to_dict for json debug output * factor out code for fields in function and add table driven tests * update citeproc types * add author as default role * add raw_affiliation * include relations from datacite * remove url (covered by doi already) Using yapf for python formatting.
| * datacite: move common date patterns out of the loopMartin Czygan2019-12-281-3/+4
| | | | | | | | Additionally, try the unspecific (%Y) pattern last.
| * improve datacite field mapping and importMartin Czygan2019-12-281-41/+139
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Current version succeeded to import a random sample of 100000 records (0.5%) from datacite. The --debug (write JSON to stdout) and --insert-log-file (log batch before committing to db) flags are temporary added to help debugging. Add few unit tests. Some edge cases: a) Existing keys without value requires a slightly awkward: ``` titles = attributes.get('titles', []) or [] ``` b) There can be 0, 1, or more (first one wins) titles. c) Date handling is probably not ideal. Datacite has a potentiall fine grained list of dates. The test case (tests/files/datacite_sample.jsonl) refers to https://ssl.fao.org/glis/doi/10.18730/8DYM9, which has date (main descriptor) 1986. The datacite record contains: 2017 (publicationYear, probably the year of record creation with reference system), 1978-06-03 (collected, e.g. experimental sample), 1986 ("Accepted"). The online version of the resource knows even one more date (2019-06-05 10:14:43 by WIEWS update).
| * datacite: add missing mappings and notesMartin Czygan2019-12-281-266/+175
| |
| * datacite: basic field mappingsMartin Czygan2019-12-281-41/+181
| | | | | | | | | | | | | | | | | | | | Currently using two external libraries: * dateparser * langcodes Note: This commit includes lots of wip docs and field stat in comment, which should be removed.
| * datacite: importer skeletonMartin Czygan2019-12-282-0/+459
| | | | | | | | | | | | * contributors, title, date, publisher, container, license Field and value analysis via https://github.com/miku/indigo.
* | importers: control update behavior with more-standard flagBryan Newbold2020-01-065-2/+10
|/
* orcid: skip non-person ORCID recordsBryan Newbold2019-12-261-0/+4
|
* datacite: extend range search queryMartin Czygan2019-12-271-1/+1
| | | | | The bracket syntax is inclusive. See also: https://www.elastic.co/guide/en/elasticsearch/reference/7.5/query-dsl-query-string-query.html#_ranges
* avoid usage of short linksMartin Czygan2019-12-271-2/+2
|
* Datacite API v2 throws 400, we cannot recover from, currently.Martin Czygan2019-12-271-0/+4
| | | | | | | | | | As a first iteration, just mark the daily batch complete and continue. The occasional HTTP 400 issue has been reported as https://github.com/datacite/datacite/issues/897. A possible improvement would be to shrink the window, so losses will be smaller.
* datacite: update documentation, add links to issuesMartin Czygan2019-12-271-10/+5
|
* datacite: use v2 of the API (flaky)Martin Czygan2019-12-271-5/+28
| | | | | | | | | Update parameter update for datacite API v2. Works fine, but there are occasional HTTP 400 responses when using the cursor API (daily updates can exceed the 10000 record limit for search queries). The HTTP 400 issue is not solved yet, but reported to datacite as https://github.com/datacite/datacite/issues/897.
* transform ingests via pmc/pmcid, not pubmed/pmidBryan Newbold2019-12-241-4/+4
|
* allow arabesque backfill ingests for some source typesBryan Newbold2019-12-241-0/+5
|
* make chocula URL updates more conservativeBryan Newbold2019-12-241-5/+5
|
* pubmed: if doing update, also do subtitle schema updateBryan Newbold2019-12-231-1/+9
|
* doi parsing fixesBryan Newbold2019-12-231-0/+7
| | | | | | | | | | Replace emdash with regular dash. Replace double slash after partner ID with single slash. This conversion seems to be done by crossref automatically on lookup. I tried several examples, using doi.org resolver and Crossref API lookup. Note that there are a number of fatcat entities with '//' in the DOI.
* pubmed: improve warning and stderr formattingBryan Newbold2019-12-231-5/+6
|
* pubmed: use standard identifier cleanersBryan Newbold2019-12-231-17/+14
|
* pubmed: remove unused extid mapping codeBryan Newbold2019-12-231-29/+0
|
* pubmed: do reference lookups by defaultBryan Newbold2019-12-231-1/+1
|
* normalizers: clean_pmid(), and handle nulls in all other cleanersBryan Newbold2019-12-231-0/+31
|
* pubmed: null doi parsing checkBryan Newbold2019-12-231-1/+1
|
* add basic MedlineDate year parsingBryan Newbold2019-12-231-0/+11
|
* fix spn/ingest importer duplication checkBryan Newbold2019-12-221-6/+8
| | | | | | Check was happing after the `return True` by mistake, allowing duplicates in SPN editgroups, and potentially in ingest request editgroups as well.
* write diagnostic messages to stderrMartin Czygan2019-12-161-2/+2
| | | | | During debugging, it can be helpful to keep stdout (e.g. processing results) and dignostic messages separate.
* Merge branch 'martin-importers-common-doc-fix' into 'master'Martin Czygan2019-12-141-13/+10
|\ | | | | | | | | Update EntityImporter docstring. See merge request webgroup/fatcat!9
| * complete parse_record docstringMartin Czygan2019-12-141-0/+6
| |
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-15 15:31:09 +0000