Record summary displays value from Date2 instead of Date1
Bug #1797207 reported by
Mary Llewellyn
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
New
|
Undecided
|
Unassigned |
Bug Description
Evergreen 3.1.6 (web client)
On serial records, the date displayed in the Record Summary is coming from the fixed field Date2. For actively published serials, this is "9999". Monographs display the value from Date1, which is preferable.
The XUL client uses the value from tag 260, subfield c, including extra characters such as "c" and "-". For reports based on pub date, the fixed field version is easier to work with, but I would expect the start date of the publication to be used.
tags: |
added: webstaffclient removed: webclient |
tags: | removed: webstaffclient |
To post a comment you must log in.
We are on web client 3.2.4.
The Record summary date is pulling from the 260 correctly with the trailing - after the date.
In a record with a 264 instead, it is pulling from the fixed field Date1, with no trailing - after the date.
I confirmed where it was coming from by changing the fixed field to an incorrect date and reloading the record in a new tab.