EAD Import

[simon sheppard]

Hello All,

I am quite new to using AtoM and have hit a problem when trying to
upload EAD which was generated via the Archives Hub. Each time I try I
just get the message "Error encountered".

Looking back over previous posts on here I noted that the dates
require to be with a "slash" rather than a "hyphen", but this does not
seem to be a problem in my case - I don't think!

I have tried uploading a catalogue with just collection level
descriptions and also one with lower levels; no luck with either.

If anyone is aware of any other issues that may be preventing my
success, or would be willing to have a look at the EAD, I would be
grateful for any pointers folks could give.

As I said, I am quite new here and am probably just missing something
quite simple.

Cheers

Simon

[JBushey, ICA-AtoM Product Manager]

Dear Simon,

Please post a sample of your EAD so we can take a look at it.
If you would rather send it privately (off list) please send it to jes...@artefactual.com

Regards,
Jessica Bushey
ICA-AtoM Product Manager

[sis...@gmail.com]

Hello Jessica,


Thanks for the reply, I have sent you a batch of EAD to your private email.

Simon

[JBushey, ICA-AtoM Product Manager]

Dear Simon,

Received. One of our developers will review and respond to you.

Best,

Jessica Bushey
ICA-AtoM Product Manager

[David Juhasz]

Hi Simon,

I tried importing your sample EAD file and though I got an error
message, the import did work. After clicking on the "View archival
description" button, I see the imported Fonds with lower-level descriptions.

However, if you want to get rid of the error message, you should include
a link to the EAD DTD definition before the opening <ead> tag, as so:

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE ead PUBLIC "+//ISBN 1-931666-00-8//DTD ead.dtd (Encoded
Archival Description (EAD) Version 2002)//EN"
"http://lcweb2.loc.gov/xmlcommon/dtds/ead2002/ead.dtd">
<ead>



Regards,
David Juhasz

--
David Juhasz
Director, Technical Services

Artefactual Systems Inc.
www.artefactual.com

[sis...@gmail.com]

Hello David,

Thank you for your reply.

Alas, I still can't seem to see anything.

You say to click on the "view archival description" and on reading the manual it says to click 'view' on the 'button block'. I cannot see the 'button block' following an attempted import. Even when able to see the 'button block' I cannot see a 'view' button.

I have also tried to import EAD to the demo version, but again was foiled.

I am sure I am probably missing something quite simple, but I just can't see what it is at the moment.

Appreciate the help.

Regards

Simon

[Jessica Bushey]

Dear Simon,

I apologize for the lack of clarity in the wording of the User Manual. I have added a new screenshot to the page on Import, so that you can see the correct button label after importing an EAD XML file: https://www.ica-atom.org/doc/Import_descriptions_and_terms.

Unfortunately the ICA-AtoM Demo will not permit users to import EAD or any other XML file due to security reasons. Additionally, the demo will not permit users to link or import digital object files (e.g., images, sound, video etc.) due to security reasons.

Regards,

Jessica

---

Jessica Bushey, MAS
ICA-AtoM Product Manager

Systems Analyst
jes...@artefactual.com

Artefactual Systems Inc.
www.artefactual.com

--
You received this message because you are subscribed to the Google Groups "ICA-AtoM Users" group.
To post to this group, send email to ica-ato...@googlegroups.com.
To unsubscribe from this group, send email to ica-atom-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg/ica-atom-users/-/jLWxm70-xGsJ.
For more options, visit https://groups.google.com/groups/opt_out.

[David Juhasz]

Hi Simon,

When you can't see the button block at the bottom of the page, it often
means that there was a fatal error somewhere that stopped page rendering
part of the way through. To test this, please put ICA-AtoM in debug
mode <https://www.qubit-toolkit.org/wiki/Debug_mode>, and then check our
FAQ <https://www.qubit-toolkit.org/wiki/FAQ> for possible solutions. If
you find an error that is *not* listed on the FAQ, then please post back
to this thread and we'll try and help you with it.



Regards,
David

[sis...@gmail.com]

Hello David,

Thank you for your suggestion - I shall forward this to the people who host the system.

I was wondering, would that fact that someone else is hosting AtoM cause any problems?

Jessica,

Thank you for making that alteration to the manual, it is nice and clear now - even to me!

Have a good weekend.

Simon

[Jesús García Crespo]

Hi Simon,

On Fri, Jun 22, 2012 at 1:48 AM, <sis...@gmail.com> wrote:

I was wondering, would that fact that someone else is hosting AtoM cause any problems?

Yes, some web servers are very limited for security reasons. Specially, shared web hosting services tend to be very restrictive and that could be a problem for ICA-AtoM.

The debug mode should clarify the problem though. Let us know how it goes.

Best regards.

 

--
Jesús García Crespo,
Software Engineer, Artefactual Systems Inc.
http://www.artefactual.com | +1.604.527.2056

[sis...@gmail.com]

Hello,

As instructed, AtoM was placed into debug mode by the folks who host it, and we tried once more to import some EAD. Again we had no luck, with the same error message showing on screen. The logs on the debug console were duly checked, but this revealed nothing to the folk who host AtoM..

I have attached the log of anyone would like to have a look at it, see if they can spot what is going on? I have also attached a screen shot of the error message I get when trying to import.

Thanks

Simon

[David at Artefactual]

Hi Simon,

Hmm, I can't see anything unusual in the debug log either.

Can you please ask your hosting provider to send a phpinfo <http://php.net/manual/en/function.phpinfo.php> report to sup...@artefactual.com?  It will let us know if there's anything in your hosting provider's php configuration that might interfere with file upload.   On that note, have you tried uploading any digital objects to the system?  If upload is working for digital objects, then that should rule out upload as an issue for EAD import.



Regards,
David

[sis...@gmail.com]

 Hello David,

I have requested our hosting provider to forward you the report you noted - I am sure they will be onto that soon.

I followed your prompt and tried uploading some images, and this worked fine. I did this more than once, just to make sure, and encountered no issues.

Regards

Simon

[David Juhasz]

Hi Simon,

I just tested your import file again, just to double-check that I had
used the right version of ICA-AtoM (I'm often using the latest
development code) and I got the same error message you did! After this
I realized that I changed the file extension from ".txt" to ".xml" the
first time I did the test, and making the change again fixed the import
problem. I feel a bit foolish that I missed something so simple, but I
honestly didn't think that the file extension would effect the import at
all.

In any case, changing the extension to ".xml" fixed the problem, so at
least it's an easy fix!



Cheers,

[sis...@gmail.com]

Hello David,

It works!

Thank you very much for you help, it may have been something quite simple in the end but I am sure that I wouldn't have worked it out myself!

Whilst it works, without showing there are any errors, when looking at the records you find there are no dates in any of the descriptions, additionally all the refcodes from upper levels appear in all the lower levels. Are there any known reasons for this?

In terms of the dates, I have checked the EAD from a catalogue created in AtoM against one which I want to import from the Hub, and the unitdate seems to be the same in both. As follows is an example; <unitdate datechar="creation" normal="2001/2001" encodinganalog="3.1.3">2001</unitdate>

Thanks again for sorting the import problem, it is appreciated.

Simon

[sis...@gmail.com]

Hi David,

I would also add, that in terms of my problem with the dates, that I did search the forum for any solutions and cam up with this thread;

 https://groups.google.com/forum/?hl=en&fromgroups#!searchin/ica-atom-users/unitdate/ica-atom-users/IXt5n0HOgrg/wPbIwIMruHwJ

My dates are nested within the <did> and do not have a line break, so whilst raising some possible causes it does not solve my problem.

I could not find any other treads which touched on this issue.

Simon

[Tim Hutchinson]

Hi,

I followed up with Simon off-list and did some testing with his file.

The file itself seems fine in terms of dates. But during the testing I ran into some really odd behaviour on my server, which so far I haven't been able to either fix or replicate.

When I first started testing with Simon's file, the Library of Congress server which hosts the EAD DTD file was down. This is the only unique factor I can think of. After changing the link to a local copy of the DTD and making a couple other tweaks to the tagging, I was able to import without errors but the date still wasn't appearing. Then, I thought I had it figured out - <origination> didn't have a <name> or <corpname> element. I'm pretty sure I saw at least one correct import, but after testing further, the date continued to not appear.

Now here's the strange part - I tested with some of my own files which I knew were OK. The date also did not appear in those cases. And then I switched to a different server (and also to a different instance on the original server). Simon's file was fine, and so were mine - dates appear correctly.

I'm at a loss to figure out how this happened (as I mentioned, the only unreplicable part is that originally the server with the DTD was down; I'm not sure if that's a factor), or how to correct it. The files that I know about relating to the import seem fine (apps/qubit/modules/object/config/import/ead.yml and� lib/model/QubitInformationObject.php). I cleared the cache, and also ran mysqlcheck. I have confirmed that the exact same file now imports differently on different instances.

Any ideas of what to look for? I know that this is a bit nebulous since I can't tell you how to replicate the problem...

(And Artefactual folks, I swear I didn't know I'd be posting a request today when I said nice things about you this morning :) )

In terms of the repeating reference code - this appears to be a configuration issue; the inheritance can be disabled via settings | global.

Thanks
Tim

On 05/07/2012 8:59 AM, sis...@gmail.com wrote:

Hi David,

I would also add, that in terms of my problem with the dates, that I did search the forum for any solutions and cam up with this thread;

�https://groups.google.com/forum/?hl=en&fromgroups#!searchin/ica-atom-users/unitdate/ica-atom-users/IXt5n0HOgrg/wPbIwIMruHwJ

My dates are nested within the <did> and do not have a line break, so whilst raising some possible causes it does not solve my problem.

I could not find any other treads which touched on this issue.

Simon



On Thursday, July 5, 2012 9:46:07 AM UTC+1, sis...@gmail.com wrote:

Hello David,

It works!

Thank you very much for you help, it may have been something quite simple in the end but I am sure that I wouldn't have worked it out myself!

Whilst it works, without showing there are any errors, when looking at the records you find there are no dates in any of the descriptions, additionally all the refcodes from upper levels appear in all the lower levels. Are there any known reasons for this?

In terms of the dates, I have checked the EAD from a catalogue created in AtoM against one which I want to import from the Hub, and the unitdate seems to be the same in both. As follows is an example; <unitdate datechar="creation" normal="2001/2001" encodinganalog="3.1.3">2001</unitdate>

Thanks again for sorting the import problem, it is appreciated.

Simon

On Tuesday, July 3, 2012 8:51:11 PM UTC+1, David at Artefactual wrote:

Hi Simon,

I just tested your import file again, just to double-check that I had
used the right version of ICA-AtoM (I'm often using the latest

development code) and I got the same error message you did! � After this

I realized that I changed the file extension from ".txt" to ".xml" the
first time I did the test, and making the change again fixed the import

problem. �I feel a bit foolish that I missed something so simple, but I

honestly didn't think that the file extension would effect the import at
all.

In any case, changing the extension to ".xml" fixed the problem, so at
least it's an easy fix!



Cheers,
David

--
David Juhasz
Director, Technical Services

Artefactual Systems Inc.
www.artefactual.com

--
You received this message because you are subscribed to the Google Groups "ICA-AtoM Users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/ica-atom-users/-/05fQb5h-I0EJ.

To post to this group, send email to ica-ato...@googlegroups.com.
To unsubscribe from this group, send email to ica-atom-user...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/ica-atom-users?hl=en-CA.

-- 
Tim Hutchinson
University of Saskatchewan Archives
301 Main Library, 3 Campus Dr.
Saskatoon, SK S7N 0G2
(306) 966-6028
e-mail: tim.hut...@usask.ca

-- 
Tim Hutchinson
University of Saskatchewan Archives
301 Main Library, 3 Campus Dr.
Saskatoon, SK S7N 0G2
(306) 966-6028
e-mail: tim.hut...@usask.ca

[Tim Hutchinson]

Hi again,

I've done some further testing and I've isolated the problem a bit better, but don't know how to fix it. Hoping that someone might have some ideas...

The problem with dates not importing can be traced to the backend database. We have two instances of ICA-AtoM on our test server; one is working correctly and the second is not (following earlier testing with Simon's file). When I edit the config/config.php file to switch the database connected to each instance, the behaviour is reversed.

I also tried re-indexing but that didn't change anything. Earlier I had run mysqlcheck and everything seemed OK.

Editing imported records to add a date works fine; and so does creating a new record through the interface (with a date).

Any ideas? In our case it would possible to start with a fresh database but it would be useful to know what's happening, since the error seems to have been triggered through the import process.

Thanks
Tim

[JBushey, ICA-AtoM Product Manager]

I have created Issue 2384 http://code.google.com/p/qubit-toolkit/issues/detail?id=2384. Please feel free to edit the issue to better capture the problems being encountered with importing EAD and dates.

Thank-you,
Jessica Bushey

To post to this group, send email to ica-atom-users@googlegroups.com.
To unsubscribe from this group, send email to ica-atom-users+unsubscribe@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/ica-atom-users?hl=en-CA.

-- 
Tim Hutchinson
University of Saskatchewan Archives
301 Main Library, 3 Campus Dr.
Saskatoon, SK S7N 0G2
(306) 966-6028
e-mail: tim.hut...@usask.ca

-- 
Tim Hutchinson
University of Saskatchewan Archives
301 Main Library, 3 Campus Dr.
Saskatoon, SK S7N 0G2
(306) 966-6028
e-mail: tim.hut...@usask.ca