Bug 6206 - can't change framework in the middle of cataloging
Summary: can't change framework in the middle of cataloging
Status: RESOLVED DUPLICATE of bug 10448
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: master
Hardware: All All
: P5 - low normal (vote)
Assignee: Galen Charlton
QA Contact: Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-19 11:10 UTC by Nicole C. Engard
Modified: 2013-08-08 11:25 UTC (History)
3 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nicole C. Engard 2011-04-19 11:10:03 UTC
If you're cataloging a record and you change the framework after entering data all the data is erased and you're left with a blank record. This is in FF4 on Mac OSX
Comment 1 Nicole C. Engard 2011-04-19 14:44:14 UTC
The same happens in Chrome - so I don't think this is a browser problem.

Nicole
Comment 2 Nicole C. Engard 2011-04-20 00:59:14 UTC
I have tested in both the TT and HTML versions and it's a bug in both.
Comment 3 Marcel de Rooy 2011-05-16 13:25:59 UTC
I would not say that this is a critical one. It could be noted as a precaution in the documentation. Our librarians know and will never change fw during cataloging. So you can handle it procedurally. You change framework at the very start or after saving your work.

Nevertheless, it is certainly a bug. The code is addbiblio is not that nice (anymore) and contains more bugs like this one. See e.g. 4513 or change framework when you chose Edit as New (duplicate). I should enter that one as a bug too.

If you agree, I would suggest to set the Importance to Normal.
Comment 4 Marcel de Rooy 2011-05-16 13:32:24 UTC
See also bug 6067. I have reopened it.
Comment 5 Katrin Fischer 2012-03-19 06:37:21 UTC
This is still true for newly entered unsaved data. I am not sure there is a way to prevent this and I agree with Marcel about severity. Perhaps we should have a note in documentation?
Comment 6 Nicole C. Engard 2013-08-08 11:25:03 UTC

*** This bug has been marked as a duplicate of bug 10448 ***