As an archivist, I would like the display string for archival components to include all dates from the associated sub-records


When creating archival components with multiple dates, only the first date shows up in the display string. Expected behavior would be that the display string shows all dates.

I've attached two screenshots, one showing the dates I created and the other showing the resulting display string.




Alicia Detelich
December 18, 2018, 5:47 PM

Per discussion in Dev. Pri. on 11/29, all dates should be displayed, and in the case of long or unusual dates the text should wrap to a new line, as currently happens with long record titles. See wraptext.png screenshot above.

Maureen Cresci Callahan
December 11, 2019, 3:09 PM

Just commenting to note that this is a problem in both the staff interface and the PUI. For instance:

Christine Di Bella
February 24, 2020, 7:19 PM

- as discussed, dates should be in the order they appear in the sub-records, separated by commas. Bulk dates (indicated by date type = Bulk Dates) should be distinguished by "bulk: ". You should use the existing rules to determine which dates to display from a particular sub-record (for example, date expression takes precedence over begin/end dates) and when to wrap or use ellipses.

current sample string: title, date1
updated sample string: title, date1, bulk: date2, date3, date4

Lora Woodford
February 24, 2020, 8:38 PM

Also - Here’s where in the largetree.js.erb that that title’s being picked up →

Jordon Steele
February 26, 2020, 3:32 PM

We just discovered this bug from the PUI perspective, so echoing Maureen’s comment that this is a problem for users, not just staff. Glad to see it is being actively worked on.





Max Eckard



Fix versions