https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23666
--- Comment #4 from Tomás Cohen Arazi <[email protected]> --- I'm submitting an RFC proposal, to sumarize: GET /patrons/:patron_id/extended_attributes POST /patrons/:patron_id/extended_attributes PUT /patrons/:patron_id/extended_attributes <- to overwrite them all DELETE /patrons/:patron_id/extended_attributes/:extended_attribute_id Extended attributes could be queried by 'extended_attribute_type' to address the original 'more granular' approach. I would add that the POST /patrons route needs to be extended to allow passing an 'extended_attributes' attribute, and that if there are some 'mandatory' extended attributes missing, patron creation should fail. GET /patrons/:patron_id could be extended to be able to 'embed' the extended attributes as well. The last two proposals should belong to their own bugs. I will file them once I have everything settled. There's also the need to implement: GET /extended_attribute_types GET /extended_attribute_types/:extended_attribute_type_id POST /extended_attribute_types PUT /extended_attribute_types/:extended_attribute_type_id DELETE /extended_attribute_types/:extended_attribute_type_id And as types can be constrained by branch/library and patron category, we could think of a route for fetching types so we can use it to render forms. I still didn't find a suitable layout, will file a bug once I clear my mind, unless someone beats me to it. -- 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/
