Summary: | Fast Add Framework has different item fields | ||
---|---|---|---|
Product: | Koha | Reporter: | Angela Kilsdonk <akilsdonk> |
Component: | Cataloging | Assignee: | Galen Charlton <gmcharlt> |
Status: | NEW --- | QA Contact: | Testopia <testopia> |
Severity: | normal | ||
Priority: | P5 - low | CC: | aleisha, dcook, m.de.rooy, veron |
Version: | Main | Keywords: | Academy |
Hardware: | All | ||
OS: | All | ||
See Also: | http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12477 | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
Angela Kilsdonk
2013-09-12 20:11:46 UTC
Nonpublic notes never show during check in - even if they're on a framework other than the fast add. The fast add should have a different item form since it's a different framework. I just checked and the item form on the default FA framework includes really too many subfields, including some that should not be edited: q - Koha out on loan r - Koha date last seen s - Koha date last borrowed I think it would be good to remove at least those subfields and some oters from the editor Picking only important item subfields for a shorter Fast Add form would be nice! Hi Katrin, Can you please confirm which fields should be removed from the Fast Add form? Aleisha Hi Aleiha, I'd hide using the hidden values (not delete) the following: - s - Date last checked out - r - Date last seen - q - Checked out - n - Total holds - m - Total renewals I think it could be helfpul to check which values those have in the default framework. Maybe also: - w - Price effective from - f - Coded location qualifier - 1 - Lost status (fast add that is already lost?) I think we could debate if it might make sense to haven even less fields for a true "fast" (quick) add feature (like: a, b, c, 2, h, y, i, 8, o, p, t, x, z) - Removing the ones listed above to match more with the normal framework should be safe. I had thought this might have been resolved with the switch to YAML files, but it's still the case. |