Use crossref event-data to expand the discovery process for interrelated publications.
Use case
Currently, the ETL can only discover review data on crossref if the review appears in work.relation['has-review']. Ideally, this is a two-way relation with is-review-of. However, that is not always the case. The API does not permit filtering based on relation.object, so we have to build a more in-depth program to accomplish this using the event data. This would allow the ETL to generate more complete docmaps in these cases where the data is patchy.
Proposed solution
The solution is more or less implied by the description.
Additional information
This may be blocked by #48 . In any case an implementation prior to #48 would duplicate some work or have to be reimplemented.
ships
commented
1 year ago
Feature Request
Packages to improve:
Description
Use crossref event-data to expand the discovery process for interrelated publications.
Use case
Currently, the ETL can only discover review data on crossref if the review appears in
work.relation['has-review']. Ideally, this is a two-way relation withis-review-of. However, that is not always the case. The API does not permit filtering based onrelation.object, so we have to build a more in-depth program to accomplish this using the event data. This would allow the ETL to generate more complete docmaps in these cases where the data is patchy.Proposed solution
The solution is more or less implied by the description.
Additional information
This may be blocked by #48 . In any case an implementation prior to #48 would duplicate some work or have to be reimplemented.