meta data editor overwrites data on save
Bug #1034373 reported by
Ralf Claussnitzer
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Goobi.Production | Status tracked in 1.10 | |||||
1.10 |
New
|
Undecided
|
Unassigned | |||
1.8 |
Fix Released
|
Critical
|
Unassigned |
Bug Description
When opening a large process A in meta data editor (multiple megabyte XML data file) data loading continues even if the user stops the request (by going back). If the user opens a second process B - while data of A is still read in the background - data B is indeed shown in the editor but gets actually overwritten with A when the first data reading thread finally finishes. If the user now saves changes to B data of A is written to B's XML file overwriting all of B's data.
Related branches
lp:~slub.team/goobi-production/bug-1034373
- Henning Gerhardt: Approve
-
Diff: 286 lines (+176/-56)4 files modifiedconfig/messages_de.properties (+1/-0)
config/messages_en.properties (+1/-0)
src/de/sub/goobi/metadaten/Metadaten.java (+57/-56)
test/src/de/sub/goobi/metadaten/MetadatenTest.java (+117/-0)
description: | updated |
To post a comment you must log in.
Effect on the file system:
# meta data files of process A
(1) -rw-r--r-- 1 tomcat6 tomcat6 1628204 Aug 7 16:07 meta.mets.xml
-rw-r--r-- 1 tomcat6 tomcat6 1628200 Aug 6 14:42 meta.mets.xml.1
# meta data files of process B (after open & save)
(2) -rw-r--r-- 1 tomcat6 tomcat6 1628204 Aug 7 16:09 meta.mets.xml
-rw-r--r-- 1 tomcat6 tomcat6 1082651 Aug 7 16:07 meta.mets.xml.1
Files (1) and (2) have the same content and size. Original data of process B is still backed up in (2). However, this backup fades away after a number of save operations on that process (number depends on backup configuration in GoobiConfig. properties) .