Skip to content

[Spike] How to organize seal of approval criteria endpoint(s) #1759

Description

@Alessandro100

For users and clients (mobilitydatabase) determine the best way to deliver all the necessary information to figure out the status of the feed based on:

  • Official
  • Available
  • Compliant
  • Fresh
  • Stable
  • Unstable

Some of this data is already available as separate endpoints or bundled in others.

Acceptance Criteria

  • A clear decision of endpoint(s) that need to be created for users to get the reliability status of the feed
  • An openAPI schema with the endpoints

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    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