Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Date type "Range" should not appear for Deaccession Dates

Description

Removing the range date type was done elsewhere in the application where it wasn't needed (see https://archivesspace.atlassian.net/browse/AR-841), but it's still there in the deaccession date sub-record. If someone used range as a date type in this kind of record, the suggested migration path in https://archivesspace.atlassian.net/browse/AR-841#icft=AR-841 also seems to be appropriate for these dates.

Environment

None

Bug Report Description

None

Attachments

1

Activity

Show:

Edgar GarciaMarch 11, 2019 at 9:21 PM

I've also confirmed that 'Range' type is not there.

Christine Di BellaMarch 6, 2019 at 7:53 PM

Right now the date types for all event types are the same, so it would be a different feature request to change that - in theory there may be other event types that need further consideration when it comes to date types as well. Please feel free to file another JIRA for that if you'd like, but pending evidence to the contrary we're hopeful that the issue described in this one has been addressed. Thanks for testing this!

Joshua ShawMarch 5, 2019 at 7:28 PM
Edited

My mistake! I just checked the deaccession stubs for both accessions and resources and the 'range' type is not in those dates. So label as fixed for me.

I guess that begs the question of whether the range type should still be in deaccession events?

Christine Di BellaMarch 5, 2019 at 7:21 PM

- looks like your screenshot is for events, not deaccession date. This fix is specifically for the date in a deaccession sub-record that can be added to accessions/resources. Do you mind checking again?

Joshua ShawMarch 5, 2019 at 7:08 PM

Does not appear to be fixed in test.archivesspace.org. See attached screenshot.

Done

Details

Assignee

Reporter

Labels

Priority

Harvest Time Tracking

Open Harvest Time Tracking

Created April 5, 2018 at 8:59 PM
Updated May 30, 2019 at 12:40 PM
Resolved May 30, 2019 at 12:40 PM
Harvest Time Tracking