How to import translation of a fonds without creating two entities

[Carolyn Sullivan]

Hello,

When we import translations of fonds, the translations import, but when we check under the institution, we see two separate fonds--one for each language (see InstitutionViewDuplicateFonds.png).  I've tested creating a fonds in the commandline and translating it, and that doesn't create two fonds (see WhatWeWant.png).  Is there any way to import a fonds so that it doesn't create two fonds?  I've attached a sample of the csv we're using.

Thank you for all your help and support!

Best,

Carolyn.

[Dan Gillean]

Hi Carolyn, 

Have you reviewed this section of the documentation?

• https://www.accesstomemory.org/docs/latest/user-manual/import-export/csv-import/#importing-translations

If yes, what about the Local Council or Provincial Council fonds CSVs is different from your test CSV, which you say works?

Glancing at the test CSV, it seems like you've gotten the general idea right. A couple high-level notes on importing translations: 

• First, not all fields work - only the free-text fields found in the main table for descriptions, the information_object_i18n table. The supported fields are listed in the doc link above. 
• Any untranslatable value such as an identifier (which is supposed to be a unique value, and therefore the same regardless of culture), a controlled term (such as an access point or a RAD GMD), a controlled date value (the start and end dates are the same regardless of culture - though I think you could add different display dates), or any part of a linked entry (such as the repository name, or your creator's name and history) should be left blank in the translation row. They will not translate via import this way, and in fact doing so may create duplicate entries on import. 
• For the related entities (subject/place/genre access points, other controlled vocab terms, linked archival institution or authority records, etc), you will need to translate them from their view pages. For example, import your description so a new authority record is created. Then go to the authority record, flip the user interface to French, and translate the authority record via the user interface. Same for your access points, repository record, etc. At this time, other entities do not support translation rows via import, so this will be a more manual process. 

If it seems like you're doing all that, and you are preparing the CSV in the same general way you've prepared your test CSV, then one last thing to try would be  running some of the common maintenance commands (such as rebuilding the nested set, clearing the application cache, restarting PHP-FPM, and repopulating the search index). It's possible there's just a hiccup there that is affecting the display. Instructions and further links for all these tasks can be found on the Troubleshooting page: 

• https://www.accesstomemory.org/docs/latest/admin-manual/maintenance/troubleshooting/
  

Cheers, 

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/220f0b7e-970e-4ba1-9370-09b1d02a87bcn%40googlegroups.com.

[Carolyn Sullivan]

Thank you so much for your support Dan!  I really appreciate it!  It WAS an issue with a column of values being filled in that the documentation stated should be left blank... radGeneralMaterialDesignation.  I removed those values and then the whole thing loaded without creating a separate fonds for each language under the Archival Institution.  

... by any chance, would you happen to know if there is a way to update the radGeneralMaterialDesignation through the backend, rather than making someone fill in all those fields?

Thanks again!

Carolyn.

[Dan Gillean]

Hi Carolyn, 

Glad you've made some progress!

If you have added the GMD terms to your descriptions in the English user interface, then all you should need to do is go to the taxonomy and translate the term once at the source. Any description with translations where the term has been linked in English should now show it in French as well when viewing the French interface - so it shouldn't be a matter of needing to add it again to dozens or hundreds of French descriptions and bulk adding or importing them somehow.

The same should be true for linked creator and repository names - thanks to culture fallback, they will display the English labels in the French interface if no translation has been provided, but once you add a French translation on the parent record (e.g. the authority or repository record itself), this will now display when using the French interface to view any linked descriptions. 

Cheers, 

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

@accesstomemory

he / him

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/35b9eb3b-7915-4c93-8a6f-7c9e90dd9d43n%40googlegroups.com.