[Archivesspace_Users_Group] "Server Error" when trying to edit Digital Objects with inclusive dates

Tue Apr 18 14:47:09 EDT 2023

Joanna,

What version of AS are you on and which exact template and job were you using when you created the DOs?

I remembered that what I was chasing was actually a bug with the accession CSV importer. I have submitted a ticket here, but this isn’t your exact scenario: https://archivesspace.atlassian.net/browse/ANW-1733

There was an old ticket for this same behavior that was issued as a fix for AS 3.2.0 and after: https://archivesspace.atlassian.net/browse/ANW-1421 but if you’re in a version after 3.2.0 and still experiencing this, it’s worth it to confirm which exact importer you were using.

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Valerie Addonizio
Sent: Tuesday, April 18, 2023 1:56 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] "Server Error" when trying to edit Digital Objects with inclusive dates

Joanna,

Generalized advice for preventing this error: The value you put in the dates column in any spreadsheet importer template should match exactly the value you see in the Value column when you navigate to System > Manage Controlled Value Lists > Date Type (date_type), and this is true for any type of date. The tiniest of differences can cause this error, like the difference between “inclusive” and “Inclusive.” If you zoom way out, a generalized best practice is to use the values you see in the Value columns whenever you are populating a controlled value list using the importer. That is why, for example, the level column is controlled when using the Excel version; you cannot put “File,” you must use “file.”

I have been meaning to submit a bug report about the date fields in particular, I even have sample data to do so. I will post that ticket number here as soon as I swing back around to it.

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> On Behalf Of Joanna Black
Sent: Tuesday, April 18, 2023 1:36 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] "Server Error" when trying to edit Digital Objects with inclusive dates

Thanks, Valerie! That seems to be the issue. Any idea how/why the importer would create this extra date type? Is this something to check for each time DOs with inclusive dates are imported via CSV files?

On Tue, Apr 18, 2023 at 10:20 AM Valerie Addonizio <vaddonizio at atlas-sys.com<mailto:vaddonizio at atlas-sys.com>> wrote:
Hi Joanna,

I speculate you may have accidentally created an invalid date type for those DOs with inclusive dates when you created them via the importer. To test this theory, navigate to System > Manage Controlled Value Lists > Date Type (date_type) and see if you have an extra date type there. This is a common issue that I see when using the spreadsheet importers.

Unfortunately, if you do have an invalid date type on those records, I do not believe there is any way to solve this from within the interface; I’ve found solutions through the API and the database directly. You do mention that you can delete the DOs; that’s another solution.

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> On Behalf Of Joanna Black
Sent: Tuesday, April 18, 2023 1:11 PM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] "Server Error" when trying to edit Digital Objects with inclusive dates

Hi all,

I am experiencing an issue editing digital object records in ASpace that have inclusive dates. They import fine in a CSV file, but when I go in to edit them in ASpace, I get a "Server Error" message and am unable to edit metadata (although the digital objects can be deleted from ASpace). See reference image below for a visual example. I was able to determine that this problem only happens with digital objects that have inclusive dates, but I can't find any reference to this issue by any other users. I am not experiencing this problem with single date digital objects.

Has anyone else encountered this? Any solution ideas? I am a lone arranger, so any input is welcome :)

[cid:image001.png at 01D97202.84A6B840]

--

[photo]

Joanna Black

Senior Archivist

William E. Colby Memorial Library

Sierra Club

Pronouns: she/her or they/them

(415) 977-5783 | Pacific Time Zone

joanna.black at sierraclub.org<mailto:joanna.black at sierraclub.org>

Represented by UAW Local 2103:

Sierra Employee Alliance

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

--

[photo]

Joanna Black

Senior Archivist

William E. Colby Memorial Library

Sierra Club

Pronouns: she/her or they/them

(415) 977-5783 | Pacific Time Zone

joanna.black at sierraclub.org<mailto:joanna.black at sierraclub.org>

Represented by UAW Local 2103:

Sierra Employee Alliance

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20230418/046f97e0/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 153647 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20230418/046f97e0/attachment.png>