does not need prio’d it has been fixed in 3.0.0 and need more details
need to work on
leaning towards should be prioritized as – this info is not displayed on the page of the specific background job – however it is somewhat displayed in the background job page
There are two distinct issues in this ticket: the note type, label, and content do not populate in RDE templates--this is a problem and I think we should pass this for dev. Top containers also do not populate in RDE templates, but I’m not sure that they should. Do we really want to be able to specify specific top containers in templates? What happens if that top container is deleted or modified? I think being able to chose top containers and then use the fill down function suffices for any use case I can think of.
Resizing columns in RDE resets column visibility. This is a problem in v. 2.7, but I wasn’t able to replicate it in v. 3.0. Close?
This ticket asks to be able to set the Ref ID in RDE. I’m not sure how helpful this functionality would be for the average institution. If it’s easy to accomplish, maybe we should pass with minor priority?
The date span calculator is producing the relevant date span but when attempting to save the result, an ‘date is invalid and could not be created’ error is returned. YYYY, YYYY-MM, and YYYY-MM-DD are are rejected. This is error is affecting v. 2.8.01 and 3.0.0
This issue is reporting that the date calculator hangs when calculating dates for larger resources with lots of dates attached. I’ve tested this in 2.8.01 with some larger catalogues (3000, 4000, 18000 archival objects) but not encountered this problem. I’ve not been able to replicate this in the 3.0.0 test instance. Hudson Molonglo have developed a possible fix but it relies on dates being expressed in iso8601 and are MySQL-specific.
This ticket is seeking a bulk date function to be added to the date calculator. The ticket requests that the bulk date would be derived by determining the first and last date within one standard deviation of the average date and providing these as the bulk date range. The ticket doesn’t seem to be requesting that a bulk date be calculated by using the bulk dates fields in the Resource.