Skip to content

Consistent methodology to signal that service is not available for fetchers #2729

@stefan-kolb

Description

@stefan-kolb

It might occur (even often with Crossref) that a fetcher is not available right now or the error is on their end 500, 503, 504.
We need a consistent method to pass this information to the user. Now for example the user only sees a DOI not found message but in fact we couldn't look for a DOI in reality.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions