https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29963
--- Comment #26 from Katrin Fischer <[email protected]> --- Hi, the inconsistency that we discussed was that the same field should show the same behaviour in all places where we can add items. These are: * Adding items in serials * Adding items in cataloguing * Adding items in acquisitions I believe that serials and acq use similar code, but the code for cataloguing is different. The issue as I understand it was the 'hidden' behaviour. People assumed that leaving the field empty would mean 'no dateaccessioned' while Koha would _always_ use today's date if left empty. Or they would feel a need to fill out the field, when it was not necessary, adding extra steps. I think reverting and adding a hint would actually be a good start. Being context aware only pre-filling when the item is added/new would also be a good compromise. I just wonder if it might upset people that do a lot of cataloguing of items with past accession dates where it might feel like an issue having to change the pre-filled value. Also another thought pro hint: if we pre-fill, setting date-accessioned to mandatory will have no effect/the warning will never trigger. This might be an issue for libraries that want to make sure the date is verified manually. -- 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/
