Imported EAD entry added always with English as Source Language

[dgm...@gmail.com]

Dear all,

I am coming across a strange behaviour. When I import an EAD3 entry in XML into Atom 2.5.2, it is always added with English as source language. 

- The entry is in Spanish and includes a reference to the language used inside the XML file (you can download the XML file from here http://pares.mcu.es/ParesBusquedas20/catalogo/description/exportEAD/5286050).

- My selected language is Spanish.

- I made Spanish the default language.

The entry looks otherwise OK but its source language should be Spanish, shouldn't it?

Thanks!

Daniel

[dgm...@gmail.com]

OK, I am answering my own question because I have realised that Atom does not yet support EAD 3.

I suppose that the location of the language information is located in different places in EAD 2002 and EAD 3.  This has already been discussed here: https://groups.google.com/forum/#!searchin/ica-atom-users/%22ead3%22%7Csort:date/ica-atom-users/ehUh0OsYRd4/lm00riuNAgAJ

I will see if I can change that in my import file.

It seems that, if AtoM cannot find the language information in the XML file, it defaults to import the entry into EN. I changed the default language here:

/apps/qubit/config/settings.yml

but this does not seem to affect the imporot.

Is there any way changing the default "Source language" for imports?

Daniel

[Dan Gillean]

Hi Daniel, 

You're correct that AtoM does not currently support EAD3. I was curious about your comments so I tried importing the example file - it does import, though you are correct that not everything comes in correctly. Also, while the EAD file is UTF-8 encoded, it appears that its source was not, since I see a number of ? characters in the document where accented characters should be. 

In my local test environment, I did not actually any language data imported. Can you perhaps show me a screenshot of what you're seeing? Additionally, what language is the user interface in when you import the record - Spanish, or something else?

There are 2 primary places where AtoM will look for language data that it imports as part of the description. The Language of material data comes from the 2-letter ISO 639-1 code included in the <language> element nested in <langmaterial>: 

<did>
   <langmaterial encodinganalog="3.4.3">
      <language langcode="[ISO code]">

See: https://www.accesstomemory.org/docs/latest/user-manual/data-templates/isad-template/#language-of-material

Similarly, information about the language of the description, which appears in AtoM's Description control area, this is taken from the ISO 639-1 code included in the <language> element that is nested in <langusage>: 

<eadheader>
   <profiledesc>
      <langusage>
         <language langcode="[ISO code]">

See: https://www.accesstomemory.org/docs/latest/user-manual/data-templates/isad-template/#language-of-description

EAD3 has introduced the intermediary <languageset> element, which AtoM doesn't recognize. This is likely why the language of material values in your EAD3 file are not importing. 

The last parameter, which I think may be what you are talking about, is the culture. This is what AtoM uses in, for example, the language facet in the search/browse results. For EAD imports, I believe his is determined by the language of the user interface at the time of import. For command-line imports, I believe it will default to using the default installation culture - this is what you were changing in the /apps/qubit/config/settings.yml configuration file. 

Hope this helps! 

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

@accesstomemory

--
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/e3fc0806-3e24-4ac8-b9b6-acd007794d3a%40googlegroups.com.

[dgm...@gmail.com]

Dear Dan,

Thanks a lot for your comments and your additional research.

It was great that you confirmed that the language of the entry after the import should be Spanish as this was my default language.

I have tried again and now it worked fine. The EADS3 entry was imported as without errors and is stored as Spanish. I don't really know why it did not work the first time.

Even if EADS3 is not officially supported it seems that the differences are not so big as to prevent the import and the data looks fine. 

I realise that importing EADS3 might not work in all cases but for the entries I have, it works a treat.

I wanted to mention also that I did not have any issues with the accents or the special characters in Spanish. From my side the file seems to be correct UTF-8. I imported it straight from my downloads folder without editing it in my computer.

I am really pleased with Atom 2. I am only wondering why I did not migrate earlier from ICA-Atom 1. :D

Daniel

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

[Dan Gillean]

Glad it's doing what you need, Daniel! Thanks for updating us - and upgrading AtoM!

Cheers, 

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

@accesstomemory

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/0f014ee3-bb68-4bc0-ba95-a86aea9d089a%40googlegroups.com.