Again, this is more of a warning than an error, because once again AtoM has a default behavior when unexpected values are found (or no values are included) in the publicationStatus CSV column.
This field also expects controlled vocabulary terms, but in this case it is not tied to a user editable taxonomy. As both an internal edit site for archivists and a public facing access catalog, AtoM uses the publication status to determine what descriptions are visible to public users, versus those that are only shown to authenticated (i.e. logged in) users. In a CSV import, this column expects one of two controlled terms:
- Published: The description will be visible to public users and logged in staff
- Draft: The description will only be visible to logged in staff
For general information on using the Publication status in AtoM, see:
This has made me realize it's not actually mentioned clearly on our CSV import documentation, so I will try to add a clarification about this here in the future:
Fortunately, AtoM has a fallback behavior in the import code when no publication status value is included for a particular import row, or else the value is not one of the two expected ones (Draft or Published). In that case, AtoM will use the default publication status that an Administrator can configure in the settings, found in Admin > Settings > Global - see:
In new installations, this setting is configured to "Draft" as the default publication status, to avoid accidentally exposing records that may not be intended for public viewing.
Invalid language: English
Here is likely the source of the error that halted the import. All language and culture fields in our CSV templates expect ISO 639-1 two-letter language codes as inputs. For example, en for English; fr for French; es for Spanish, etc. You can see a full list of supported languages and their related codes here:
This is mentioned in the CSV import documentation here:
Since AtoM can't know what language your metadata is in, and AtoM itself is designed to support multilingual content, there is no default fallback behavior here when encountering unexpected results. I suspect that if you change the value in your CSV row from English to en the CSV would import.
I hope this helps!