rhigman

Results 31 issues of rhigman

Related to zenodo/zenodo#1483. The [REST API documentation](https://developers.zenodo.org/#representation) for `language` metadata states "Specify the main language of the record as ISO 639-2 or 639-3 code, see [Library of Congress ISO 639...

On successful [dissemination](https://github.com/thoth-pub/thoth-dissemination), add a new Location entry to the relevant Publication in Thoth, recording the URL(s) of the newly-created directory entry and/or copy of the content. To be added...

Work on https://github.com/thoth-pub/thoth/issues/405 required downloading PDF publication files directly from Location fullTextUrls, including checking that the URL returned `Content-Type: application/pdf`. This uncovered many user-entered fullTextUrls which instead returned `Content-Type: text/html`....

enhancement
discussion-needed

Following the creation of a first-pass KBART output under #88, this card tracks the following recommendations which were originally part of #88: > Recommendation 49. COPIM must review the resources...

feature
feature/output
recommendation

Not all metadata output formats appropriately handle non-`ACTIVE` works. - KBART output includes all works in publisher record, irrespective of work status. There is no representation of work status in...

enhancement
feature/output

The assumption in the existing Crossref DOI deposit logic is that if a publisher's bothered to enter chapters for a work at all, they must be wanting to register them...

feature/output

While compiling Crossref DOI deposit output, if a work has no DOI, we only raise an error if it's a chapter, not the parent work. https://github.com/thoth-pub/thoth/blob/6532713b89fd36ed734164c058d8aef175938da0/thoth-export-server/src/xml/doideposit_crossref.rs#L437-L444 This is because it's...

bug

Example: _Neo-Aramaic and Kurdish Folklore from Northern Iraq: A Comparative Anthology with a Sample of Glossed Texts_ (three Thoth records: _Set_, _Volume 1_, and _Volume 2_; Thoth work ID for...

bug
feature/output

https://www.crossref.org/blog/roring-ahead-using-ror-in-place-of-the-open-funder-registry/ "We are evolving our metadata schema so that we can collect ROR IDs in places where we already support the collection of Funder IDs – for instance, in [the...