Hi Christine,

Thank you for your reply. Yes! I was able to successfully import both
spreadsheets in the sandbox! No error messages. Is there a patch that we
can apply to our instance to make this work for us?

This does, however, lead me to another question. We are hoping to use the
File version URI field to enter an internal file path (not an actual link),
and I thought that if I used column BL on the import spreadsheet (column K
on the DO spreadsheet) that the file path would populate the URI
field--alas, it doesn't. But I don't see another field on the spreadsheet
where one can place the non-linking file path to have it populate the URI
field. Is there one that I'm just not interpreting properly?

Many thanks,
Wendy

____________________________________

WENDY SCHEIR
*DIRECTOR*

66 5TH AVENUE, NEW YORK, NY 10011
sche...@newschool.edu

T 212.229.5942 x2888

Explore the Archives <http://library.newschool.edu/archives> | Digital
Collections from the Archives
<http://digitalarchives.library.newschool.edu/> | New School Histories
<http://newschoolhistories.org/> | @tnsarchives
<https://twitter.com/tnsarchives>



On Wed, Sep 30, 2020 at 2:43 PM Christine Di Bella <
christine.dibe...@lyrasis.org> wrote:

> Hi Wendy,
>
>
>
> Can you try importing your file into a dummy record on our test server:
> http://test.archivesspace.org/staff/? (username admin, password admin)
>
>
>
> We’ve been working on a number of changes to the importer based on
> feedback since 2.8.0. The pretty_inspect message usually means there’s a
> data error that should be caught by the logging process that shows up
> post-import. Some errors were not accounted for in the version in 2.8.0 so
> you get that message instead of the error, but should be there. The digital
> objects issue is not familiar to me, but I’m wondering if that may be
> different there too.
>
>
>
> You’ll start the import the same way you usually would on the test server,
> but it will move the process over to a background job so that it can run
> more quickly and the log is more easily downloadable afterwards. If you
> need any more guidance on that, please let me know.
>
>
>
> Christine
>
>
>
> Christine Di Bella
>
> ArchivesSpace Program Manager
>
> christine.dibe...@lyrasis.org
>
> 800.999.8558 x2905
>
> 678-235-2905
>
>
>
>
>
> [image: ASpaceOrgHomeMedium]
>
>
>
>
>
>
>
> *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org <
> archivesspace_users_group-boun...@lyralists.lyrasis.org> *On Behalf Of *Wendy
> Scheir
> *Sent:* Wednesday, September 30, 2020 2:14 PM
> *To:* Archivesspace Users Group <
> archivesspace_users_group@lyralists.lyrasis.org>
> *Subject:* Re: [Archivesspace_Users_Group] spreadsheet imports in 2.8v SUI
>
>
>
> Hi,
>
>
>
> In addition to the DO import spreadsheet error that I indicated in my
> recent email re: duplicate field codes, another error message I'm receiving
> in trying to import the DOs is: "{"error":"undefined method
> `pretty_inspect' for #"}"
>
>
>
> I'd be grateful for any insight you can provide on these issues.
>
>
>
> Many thanks,
>
> Wendy
>
>
>
> On Wed, Sep 30, 2020 at 1:28 PM Wendy Scheir <sche...@newschool.edu>
> wrote:
>
> Hi,
>
>
>
> In attempting to upload spreadsheets into ASpace using the Load via
> Spreadsheet functionality in the 2.8v SUI, I'm running into 2 issues and
> hoping that someone can shed some light. In each case, I'm using the import
> spreadsheets downloaded from Github:
>
>
>
> (1)  Using the general import spreadsheet to upload a collection that
> includes digital objects--fields BJ (digital_object_id), BK
> (digital_object_title), BL (digital_object_link) the archival objects
> imported, but not the digital objects.
>
>
>
> (2) Using the DO import spreadsheet (again, downloaded directly from
> Github), I'm getting the error message "This spreadsheet has duplicate
> Archive Space Field codes:  , , , , , , , , , , , , ," However, I don't see
> any obvious duplicate field codes in Row 4 of the spreadsheet.
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Reply via email to