As a data analyst, I want clear information on APIs, so I can see what is available to me

[mwigham]

Feedback René: Expects SPARQL/Linked Data to be on the highest level (couldn't find it, as it is a subheading on the B&G Media Catalog APIs page), also expects APIs to be organised according to technical protocol, not according to the content of the datasets. The GTAA page links through to a result page, would expect a query endpoint.

(general comment: APIs are only interesting once you want to get information about a dataset)

Tasks:

• Review the API information, consider how we can reorganise them to make it easier to find what you need. Should the APIs page be pure technical with links to datasets that can be accessed via the API (and then link to the API page from the content datasets)?
• Review the link from the GTAA page, can this be to an endpoint? Or is that not feasible/desirable?
• Test with René, and other users if we can find them

Acceptance criteria:

• A technical user can find the information they need about APIs

[rozelemarijn]

heel relevant - hopelijk kunnen we dit binnenkort bespreken. zou officieel buiten scope zijn muv MOZ, maar zie niet wanneer we hier anders aan toe komen en vind het wel belangrijk.

[KleinRana]

Depends on policy around (search) API's/ API use
Depends on if we can use schatkamer OAIPMH
list of API's