This is an automated notification sent by LCG Savannah.
It relates to:
task #11314, project CDS Invenio
==============================================================================
LATEST MODIFICATIONS of task #11314:
==============================================================================
Follow-up Comment #3, task #11314 (project cdsware):
Merged as 036e94e8579d42ec1697e035cffe93173616fa5a.
==============================================================================
OVERVIEW of task #11314:
==============================================================================
URL:
<http://savannah.cern.ch/task/?11314>
Summary: BibEdit: volatile fields should disappear if not
filled in
Project: CDS Invenio
Submitted by: piotr
Submitted on: 2009-09-24 09:23
Should Start On: 2009-09-24 00:00
Should be Finished on: 2009-09-24 00:00
Category: BibEdit
Priority: 5 - Normal
Status: Done
Privacy: Public
Percent Complete: 100%
Assigned to: piotr
Open/Closed: Closed
Discussion Lock: Any
Effort: 0.00
_______________________________________________________
When a record is created fgrom the template and volatile fields are not
filled in, their values should disappear rather than be uploaded as
"VOLATILE: field description"
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: 2009-11-30 16:03 By: Tibor Simko <simko>
Merged as 036e94e8579d42ec1697e035cffe93173616fa5a.
-------------------------------------------------------
Date: 2009-10-16 09:38 By: Piotr Praczyk <piotr>
Solved by the commit: c22035dd9e5314d64593d6360bc9f5dd1ba6ca97
The behaviour of volatile fields has changed a little:
- Every field whose value starts with VOLATILE: will be
displayed as such
- When displaying a volatile field, the VOLATILE: prefix is
omitted
- When editing a volatile field, all the content is
automatically selected so that the description appearing by
default can be replaced easily
- When editing a normal field, the changes are appended at
the end rather than replacing (the content is not selected)
- writing VOLATILE: at the beginning of value changes the
field to volatile ( with all the consequences such as not
displaying the VOLATILE: prefix and changing the css class
- all the subfields starting with VOLATILE: are omitted when
submitting a change
-------------------------------------------------------
Date: 2009-09-24 09:26 By: Tibor Simko <simko>
See also task #10258. Kyriakos fixed the removing of empty fields, but
VOLATILE fields were introduced later, so the old removing fix is no longer
fully valid.
_______________________________________________________
Carbon-Copy List:
CC Address | Comment
------------------------------------+-----------------------------
1576 | -COM-
5686 | -SUB-
==============================================================================
This item URL is:
<http://savannah.cern.ch/task/?11314>
_______________________________________________
Message sent via/by LCG Savannah
http://savannah.cern.ch/
