https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27358
--- Comment #8 from Katrin Fischer <[email protected]> --- Hi Tomas, if I understood correctly you wanted me to check on what fields should not be exposed on the public route? One is easy: itemnotes_nonpublic We also have libraries requesting to hide the acq related information (price fields, booksellerid, etc.) and other fields describing internal processes too. Maybe it would be easier to work backwards on what fields make the most sense to expose? Database fields (not the names for the API) itemnumber biblionumber homebranch holdingbranch location collectioncode itemcallnumber copynumber enumchron barcode dateaccessioned (for finding new things) itemnotes onloan uri itype Not sure how useful these would be as they require a solution for resolving the internal codes into something more useful: notforloan damaged itemlost withdrawn restricted It might make more sense to replace these by a more general availability route? I think we had done some work to specify things like "can be renewed", "can be checked out", "can be placed on hold" etc. A more difficult one: sometimes strictly internal, sometimes visible in the OPAC: materials How will we be handling more_subfields_xml? As it can contain about anything, probably best to hide by default. Could it make sense to fall back on the "visible in OPAC" setting in the frameworks here? -- 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/
