CSV Import Error Message - Could not find "person" in type of entity terms array

[etea...@gmail.com]

Hi All,

A month in and I'm still trying to import a CSV file for authority records. I recently upgraded from 2.4 to 2.5 to improve indexing and have converted my Excel to CSV using LibreOffice to ensure the correct line-endings. Keep getting the following error message. Any idea what it means? Thanks! Eva

 PHP Warning: Module 'apc' already loaded in Unknown on line 0; Could not find "person" in type of entity terms array.

[Dan Gillean]

Hi there, 

There are 2 separate things going on here - a warning about the php-apc module, and the "person" entity type error. I'll answer the second part first. 

The short version is: try capitalizing it to Person, as it is in the example CSV. 

The explanation: some of our older import code is a bit too exacting - it does not normalize case when looking for existing terms and, even though the taxonomy terms are user-editable, the older code sometimes throws an error instead of simply creating a new term and reporting in the console (as you would expect) when no existing term matches. I suspect this is happening because of this. I'll try to test and file a bug report if so - AtoM should a) be able to match "person" with the existing term "Person" and b) even if "Person" didn't exist in your installation, it should be able to create a new term and continue without halting the import. 

In the meantime, see if capitalizing it helps you workaround this issue. 

Now, the apc warning: 

php-apcu is a PHP extension we use in AtoM that helps with caching. In this section of the 2.5 documentation, you can see where we install it as php-apcu: 

• https://www.accesstomemory.org/docs/2.5/admin-manual/installation/linux/ubuntu-bionic/#php  
  

If you look at the sample atom.conf configuration block in that section as well, you can see where we set some APC parameters. The instructions are the same in the 2.5  Ubuntu 16.04 documentation. 

You mentioned that you've just upgraded from 2.4. One important thing to consider: there are changes in packages between versions, based on what was supported in Ubuntu at the time. Looking back through our documentation it seems like we had the following: 

• 2.4 on Ubuntu 14.04 - php-apc
• 2.4 on Ubuntu 16.04 - php-apcu & php-apcu-bc
• 2.5 on Ubuntu 16.04 and 18.04 - php-apc

I don't know enough about PHP and Ubuntu packages and apcu in general to explain all of this, but php-apcu-bc is a "backwards compatibility" version that was a community release to support some functionality with older PHP versions. 

I found an older development ticket here, with a comment that notes: 

When using php 7.2 (Ubuntu 18.04 or Centos 7), the apcu_bc extension is not only not needed, but also breaks atom. We should update the install instructions in order to add the following packages:
- Ubuntu 18.04: php-apcu
- Centos 7: rh-php72-php-pecl-apcu

Also, in the atom25-1604 vm, apcu_bc doesn't seem installed, so I think we should remove the paragraph from the install instructions.

So: if you've just upgraded, but installed the new 2.5 version on the same server as your 2.4 instance, then it's possible that the problem is that php-apcu-bc is still installed. I'd suggest asking your IT team to take a look at that first. 

Make sure you also check what version of PHP you have installed - if you're using Ubuntu 18.04, our documentation recommends PHP 7.2. If you're using Ubuntu 16.04, we recommend PHP 7.0 - though I believe that PHP7.2 should work on a 16.04 installation as well. In the 2.4 release we were still supporting Ubuntu 14.04, which required the use of PHP 5.x - so again, make sure if you've upgraded on the same server, that you are using the correct PHP version. 

Let me know if this helps!

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

he / him

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/d3246ac5-a121-49c3-ba6f-2d12e086300f%40googlegroups.com.

[etea...@gmail.com]

Thanks, Dan,

You were correct about the capitalization of Person. I made the change in the file and the error was eliminated. Interestingly, The job shows as successful, but no new authority records appear. Instead, I get blank archival description records with only two description control fields populated - Rules or conventions or services used. This has happened with every import that has come back "successful" (there have been 3 so far). I will contact the support team about the apc warning, but wanted to update you in the meantime in case the blanks are significant.

Thanks! Eva

To unsubscribe from this group and stop receiving emails from it, send an email to ica-ato...@googlegroups.com.

[Dan Gillean]

Hi Eva, 

That's strange. I suspect it could have to do with installation configuration things, so do follow-up on that. 

In the meantime, if you'd like (and the data isn't sensitive), I would be willing to take a look at your CSV to see if I can spot any obvious problems, and run a test import in my test instance to see if there are any lingering encoding issues from it being converted from Excel. 

If so, feel free to send me a copy off-list (dan [at] artefactual [dot] com), and I'll try to take a look soon. 

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

he / him

To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/52b61dd8-816f-4020-ab23-1073cdb77639%40googlegroups.com.