| Summary: | Date Acquired automatically saved as today's date when left blank when adding a new item | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Lisette Scheer <lisette> |
| Component: | Cataloging | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | normal | ||
| Priority: | P5 - low | CC: | jonathan.druart, m.de.rooy |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: | https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30931 | ||
| Change sponsored?: | --- | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
| Bug Depends on: | 29963 | ||
| Bug Blocks: | |||
|
Description
Lisette Scheer
2023-06-06 22:46:34 UTC
Koha enforcing today's date as dateaccessioned on saving has been the default behavior as long as I can remember and we actually train and rely on it. It serves as the 'date added' for libraries not using the acq module. Any change here should be discussed carefully. As Koha always enforced a dateaccessioned also when importing items there could also be side effects. (In reply to Katrin Fischer from comment #2) > Koha enforcing today's date as dateaccessioned on saving has been the > default behavior as long as I can remember and we actually train and rely on > it. It serves as the 'date added' for libraries not using the acq module. > > Any change here should be discussed carefully. As Koha always enforced a > dateaccessioned also when importing items there could also be side effects. Katrin, I definitely remember a time a while back it wasn't doing that, but it sounds like it was a bug. We have a partner using the acq. module who don't like that it's filling on order, even though it's updated when the item is received. It sounded from Bug 29963 like it was not expected behavior and they had it stop filling but it was still saving so I thought it was an extension of that bug. Since it wasn't, it sounds like this would be a pretty big change to Koha and probably would cause more problems for more people. I think it's one of those cases where you don't want to change existing behaviour needlessly, but maybe it could be a configuration thing. For the side effects, I am not sure, it could be that we have some display issues or we could have something explode, it's just hard to tell. Maybe nothing happens at all :) |