Closed nichtich closed 5 years ago
related to #5 (download-URLs need to be changed to absolute URLs)
/concordances
. xxxx
be in this case? Wouldn't it be enough to add the whole concordance as a JSON object? Do we even want/need a PUT endpoint for this?uri=
to /concordances
).concordance
option to specify the mappings' concordance. No validation is done for this yet./mappings
now supports the partOf=
parameter to specify the concordance (or concordances).We don't need update via HTTP by now, so closing this issue and adding #26 instead.
This is a more complex issue but required to deliver mapping provenance metadata.
/concordance
endpoint returning a list of concordances. A sample list (ndjson) is available at http://coli-conc.gbv.de/concordances/csv/concordances.ndjson/concordance/xxxx
where xxx can be[a-z0-9_-]
to add a new concordance.concordance
when adding mappings to specify a concordance that the mappings result from. During import validation should make sure that mappings actually fit to the concordance. The concordance URI is added to each mapping in fieldpartOf
in
to/mappings
endpoint to filter mappings by concordance they belong to (this can be implemented independently)