[Archivesspace_Users_Group] Agent Dates of Existence Lost to Update 2.8.1 to 3.1.1
Corey Schmidt
Corey.Schmidt at uga.edu
Tue Feb 22 09:08:26 EST 2022
All,
Just as a follow-up, we were unable to figure out the exact cause of the missing dates of existence, but we believe it was an indexing error. Since the timing for the update prohibited us from running a re-index, we weren't able to confirm this. However, since many of the issues we've had in the past were solved with a re-index and no one else reported losing their data on this kind of jump, we feel reasonably confident in our assumption.
I apologize for causing a stir. It's a good reminder that running a re-index should be a part of our error checking process and we will update our upgrade and testing procedures to account for this in future upgrades.
Sincerely,
Corey
From: Corey Schmidt
Sent: Wednesday, February 16, 2022 12:09 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Agent Dates of Existence Lost to Update 2.8.1 to 3.1.1
Dear all,
Hello, this is Corey from the University of Georgia. We are testing an update to ArchivesSpace, going from version 2.8.1 to 3.1.1. During testing, we discovered that over 660 agent records lost their dates of existence information. Not all agents lost their dates of existence, however, with the vast majority migrating properly into 3.1.1. We are unsure why these agents in particular lost this info, but we know that the 3.0.0 release came out with two patches because of issues related to the dates of existence field (listserv email<http://lyralists.lyrasis.org/mailman/htdig/archivesspace_users_group/2021-June/008561.html>, JIRA ticket<https://archivesspace.atlassian.net/jira/software/c/projects/ANW/issues/ANW-1334>). Agents with range and single types are both affected.
Has anyone encountered this issue before? What might be the cause? For reference, I'm adding the JSON of an agent that lost their date of expression during the migration, as well as screenshots of what our agent records look like on 2.8.1 and 3.1.1:
"dates_of_existence": [
{
"lock_version": 0,
"begin": "1905",
"end": "1983",
"created_by": "cschmidt",
"last_modified_by": "cschmidt",
"create_time": "2021-02-23T14:45:47Z",
"system_mtime": "2021-02-23T14:45:47Z",
"user_mtime": "2021-02-23T14:45:47Z",
"date_type": "range",
"label": "existence",
"jsonmodel_type": "date"
}
],
Any help or info would be appreciated. Thanks.
Sincerely,
Corey
Corey Schmidt
Special Collections Libraries | ArchivesSpace Project Manager
Athens, GA 30605
Corey.Schmidt at uga.edu<mailto:Corey.Schmidt at uga.edu>
[University of Georgia]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20220222/9053c5c7/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 8920 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20220222/9053c5c7/attachment.png>
More information about the Archivesspace_Users_Group
mailing list