https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25870
--- Comment #3 from Tomás Cohen Arazi <[email protected]> --- (In reply to Paul Derscheid from comment #2) > There's another thing: I think that the only Content-Type that makes sense > for the return value is 'application/marc-in-json' because we return 1..n > records instead of a single one. > > Additionally I can't imagine a use-case in which you wouldn't want JSON as a > return value for that route. > > Is there any sane way to discern marc records from one another in an api > response? All of the accepted formats in GET /biblio/{biblio_id} have their plural representations [1] BUT I think we could start with 'application/marc-in-json'. and add things 'as-needed'. So if you want to work on this, it'd be ok to just implement marc-in-json for now. [1] "application/json" => this is the biblio + biblioitem table, plural is an arrary, "application/marcxml+xml" => there's '<collection>' for multiple records, "application/marc-in-json" => as you said, an array, "application/marc" => concatenated usmarc records would work, "text/plain" => double new line separator would work. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
