[Archivesspace_Users_Group] buggy "Range" in RDE

Lora Davis ljdavis at jhu.edu
Fri Feb 19 09:47:59 EST 2016

Hi Lydia,

This seems related to a ticket I submitted a few months ago while at Colgate; see https://archivesspace.atlassian.net/browse/AR-1333.  What version are you running?  The problem has been fixed, but only as of 1.4.3-dev17 according to JIRA.

And, yes, "Range" is intended only to be used in certain specific scenarios (e.g. in agent records), but not when describing materials.  This was corrected a few releases ago, and "Range" removed from non-RDE fields, but it clung on in RDE causing the issue you encountered.



-----Original Message-----
From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia
Sent: Friday, February 19, 2016 9:37 AM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] buggy "Range" in RDE

Good morning!
In the Rapid Data Entry drop down lists for Date Type, we have “Range” as well as "Inclusive."  Besides sometimes being a little confused about when it would be best to use one over the other, I realized that Range is not included in the conventional entry date drop-down at all, and when I revisit RDE objects with Range, the Date Expression was automatically changed to “other” from our default “creation.”  It sounds like Range would like to be phased out completely (if going off of the conventional entry), which would streamline and clean up data.  If so, could the RDE Range drop-down option just be killed, to avoid confusion?  Thanks for your help!

Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org

More information about the Archivesspace_Users_Group mailing list