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

[Joanna Black]

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>
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 <
> 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
> *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 :)
>
>
>
>
>
> --
>
> *[image: 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
>
>
>
> *Represented by UAW Local 2103: *
>
> *Sierra Employee Alliance*
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>


-- 

[image: 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


*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/feedbe83/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 153647 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20230418/feedbe83/attachment.png>