[Archivesspace_Users_Group] Time markings in date fields from bulk import spreadsheet

[Bowers, Kate A.]

Anytime you edit a cell in excel and it looks like a date, excel will convert it to a date. It’s horrific if you don’t notice until it’s too late. There are lots of tricks to get around this, but excel is tricky. Pre-1900 dates are another level of awful.

That said, I use Excel a lot, but not without caution.

Kate

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of John F. Anderies
Sent: Tuesday, July 25, 2023 12:57 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Time markings in date fields from bulk import spreadsheet

Hi VivianLea,

Ah, thanks, that is good to know. I thought I had set the date fields to TEXT suspecting that the format could get wonky, but looking back at my spreadsheet I see that they somehow converted themselves back to DATE format again!

Best,
John

-----
John Anderies (he/him), Director
John J. Wilcox, Jr. Archives and Library
William Way LGBT Community Center


On Tue, Jul 25, 2023 at 12:09 PM Solek, VivianLea <VivianLea.Solek at kofc.org<mailto:VivianLea.Solek at kofc.org>> wrote:
Hi John,

I found that if you turn the fields into a text field, you do not get the time stamp after it. I do not know if that causes any other issues (we’ll see if any of the ASpace staff weigh in), but I hated the look of the timestamp too.

One thing to watch for….if there are true dates already in the field, converting them to text will often mess up the date. I copy the column, turn the new column into a text field and then go down and correct those dates that have changed. It’s a bit more work, but is so worth it for me.

Hope that fix helps you out.

All the best,
VivianLea

VivianLea Solek
Archivist
Knights of Columbus Supreme Council Archives

1 State Street
New Haven, CT 06511-6702
Phone 203 752-4578
Fax 203 865-0351
[cid:image001.png at 01D9BEF8.2FC5F690]

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 John F. Anderies
Sent: Tuesday, July 25, 2023 11:39 AM
To: Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Time markings in date fields from bulk import spreadsheet

Caution: This email originated outside of the Knights of Columbus. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Apologies if this has been asked and answered before.

I'm using the bulk import template to import a container inventory into a resource record in ASpace. This is the first time that I have used dates in the spreadsheet that include year, month and date (in the form of YYYY-MM-DD), as opposed to just year.

Once the import is completed, I find that the date fields are rendered with T00:00:00+00:00 following the correctly imported YYYY-MM-DD characters. Is it possible I am doing something wrong in how I'm rendering the dates in the spreadsheet or is there a way to prevent what I presume is time related data from being included? I can edit these out directly in ASpace, but it's a time consuming process that defeats the purpose of using the spreadsheet to import data.

With thanks,
John

-----
John Anderies (he/him), Director
John J. Wilcox, Jr. Archives and Library
William Way LGBT Community Center
CONFIDENTIALITY NOTICE: This message and any attachments may contain confidential, proprietary or legally privileged information and is intended only for the use of the addressee or addressees named above for its intended purpose. If you are not the intended recipient of this message, this message constitutes notice that any review, retransmission, distribution, copying or other use or taking any action in reliance on the information in this message and its attachments, is prohibited. If you receive this communication in error, please immediately advise the sender by reply e-mail and delete this message and its attachments from your system without keeping a copy. Unless expressly stated in this e-mail, nothing in this message may be construed as a digital or electronic signature. Thank you.
_______________________________________________
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<https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwMFaQ&c=WO-RGvefibhHBZq3fL85hQ&r=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY&m=xe8Msz1VsSaJklACDwQJ92nqyAkDMGankJxYv5oU_Rqk4q_HDpxyonl72izvb2sS&s=vbKp8h33eNtcNc9MOGudYEPiA8u7HhKQkZU-v85L418&e=>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20230725/9325170d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 31887 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20230725/9325170d/attachment.png>